> ## Documentation Index
> Fetch the complete documentation index at: https://helium-mintlify-create-navigation-structure-42614.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Third-party analytics integrations

> Connect Helium with your analytics platforms

Helium can forward paywall events to your existing analytics platforms so you can track paywall performance alongside the rest of your product data — without writing any additional instrumentation code.

***

### **Supported Platforms**

| Platform      | Description                                                                                                       |
| :------------ | :---------------------------------------------------------------------------------------------------------------- |
| **Mixpanel**  | Paywall events appear as Mixpanel events, tied to user identity. Build funnels from paywall open to subscription. |
| **Amplitude** | Paywall events flow into Amplitude for behavioral analysis and cohort building.                                   |
| **PostHog**   | Paywall events as PostHog events, useful for product analytics and session replay correlation.                    |
| **Statsig**   | Paywall events forwarded to Statsig for feature flag analysis and experimentation.                                |

You can connect **multiple platforms at the same time**. Events are sent to all connected destinations simultaneously.

***

### **How It Works**

1. The **Helium SDK** captures paywall interactions in your app.
2. Events are sent to Helium's event pipeline (a Segment-compatible layer).
3. The pipeline **routes events** to Helium's own analytics (for your dashboard metrics) *and* to any third-party destinations you've configured.

Once connected, forwarding is fully automatic. No SDK changes or additional code required.

***

### **Events Forwarded**

| Event                           | When it fires                                                   |
| :------------------------------ | :-------------------------------------------------------------- |
| helium\_paywallOpen             | A paywall is displayed to the user.                             |
| helium\_paywallDismissed        | The user dismisses the paywall.                                 |
| helium\_subscriptionPressed     | The user taps the subscribe button.                             |
| helium\_subscriptionSucceeded   | The purchase completes successfully.                            |
| helium\_subscriptionFailed      | The purchase fails.                                             |
| helium\_subscriptionCanceled    | The user cancels during the purchase flow.                      |
| helium\_paywallsDownloadSuccess | The SDK successfully initializes and downloads paywall configs. |

Each event includes contextual properties: paywall ID, paywall name, trigger name, experiment ID and variant (if applicable), device type, OS, and user identifiers.

***

### **Setup**

<Steps>
  <Step title="Go to Integrations → Analytics in the Helium dashboard" />

  <Step title="Select a platform" />

  <Step title="Enter your credentials:">
    * **Mixpanel** — Project Token
    * **Amplitude** — API Key
    * **PostHog** — Project API Key and Host
    * **Statsig** — Server Secret Key
  </Step>

  <Step title="Save. Events begin forwarding immediately" />
</Steps>

To disconnect, open the integration and remove it from the Integrations page. Forwarding stops right away.

***

### **Key Points**

* **No SDK code changes needed** — connecting a destination in the dashboard is all it takes.

* Events are forwarded **in real time** as they occur in the app.

* **Fallback paywalls also send events** — the analytics configuration is embedded in the fallback bundle, so tracking works even when the paywall is served from cache.

* Helium's own dashboard metrics are **not affected** by third-party integrations — they always use Helium's primary data pipeline regardless of what destinations are connected.