container audit
GTM-59WHG4X
This container ships 165 hand-written scripts (66 KB of JavaScript) to every visitor — more than 99% 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.
- 388 published versions — each one live for every visitor the moment it was published.
inner-htmlis uncommon — under 6% 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.
Tags308
Custom scripts165
Third parties9
Delivered809 KB
Versions388
What we observed
A real browser loaded myer.com.au 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
www.myer.com.au — the site's own host, at /scripts-myer/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
sgtm.myer.com.au — not GoogleMeasurement 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 ×5 — 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).
Third parties contacted
25 hosts — content-us-5.content-cms.com, web-assets.stylitics.com, cdn.dynamicyield.com, st.dynamicyield.com, edge.curalate.com, myr-cdn.truefitcorp.com, shopping-muse.dynamicyield.com, 7322496.collect.igodigital.com, and 17 more
dataLayer events seen
gtm.js, custom.user.engagement, gtm.dom, DY Variation Impression, page_view, pageLoad, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to sgtm.myer.com.au, not to Google. observed on myer.com.au 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.
reviewWrites cookies directly (3)
3 pieces 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
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% 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
infoOne variable that a great deal depends on (46)
"form_name" is read by 46 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 (19)
19 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 (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
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 »
vimeo.com ×4analytics.tiktok.com ×1apps.bazaarvoice.com ×1beacon.krxd.net ×1cdn-us.algoliaradar.com ×1cnstrc.com ×1tagassistant.google.com ×1tags.pw.adn.cloud ×1www.vimeo.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_5RM3Q gallery injects code from connect.facebook.net · runs page-level globals__cvt_7411574_9154 private injects code from t.contentsquare.net · runs page-level globals__cvt_7411574_9156 private runs page-level globals__cvt_7411574_9244 private runs page-level globals__cvt_7411574_9893 private runs page-level globals__cvt_7411574_9913 private injects code from dynamic.criteo.com__cvt_MRQN8 gallery 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-59WHG4X |
|---|---|
| Published version | 388 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 22:17:04 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-59WHG4X |
| Body checksum | 1f36a93afc3aea0e5764ca40595d78eb43cff19b6535894b2b69eb30b735720cEvidence 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 »