container audit
GTM-KTXVXPV
This container ships 275 hand-written scripts (118 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.
- 12 third-party hosts reachable from its tags — more than 80% of the 46,522 containers we have measured.
- 637 published versions — each one live for every visitor the moment it was published.
Tags318
Custom scripts275
Third parties12
Delivered684 KB
Versions637
What we observed
A real browser loaded melaleuca.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
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
12 hosts — fonts.googleapis.com, use.typekit.net, cdn.evgnet.com, 1036137.collect.igodigital.com, cdn.appdynamics.com, www.googletagmanager.com, web-sdk.smartlook.com, nova.collect.igodigital.com, and 4 more
dataLayer events seen
gtm.js, promoView, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on melaleuca.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 (8)
8 pieces 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
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 (97)
"gtm.elementClasses" is read by 97 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
infoLoads JavaScript from another host (13)
13 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
infoUses browser storage (2)
2 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
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 ×43melaleucasgmyprep.uat.productrecs.optimizely.com ×2melaleucatwhkprep.uat.productrecs.optimizely.com ×2melaleucaaunzprod.uswe01.productrecs.episerver.net ×1melaleucajpprep.uat.productrecs.optimizely.com ×1melaleucajpprod.uswe01.productrecs.episerver.net ×1melaleucakrprep.uat.productrecs.optimizely.com ×1melaleucakrprod.uswe01.productrecs.episerver.net ×1melaleucaphprep.uat.productrecs.optimizely.com ×1melaleucaprep.uat.productrecs.optimizely.com ×1melaleucaprod.uswe01.productrecs.episerver.net ×1melaleucatwhkprod.uswe01.productrecs.episerver.net ×1
Detected 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-KTXVXPV |
|---|---|
| Published version | 637 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 13:16:47 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KTXVXPV |
| Body checksum | 56c701ea57dfb7d3f4fa4fe29e2d77ff42c084eefaac63b4372c11423c1b9babEvidence 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 »