How To Use Analytics To Double Your App Ad Revenue

How To Use Analytics To Double Your App Ad Revenue

The difference between an app earning $200/month and the same app earning $400/month from ads is rarely more users. It is usually better use of existing traffic. Most developers look at top-line ad revenue and do not know which users, screens, or sessions are generating the majority of their earnings.

Here is how to build the analytics visibility that makes ad revenue optimizable.

The Four Metrics That Actually Matter

eCPM (effective cost per mille) — your actual earnings per 1,000 impressions. This is the number to optimize, not fill rate alone.

Fill rate — percentage of ad requests that return a paid ad. Low fill rate means you are requesting ads for users who are not being matched. Floor prices and network selection affect this.

Impressions per session — how many ad impressions the average session generates. Low numbers often mean placements are not being seen (below the fold, quick exit sessions).

Revenue per session — eCPM × impressions per session / 1000. The combined metric that tells you how much a typical user session is worth.

Segment By Screen

Not all screens in your app are equal for ad revenue. A screen where users spend 10 minutes generates 10x the impressions of a screen where they spend 1 minute.

Log ad revenue (or impressions) by screen and sort by total earnings. You will almost always find that 20% of screens generate 80% of ad revenue. This tells you:

  1. Which screens are worth optimizing placement on
  2. Which user journeys drive the most valuable traffic
  3. Whether your onboarding guides users toward high-value screens

Segment By User Cohort

New users and returning users have very different ad revenue profiles:

New users: Short sessions, low impressions, low trust in consent requests. Often low ad revenue per session.

Retained users (Day 7+): Longer sessions, higher impressions, higher consent rates. Often 3-5x the ad revenue per session of new users.

This has a direct implication: improving Day-7 retention improves ad revenue even without a single change to your ad implementation. A 10% improvement in retention on a 5,000-user app is worth more than significant optimization of new user ad placements.

Floor Price Testing

Most developers set CPM floor prices once and forget them. But floor prices should be dynamic based on what you learn from your data.

How to test floors:

  1. Start at your current floor price (or $0.50 if you have never set one)
  2. Increase it by $0.25 and measure fill rate vs. revenue change for 2 weeks
  3. If fill rate drops by less than revenue/1000 increases, the floor increase was worth it
  4. Keep increasing until you find the point where fill rate drops too much

Example: Current floor $0.50, 90% fill rate, eCPM $0.80. Test floor $0.75: fill rate drops to 75%, eCPM becomes $1.10. Revenue per 1000 requests: before = $0.72 (0.9 × $0.80), after = $0.825 (0.75 × $1.10). Floor increase improved revenue per request.

Consent Rate Analytics

If you use data monetization, your consent rate is a critical lever. Track:

A 10-percentage-point improvement in consent rate (say, 55% to 65%) is a 18% improvement in data revenue with no other changes. Consent UI testing is among the highest-ROI optimization activities for apps using data monetization.

The Revenue Attribution Dashboard

If you build one internal analytics dashboard for ad revenue, build this:

MetricToday7-day avg30-day avg
eCPM
Fill rate
Impressions per session
Revenue per session
Consent rate (if applicable)
Top 5 screens by revenue

Reviewing this weekly takes 10 minutes and surfaces anomalies (fill rate drop = network issue, eCPM drop = floor price needs adjustment, impressions per session drop = placement visibility issue).

What Good Looks Like

For a developer-facing app with 5,000 DAU:

If your numbers are significantly below this range, the analytics will tell you which metric is the bottleneck.

Last updated: September 2026