Skip to main content
Paddle integration / Go-live checklist.
It’s pretty simple: once you’ve synced your web products, add them to a standard paywall and link a simple hosted web paywall. A purchase action on a web product opens that web paywall in the browser.When the user subscribes or dismisses the web paywall, Helium takes them back into your app.Here’s the full paywall-building guide.
You have two options:
  • Through your workflow: target the App2Web paywall to an eligible test audience, then open it through your app’s normal trigger.
  • Triple-tap previews: in TestFlight, open any Helium paywall, triple-tap anywhere on it, and select your in-app App2Web paywall.
On an eligible US device, previews default to real purchases, which charge your card; switch to simulated in preview settings if needed. Ineligible devices always simulate purchases. Also test through your workflow to check targeting and post-purchase handlers, which previews bypass.See the preview guide and SDK requirements or the full testing guide.
We recommend starting with App2Web previews. Use a real purchase on an eligible US device to test entitlement delivery; simulated purchases don’t charge you or grant entitlements.Then make a real purchase through your app’s trigger and check that access unlocks when you return. Previews bypass targeting and your post-purchase handlers. See the Paddle tests and user-ID setup.You can use Paddle’s webhook simulator to test delivery separately; it doesn’t create a real purchase.Using RevenueCat? Also check that:
  • Paddle webhooks reach RevenueCat for the correct user.
  • Web products grant the right entitlement tier.
  • Paddle and RevenueCat webhooks reach Helium as configured, and the purchase appears there.
We recommend analytics forwarding for supported analytics destinations: manage your connections in one place, and let Helium forward events with user, product, paywall, and experiment details.Already tracking Helium’s purchase-success events? That still works when users return to your app. StoreKit-only tracking won’t capture web purchases.Once your events arrive, you can forward conversions to Meta through destinations such as PostHog or Amplitude. Our setup guide covers each provider and other MMP routes.Here’s how to connect your analytics provider or MMP.
We host your web paywall on clickthrough.to. Here’s what users will see:
  • Price: we calculate it from the selected offer. Free trials show $0.00 due today in USD; paid trials show the initial charge.
  • Names: make both product and price names customer-facing. We recommend leaving dollar amounts out; checkout already shows the price. Paddle’s Apple Pay title uses the product name.
Your Manage Subscription button takes users to the Paddle customer portal. If they cancel at the end of the billing period, they keep access until then.
We recommend running App2Web against your current IAP paywall in an experiment. Start with:
  • Conversion rate: trial starts or direct purchases per exposed user. Around 500+ conversions is a checkpoint, not proof of significance; check confidence intervals.
  • Take-home ARPU: revenue after fees, taxes, and refunds, divided by all exposed users.
Proceeds is still in beta, so we’d cross-check it with your actual revenue and fees. Incorrect RevenueCat Small Business Program dates can skew its commission data.Example: $10 gross ARPU, 60% web / 40% IAP revenue, assumed fees of 2% web / 30% IAP:
  • App2Web: $10 x (0.60 x 0.98 + 0.40 x 0.70) = $8.68 (24% more).
  • IAP-only: $10 x 0.70 = $7.00.
Use your own fees here; these are illustrative rates. Weight by revenue share, not conversion share, unless revenue per conversion is equal.This example excludes taxes, refunds, and renewals. Revisit equal-age cohorts as revenue accumulates; stronger web renewals can increase lift.