Add in-app purchases to your Unity app
Add subscriptions and one-time purchases to a Unity game without building your own purchase backend.
The SDK handles product fetching, purchase flow, entitlement checks, and subscription status, while hosted reporting and integrations cover the business side after checkout.
How the purchase flow should work in Unity
A Unity purchase setup has three jobs: show the right offer, complete checkout through the store, and unlock content only for people who actually paid. Splitting those jobs makes debugging easier.
- Fetch: retrieve the packages you configured for the current platform before showing a paywall.
- Buy: pass a package to the purchase call and handle the callback, including the case where the user cancels.
- Gate: inspect active entitlements in the returned purchaser info, then unlock the matching feature. Do not unlock based only on a successful store dialog.
The supplied Unity example follows that pattern: it obtains the Purchases component, calls PurchasePackage, and checks whether a named entitlement is present in Entitlements.Active before unlocking pro content. That check is the decision point to reuse in your own feature flags, level unlocks, or premium currency grants.
Checklist before release:
- Confirm each product and entitlement identifier matches between the store, the dashboard configuration, and the game code.
- Test a cancelled purchase and confirm no content is unlocked.
- Test an active entitlement on a second device to confirm cross-platform access follows the same identity.
- Verify renewal, cancellation, expiration, and billing-issue events appear in reporting and webhooks.
- Grant a promotional subscription from the customer view and confirm the game reflects it without a promo code redemption.
Manage products and customers without release cycles
Remote product configuration lets you change products and pricing from a dashboard instead of shipping a new build for every price test. That matters when you want to run an experiment, fix a mispriced item, or retire an offer quickly.
A single customer record across platforms reduces duplicate support work. Identity validation keeps subscriber identity tied to the right user and consistent across devices, while cross-platform entitlements unlock access for the right people wherever they play.
For support, a customer timeline showing purchases and active subscriptions helps an agent see what happened before answering. Promotional subscriptions can be granted directly from that view when a goodwill gesture is needed.
Turn purchase events into reporting and action
Built-in charts cover revenue, churn, and retention, with filters and segments for deeper cuts. You can break results down by store, country, and subscription plan to spot where a problem or opportunity is concentrated.
Purchase events flow to analytics, marketing, support, and data tools, covering moments such as initial purchase, trial start and conversion, renewal, cancellation, uncancellation, billing issues, expiration, product change, and refund. Attribution integrations add media source, creative, ad group, campaign, and keyword dimensions, so you can see which creative or keyword is driving conversion rather than guessing.
Named integrations by category:
- Advertising and monetization: Adjust, Airbridge, Apple Search Ads, AppsFlyer, Branch, Meta Ads, Singular, SplitMetrics Acquire, Tenjin.
- Analytics: Amplitude, Firebase, Mixpanel, mParticle, PostHog, Segment, Statsig.
- Marketing and engagement: Airship, Braze, CleverTap, Customer.io, Iterable, OneSignal.
- Customer support: Discord, Intercom, Slack, Zendesk.
- Data management: Amazon S3, Scheduled Data Exports, Google Cloud, Webhooks.
- Billing and payments: Paddle, Stripe, Stripe Dashboard App.
Use the events by job:
- Analytics tools: understand when users convert and whether a new feature changed retention.
- Engagement tools: trigger onboarding after a new download or trial start, and send win-back offers to recently churned users.
- Support tools: receive real-time alerts for churn, conversion, or billing errors.
- Data storage: deliver normalized cross-platform events to cloud storage through scheduled exports or webhooks.