container audit
GTM-MVJGH7J
125 tags, 14 custom scripts, 9 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 14 custom HTML tags carrying 9 KB of JavaScript. 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.
Tags125
Custom scripts14
Third parties9
Delivered532 KB
Versions219
What we observed
A real browser loaded jaggaer.com 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
not observed loading
Measurement sent to
google-analytics.com — GoogleWhere the data goes
Nothing fired — we loaded the page and no tag library or measurement request ran, which usually means a consent banner held everything back. The container below still describes what would run once it does. observed on jaggaer.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.
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 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
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 ×16www.googleadservices.com ×9px.ads.linkedin.com ×4go.jaggaer.com ×2googleads.g.doubleclick.net ×1j.6sc.co ×1js.qualified.com ×1tracking.intentsify.io ×1wec-assets.terminus.services ×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_5RFHV gallery injects code from consent.trustarc.com · runs page-level globals__cvt_MQDKZ gallery injects code from www.clarity.ms · 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-MVJGH7J |
|---|---|
| Published version | 219 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 14:03:28 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MVJGH7J |
| Body checksum | 587640ee274ef4bd20f9f44a5e84940080675041070b1037604b7eddc6697e21Evidence 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 »