iOS in-app purchases and subscriptions: setup, management and reporting
Add purchases and subscriptions to an iOS app without building every store edge case yourself.
This guide covers the SDK workflow, remote product control, customer lookup, event integrations, and the checks to run before you ship.
What the SDK handles
A native iOS SDK is intended to shorten the path from installation to a working purchase flow. The core operations are fetching available products, completing a purchase, and checking whether a subscription is active. Product and pricing changes can be hosted and configured from a dashboard, so routine updates do not always require a new app release.
Use this as your launch checklist:
- Confirm the SDK is configured with your API key before any purchase call.
- Fetch products first and verify the product you intend to sell is returned.
- Complete a test purchase in a sandbox environment and confirm the entitlement unlocks.
- Check subscription status after purchase, renewal, cancellation and expiration.
- Verify a webhook or event is received for a real-time change.
- Confirm the same customer can be found across devices before you rely on cross-platform access.
The supplied Swift example is retained as protected module code0001. Follow the exact module contents for configuration and purchase calls; do not substitute field names or call signatures from memory.
Why teams use a managed layer
Three practical benefits recur for teams adopting a managed layer. First, products and pricing can be changed remotely, avoiding long release cycles for routine commercial updates. Second, platform edge cases and store updates are handled centrally rather than reimplemented in each app. Third, customer status becomes a single reference point across platforms and third-party tools, which reduces mismatches between what support sees and what the app enforces.
A useful distinction: remote configuration changes what is offered and at what price; it does not replace testing the purchase flow itself. Always re-test checkout after a pricing or product change, even when no app code changed.
Reporting and customer management
Reporting is built around revenue, churn and retention, with filters and segments to narrow the view. For support, a customer record should show purchase history and active subscriptions on a timeline, so a billing question can be debugged without asking the user to repeat their history. Promotional subscriptions can also be granted directly, without requiring the user to redeem a promo code.
Before launch, check that a support user can answer these in under a minute: What did this customer buy, when, and is it still active? If the answer requires engineering help, the customer view is not ready.
Integrations by job
Purchase and subscription events can flow to the tools your team already uses for attribution, analytics, engagement, support and data storage. Each category below lists the event types it receives and the named tools available for that job, so you can wire the right events to the right destination from the start.
Advertising and attribution tools receive trial, subscription, renewal, cancellation and conversion events, plus media source, creative, ad group, campaign and keyword dimensions. Named examples include Adjust, Airbridge, Apple Search Ads, AppsFlyer, Branch, Meta Ads, Singular, SplitMetrics Acquire and Tenjin.
Analytics tools receive initial purchase, trial started, trial converted, trial cancelled, renewal, cancellation, uncancellation, billing issues, expiration and product change events. Named examples include Amplitude, Firebase, Mixpanel, mParticle, PostHog, Segment and Statsig.
Engagement tools use product change, trial, purchase, cancellation, refund, expiration, uncancellation and billing issue events to trigger onboarding, win-back and lifecycle campaigns. Named examples include Airship, Braze, CleverTap, Customer.io, Iterable and OneSignal.
Support tools receive real-time cross-platform customer data and alerts for churn, conversion and billing errors. Named examples include Discord, Intercom, Slack and Zendesk.
Data tools receive normalized cross-platform events for cloud storage and analysis, including INITIAL_PURCHASE, NON_RENEWING_PURCHASE, RENEWAL, PRODUCT_CHANGE, CANCELLATION, UNCANCELLATION, BILLING_ISSUE, SUBSCRIPTION_PAUSED, TRANSFER and EXPIRATION. Named destinations include Amazon S3, Google Cloud, scheduled data exports and webhooks.
Web billing connections are also listed for Paddle, Stripe and the Stripe Dashboard App, for teams that need web purchase data alongside app data.
Identity, entitlements and growth analysis
Two identity checks prevent the most common support failures. Identity validation matches a subscriber to the correct user and keeps that mapping consistent across devices. Cross-platform entitlements then unlock access for the right users on each device. Test both with a second device or platform before launch: sign in as the same user, confirm access follows them, and confirm a different user does not inherit it.
For growth work, the same event stream supports practical questions: which creative drives conversion, which referrals produce the highest lifetime value, and which keywords or campaigns perform. Interactive reports help explain when users convert and why, measure retention impact after a feature release, and surface problem areas by store, country or subscription plan. Treat these as analysis workflows, not automatic answers — segment by one dimension at a time and compare against a baseline period.
| Integration category | Typical events or data | Named examples from source |
|---|---|---|
| Advertising and attribution | Trial starts, subscriptions, renewals, cancellations, trial conversions; media source, creative, ad group, campaign, keyword | Adjust, Airbridge, Apple Search Ads, AppsFlyer, Branch, Meta Ads, Singular, SplitMetrics Acquire, Tenjin |
| Analytics | Initial purchase, trial started/converted/cancelled, renewal, cancellation, uncancellation, billing issues, expiration, product change | Amplitude, Firebase, Mixpanel, mParticle, PostHog, Segment, Statsig |
| Marketing and engagement | Product change, trial, purchase, cancellation, refund, expiration, uncancellation, billing issues | Airship, Braze, CleverTap, Customer.io, Iterable, OneSignal |
| Customer support | Initial purchase, trial, renewal, cancellation, uncancellation, billing issues, expiration, product change | Discord, Intercom, Slack, Zendesk |
| Data management | INITIAL_PURCHASE, NON_RENEWING_PURCHASE, RENEWAL, PRODUCT_CHANGE, CANCELLATION, UNCANCELLATION, BILLING_ISSUE, SUBSCRIPTION_PAUSED, TRANSFER, EXPIRATION | Amazon S3, Google Cloud, Scheduled Data Exports, Webhooks |
| Billing and payments | Web purchase data connections | Paddle, Stripe, Stripe Dashboard App |
Examples are those named in the source; availability and configuration must be confirmed in the integration directory before implementation.