Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Google Consent Mode v2: Implement, Audit and Fix for Google Ads and GA4

    1

    Set up or repair Google Consent Mode v2 in gtag.js or Tag Manager so Ads and GA4 respect consent and stay eligible for modeling.

    $3

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Google Consent Mode v2: Implement, Audit and Fix for Google Ads and GA4

    Google Consent Mode v2: Implement, Audit and Fix for Google Ads and GA4

    Example session with this skill installed

    Our Laravel shop uses GTM with a custom cookie banner. Since we launched it, Google Ads conversions in Germany and France dropped. Audit our consent setup and fix it.

    • Read your context and instructions
    • Compiled the google consent mode

    A Consent Mode v2 audit report with verdict FIX NEEDED: the default is set inside an async banner callback after GTM loads (Critical), ad_user_data and ad_personalization are missing (Critical), and stored choices are not re-applied on later pages (High). Includes a GTM template using setDefaultConsentState on Consent Initialization, a purpose-to-consent mapping table, a region defaults table with full EEA/UK/CH codes, and a Tag Assistant verification log.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Consent Mode tells Google tags what each visitor has agreed to, so tags can adjust storage and data use instead of either ignoring consent or losing all measurement. Most broken setups fail in a few predictable ways: the default command runs too late, one of the two v2 parameters (ad_user_data, ad_personalization) is missing, the banner's choice never reaches update, or tags are hard-blocked so Google cannot model. This skill walks an agent through choosing the right mode, writing a correct implementation for plain gtag.js or Google Tag Manager, verifying it with Tag Assistant, and producing a clear audit report. It is technical guidance, not legal advice: the site owner and their counsel decide which consent the law requires.

    • A site serves Google Ads, GA4, Floodlight or other Google tags to visitors in the EEA, the UK or Switzerland (Google's EU user consent policy region), or anywhere the owner wants consent-aware measurement.
    • A consent banner or CMP is being added, replaced or connected to Google tags.
    • Conversions, remarketing audiences or GA4 users dropped after a banner went live.
    • Tag Assistant shows an empty Consent tab or "default consent set too late".
    • The team needs to prepare for GA4 using Consent Mode as the single Ads data control (from 15 June 2026).

    Do not use this skill to design the banner's legal wording or decide which purposes need consent; hand that to the site's privacy owner.

    InputWhy it matters
    Tag stack: gtag.js only, GTM web container, or bothDecides syntax: gtag('consent', ...) vs GTM consent APIs
    CMP or banner in use (vendor or custom) and whether it has a native Google integrationNative integrations already call default/update; do not duplicate them
    Google products in use: Google Ads, GA4, Floodlight, AdSense/Ad ManagerPublisher products have extra CMP rules (see reference/policy-and-modeling.md)
    Regions served and whether defaults should differ by regionDrives the region parameter
    Desired mode: basic or advancedChanges when tags load and whether modeling is possible
    Page templates or the GTM container exportNeeded to check load order

    Technical implementation guidance only, not legal advice: it does not write banner wording or decide which purposes need consent. It does not provide a consent banner or CMP. The offline checker cannot see defaults set by a remotely loaded CMP; use Tag Assistant for those. Google thresholds and dates reflect Google documentation as of October 2026.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    Permissions

    File Scopes

    Saved
    HTML
    pages
    or
    GTM
    container
    exports
    the
    user
    provides

    The bundled script reads only the files passed to it and makes no network requests.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    Set up or repair Google Consent Mode v2 in gtag.js or Tag Manager so Ads and GA4 respect consent and stay eligible for modeling.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Google Consent Mode v2: Implement, Audit and Fix for Google Ads and GA4 on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in E-commerce