Click & destination
Abusive experience
- Ad Manager API value
- ABUSIVE_EXPERIENCE
What Google's rule says
The Ad Manager API defines ABUSIVE_EXPERIENCE as the landing page containing an abusive experience. Google's own definition of an abusive experience is one designed to mislead visitors — auto-redirects that move a visitor without any action on their part, and ads designed to trick users into interacting with them.
What actually causes it
- A landing page that redirects on arrival without any user action.
- Fake system warnings, fake close buttons or fake play buttons on the destination site.
- Pop-ups and interstitials that disable browser navigation or trap the back button.
- Something on an unrelated part of the destination site — the status is assessed for the site, not the page you booked.
How to fix it
Check the destination site's status in the Abusive Experience Report in Search Console, not just the campaign landing page. If the site is Failing, the fix belongs to whoever owns the site, and a creative change will not clear it.
The part that is not obvious
This is the only common disapproval reason whose consequences reach past advertising entirely. The status is assessed per site in the Abusive Experience Report, and Google documents that Chrome prevents new windows and tabs from opening on a Failing site, and removes all ads on sites that have been Failing for more than thirty days. So the disapproval is the small half of the problem: the same finding is quietly costing the destination site its own Chrome behaviour and its own ad revenue. Review requests are also rate-limited — two without delay, then a thirty-day wait before a third.
Related reasons
Reason name and API value verified against Chrome enforcement — Abusive Experience Report, Web Tools Help on 30 July 2026 (Ad Manager SOAP API v202602). The causes and fix above are practitioner guidance, not Google policy text.