How to Make Every Tag Manager Tag Wait for Consent

A Google Tag Manager tag fires on its trigger whatever the cookie banner says, until the container requires consent for it. Every tag starts on "Not set", which Google says performs no additional consent checks. Google Tag Manager is named in 63 website tracking complaints in the 12 months to September 26, 2026. Three settings make Meta, TikTok and LinkedIn tags wait.

What Google Tag Manager does before a visitor chooses

Google Tag Manager is a container: one script, gtm.js, that loads on every page and then fires the tags inside it when their triggers match. A tag on the All Pages trigger fires as soon as the page view registers, which on a first visit is before anyone has read the banner.

Google's Tag Manager help center describes three consent states for a tag, under Advanced Settings, Consent Settings, Additional Consent Checks:

• Not set, the default: "No additional consent checks are performed by this tag."
• No additional consent required: the tag was reviewed and needs no check.
• Require additional consent for tag to fire: the tag fires only if every consent type listed is granted when it is triggered.

Google's own Google Ads, Google Analytics and Floodlight tags also carry built-in consent checks, logic that changes what the tag sends when consent is denied. A Meta Pixel, TikTok Pixel or LinkedIn Insight Tag added as a custom HTML tag has no such logic, and a community template has it only if its author built it in. On "Not set" such a tag fires on its trigger, whether or not the site's banner has been answered.

That is the pattern a website tracking complaint describes: requests to an ad network leaving the browser before the visitor chose. Suitcast's free scan records it with the second each request fired, and names the script it came from.

Why website tracking complaints name Google Tag Manager

Website tracking complaints rest on the California Invasion of Privacy Act, CIPA. Penal Code section 631(a) reaches anyone who, "willfully and without the consent of all parties to the communication", reads or attempts to learn the contents of a communication in transit. Section 638.51 bars installing or using a pen register without a court order, and section 638.50 defines one as a device or process that records routing and addressing information, "but not the contents of a communication". Section 637.2 allows the greater of five thousand dollars per violation or three times actual damages, and says a plaintiff need not have suffered actual damages. All four were read on leginfo.legislature.ca.gov on September 26, 2026.

On Suitcast's tracker catalog, in the 12 months to September 26, 2026, the Google Tag Manager page counts 63 verified complaints naming the container, with medical and health providers the industry sued most among them. The pixels a container can load are named more often: the Meta Pixel in 138, the TikTok Pixel in 116 and the LinkedIn Insight Tag in 87. When those pixels are loaded through a container, it is also the one place where all of them can be held.

Senate Bill 690, as enrolled, would let only the Attorney General sue over section 638.51 claims arising from a website or app, and leaves section 631 claims as they are. It was presented to the Governor on September 4, 2026, and leginfo showed no later action on September 26. Check its status again before relying on it.

The three settings that hold a tag

Google Tag Manager has three pieces that work together, all documented on the same help page:

1. The Consent Initialization trigger. Every web container has a "Consent Initialization - All Pages" trigger by default, and Google says it "will always fire before all other tags". It is for the banner's own tag, the one that sets the consent state, and nothing else.
2. The tag's consent setting. In each tag, open Advanced Settings, Consent Settings, choose "Require additional consent for tag to fire", and add the consent type the tag needs: ad_storage for advertising pixels, analytics_storage for analytics and session replay tags.
3. The Consent Overview. In Admin, Container Settings, under Additional Settings, select "Enable consent overview". The Tags list then shows a Consent Overview icon, and the page it opens lists every tag still in the "not set" state under Consent Not Configured. Select several tags, edit their consent settings together, and publish.

The banner itself usually arrives as a template. Google's help center lists more than thirty consent management platforms whose Tag Manager templates work with these settings, among them Complianz and CookieYes, which also run on WordPress, and Cookiebot, OneTrust, Osano and Termly.

A dental practice whose agency added a LinkedIn Insight Tag and a Meta Pixel to the container a year ago is the usual case. Neither tag was wrong when it was added. Both were simply left on "Not set", and the Consent Overview lists them in one screen.

A default of denied comes first

A consent requirement is only as good as the consent state it reads. Google's developer documentation for tag templates says a consent type is considered granted "if the consent type has been set to 'granted' or not set at all". A container where nothing sets a default has nothing for the check to hold on.

