Add in-app purchases to your Android app
Add Android purchases and subscriptions with a native SDK, then manage products, entitlements, customers, and reporting from one place.
This guide explains the setup, the purchase flow, and the integrations that turn subscription events into action.
Set up the purchase flow
A practical setup has four parts. First, install the native SDK in the Android project. Second, fetch the available products or packages. Third, start a purchase and handle both success and cancellation or error. Fourth, check the customer's entitlement before unlocking paid features. The protected example in module code0001 follows that sequence: it receives a purchase and customer information on completion, checks a named entitlement, and has a separate error path when no purchase occurs. Keep the entitlement check on the client decision path, and treat the error callback as a normal outcome rather than a crash.
Manage products without release delays
Host products and pricing remotely so catalogue changes can be published without waiting for a store release cycle. Use the dashboard as the place to review what is offered, then confirm in the app that the fetched package matches the intended offer. This separation helps when prices change, a product is replaced, or a promotional offer needs to be tested.
Check entitlements and support customers
Treat entitlement status as the single answer to whether a customer can access paid features. Identity mapping should stay consistent when the same person uses more than one device, so access follows the subscriber rather than a single install. For support, a timeline of purchases and active subscriptions makes it easier to explain what happened and to grant a promotional subscription when appropriate.
Measure revenue and acquisition quality
Use reporting to compare revenue, churn, and retention across stores, countries, and subscription plans. Break results down by campaign, creative, media source, ad group, and keyword to see which acquisition activity is producing valuable subscribers. A useful review routine is: check conversion by creative, compare lifetime value by referral source, watch retention after a feature release, and investigate drops by store or plan before changing spend.
Connect events to your stack
Send subscription events to the tools your team already uses. Analytics destinations can receive events such as initial purchase, trial started, trial converted, renewal, cancellation, billing issue, expiration, and product change. Engagement tools can use moments such as a new download, trial start, or recent churn to trigger onboarding or win-back messages. Support tools can receive alerts for churn, conversion, or billing errors. Data destinations can receive normalized events for warehouse reporting, and webhooks can notify your own systems in real time.
Launch checklist
Before launch, work through this checklist: confirm the SDK package and repository supplied by the owner; fetch products and verify the package shown to users; complete a test purchase and confirm the entitlement becomes active; cancel a purchase and confirm paid content stays locked; check that the same subscriber is recognised across devices; verify that trial, renewal, cancellation, and billing-issue events reach the selected destinations; and confirm that support can see the customer's purchase timeline.
| Destination type | Useful events | Example action |
|---|---|---|
| Analytics | Initial purchase, trial started, renewal, cancellation | Compare conversion and retention by plan or country |
| Attribution | Trial starts, subscriptions, renewals, trial conversions | Compare creative, campaign, keyword, and media source |
| Engagement | New download, trial start, churn | Trigger onboarding or win-back messages |
| Support and alerts | Billing issue, expiration, conversion, churn | Notify the team and investigate the customer timeline |
| Data storage | Normalized subscription events | Build warehouse reports and scheduled exports |
Event availability depends on the selected integration and configuration.
Frequently asked questions
What does the Android SDK handle in the app?
Use the native SDK to fetch products, start a purchase, and check whether an entitlement is active. The protected purchase example in module code0001 shows the completion and error callbacks that gate access to paid content.
Can product and pricing changes be made without an app release?
Yes. Products and pricing can be hosted and changed from a dashboard, so routine price or catalogue updates do not need a new app release.
How does customer management help support?
Customer records show purchase history and active subscriptions in one timeline. Support can use that view to investigate a report, and a promotional subscription can be granted without requiring the customer to redeem a promo code.
Which events can be shared with other tools?
Subscription events can be sent to analytics, engagement, support, attribution, and data-storage tools. Examples include trial starts, renewals, cancellations, billing issues, expirations, and product changes, depending on the destination.