Statsig Destination

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 automates the grunt work so that A/B tests are always running automatically and you always know how your features are performing.

This destination is maintained by Statsig. For any issues with the destination, contact the Statsig Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Statsig” in the Destinations Catalog, and select the “Statsig” destination.
3. Choose which Source(s) should send data to the “Statsig” destination.
4. Go to the Statsig dashboard, find and copy the Statsig “Server Secret Key”.
5. Enter the Statsig “Server Secret Key” in the “Statsig” destination settings in Segment.

Supported methods

Statsig supports the following methods, as specified in the Segment Spec.

Page

Send Page calls to Statsig. For example:

analytics.page("Home")

Segment sends Page calls to Statsig as:

{
  "event": "segment_page:Home"
}

These events are included in any experiments running on Statsig and will show up in all Metrics data.

Screen

Send Screen calls to Statsig. For example:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to Statsig as:

{
  "event": "segment_screen:Home"
}

These events are included in any experiments running on Statsig and will show up in all Metrics data.

Track

Send Track calls to Statsig. For example:

analytics.track('Login Button Clicked')

Segment sends Track calls to Statsig as:

{
  "event": "segment_track:Login Button Clicked"
}

These events are included in any experiments running on Statsig and will show up in all Metrics data.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.