Tracking In-App Ad Revenue Next to Purchases: A Unified Monetization View
Hybrid apps earn from two engines at once, and the two engines usually report into different tools. This guide covers what changes when ad revenue events land in the same analytics layer as subscriptions and one-time purchases, which ad metrics answer which question, how the two SDK integration paths differ, and how to read a gap between your ad network and your own numbers.
Why split revenue data hides the real picture
When ad income and purchase income live in separate systems, every cross-channel question turns into a manual exercise: export from one dashboard, reconcile against another, and hope the definitions line up. The practical cost is decision speed. Lifetime value figures built only from purchase data describe subscribers, not the whole user base, so teams end up ranking channels and cohorts on partial evidence. Folding ad events into the same analytics layer as subscriptions and one-time purchases makes total revenue mean what it says, and gives cohort value a basis that includes every monetization channel.
What a unified revenue view includes
Ad revenue events are ingested in real time next to purchase data, so you no longer alternate between an ad network dashboard and a purchase analytics tool to see the whole number. Two views change as a result: the main revenue chart now folds ad revenue into total revenue, and realized LTV includes ad income, which gives cohort value a fuller basis than subscriber payments alone.
The ad metrics and what each one answers
A dedicated Ads section in the charts area groups the numbers that matter to an ad monetization strategy. Use the metric map below to decide which number answers your question before you start building reports. A workable order for a first pass: start with Ad Revenue to size the channel, then ARPDAU to judge blended health, then Impressions and Fill Rate to check whether delivery is constrained, and finally RPM, CTR, and eCPM to compare efficiency across periods, countries, or platforms.
Per-user ad visibility
A dedicated Ads tab on the customer details page lets you open an individual profile and review that user's total ad revenue, impressions, clicks, fill rate, CTR, eCPM, and impression timestamps. This is the view to use when a cohort-level number looks odd and you need to see whether a specific user's ad activity explains it.
Integration: one SDK, two paths
Setup runs through the same SDK you already use for purchases. With Google AdMob, you replace the standard AdMob loading calls with the SDK's loadAndTrack methods and ad events are tracked automatically. With any other mediation platform that supplies impression-level revenue data — AppLovin MAX, ironSource, Unity Ads, and others — you call the AdTracker methods inside your ad SDK callbacks at the appropriate moment. Either way the underlying SDK is the same. The choice is therefore about your mediation stack, not about adopting a second client library.
What the feature is not, and how to read a mismatch
This is not a measurement partner for campaign attribution, and it does not replace your mediation platform. What it adds is subscription context around your ad data. Expect small differences between the two sides: the SDK reports real-time data, while mediation platforms such as AdMob report post-processed, fraud-filtered figures. Use this distinction before you debug: a consistent, small offset that tracks with network-side filtering is the known data-path difference, whereas ad activity that never appears at all points to the event not being sent — a missing or mis-timed loadAndTrack or AdTracker call in your integration.
Where the feature is heading
The beta concentrates on getting the foundational data right and providing a unified revenue view. Planned follow-ups include blended ARPDAU across all users; later updates are expected to add predicted LTV that accounts for ads, plus analytics on how ad exposure relates to subscription conversion and churn.
Getting access
The source announcement described In-App Ad Revenue Tracking as a public beta, and stated that any customer could request access by navigating to the Ads page in their dashboard. Apps monetizing through platforms such as Google AdMob or AppLovin could begin sending ad events at that point. Current availability and the access path should be confirmed against the live product before you plan around it: {{OWNER_FEATURE_AVAILABILITY}}.
| Metric | What it measures | Use it when you want to... |
|---|---|---|
| Ad Revenue | Total revenue generated from ads | See the foundational ad income number |
| ARPDAU (Ad Users) | Average revenue per daily active user | Judge blended health for a hybrid app |
| Ad Monetized Users | Number of times users clicked on ads | Understand engagement and which placements or formats work |
| Ad Impressions & Fill Rate | Total ad displays and the share of ad requests successfully filled | Spot targeting issues or limited ad inventory |
| Ad RPM & CTR | Revenue per thousand impressions and click-through rate | Measure monetization efficiency and engagement quality |
| eCPM | Effective cost per thousand impressions | Compare efficiency across periods, countries, or platforms regardless of impression volume |
Metric definitions reflect the feature as described at the time of the original announcement; confirm current definitions in the product documentation.
| What you observe | Likely explanation | Next check |
|---|---|---|
| Small, consistent difference between network totals and SDK-reported ad revenue | Real-time SDK data versus post-processed, fraud-filtered network data | Confirm the offset tracks with network-side filtering; treat as documented behavior |
| Ad activity for a user or period is absent entirely | Ad event not sent from the app | Verify loadAndTrack (AdMob) or AdTracker calls in ad SDK callbacks fire at the right moment |
| Cohort-level ad figure looks wrong but the aggregate is plausible | One user's ad activity skewing the view | Open the customer's Ads tab and inspect total ad revenue, impressions, clicks, and timestamps |
Triage guidance is derived from the captured feature description, not from runtime testing.
Frequently asked questions
Can I see ad revenue and subscription revenue in one place?
Yes. Ad revenue events are ingested alongside purchase data, and ad income is folded into the main revenue chart and into realized LTV, so total revenue covers subscriptions, one-time purchases, and ads together.
Do I need a different SDK for ad tracking?
No. It is the same SDK used for purchases. AdMob users swap standard loading calls for loadAndTrack methods; other mediation platforms with impression-level revenue data use AdTracker calls in ad SDK callbacks.
Why do my ad numbers not match my ad network exactly?
The SDK reports real-time data, while mediation platforms such as AdMob report post-processed, fraud-filtered data. Small discrepancies are expected and documented. A total absence of ad activity is a different problem and usually points to the event not being sent.
Does this replace my mediation platform or measure campaign attribution?
No. It does not measure campaign attribution and does not replace mediation. Its role is to add subscription context to ad data.
How do I get access?
The source announcement said any customer could request access from the Ads page in their dashboard. Confirm current availability before relying on it: {{OWNER_FEATURE_AVAILABILITY}}.