> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhelium.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Helium is a paywall platform for mobile apps. Paywalls, workflows, triggers, targeting and experiments are configured in the dashboard (https://app.tryhelium.com); the SDK's job is to initialize, present a paywall for a trigger, and report purchases.
> Pick the SDK page for the user's platform: /sdk/quickstart-ios (Swift), /sdk/quickstart-android (Kotlin), /sdk/quickstart-react-native, /sdk/quickstart-flutter. Method names differ per platform; copy them from the page for that platform, never from another platform's page.
> Pages under /sdk/quickstart-ios-v3 and /sdk/quickstart-android-v0 are legacy SDK versions. Use them only when the user is on that version; for upgrades use the /migrations pages.
> For live dashboard data (paywalls, workflows, metrics) connect the Helium MCP server at https://app.tryhelium.com/api/mcp (see /ai-tools/mcp). For SQL over events, revenue, subscriptions and users use the Data Access API (/data-access/overview) and the helium-data-access skill (/data-access/agent-skill). This documentation site also exposes a docs-search MCP server at https://docs.tryhelium.com/mcp.
> Web checkout (App2Web) with Stripe or Paddle is a separate flow from in-app purchases; start at /web-checkout/overview.
> Every page is available as Markdown by appending .md to its URL. The full index is at https://docs.tryhelium.com/llms.txt.

# Rolling Out Helium

> A simple guide for rolling out Helium and monitoring performance.

Here are our tips for rolling out Helium smoothly. Start small, make sure the basics are working, and ramp up from there.

## Set up the rollout

Use your existing feature flag or experimentation tool to split users between your current paywall and Helium. PostHog, Statsig, Firebase Remote Config, LaunchDarkly, or your own feature flag system all work.

For an A/A comparison, keep the paywall design, products, targeting, and purchase behavior as similar as possible between the two groups.

> [!TIP]
>
> Initialize Helium at app launch for all users. Use the feature flag to decide whether a user sees the current experience or Helium.

## Start small

First, test with internal or allowlisted users. Confirm the paywall opens and dismisses correctly, the right products appear, purchases work, and analytics are flowing.

Then roll Helium out to a small percentage of users, usually around 5%, for 24-48 hours. This is mostly a check that everything works in production.

## Validate the data

At this stage, make sure:

* Data is showing up in Helium
* Paywall views and conversions are being recorded
* Analytics are flowing for each paywall and trigger
* Error logs do not show any new problems

This step is about confirming the data is working, not comparing aggregate performance yet.

## Ramp up

Once everything looks healthy, you can roll Helium out to everyone.

If you want to confirm conversion is maintained first, move to a 50/50 split between your current experience and Helium. At that point, loosely compare the users in each rollout group, paywall views, and paywall conversion rate.

Run it long enough to get a useful amount of conversion data for your traffic level, then complete the rollout.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.