Good to know: Event Cloud source
The Statsig Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
Statsig helps companies safely A/B test features in production before rolling them out, avoiding product debates and costly mistakes when shipping out new features. Statsig serves all your experimentation needs with a unified platform that connects what you build with the impact you deliver. Statsig powers A/B tests and experiments on any device, in any part of the application stack, at any scale. Statsig gives you a comprehensive 360° view of how your product is performing.
The Statsig integration enables custom events and exposure events to be forwarded from Statsig to Segment without any additional work on the client — this is a pure server-to-server integration.
This is an Event Cloud Source which can not only forward data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.
This source is maintained by Statsig. For any issues with the source, contact their Support team.
- From the Segment dashboard, navigate to Catalog and search for
Statsigon the Sources tab.
- Click the Statsig tile, and then click on the blue Add Source button.
- Name the instance of this source click Add Source.
- Locate your Write Key on the Source Overview page and copy it.
- Log into the Statsig console and navigate to the Integrations page. Click the Segment card.
- Click the Outgoing tab. Paste the
Write Keycaptured on step #4” and click “Enable”.
- Now, configure how data should be mapped and which events to include. The “Event Filtering” screen allows you to select which events & event types Statsig sends to Segment. The “Map Identifiers” configuration will map Statsig identifiers to a corresponding Segment allocation of your choice. Press “Confirm” and you will see an “Integration Updated” dialogue ✅
- Within a few minutes, you can observe your statsig events being ingested in Segment within the “Debugger” panel as shown below.
The table below lists events that Statsig sends to Segment. These events appear as tables in your warehouse, and as regular events in other Destinations. Statsig will include the
userId if available.
|statsig::config_exposure||User was exposed to a set of configuration values|
|statsig::experiment_exposure||User was exposed to an experiment|
|statsig::gate_exposure||User was exposed to a gate|
|custom_event||Any custom event name tracked|
The table below lists the properties included in the events listed above.
|event||Name of the event|
|userId||ID of the user (may not always be present)|
|Email of the user|
|anonymousId||An anonymous identifier, typically the Statsig
|properties.metadata||Any other contextual event metadata|
|properties.value||Value associated with the event|
|originalTimestamp||Timestamp the event was triggered|
|receivedAt||Timestamp the event was received|
Now that your Source is set up, you can connect it with Destinations.
Log into your downstream tools and check to see that your events appear as expected, and that they contain all of the properties you expect. If your events and properties don’t appear, check the Event Delivery tool, and refer to the Destination docs for each tool for troubleshooting.
If there are any issues with how the events are arriving to Segment, contact the Statsig support team.
This page was last modified: 29 Sep 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!