container audit
GTM-WZW3WRJ7
This container ships 39 hand-written scripts (23 KB of JavaScript) to every visitor — more than 90% of the 46,522 containers we have measured. That is an application's worth of code, delivered as tag configuration.
- 9 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
Tags82
Custom scripts39
Third parties9
Delivered536 KB
Versions152
What we observed
A real browser loaded camper.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
www.camper.com — the site's own host, at /gtm/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
www.camper.com — not Google, at /gtm/g/collectMeasurement runs through the site's own infrastructure. Part of the tag library still comes from Google, which is normal — the two are loaded separately.
Forwarded to
GA4 ×10 — read from the measurement id, not the hostname
Consent
no consent gate responded on this page, so there was nothing to hold measurement back (banners are often shown only to visitors in certain regions, and this was not a European visit). Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — gepi.global-e.com, web.global-e.com, search.unbxd.io, globale-analytics-sdk.global-e.com, webservices.global-e.com, utils.global-e.com, www.googletagmanager.com, init.blackcrow.ai, and 17 more
dataLayer events seen
gtm.js, view_item_list, view_promotion, cart_sync, gtm.dom, gtm.load, core_web_vitals, oct8ne_event
Where the data goes
Confirmed — a browser watched this site send measurement data to www.camper.com, not to Google. observed on camper.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.
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
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
infoUses browser storage (11)
11 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
infoLoads JavaScript from another host (7)
7 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 (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 »
accessibilityserver.org ×2cloud.camper.com ×2bzrcdn.openai.com ×1client-version.cf.emarsys.net ×1schema.org ×1static-eu.oct8ne.com ×1unpkg.com ×1www. ×1www.camper.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_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-WZW3WRJ7 |
|---|---|
| Published version | 152 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:54:06 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WZW3WRJ7 |
| Body checksum | b451d28f55155f48a4601f021e9cfbcd7e8de04fd466d10c5271ee874cb74d30Evidence 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 »