---
title: Amplitude Native
description: Forward Statsig exposures and custom events into a linked Amplitude project so you can query Statsig data alongside your Amplitude events.
product: general
lang: en
token_estimate: 1349
---
# Amplitude Native

The Amplitude Native integration forwards Statsig exposures and custom events into an Amplitude project, so you can query Statsig data with Amplitude charts, cohorts, and dashboards. The integration uses the link between your Statsig and Amplitude organizations instead of an API key. Amplitude doesn't count forwarded events toward your event volume.

> For AI agents: a documentation index is available at [/llms.txt](/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

Statsig Cloud and Warehouse Native projects both support this integration.

Use Amplitude Native when you want Statsig data in Amplitude. To build Statsig metrics from Amplitude events, use [Amplitude events as a metric source](https://docs.statsig.com/integrations/data-connectors/amplitude/metric-source) instead.

## Prerequisites

- You've linked your Statsig organization to your Amplitude organization, and linked the Statsig project to an Amplitude project. Refer to [Amplitude](https://docs.statsig.com/integrations/data-connectors/amplitude) for the linking steps.
- The Amplitude project uses the US data center.
- You have admin access to the Statsig project.

## Create the integration

1. In Statsig, go to _Settings > Product Configuration > Integrations_.
2. Under _Your Integrations_, click **Amplitude Native**.
3. Create a new integration and enter a name for it.
4. Under _Configuration_, select the Amplitude project that receives the events.
5. Click **Confirm**.

Statsig sends no data to Amplitude until you select event types.

## Select the events to forward

1. On the Amplitude Native integration, open the **Event Filtering** tab.
2. Select **Exposures**, then click **Show Detailed Options** to choose individual exposure types.
3. Under **Custom Events**, select the Statsig events you want in Amplitude. The table lists each event with its volume over the last day, so you can judge the cost of forwarding each event.
4. Click **Save**.

Statsig recommends that you start with exposures and a small set of custom events. Widen the selection after you confirm the data in Amplitude.

To forward every new custom event automatically, turn on **Include new events by default**. Leave the setting off when you want to approve each event.

### Exposure types

| Option | Forwarded event name |
| --- | --- |
| Gate Exposures | `statsig::gate_exposure` |
| Experiment Exposures | `statsig::experiment_exposure` |
| Autotune Exposures | `statsig::experiment_exposure` |
| Dynamic Config Exposures | `statsig::config_exposure` |
| Layer Exposures | `statsig::layer_exposure` |
| Holdout Exposures | `statsig::holdout_exposure` |

Autotune exposures and experiment exposures share the `statsig::experiment_exposure` event name. Use the `statsig::config` property to distinguish the two in Amplitude.

**Disabled Entity Exposures** changes which exposures qualify rather than adding an event name. Turn it on to also forward the exposures Statsig records for disabled gates, dynamic configs, and experiments, under the event names in the table.

Custom events keep their original Statsig names in Amplitude. An event named `checkout_started` in Statsig arrives as `checkout_started`, not under a `statsig::` prefix.

For the full list of properties on each forwarded event, refer to [Statsig events in Amplitude](https://amplitude.com/docs/data/statsig-forwarded-events).

## Restrict forwarding by environment

Use the **Environments** section of the **Event Filtering** tab to forward events from only some Statsig environments. Project linking maps one Amplitude project to each Statsig environment, so restricting environments keeps development traffic out of a production Amplitude project.

## Verify that events arrive

1. In Amplitude, go to _Data > Events_.
2. Look for the exposure events you selected, such as `statsig::gate_exposure`.

Events usually appear within a few minutes, but can take up to an hour. For delivery detail on the Statsig side, open the **Debug** tab on the integration. The **Usage** tab shows how much data the integration has forwarded.

## Change or remove the integration

Open the integration, then click **Disable** to stop forwarding and keep the configuration. Click **Delete** to remove the integration. Disabling stops new events; Amplitude keeps the events it already ingested.

## Limitations

> **Note:**
>
> Statsig forwards only the first exposure recorded for each identity and configuration each day. The day resets at midnight UTC, not in your project's configured timezone. Exposure counts in Amplitude won't match Statsig Metrics Explorer exactly.

> **Note:**
>
> Statsig forwards only events tied to a User ID or a Device ID. Amplitude drops events whose Statsig identity uses another unit ID, such as `companyID`.

> **Note:**
>
> There's no historical backfill. Statsig forwards only events generated after you configure the integration.

> **Note:**
>
> Statsig resolves device and location dimensions with its own methods. As a result, values such as operating system, browser, and country can differ from the values Amplitude resolves for the same user. Forwarded events keep the Statsig values.

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