What Google actually said
On 20 August 2026 Google announced that standalone Google tags will be upgraded into fully capable Tag Manager containers. The interface comes with it, along with debugging and version control. Google states that the update will not change the in-page behavior of the Google tags, that adoption is optional, and that nothing changes automatically.
All of that is accurate and, on its own, fairly boring. The source is Google's Tag Manager announcement of 20 August 2026, and it is worth reading directly. Google edits these articles in place.
The line that matters
Further down: new deployment snippets exclude the gtag config command, and Google recommends configuring initialization via the gtm.init trigger.
That is the whole piece.
Why order of operations is the story
A consent default is a before-anything-else instruction. It says: until you hear otherwise, assume this state. It only does its job if it is already in place when the first tag looks.
A trigger is a when-this-happens instruction. It says: at this point in the sequence, run this.
Those are not the same shape. Moving a piece of setup from a snippet that runs inline into something that runs on a trigger is a change in when it lands relative to everything else, and consent defaults are unusually sensitive to that.
The failure mode, as a sequence rather than an error
Picture what it looks like if a default arrives late.
- The container loads.
- A tag fires.
- It has no consent state to read, so it proceeds on whatever the implicit assumption is.
- Data arrives in the reporting platform.
- The dashboard looks completely normal.
Nothing errors. A tag that fires before its default is known does not fail. It succeeds, quietly, on an assumption nobody made deliberately, and there is no surface anywhere that records which assumption it was.
The base this is being offered to
Our Website Privacy Index scanned 47,505 public websites and scored 47,419, January to September 2026. Of those, 23,307 (49.2%) ran Google tags with no Consent Mode signal at all, against 2,108 (4.4%) showing a working Consent Mode v2 signal.
Not a broken signal. No signal. That is the state roughly half this sample is already in before anybody migrates anything.
Who does optional migrations
This is the part worth being honest about, and it is nobody's fault.
Optional work goes to whoever has capacity. It does not go to whoever understands the consent wiring, because optional work is not scoped that carefully. The person who clicks upgrade is usually the person who had a quiet Thursday, and the consent default is not in the upgrade dialog.
Three things before anyone clicks upgrade
- Capture the current consent default state in preview mode first. Not from documentation, from the actual page. You need a before that somebody recorded, for the same reason we argued in the change log piece.
- Identify who owns the gtag config command on the site today. It may be in a template, in a theme, in a plugin, or pasted into a CMS field by somebody who left. If nobody can say, that answer is the finding.
- Decide the rollback, and confirm somebody has used container version history under pressure at least once. A rollback path nobody has exercised is a plan, not a capability.
Why September is cheaper than November
Because it is optional, you get to pick the week. Most organizations run some form of change freeze from late in the year, and a migration deferred into a freeze usually gets done in a hurry afterward by whoever is around.
An optional change is a rare gift in vendor land. Spending it on a quiet week is the whole advantage.
One thing this piece is deliberately not about
The same announcement introduces Visual Tagging. That deserves its own treatment, because it interacts with conversion counting rather than with consent, and folding it in here would dilute both. It is covered in the piece on counting the same order twice.
Who would notice
When your container version changes, who sees it, and could anybody say which settings moved? The earlier stage of this staged rollout is covered in our piece on the Google tag migration, and the publish habit that catches it in the default workspace piece.
A consent gate can stop holding on any publish, which is the argument for watching it continuously rather than auditing it once. That is what Managed Privacy does. For a single review of the whole tag layer, book a data and tracking audit.
Not legal advice. Rawsoft determines what a system technically does: which tags fire, when, under what consent state, and what data is transmitted. We do not determine which laws apply to your organization, how a regulator would read them, or whether your organization is in compliance. Those are determinations for your counsel. Everything above describes behavior an automated scan observed on public pages at the time of the scan, and nothing in it is a legal conclusion about any site.