惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Martin Fowler
Martin Fowler
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
雷峰网
雷峰网
J
Java Code Geeks
G
Google Developers Blog
博客园 - 司徒正美
The GitHub Blog
The GitHub Blog
L
LangChain Blog
人人都是产品经理
人人都是产品经理
GbyAI
GbyAI
Vercel News
Vercel News
S
SegmentFault 最新的问题
Engineering at Meta
Engineering at Meta
H
Hackread – Cybersecurity News, Data Breaches, AI and More
云风的 BLOG
云风的 BLOG
F
Fortinet All Blogs
Y
Y Combinator Blog
博客园_首页
Last Week in AI
Last Week in AI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
A
About on SuperTechFans
B
Blog
Microsoft Security Blog
Microsoft Security Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why eCPM Alone Can Mislead You When Mobile Game Ad Revenu...
Xia Yu · 2026-06-22 · via DEV Community

Xia Yu

When mobile game ad revenue drops, it is tempting to open the ad dashboard and check one number first:

eCPM.

If eCPM is down, it feels like the answer is obvious. Demand is worse. The network is paying less. Maybe the mediation setup is broken.

But in practice, eCPM alone can be a misleading first signal.

For small mobile game and app teams, the better question is:

Which driver actually changed first?

Revenue Is Not Just eCPM

At a simple level:

ad revenue = impressions / 1000 * eCPM

That means revenue can drop even when eCPM is stable.
It can also look like eCPM dropped when the real issue is that your traffic mix changed.

Before changing floors, mediation settings, ad units, or user acquisition decisions, I like to split the movement into a few practical drivers.

The Six Drivers I Check

When revenue drops, I usually check these in order:

  1. impressions
  2. fill rate / match rate
  3. eCPM
  4. country mix
  5. placement exposure
  6. ad source / mediation source

This is not a perfect science, but it prevents a lot of premature conclusions.

Case 1: Revenue Down, eCPM Stable

Revenue: -28%

eCPM: stable

Impressions: stable

Fill rate: 78% -> 54%

This is probably not an eCPM problem.

If eCPM stayed stable but fill rate dropped sharply, the first checks should be serving and mediation:

  • did one ad source stop filling?
  • did match rate drop in one country?
  • did a floor or waterfall setting change?
  • did a platform or SDK issue affect requests?
  • did timeout behavior change?

Changing eCPM floors at this point may make the problem harder to diagnose.

Case 2: eCPM Down, Country Mix Changed

Revenue: -18%

Total eCPM: -20%

US eCPM: stable

US impressions share: down

Lower-eCPM countries: up

At first glance, this looks like demand got worse.

But if your high-value countries lost share and lower-eCPM countries gained share, total eCPM can drop even when pricing inside each country is normal.

In this case, I would check:

  • traffic source changes
  • user acquisition campaigns
  • organic installs by country
  • country-level impressions share
  • placement exposure by region

This is a traffic mix issue before it is a pricing issue.

Case 3: One Placement Lost Exposure

Revenue: -22%

eCPM: mostly stable

Fill rate: mostly stable

Rewarded video impressions: down

Interstitial impressions: stable

This may be a product or placement exposure issue.

Maybe a button was moved. Maybe a rewarded entry point became less visible. Maybe an update changed level flow or session length.

In this case, the ad dashboard alone may not explain the drop. You need to compare placement exposure with product behavior.

A Simple Diagnosis Table

What changed? More likely issue
Revenue down, impressions down traffic, product flow, placement exposure
Revenue down, fill rate down serving, mediation, source availability
Revenue down, eCPM down demand, pricing, country mix, source performance
Total eCPM down, top-country eCPM stable country mix
One placement down UI, session flow, placement logic
One source down mediation, bidding, source status, floor setup

The goal is not to magically increase revenue from one table.

The goal is to avoid fixing the wrong thing.

Why This Matters For Small Teams

Large studios often have analysts, dashboards, alerting, and internal data pipelines.

Small teams usually do not.

They may be checking AdMob, AppLovin MAX, Unity LevelPlay, TopOn, Unity Ads, or CSV exports manually.

That makes diagnosis slow. It also makes it easy to overreact to one number.

What I Am Building

I am building a small tool called eCPM Bazaar around this diagnosis workflow.

The current version is intentionally simple:

  • browser-only demo
  • CSV templates
  • anonymized examples
  • copyable diagnosis output
  • free test diagnosis by email

It is not meant to replace AdMob, AppLovin MAX, Unity LevelPlay, TopOn, or any mediation dashboard.

The goal is narrower:

help small mobile game and app teams understand why ad revenue changed.

If you monetize a mobile game or app with ads, I would love to know:

  • what do you check first when revenue drops?
  • do you trust eCPM as the first signal?
  • do you look at fill rate, country mix, placement exposure, or source performance?
  • would a short copyable diagnosis report be useful?

I am looking for a few developers with anonymized ad monetization data to test the workflow.

Public demo: https://ecpmbazaar.com/demo/

Free diagnosis: https://ecpmbazaar.com/free-diagnosis/