container audit
GTM-WXJ4DQ9
23 tags, 5 custom scripts, 5 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 5 custom HTML tags carrying 3 KB of JavaScript. 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.
Tags23
Custom scripts5
Third parties5
Delivered494 KB
Versions12
What we observed
A real browser loaded samsontech.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. 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. Google recorded
gcs=G111 (all granted). 4 advertising hosts were contacted before anything was granted.Third parties contacted
16 hosts — sam-media.cdn-rs.com, ik.imagekit.io, buynow.omacro.com, maps.googleapis.com, services-v2.omacro.com, www.googletagmanager.com, cdn.cookielaw.org, www.google-analytics.com, and 8 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, OneTrustLoaded, OptanonLoaded
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on samsontech.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.
reviewUniversal Analytics tags still shipped (5)
5 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
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-D6F47WNG4E 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
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
infoVendor IDs written into custom code (1)
1 vendor ID is 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 »
www.google-analytics.com ×7www.googleadservices.com ×4www.facebook.com ×2connect.facebook.net ×1googleads.g.doubleclick.net ×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_WP4D8 gallery injects code from cookie-cdn.1trust.app, cdn.cookielaw.org, cdn-ukwest.onetrust.com, cookie-cdn.cookiepro.com, cdn-au.onetrust.com, cdn-apac.onetrust.com · 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-WXJ4DQ9 |
|---|---|
| Published version | 12 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:22:49 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WXJ4DQ9 |
| Body checksum | 4faa1ea6f9cd216d3401d8f3d828ea7606dd555005bd4de5e127a8854e3bd7c5Evidence 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 »