Google Ads Consent Mode: Check Whether Tags Are Blocked

A blocked Google Ads tag is not automatically broken. Check whether it behaves as intended for your site’s consent mode: in basic consent mode, blocking tags until a visitor interacts with the banner is expected; in advanced consent mode, Google tags load with the default consent state. This walkthrough is for marketers and site operators diagnosing website conversion tracking. Confirm your intended implementation and applicable requirements before changing a consent or blocking rule.

What a blocked tag can mean

Google’s Consent mode overview describes two different behaviors. In basic consent mode, Google tags are blocked until the visitor interacts with the banner. If the visitor does not consent, no consent status is transmitted, and Google Ads uses a general model for conversion modeling. In advanced consent mode, tags load with the defaults; when consent is denied, they can send consent state and measurements without cookies. Google describes modeling for this mode as advertiser-specific.

Those differences matter when interpreting Tag Assistant. A tag that does not fire before a choice may be consistent with basic mode, rather than evidence of a defect. Conversely, a tag that stays blocked after a visitor makes a choice may warrant investigation if that choice should allow it to fire under your chosen setup.

Google Ads Help says blocked tags cannot send information, and delayed or blocked tags can make modeled conversions less accurate. Missing signals can limit information available for measurement and bidding systems, but one browser test cannot establish a measurable change to your account’s reported conversions or bidding performance.

Test consent and the conversion tag in Tag Assistant

Start a fresh Tag Assistant session. Connect to the site and reproduce the page and conversion path you want to check. Confirm that you can test the banner state you intend to inspect; a previously saved choice may affect whether the banner appears.
Inspect the earliest Consent event. Before interacting with the banner, open the earliest Consent event and review its default parameters. Check that the defaults are present before relevant tags fire. The expected values depend on your implementation and requirements; this test does not determine what those values should be.
Make a banner choice. Choose the consent option you need to test. In Tag Assistant, inspect the later Consent event or the On-page Update column to see whether the consent state changed as intended.
Check the Google Ads conversion tag. In the Tags view, review Tags Fired and Tags Not Fired for the expected conversion tag. Compare its behavior with your intended setup. For example, blocking before a choice can be expected in basic mode; advanced mode loads tags with defaults, including when consent is denied.
Repeat relevant cases. Test other banner choices and any region-specific configurations relevant to your site. A Tag Assistant session verifies only the conditions you tested; it does not establish that every region, browser, page template, visitor, or CMP state behaves the same way.

Google’s Tag Assistant troubleshooting guide describes how to inspect consent events, updates, and tag behavior. Basic verification evidence is: defaults appear before tags fire; the banner interaction produces the intended consent update; and each relevant tag fires or remains blocked in a way that matches the site’s chosen implementation.

Trace a tag that did not fire

First open the tag’s details in Tag Assistant. Then check the configuration layers that can prevent it from firing:

Tag Manager consent conditions: Review consent-based trigger conditions and any Required Additional Consent on the Google tag.
Exception triggers: Check whether an exception trigger prevents the tag from firing.
Your CMP: Review whether the consent management platform is blocking the tag or changing its behavior.
Timing of defaults: Check whether consent defaults arrive before tags fire. Defaults set too late can cause unexpected behavior.

Google Ads’ troubleshooting guidance lists exception triggers, additional consent checks, CMP blocking, and late consent defaults among possible causes of blocked Google tags. Check each tagging method and the CMP configuration that applies to it. Do not remove a restriction or consent check just to make a tag fire: first confirm its purpose and whether changing it fits the site’s intended implementation and applicable requirements.

Hypothetical example: the visitor accepts, but the tag stays blocked

A visitor accepts through the banner. Tag Assistant shows the expected consent update, but the Google Ads conversion tag appears under Tags Not Fired. The update shows that a consent change is visible in the tested session; it does not prove every separate firing condition is satisfied.

Open the tag details, then inspect its Tag Manager trigger, exception triggers, and Required Additional Consent. If the tag has an additional consent requirement, compare that requirement with the state shown in Tag Assistant. Also check whether the CMP applies another block. This can help locate the discrepancy without assuming the extra check should be removed. The appropriate configuration depends on the site’s intended consent behavior and requirements.

Check Google Ads diagnostics separately

Tag Assistant checks browser behavior. Google Ads conversion diagnostics provide a separate, account-level view. Google Ads Help distinguishes “Consent mode is implemented” from “Consent mode is implemented and modeling is active.” A working Tag Assistant test does not, by itself, establish that modeling is active.

Google states that active consent mode status may take 48 hours to appear in Ads and, in some instances, up to two weeks. So a missing status immediately after a successful test does not prove the setup is broken. Google’s help page also describes a modeling threshold of 700 ad clicks over 7 days per domain-country grouping. Treat that as Google’s stated threshold in this diagnostic context—not a universal eligibility rule or a promise that modeling will activate once it is met.

Verification checklist

Record the default consent parameters in the earliest Consent event, before tags fire.
Make a banner choice and confirm the later Consent event or On-page Update shows the intended change.
Check the expected Google Ads conversion tag under Tags Fired or Tags Not Fired.
If it did not fire unexpectedly, inspect its Tag Assistant details, Tag Manager consent conditions, exception triggers, Required Additional Consent, CMP blocking, and default timing.
Decide whether blocking matches the site’s intended basic or advanced setup before changing any control.
Test relevant choices and regional configurations separately, then check Google Ads conversion diagnostics and allow for its documented reporting delay.

Which part of your consent-to-conversion test is hardest to verify: the banner update, the Tag Manager checks, or the Ads diagnostics? Share the issue without including account or visitor data.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.