How to Verify Google Ads Consent Mode in Tag Assistant

Use Tag Assistant to verify that your Google tags receive the expected consent default and the update from a banner interaction. Then check the relevant website conversion action’s Google Ads Diagnostics: a completed implementation does not, by itself, mean conversion modeling is active. For a U.S. small-business advertiser or account operator, keeping those checks separate helps distinguish a tag or banner problem from a status delay or an impact-results eligibility issue.

What each check can tell you

Tag Assistant checks implementation behavior: whether consent parameters appear in the expected order and how tags fire or are blocked. Google’s Google Ads Help: Verify Consent Mode Implementation recommends checking consent events before and after interacting with the banner.

Google Ads Diagnostics checks account status: Google distinguishes “Consent mode is implemented” from “Consent mode is implemented and modeling is active.” The first status is not evidence that modeling is active, nor does either status alone prove that modeled conversions are being reported for a particular advertiser.

Impact results are a separate check: when available, they show modeled impact for a domain-by-country grouping. An absent result does not, by itself, prove the implementation is broken.

Verify the default, banner update, and tags

Run the test in Tag Assistant on a page where the consent banner and Google tags are present. Use a controlled interaction that reflects the test scenario and the choice made in the banner. Do not change a visitor’s choice or bypass your consent-management process.

Find the earliest Consent event. Inspect its API Call or On-page Default values. Check ad_storage, ad_personalization, ad_user_data, and analytics_storage. Compare the values with the default configured for this site and test scenario; there is no one default this guide can prescribe for every business or visitor.
Check the order. The expected sequence is for the default consent state to be set before measurement commands. Google’s Google Tag Platform: Set Up Consent Mode on Websites describes setting the default before measurement and updating consent based on the user’s interaction.
Interact with the banner. Make the choice that represents your controlled test. Then, before navigating away, inspect the most recent Consent event on that page. Check its API Call or On-page Update values and confirm the update reflects the interaction you made.
Review the Tags tab. Check which tags fired and which were blocked. Compare their behavior with the consent configuration and the test choice. The relevant behavior depends on the setup; do not assume every tag must fire or that one universal tag list applies.

If the default is missing, appears after measurement commands, or the update is absent or inconsistent with the interaction, investigate the banner and tag implementation first. Check that consent coverage and Google tags are present across the pages where they are needed. Google’s Google Ads Help: About Consent Mode Impact Results also recommends checking whether defaults or updates fire before Google tags and whether the Google tag is present throughout the site.

Read Google Ads Diagnostics separately

Open the relevant website conversion action and review its Diagnostics status. Account layouts and labels may change, so focus on the status associated with that conversion action rather than expecting every account to have an identical interface.

“Consent mode is implemented” is implementation status; it does not establish that modeling is active.
“Consent mode is implemented and modeling is active” is the distinct status to look for when assessing active modeling.

Google’s verification guidance gives a modeling threshold of 700 ad clicks over 7 days for a domain-by-country grouping. Check the grouping relevant to your traffic before treating a lack of active-modeling status as a configuration failure. Google says status may take 48 hours to appear and, in some instances, up to two weeks. If Tag Assistant shows the expected behavior, allow for that processing time before diagnosing the Ads status as a tag problem.

Hypothetical example: implementation complete, modeling not active

Hypothetical: Tag Assistant shows the configured default on the earliest Consent event, the expected update after a test banner interaction, and tag behavior consistent with that setup. The conversion action’s Diagnostics status says “Consent mode is implemented,” but not that modeling is active.

Those results do not conflict: Tag Assistant has shown evidence about implementation behavior, while Diagnostics has not confirmed active modeling. Check whether the relevant domain-by-country grouping meets Google’s documented 700-clicks-over-7-days threshold, and allow for the possible 48-hour-to-two-week status delay. If Tag Assistant instead shows a missing or mistimed default or update, investigate the implementation regardless of the account status.

Check impact results and their timing

If impact results are available, inspect the domain-by-country result and its modeling start date. Google says modeled impact uplift is shown for four weeks after modeling starts and refreshed weekly. Results may be absent because there is insufficient data, the reporting window has passed, or uplift is below the 1% display threshold.

So, a missing impact result is not enough to conclude that consent mode is broken. First consider the grouping, available data, modeling start date, reporting window, and display threshold. If implementation evidence is also unclear, return to Tag Assistant and check page coverage and the order of consent calls and Google tags.

Google explains that consent-related measurement gaps can arise when consent is denied and observable paths are lost. Modeled conversions may appear in the Conversions column and flow into downstream reports and bidding tools, but these documents do not establish the size or direction of a change for a specific advertiser. Do not use a missing impact table—or an implementation status alone—to infer how much reporting or bidding will change.

Verification checklist

Investigate implementation: The earliest Consent event lacks the expected configured default, the default comes after measurement commands, the banner interaction does not produce the expected update, or tag behavior does not match the setup. Check the relevant page and the page where the interaction occurs.
Wait for status processing: Tag Assistant shows the expected default, update, and tag behavior, but Google Ads has not yet shown the expected status. Check the domain-by-country grouping and allow up to two weeks for status to appear.
Assess modeling eligibility: Diagnostics says implementation is complete but modeling is not active. Check whether that grouping meets the documented 700 ad clicks over 7 days threshold; do not treat implementation completion as proof of active modeling.
Interpret missing impact results: Check the modeling start date, weekly refresh, four-week display period, data sufficiency, and 1% display threshold before treating an absent result as an implementation defect.

When you troubleshoot, keep the evidence from Tag Assistant, Diagnostics, and impact results distinct. That makes it easier to identify whether the next step is fixing consent timing or page coverage, allowing Ads status to process, or checking impact-result eligibility and timing.

Which of these checks helped you identify the source of a Consent Mode discrepancy? Share the step that clarified it, without posting 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.