Weight & build
Maximum number of HTTP calls exceeded
- Published limit
- 100 HTTP/HTTPS fourth-party calls
What Google's rule says
Google's stated rule is that the ad makes more than 100 HTTP/HTTPS (fourth-party) calls. Authorized Buyers words the same reason as the number of calls exceeding 100.
What actually causes it
- Several measurement vendors stacked on one creative, each firing its own beacons.
- Identity or cookie-sync pixels bundled into the creative rather than handled at the page level.
- A dynamic creative pulling a feed item, its images and its fonts as separate requests.
- Retry logic that re-fires a failing call rather than giving up on it.
How to fix it
Count the requests the creative itself initiates after it has loaded, and separate them by host. Whichever host appears most often is the one to renegotiate — cutting a vendor with forty beacons buys far more headroom than optimising your own assets.
The part that is not obvious
The word doing the work here is fourth-party. Google is not counting the publisher's requests or the ad server's; it is counting what the creative reaches out for on its own once it is running. That distinction is why the number looks impossibly generous until you realise a single verification vendor can spend a quarter of the budget by itself, and why the fix is nearly always a conversation with a vendor rather than an edit to the creative.
Related reasons
Reason name, threshold verified against Common ad disapproval reasons — Authorized Buyers Help on 30 July 2026. The causes and fix above are practitioner guidance, not Google policy text.