Skip to content

Commit ea1187a

Browse files
tcgilbertmarkzegarelli
tcgilbert
and
markzegarelli
authored
Docs for new Statsig source (#3574)
* Docs for new Statsig source * Edits and remove images * delete image source files Co-authored-by: markzegarelli <[email protected]>
1 parent f1ae0c7 commit ea1187a

File tree

2 files changed

+69
-0
lines changed
  • .github/styles/Vocab/Docs
  • src/connections/sources/catalog/cloud-apps/statsig

2 files changed

+69
-0
lines changed

‎.github/styles/Vocab/Docs/accept.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,7 @@ Skalin
111111
Smartly
112112
Snapchat
113113
Spideo
114+
Statsig
114115
subaction
115116
Subnet
116117
svg

‎src/connections/sources/catalog/cloud-apps/statsig/index.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: Statsig Source
3+
id: 3x07B5Dn5h
4+
---
5+
6+
[Statsig](https://www.statsig.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) 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.
7+
8+
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.
9+
10+
This is an [Event Cloud Source](/docs/sources/#event-cloud-sources) which can not only forward data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.
11+
12+
This source is maintained by Statsig. For any issues with the source, [contact their Support team](mailto:[email protected]).
13+
14+
## Getting Started
15+
16+
1. From the Segment dashboard, navigate to **Catalog** and search for `Statsig` on the **Sources** tab.
17+
2. Click the Statsig tile, and then click on the blue **Add Source** button.
18+
3. Name the instance of this source click **Add Source**.
19+
4. Locate your Write Key on the Source Overview page and copy it.
20+
5. Log into the Statsig console and navigate to the [Integrations](https://console.statsig.com/integrations) page. Click the Segment card.
21+
6. Click the **Outgoing** tab. Paste the `Write Key` captured on step #4" and click "Enable".
22+
7. 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 ✅
23+
8. Within a few minutes, you can observe your statsig events being ingested in Segment within the "Debugger" panel as shown below.
24+
25+
26+
## Events
27+
28+
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.
29+
30+
> info ""
31+
> More details on event payloads can be found in [Statsig's documentation](https://docs.statsig.com/integrations/data-connectors/segment#configuring-outbound-events){:target="_blank"}.
32+
33+
34+
| Event | Description |
35+
| ---------------------------- | ------------------------------------------------- |
36+
| statsig::config_exposure | User was exposed to a set of configuration values |
37+
| statsig::experiment_exposure | User was exposed to an experiment |
38+
| statsig::gate_exposure | User was exposed to a gate |
39+
| custom_event | Any custom event name tracked |
40+
41+
42+
## Event Properties
43+
44+
The table below lists the properties included in the events listed above.
45+
46+
> info ""
47+
> More details on event payloads can be found in [Statsig's documentation](https://docs.statsig.com/integrations/data-connectors/segment#configuring-outbound-events){:target="_blank"}.
48+
49+
50+
| Property Name | Description |
51+
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
52+
| event | Name of the event |
53+
| userId | ID of the user (may not always be present) |
54+
| email | Email of the user |
55+
| anonymousId | An anonymous identifier, typically the Statsig `stableID`. This can be controlled in the Statsig mapping settings shown in step #7 above. |
56+
| properties.metadata | Any other contextual event metadata |
57+
| properties.value | Value associated with the event |
58+
| originalTimestamp | Timestamp the event was triggered |
59+
| receivedAt | Timestamp the event was received |
60+
61+
## Add Destinations
62+
63+
Now that your Source is set up, you can connect it with Destinations.
64+
65+
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](/docs/connections/event-delivery/) tool, and refer to the Destination docs for each tool for troubleshooting.
66+
67+
If there are any issues with how the events are arriving to Segment, [contact the Statsig support team](mailto:[email protected]).
68+

0 commit comments

Comments
 (0)