Connect AdSense / Ad Manager to SiteOps
For an ad-supported publisher, traffic isn't the goal — it's the raw material. The business is the money that traffic earns, measured in page RPM and total earnings. Without a read on AdSense or Ad Manager, SiteOps could show The Dispatch its visits climbing while the one number that pays the bills stayed completely invisible.
Connecting AdSense or Google Ad Manager puts that number on the page. Earnings and page RPM land next to your traffic, read-only, so a spike in visits and a spike in revenue can finally be read in the same glance — and a traffic win that didn't earn is something you notice instead of celebrate.
It reads your earnings reports and nothing else. SiteOps never changes an ad unit, blocks a category, or touches a payment. Disconnect and the reads stop the same minute.
Set it up, step by step
0 of 4 done
- AdSense
- Sites
- Settings
- Connections
- AdSense / Ad Manager
One consent screen — read-only earnings, nothing more
If something does not work
- Earnings show as zero or blank
- Usually the account you approved doesn't own this property, or the site's ad units are new and haven't earned in the period shown. Confirm the property under the account you connected, and widen the date range if the site is fresh.
- The number differs from my AdSense dashboard
- AdSense finalizes earnings over a few days, and SiteOps reads on a short delay — recent days are estimates that settle. Compare a closed period (last month) rather than today, and the numbers line up.
- Can SiteOps change my ad setup?
- No — deliberately. The consent is read-only; there is no scope and no code path that edits an ad unit, a block or a payment setting. Your ad configuration stays entirely yours.
- I use Ad Manager, not AdSense — does it still work?
- Yes. The same connector reads Google Ad Manager earnings and RPM. Pick the network the account owns during connect; the numbers land the same way.