So the banner's template, on the Consent Initialization trigger, has to set every type the tags require to denied before anything else fires, and update them when the visitor accepts. The same documentation says any value other than granted is treated as denied. A banner template does this when its default is configured; check that the default for ad_storage and analytics_storage is denied for United States visitors, because a template can be set to apply its defaults in some regions only.

The second trap is timing. Google's wording is that the tag fires only if every listed type is granted "when the tag is triggered". A Meta tag on the All Pages trigger, blocked on page load, is not sent for that page when the visitor accepts a few seconds later. When that page view matters, give the tag a second trigger that runs after the choice: a Custom Event trigger on the event name the banner template pushes to the data layer when consent changes. The template's documentation names it.

Tags in a container compared

Each kind of tag behaves differently until its consent setting is changed. The table follows Google's Tag Manager help center as read on September 26, 2026.

Read it from the top. Without the first row nothing below it holds, whatever each tag says. Google's own tags differ from the rest: in advanced consent mode they still load and send cookieless pings with consent denied, which the Google Analytics 4 guide compares with basic mode. Every other tag is on "Not set" until someone changes it, and the session replay guide covers the vendor settings for Clarity and Hotjar that sit alongside the container.

How to check whether the container holds

A published container is the only version that counts, so test the live site after publishing, not the preview:

1. Open a page in a private window with the network panel recording.
2. Do not touch the banner. Filter the requests by facebook, tiktok and licdn in turn. Any request to connect.facebook.net, analytics.tiktok.com or snap.licdn.com came from a tag that did not wait.
3. Click reject, reload, and filter again. A request that still appears ignores the choice.
4. Click accept on a fresh private window and confirm the tags now fire, so the trigger after the choice works.
5. Fix the tags the test caught in the Consent Overview, publish, and repeat.

A request to www.googletagmanager.com/gtm.js will still be there in step 2. That is the container itself, which has to load for its Consent Initialization trigger to run. What the settings change is whether the requests to the ad networks follow it.

The card below comes from a Suitcast report on a reserved example address: a law firm site where the LinkedIn Insight Tag, left on "Not set" in the container, fired on three pages before any choice and kept firing after reject on the contact page.

The scan logs every request from the moment a page starts loading until the network goes quiet or 8 seconds pass, without clicking anything, and matches each one against the 43 scripts in its catalog, Google Tag Manager among them, rated medium. It then presses reject when a banner offers it, never accept, and watches 3 more seconds. The methodology page sets out the rules, and the scanner policy says how SuitcastBot identifies itself.

Keeping the container held after the next publish

A container changes more often than the site around it. An agency adds a conversion tag for a new campaign, a marketing hire imports a template from a vendor, or a workspace from last year is published over this one. Each new tag starts on "Not set", and one publish puts a request to an ad network back in front of the banner without anyone opening the network panel.

A free scan is one dated snapshot of 5 pages. Suitcast's Monitor plan scans up to 100 pages every week, keeps every report with its PDF, and sends a weekly email naming the scripts that are new since the last scan, the fixes that did not hold, and the new filings that match the site by state, industry or script. It costs $39 a month or $390 a year, less than one hour of a privacy lawyer's time. A dental practice whose agency manages the container, or a Shopify store that runs its pixels through Tag Manager, sees the week a new tag started firing early. An agency covers five client containers on Pro for $79 a month or $790 a year, with its own name on each PDF, which the agency guide describes. The pricing page compares the plans.

Limitations

This guide quotes California Penal Code sections 631, 637.2, 638.50 and 638.51 and the enrolled text of Senate Bill 690 as published on leginfo.legislature.ca.gov, and Google's Tag Manager help center and tag template documentation, all read on September 26, 2026. Google changes the Tag Manager interface and its documentation without notice. Whether a given container setup breaks CIPA is a question for a lawyer and a court, not a scan. Nothing here is legal advice; the not legal advice page says what a score and a count mean.

A scan sees only what leaves a visitor's browser. A server-side Tag Manager container forwards events to ad networks from a server, and those requests are invisible to it. The complaint counts are verified federal filings plus state filings with a public source, and a case is linked to a script only when its complaint text names it, so 63 is a floor; the dataset explains how cases are counted.