Google Ads cloaking enforcement scope: ad, campaign, account, manager account and payments profile

Why scope matters more on Google than on other platforms

On most social platforms, enforcement for destination issues is concentrated in two places: the ad and the ad account. Google Ads is different in two ways. First, its policy framework distinguishes between ordinary violations, which follow a warning-and-strike pattern, and a small set of egregious violations, which lead to suspension without prior warning. Circumventing systems — the policy under which cloaking, sneaky redirects and showing different content to Google's systems than to users are listed — is in the second set. Second, Google's account suspension help states plainly that when an account is suspended, related accounts may also be suspended, and that any new accounts created to continue advertising after the suspension can be suspended too. What counts as "related" is where manager accounts and payments profiles enter the picture.

Taken together, these mean a destination-related finding on Google can have a far wider blast radius than the same finding elsewhere, and that radius is defined by account relationships the advertiser may not think of as part of "the landing page". Why Google Ads accounts get suspended covers the suspension event itself; here the subject is the structure around it.

The five layers of Google Ads enforcement

The table summarises each layer, what typically triggers action there, what is affected and what the notice looks like. Google does not publish a single document that describes these as "layers"; the structure below is assembled from the destination requirements, the circumventing systems policy, the account suspension help and the manager account policy.

How a cloaking-related finding travels between layers

The ad layer is where destination findings usually begin. Google's systems fetch the final URL, compare what they receive with what users receive, and compare both with the ad. A mismatch — a page that differs materially from the ad, a destination that does not load from the crawler's location, a redirect to a different domain — produces a disapproval under the destination requirements. That is the fixable outcome: correct the page, request review, resume serving. What Google compares when it checks a destination goes into those signals in detail.

The jump to the account layer happens when the same evidence is read as deliberate. The circumventing systems policy lists the behaviours that trigger that reading: showing different content to Google's systems than to users, redirecting users to a different page after review, using dynamic DNS or similar techniques to switch content, and creating variations of ads, domains or accounts after a violation. None of these require a large difference between pages. They require a pattern that looks like an attempt to control what the review sees. Once a finding is categorised that way, there is no strike and no warning; the account is suspended.

From the account layer upward, propagation is relational rather than evidential. Google does not re-examine the landing page for each related account; it identifies relationships through signals that are not fully published but include shared payment methods, shared administrative users, shared domains or conversion tracking, and manager-account links. Accounts that match may be suspended on the basis of the relationship alone. This is the part of the chain that surprises advertisers most: a finding about one landing page on one account ends up affecting accounts that never served that ad.

What this means for manager accounts and routing vendors

Manager accounts exist so that agencies and larger advertisers can run many accounts from one place. They are also a relationship Google can see. The practical consequence is shared exposure in both directions. If an advertiser's account is suspended for circumventing systems while linked under an agency's manager account, the agency's structure now carries a related-account signal. If another client of the same agency is suspended, the advertiser's account sits in a structure that has a suspension in it. Neither case guarantees action, but both widen the surface that a single finding can touch.

This changes what to ask a Google Ads routing vendor, beyond the general questions in vendor evaluation platform by platform. Whose name is the ad account in? Whose payments profile funds it? Is the vendor linked as a manager with access that can be removed, or does the account live inside the vendor's structure? Does the vendor run other clients from the same manager account, and in which categories? A vendor who cannot answer these in writing is asking the advertiser to accept an exposure it cannot measure.

• The ad account, payments profile and domain are registered to the advertiser, not the vendor.
• The vendor is linked as a manager with role-limited access, and the link can be removed without losing history.
• Conversion tracking and audiences live in the advertiser's account or in a Google tag the advertiser controls.
• The vendor states, in writing, which other accounts share its manager structure and payment arrangements.
• Per-visit records for the destination are exportable and reconcilable with Google Ads reporting.

Keeping enforcement at the ad layer: a compliance-first checklist

The only durable way to limit scope is to make sure that whatever Google finds stays a destination disapproval rather than a circumventing systems finding. That is a question of behaviour, not of tooling.

• One destination for everyone. Google's systems, users in the targeted regions and users elsewhere receive the same page at the same URL. Personalisation by language, device or region is fine when it stays inside one page and does not change the offer or the product; cloaking versus compliant personalisation draws that line.
• Working pages from every location. A page that returns an error or a blank state to the crawler's location is a destination finding waiting to happen.
• Display path, final URL and tracking template point at the same domain and do not change after approval; see display path and final URL rules.
• No post-approval switch. Changing the destination after review, by DNS, by rule or by hand, is the behaviour the policy names.
• Per-visit records that show what each arrival was served and why, so a question from Google or from a payments review can be answered with evidence rather than assertion.

An advertiser who can show that every visitor got the same page has an ad-layer problem at worst. An advertiser who cannot has handed the categorisation over to inference.

Misreadings that do the most damage

• "A disapproval is the first warning." It is, for ordinary policies. For circumventing systems there is no first warning.
• "The payments profile is a billing detail." It is one of the signals Google uses to relate accounts.
• "A new account starts clean." Creating accounts to continue after a suspension is a listed form of circumventing systems. It is the fastest way to extend scope rather than reset it.
• "A manager link is just a permission." It is a relationship visible to Google and, in both directions, a channel for related-account signals.
• "If the mismatch is small, it is only a disapproval." Categorisation depends on whether the pattern looks deliberate, not on the size of the difference.

What these misreadings share is the assumption that Google's enforcement looks only at the page. It looks at the page plus the relationships between accounts. Every item on the red lines is the kind of pattern that pushes a finding from the ad layer to the account layer.

Frequently asked questions