Google Ad Manager MCM, explained for publishers
MCM — Multiple Customer Management — is the Google Ad Manager feature that lets an approved network monetize other publishers' sites inside its own Ad Manager account, while keeping each publisher's revenue and reporting separate. It's the mechanism that powers most managed Google Ad Manager networks, including pubads.io. This guide explains how it works and what to look for in an MCM partner.
What MCM is
Multiple Customer Management (MCM) is a Google Ad Manager program that lets a vetted "parent" publisher represent the inventory of other "child" publishers. Before MCM, a network that wanted to monetize many sites through Google's premium AdX demand faced heavy operational and approval overhead. MCM formalized the relationship: Google approves the parent network, the parent onboards child sites, and Google's systems keep each child's impressions and earnings attributed correctly. For you as a publisher, MCM is what makes it possible to earn from Google Ad Manager demand without running your own Ad Manager instance.
The key idea is delegation: the child publisher authorizes the parent network to sell their inventory, but how much access that grants depends on the delegation type.
Manage Account vs Manage Inventory
MCM offers two delegation types, and the difference matters a great deal for account safety. They describe how much of your setup the parent network touches.
| Delegation type | What the parent can do | Do you need your own Ad Manager account? | Typical use |
|---|---|---|---|
| Manage Account | Operates within the child's own Google Ad Manager account on their behalf | Yes — you have an account the parent helps run | Publishers who already have Ad Manager and want hands-on help |
| Manage Inventory | Represents the child's inventory inside the parent's own network | No — your site runs in the parent's account | Publishers who want Google demand without owning Ad Manager |
Manage Inventory is the lighter, safer model for most publishers. Your site is monetized inside the parent's Ad Manager network, so there is no separate account of yours for anyone to take over — and nothing for you to set up. pubads.io uses Manage Inventory delegation, which is why joining requires nothing more than one ads.txt line and approval, not a full Ad Manager onboarding.
How a child site gets into a parent network
Getting your site into an MCM network is a short, well-defined sequence. The parent handles the Google-side mechanics; your part is mostly the ads.txt line and the wait for review.
- You authorize the network. You add a single line to your site's ads.txt that names the parent's Google Ad Manager account as authorized to sell your inventory.
- The parent adds your site. The network registers your domain as a child in its Ad Manager network under the chosen delegation type.
- Google reviews the site. Google checks your site against its publisher policies — content, ad placements, and traffic quality.
- You go live. Once approved, you add the ad units / tags the network provides, and Google's demand starts serving ads on your pages.
The ads.txt line that authorizes MCM
The ads.txt line is the public record that proves the parent network is allowed to sell your inventory. It tells advertisers and Google that impressions sold under that account are legitimate. A Google Ad Manager MCM authorization line follows the standard ads.txt format:
google.com, pub-XXXXXXXXXXXXXXXX, RESELLER, f08c47fec0942fa0
Reading it left to right: google.com is the ad system, pub-XXXX… is the parent network's publisher ID, RESELLER indicates the inventory is sold by an authorized third party (the network) rather than the site owner directly, and f08c47fec0942fa0 is Google's certification authority ID. Your network gives you the exact line; you paste it verbatim. For a full breakdown of the format, see our ads.txt guide.
Approval and the Google review timeline
The approval timeline is driven by Google's policy review, not the network's paperwork, so it can vary. After your ads.txt line is live and the parent submits your site, Google review commonly takes anywhere from a few days to about two weeks. Factors that speed it up include original content, clean ad placements, a correctly formatted ads.txt, and a site with genuine human traffic. Factors that slow it down or cause rejection include thin or scraped content, policy-violating material, or invalid-traffic signals. A good partner pre-screens your site before submitting so you don't burn a review cycle on an avoidable issue.
What to look for in an MCM partner
Because an MCM partner sits between you and Google's demand, the partner you choose determines both your earnings and your account safety. Evaluate them on these points:
- Delegation transparency. They should tell you plainly whether they use Manage Account or Manage Inventory. Manage Inventory means you never hand over an account.
- Invalid-traffic protection. They should filter IVT before it reaches Google, protecting network-wide account health and your fill. See our trust layer.
- Reporting transparency. You should see your own impressions, eCPM, RPM, and revenue, reconciled against Google's source reporting — not a black-box number.
- Honest revenue share & payouts. A disclosed split (pubads is 85%), a clear payout schedule, and multiple payout methods. See revenue share and payouts.
- Pre-submission review. They check your site against Google policy before submitting, reducing rejections and delays.
How pubads.io fits
pubads.io is a managed Google Ad Manager network built on MCM Manage Inventory delegation. In practice that means you get Google's AdX demand and reporting without owning an Ad Manager account, without a traffic minimum, and without ad operations. You add one ads.txt line to authorize us, we run your site against Google policy and submit it to our network, and once Google approves it you paste the ad-unit tags we generate. From there Google serves the ads and your revenue lands in one normalized ledger at an 85% publisher share. Read the full flow on how it works.