container audit
GTM-KR7VQ5S
This container ships 40 hand-written scripts (27 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.
- 396 published versions — each one live for every visitor the moment it was published.
evalis uncommon — under 1% 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.
Tags144
Custom scripts40
Third parties18
Delivered567 KB
Versions396
What we observed
A real browser loaded eightsleep.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
googletagmanager.com — GoogleMeasurement sent to
www.eightsleep.com — not Google, at /metrics/ag/g/cMeasurement is first-party; the container still loads from Google. These are separate decisions, and this is the more common of the two.
Forwarded to
GA4 ×2 — read from the measurement id, not the hostname
Consent
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). 1 host appeared only after consent was granted. 10 advertising hosts were contacted before anything was granted.
Third parties contacted
25 hosts — res.cloudinary.com, static.shopmy.us, static.klaviyo.com, sdk.lifesight.io, decagon.ai, connect.facebook.net, snippet.maze.co, static.fbot.me, and 17 more
dataLayer events seen
gtm.js, OneTrustLoaded, OptanonLoaded, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to www.eightsleep.com, not to Google. observed on eightsleep.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.
reviewWrites cookies directly (2)
2 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
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
revieweval() (1)
1 piece of custom code call eval().
Whyeval turns a string into executing code. If any part of that string comes from the page, the URL or a cookie, whoever controls that input controls the code.
CheckTrace where the evaluated string comes from. A fixed literal is harmless; anything derived from user-controllable input is not.
Seenseen in 0.5% of 46,522 containers measured
reviewUniversal Analytics tags still shipped (1)
1 Universal Analytics tag is 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
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
infoLoads JavaScript from another host (8)
8 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 (1)
1 piece 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 ×10www.googleadservices.com ×9pixel.pointmediatracker.com ×4analytics.twitter.com ×2eightsleep.dexecure.net ×2tag.simpli.fi ×2campaign.fbot.me ×1cdn.amplitude.com ×1cdn.levelaccess.net ×1cdn.pdst.fm ×1cdn1.affirm.com ×1googleads.g.doubleclick.net ×1init.blackcrow.ai ×1px.adentifi.com ×1s.yimg.com ×1static.ads-twitter.com ×1static.fbot.me ×1www.clarity.ms ×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_8047186_268 private injects code from cdn.taboola.com__cvt_8047186_347 private injects code from www.redditstatic.com · runs page-level globals__cvt_K4VXG gallery injects code from sc-static.net, tr.snapchat.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-KR7VQ5S |
|---|---|
| Published version | 396 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:40:28 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KR7VQ5S |
| Body checksum | 196b0ca11097a65c095c9ab283a5e65d9192fd68e660e2bc04ce84bf1fdfa310Evidence 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 »