container audit
GTM-MVC64CR
180 tags, 21 custom scripts, 10 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 21 custom HTML tags carrying 30 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 10 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
- 447 published versions — each one live for every visitor the moment it was published.
duplicate-ads-conversionis uncommon — under 4% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags180
Custom scripts21
Third parties10
Delivered671 KB
Versions447
What we observed
A real browser loaded devon.gov.uk 2 months ago and recorded every request it made. This is what happened, as distinct from what the container is configured to do. It is one page load — anything that fires only deeper in the site did not fire here.
Container loaded from
googletagmanager.com — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
a consent banner was present and we accepted it. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 3 fired afterwards. That is the outcome consent is meant to produce. 7 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
11 hosts — www.googletagmanager.com, cc.cdn.civiccomputing.com, analytics.ahrefs.com, apikeys.civiccomputing.com, static.hotjar.com, signup.es-mail.co.uk, clapi.civiccomputing.com, rest-api.e-shot.net, and 3 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.click, gtm.triggerGroup
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on devon.gov.uk More info »
Findings
Ordered by consequence. review has a concrete cost when it bites; info is real but depends on your setup. Seen is how common it is across the containers we have measured — reported separately on purpose, because common and harmless are different claims.
reviewUniversal Analytics tags still shipped (20)
20 Universal Analytics tags are still in the container.
WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.
CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.
Seenseen in 23.2% of 46,522 containers measured
reviewHardcoded http:// URL (1)
1 piece of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% of 46,522 containers measured
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% of 46,522 containers measured
reviewWrites cookies directly (1)
1 piece of custom code set cookies in code.
WhyCookies set this way bypass GTM's consent settings, because the consent checks live in the tag templates rather than in raw JavaScript.
CheckIf any of these cookies are used for analytics or advertising, confirm they are still gated on a consent decision.
Seenseen in 21.2% of 46,522 containers measured
reviewSame GA4 property configured more than once (1)
G-ZMKT1MK7M5 is configured by 2 separate tags.
WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.
CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.
Seenseen in 4.8% of 46,522 containers measured
reviewSame Google Ads conversion defined more than once (1)
1 conversion action is defined by more than one tag.
WhyA conversion ID plus label identifies one action. Two tags carrying the same pair can report the same conversion twice, inflating conversion counts and the ROAS that bidding runs on.
CheckCheck whether both tags can fire on the same page. If they can, your Ads reporting is overstating this action and automated bidding is optimising against it.
Seenseen in 3.8% of 46,522 containers measured
infoOne variable that a great deal depends on (86)
"gtm.triggers" is read by 86 tags and triggers — more than anything else in this container.
WhyGTM shows you where a variable is defined, never how much depends on it. Editing this one touches a large share of the container at once, and whatever breaks will surface somewhere that looks unrelated to the change.
CheckBefore changing it, check what reads it. If it feeds both measurement and consent or routing logic, split those uses apart first.
Seenseen in 10.1% of 46,522 containers measured
infoVendor IDs written into custom code (4)
4 vendor IDs are pasted directly into custom HTML rather than held in a variable or template.
WhyChanging a property, pixel or account then means editing every tag that mentions it, and any one that gets missed keeps sending to the old destination indefinitely.
CheckFine if the ID never changes. If you have ever migrated a property, check that none of these still point at the old one.
Seenseen in 31.4% of 46,522 containers measured
infoLoads JavaScript from another host (3)
3 pieces of custom code fetch and run JavaScript from another host.
WhyWhatever that host serves executes with full access to the page — it can read the DOM, cookies and form fields. The code is not in this container, so it can change at any time without any change here.
CheckConfirm you recognise every host below and that someone owns the relationship. A host you cannot name is the one to chase.
Seenseen in 54.4% of 46,522 containers measured
infoConsent configuration detected (2)
The container declares one or more consent signals.
WhyConsent handling is present in the container. This describes what the artifact declares; what actually happened on the page is measured separately, above.
CheckConfirm these settings match the consent policy you intend to enforce, and compare them with the before-and-after observation.
Seenseen in 44.6% of 46,522 containers measured
Third parties it can reach
Each host is a party that can execute code or receive data in a visitor's browser. Follow one to see who else loads it. More info »
www.google-analytics.com ×82www.googleadservices.com ×20connect.facebook.net ×4www.facebook.com ×4analytics.ahrefs.com ×1googleads.g.doubleclick.net ×1localhost ×1script.advertiserreports.com ×1signup.es-mail.co.uk ×1static.hotjar.com ×1
What the custom templates can do
Custom templates are third-party code shipped inside the container. Injecting scripts and running page globals is ordinary for them — most tag templates need it to work — so this is an inventory, not a warning. It lists the capability each template declares so you can match it against templates you meant to install.
__cvt_7581802_162 private injects code from x.cookiebot.com, x.cookiebot.eu__cvt_7581802_623 private injects code from cc.cdn.civiccomputing.com · runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net · runs page-level globals__cvt_K54WP gallery injects code from plausible.io · runs page-level globals__cvt_TB7ZX gallery injects code from snap.licdn.comDetected on
Sites observed loading this container. A container used across many hosts is a shared template; one on a single host is a bespoke build. Follow a site to see every container it loads.
What this audit describes
Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.
| Container | GTM-MVC64CR |
|---|---|
| Published version | 447 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:49:29 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MVC64CR |
| Body checksum | 606dcad813400ff71a609a72cd245d60a3de9e83de1035e1563b025068db3fb0Evidence of the exact bytes we read, not an identity: Google varies the response per request, so re-fetching an unchanged container yields a different checksum. Compare the published version instead. |
Re-audit
This reading is from 2 months ago. A container can be republished at any time, and nothing here updates on its own — a fresh read is the only way to know whether it still says this. Running it again replaces this page in place, so the link keeps working.
Put this container under version control. Tagora exports it to a repository you own, so every change arrives as a pull request. How it works »