container audit
GTM-TS9WDL6F
90 tags, 15 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 15 custom HTML tags carrying 9 KB of JavaScript — more than 70% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 5 third-party hosts reachable from its tags.
duplicate-ga4-configis uncommon — under 5% 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.
Tags90
Custom scripts15
Third parties5
Delivered580 KB
Versions42
What we observed
A real browser loaded fm.com a month 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
OneTrust answered its own API. 10 hosts appeared only after consent was granted.
Third parties contacted
17 hosts — cdn.cookielaw.org, privacyportal-cdn.onetrust.com, cdnjs.cloudflare.com, geolocation.onetrust.com, privacyportal.onetrust.com, www.googletagmanager.com, www.google-analytics.com, tag.demandbase.com, and 9 more
dataLayer events seen
OneTrustLoaded, OptanonLoaded, gtm.js, gtm.dom, gtm.load, gtm.triggerGroup, gtm.scrollDepth, Demandbase_Loaded, gtm.timer, client_id_event
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on fm.com 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.
reviewSame GA4 property configured more than once (6)
G-278LB5SBY4 is configured by 2 separate tags; G-GM9H88WHD6 is configured by 2 separate tags; G-60TX9X6LTT is configured by 2 separate tags; G-TYWCR3Z1ZC is configured by 2 separate tags; G-J2RE87DEWJ is configured by 2 separate tags; G-BP4XN9P8P0 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
reviewdocument.write (2)
2 pieces of custom code call document.write.
Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.
CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.
Seenseen in 18.4% 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
infoOne variable that a great deal depends on (40)
"gtm.triggers" is read by 40 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
infoUses browser storage (8)
8 pieces of custom code read or write localStorage or sessionStorage.
WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.
CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.
Seenseen in 23.3% of 46,522 containers measured
infoConsent configuration detected (1)
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 »
fls.doubleclick.net ×11secure.leadforensics.com ×2www.google-analytics.com ×2tag.demandbase.com ×1www.googleadservices.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_186533322_296 private injects code from snap.licdn.com__cvt_186533322_499 private injects code from cdn.quantummetric.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-TS9WDL6F |
|---|---|
| Published version | 42 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:13:04 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TS9WDL6F |
| Body checksum | d749e9227c13e3c2737d276c0c84f7f6118a68345bf38338ba467be02f158b29Evidence 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 a month 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 »