In-app purchase (IAP)

What is In-app purchase (IAP)?

An in-app purchase (IAP) is a transaction made within a mobile application that allows users to buy additional content, features, or virtual items without leaving the app. IAPs are processed through the platform's native payment system, such as Apple App Store or Google Play, which handles billing and security. They represent one of the primary revenue models for mobile apps across gaming, entertainment, productivity, and beyond.

How it works

In-app purchases are facilitated by the platform's native SDK, either Apple's StoreKit on iOS or Google Play Billing on Android. When a user initiates a purchase, the platform authenticates the transaction, processes payment, and returns a receipt that the app server validates to confirm legitimacy. Developers define purchasable items in the app store console and reference them by product ID within the app.

Types of In-App Purchases

Consumables are items that are used up after purchase and can be bought repeatedly. Examples include virtual currency in games, extra lives, and one-time power-ups. Consumables drive repeat transactions and are a core mechanism in freemium gaming monetization.

Non-consumables are permanent unlocks that a user purchases once and retains indefinitely. Examples include additional levels, ad removal, or premium feature upgrades. These provide a one-time revenue event per user but can meaningfully increase perceived app value.

Non-renewing subscriptions grant access to content or features for a fixed period without automatic renewal. They are suited for seasonal content or limited-time offerings where predictable end dates matter.

Auto-renewable subscriptions automatically charge users on a recurring basis, such as monthly or annually, until the user cancels. They are the dominant model for streaming services, productivity tools, and fitness platforms because they generate stable, predictable recurring revenue.

Platform Processing

Both Apple and Google take a commission on IAP revenue, which developers must account for in pricing strategy. Apple introduced App Store Server API and StoreKit 2 as the current standard for receipt validation, replacing the deprecated verifyReceipt endpoint. On Android, the Google Play Billing Library handles all transaction logic and server-side validation.

Why it matters

In-app purchases are a foundational revenue driver for mobile apps. Unlike one-time paid downloads, IAPs allow developers to offer a free entry point that reduces acquisition friction while monetizing engaged users over time. Auto-renewable subscriptions in particular provide recurring revenue that supports sustainable business operations and long-term product investment.

For marketers and growth teams, IAP behavior is a critical signal for measuring user quality. A user who completes a purchase is significantly more valuable than one who does not, and this distinction directly shapes campaign optimization decisions. Tracking IAP events within an MMP like Airbridge allows teams to connect ad spend to actual revenue, calculate accurate return on ad spend (ROAS), and identify which acquisition channels produce paying users rather than just installs.

IAP data also informs lifetime value (LTV) modeling. By analyzing purchase frequency, average order size, and subscription retention, teams can build predictive models that guide budget allocation and bidding strategies. Receipt validation is essential to ensuring that IAP data feeding these models is accurate and not distorted by fraudulent or duplicate transactions.

How to measure in-app purchase performance

Measuring IAP performance requires connecting purchase events to the full user journey, from ad exposure through install to first and repeat purchases.

1. Instrument IAP events in your analytics stack. Trigger an in-app event immediately after a successful transaction is confirmed by the platform. Pass key parameters including product ID, revenue amount, currency, and purchase type (consumable, non-consumable, or subscription).

2. Validate receipts server-side. Use Apple's App Store Server API or Google Play Developer API to verify that each transaction is genuine before recording it as confirmed revenue. This prevents inflated purchase data from test transactions or tampered receipts.

3. Connect purchase events to attribution. Send confirmed IAP events to your MMP so revenue can be attributed back to the originating campaign, creative, and channel. This enables accurate ROAS calculation at the channel and campaign level.

4. Segment by purchase type and user cohort. Analyze consumable purchases separately from subscriptions. Cohort analysis reveals how quickly users convert to paying status after install, which is a strong indicator of campaign quality.

5. Monitor key IAP metrics. Track average revenue per user (ARPU), average revenue per daily active user (ARPDAU), conversion rate from free to paying, and subscription renewal rate. Declining renewal rates signal churn risk that warrants re-engagement campaigns.

6. Use LTV modeling to guide acquisition spend. Platforms like Airbridge allow teams to project lifetime value based on early IAP signals, enabling smarter bid optimization toward users who are likely to generate meaningful revenue over time.

Related concepts