React Native in-app purchases without building purchase infrastructure
Add subscriptions and one-time purchases to a React Native app across iOS, Android, and the web, then manage products, entitlements, reporting, and customer support from one place instead of maintaining separate store logic and servers.
Start with the purchase flow
The core workflow is intentionally small: fetch the available packages, present a purchase, call the purchase method, and then check whether the relevant entitlement is active before unlocking content. The protected example in module code0001 shows that pattern, including a catch path for a failed or absent purchase. In practice, separate the purchase result from the entitlement check so a completed transaction, a cancelled checkout, and a user who simply lacks access are not treated as the same state.
Manage products and access remotely
Remote product management lets you change products and pricing without waiting for an app release. A single customer-status view reduces the need to reconcile iOS, Android, and web records manually. Identity validation keeps the mapping between a subscriber and a user stable across devices, while cross-platform entitlements decide who receives access wherever they sign in.
A practical launch checklist
Use this checklist before enabling a package in production: confirm the product is configured in the dashboard, verify the entitlement name used by the app, test a purchase and a cancellation, check the customer timeline, and confirm the expected event reaches each connected tool. For support, the customer view should show purchase history and active subscriptions in one timeline, and promotional subscriptions can be granted directly when a code-based flow is not needed.
Measure revenue, retention, and acquisition together
Reporting covers revenue, churn, and retention, with filters and segments for store, country, and subscription plan. Interactive views help you see when users convert and why, and whether a feature release affects retention. For acquisition, filter by campaign creative, influencer, referral, keyword, media source, ad group, and campaign so spending follows the sources that produce lifetime value rather than only installs.
Connect events to the tools you already use
Choose integrations by the job they perform. Attribution tools receive trial, subscription, renewal, and cancellation events with media and campaign dimensions. Analytics tools receive lifecycle events such as trial conversion, billing issues, expiration, and product change. Engagement tools can trigger onboarding for new downloads and trial starts, or win-back offers for recently churned users. Support tools receive real-time cross-platform data and alerts for churn, conversion, or billing errors. Data tools receive normalized events through webhooks or scheduled exports to cloud storage.
Integration groups at a glance
The integration groups named on the page include attribution partners such as Adjust, Airbridge, Apple Search Ads, AppsFlyer, Branch, Meta Ads, Singular, SplitMetrics Acquire, and Tenjin; analytics partners such as Amplitude, Firebase, Mixpanel, mParticle, PostHog, Segment, and Statsig; engagement partners such as Airship, Braze, CleverTap, Customer.io, Iterable, and OneSignal; support partners such as Discord, Intercom, Slack, and Zendesk; data destinations including Amazon S3, Google Cloud, scheduled exports, and webhooks; and web billing connections including Paddle and Stripe.
| Integration group | Use it when you need to | Example events or dimensions |
|---|---|---|
| Advertising and monetization | Attribute revenue to acquisition sources | Trial starts, subscriptions, renewals, cancellations, creative, keyword, campaign |
| Analytics | Understand conversion, retention, and problem areas | Initial purchase, trial converted, billing issues, expiration, product change |
| Marketing and engagement | Trigger onboarding and win-back campaigns | New downloads, trial starts, churned users |
| Customer support | Give support real-time customer context and alerts | Churn, conversion, billing error |
| Data management | Send normalized events to storage or your own systems | Initial purchase, renewal, cancellation, subscription paused, transfer |
Availability and exact event payloads should be confirmed for the selected integration before implementation.
Frequently asked questions
Do I need to build a backend to use this approach?
No server work is required for the core purchase flow described here. The SDK handles fetching products, completing purchases, and checking entitlement status, while the dashboard handles remote product configuration and customer views. Webhooks and integrations are available when you want events elsewhere.
How is access kept consistent when a user switches devices?
Yes. Identity validation keeps the subscriber mapping consistent across devices, and cross-platform entitlements determine which users should have access on each device. That gives support a single customer status to check instead of separate store records.
What can support see for an individual customer?
You can view a customer's purchase timeline and active subscriptions, and grant a promotional subscription from the dashboard without a promo code. That timeline is intended to help support debug issues faster.
Which subscription events can be sent to other tools?
Events include initial purchases, trial starts and conversions, renewals, cancellations, uncancellations, billing issues, expirations, product changes, refunds, and paused subscriptions, depending on the integration. Normalized event names are also available for data exports.