Statsig events in Amplitude

The Statsig Amplitude Native integration forwards Statsig exposures and custom events into a linked Amplitude project, where the forwarded events behave like any other Amplitude event. This page lists the events that arrive, the properties on each one, and the behavior that makes forwarded counts differ from the counts Statsig reports.

You configure the integration in Statsig, not in Amplitude. For the setup steps, refer to Amplitude Native in the Statsig documentation.

Forwarded events

Statsig forwards exposures under reserved event names and leaves custom event names unchanged.

Experiment exposures and autotune exposures share the statsig::experiment_exposure name. Use the statsig::config property to separate them.

Custom events keep the names they have in Statsig. An event called checkout_started in Statsig arrives in Amplitude as checkout_started, with no prefix. The forwarded event looks the same as an event sent directly to Amplitude.

Forwarded events arrive as unexpected events because they aren't in your tracking plan. Add the events you plan to chart to the tracking plan so they carry the same descriptions and governance as your other events. For the procedure, refer to Create a tracking plan.

Gate exposure properties

statsig::gate_exposure carries these properties.

Experiment exposure properties

statsig::experiment_exposure carries these properties.

Dynamic config, layer, and holdout exposures carry the same properties. Only the property that names the evaluated object changes, to match the object type.

Duplicated properties

Several diagnostic fields arrive twice, once under a statsig:: prefix and once without it. Both copies hold the same value. Prefer the prefixed copy, which Statsig sets consistently across every exposure type.

Why exposure counts differ from Statsig

Exposure counts in Amplitude don't match the counts in Statsig Metrics Explorer, for two reasons:

• One exposure per identity per day: Statsig forwards only the first exposure it records for each identity and configuration each day, not every exposure.
• UTC day boundaries: The daily window resets at midnight UTC, not in your Amplitude project's configured timezone.

If you change a dynamic config's targeting so a user matches a different rule, Statsig records a new exposure. The same user can then produce a second forwarded exposure on the same day.

Identity resolution

Statsig forwards only events tied to an Amplitude user_id or device_id. Amplitude drops events whose Statsig identity uses another unit ID, such as companyID.

Unlike the Statsig event-streaming destination, Amplitude Native doesn't promote a Statsig stableID into the Amplitude user_id field. A Statsig stableID maps to device_id instead.

Device and location properties

Statsig resolves device and location dimensions itself before forwarding. Operating system, browser, device model, country, region, and city can hold different values than Amplitude resolves for the same user from its own SDK traffic. Forwarded events keep the Statsig values.

Event volume

Amplitude doesn't count events arriving through Amplitude Native toward your event volume. Statsig events that reach Amplitude through the Statsig (Event Stream) destination do count toward event volume.