container audit
GTM-PLWV7K
210 tags, 22 custom scripts, 9 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 22 custom HTML tags carrying 6 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 9 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
Tags210
Custom scripts22
Third parties9
Delivered637 KB
Versions70
What we observed
A real browser loaded invisalign.in 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
a consent banner was present and we accepted it. 2 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. 6 advertising hosts were contacted before anything was granted.
Third parties contacted
25 hosts — images.ctfassets.net, consent.trustarc.com, cdn.optimizely.com, www.googletagmanager.com, videos.ctfassets.net, www.clarity.ms, connect.facebook.net, www.google-analytics.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, gtm.historyChange-v2, gtm.click, useractioncomplete, cookie_prefs_set
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on invisalign.in 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 (16)
16 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
reviewdocument.write (1)
1 piece 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
reviewNo consent signal in the container (1)
Nothing in this container sets, reads, or gates on a consent state.
WhyThe container itself neither sets a Consent Mode default, holds any tag back for consent, nor references a known consent platform. Either enforcement lives entirely outside GTM — where it cannot be audited from here — or tags fire regardless of what a visitor chose.
CheckIf a consent platform blocks scripts before GTM loads, this is fine — confirm that is actually the case. If not, tags are firing on a choice nobody recorded.
Seenseen in 52.1% of 46,522 containers measured
infoVendor IDs written into custom code (2)
2 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
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 ×101www.google-analytics.com ×22www.googleadservices.com ×4connect.facebook.net ×3googleads.g.doubleclick.net ×2www.facebook.com ×2a.quora.com ×1q.quora.com ×1static.ada.support ×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_1766112_375 private injects code from p.teads.tv · runs page-level globals__cvt_K4VXG gallery injects code from sc-static.net, tr.snapchat.com · runs page-level globals__cvt_MQDKZ gallery injects code from www.clarity.ms · runs page-level globalsDetected 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-PLWV7K |
|---|---|
| Published version | 70 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-13 14:57:40 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-PLWV7K |
| Body checksum | 94f88beaa29c7224af8b2dcc66b0673a985757ac0ef45e3649dbba4521b96576Evidence 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 »