Can an AI agent change my AdMob mediation waterfall?

The tools exist — create and update mediation groups, create apps and ad units, configure adapter mappings. But Google gates every AdMob monetization method behind limited access, so unless your account is allowlisted the expected answer is a 403 asking you to contact your account manager.

What is AdMob limited access?

An allowlist Google controls over the monetization write methods in the v1beta API. It is independent of OAuth scopes and of anything a third-party tool does — correct implementation on both sides still returns 403 without it.

Why does OBSERVED_ECPM fail in AdMob?

Because it is an Ad Manager metric, not an AdMob one. The three Google publisher products share concepts but not metric names, and borrowing a name across them fails with an unhelpful error.

Is the AdMob write integration available to everyone?

Yes — the admob.monetization scope completed Google's verification and was released to every organization on 18 September 2026. Google's own limited-access gate on the monetization methods still applies on top of that, and it is independent of us.

Playbooks

Automating AdMob mediation groups and ad units with an AI agent

TL;DR

AdMob analysis has always been able to rank ad sources by observed eCPM and fill rate and name the exact waterfall change worth making. Applying it was a manual step in the console. Write tools close that loop — with one caveat that is Google's rather than ours, and that you should check before planning around it.

Check this before anything else

Google gates every AdMob monetization write method behind "limited access". A call returns 403 with a message telling you to contact your account manager, and no amount of correct implementation on either side changes that — it is an allowlist Google controls.

So the honest first step is not "connect and automate", it is "find out whether your account is allowed to". The tools report that 403 as what it is rather than dressing it up as a permissions bug, which at least means you learn it in one call rather than three days.

On top of that, the integration itself is in preview while Google verifies the admob.monetization scope. Two gates, and they are independent.

What the write tools cover

create_app — register an app for monetization.
create_ad_unit — the inventory itself.
create_mediation_group and update_mediation_group — waterfall lines, CPM values and targeting.
create_ad_unit_mapping — third-party adapter configuration, which is where mediation setups usually break.

Eleven reads sit alongside them, including the mediation report that makes any of this worth doing.

The loop this closes

That step-three gap is the whole point. A recommendation you have to re-enter by hand gets applied late, partially, or not at all — and the analysis that produced it was the expensive part.

1The agent pulls the mediation report and ranks ad sources within each group by observed eCPM and fill rate.
2It names the specific change — which source moves up, which CPM line is wrong, which adapter is misconfigured — with the numbers behind it.
3Previously this is where it stopped and you opened the AdMob console.
4Now it drafts the mediation group update, and you approve it.
5Re-read after the change, because a waterfall edit is exactly the kind of thing that should be verified rather than assumed.

One metric that does not exist, and why it matters here

OBSERVED_ECPM is an Ad Manager metric. It is not in AdMob's vocabulary, and a query using it fails with an error that does not say "that belongs to a different Google product".

This is the general hazard of publisher work: three Google products with overlapping concepts and non-overlapping metric names. An agent that assumes one shared namespace produces confident nonsense, which is why the vocabulary belongs in the tool rather than in a prompt asking the model to remember.

Driving this from an MCP client? The AdMob MCP server guide covers the configuration.

What to put on a schedule

A weekly mediation review that ranks sources and proposes the waterfall change, whether or not you can apply it automatically.
Revenue anomaly alerts across AdMob, AdSense and Ad Manager together, since app and web inventory move for different reasons.
Fill-rate monitoring per app and format, which is where a broken adapter shows up first.
eCPM drift by country, the slow problem nobody notices in a single week's numbers.

Frequently asked questions

Can an AI agent change my AdMob mediation waterfall?: The tools exist — create and update mediation groups, create apps and ad units, configure adapter mappings. But Google gates every AdMob monetization method behind limited access, so unless your account is allowlisted the expected answer is a 403 asking you to contact your account manager.
What is AdMob limited access?: An allowlist Google controls over the monetization write methods in the v1beta API. It is independent of OAuth scopes and of anything a third-party tool does — correct implementation on both sides still returns 403 without it.
Why does OBSERVED_ECPM fail in AdMob?: Because it is an Ad Manager metric, not an AdMob one. The three Google publisher products share concepts but not metric names, and borrowing a name across them fails with an unhelpful error.
Is the AdMob write integration available to everyone?: Yes — the admob.monetization scope completed Google's verification and was released to every organization on 18 September 2026. Google's own limited-access gate on the monetization methods still applies on top of that, and it is independent of us.