container audit
GTM-MV96C4HG
2 tags, 1 custom scripts, 0 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 custom HTML tag carrying 0 KB of JavaScript. This runs on every page the container loads on.
Tags2
Custom scripts1
Third parties0
Delivered330 KB
Versions2
What we observed
A real browser loaded stihl.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
sgtm.stihl.com — the site's own host, and googletagmanager.comMeasurement sent to
sgtm.stihl.com — 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 ×6 — read from the measurement id, not the hostname
Consent
OneTrust answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 3 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
15 hosts — rum.hlx.page, cdn.cookielaw.org, geolocation.onetrust.com, cdn.trkkn.com, www.googletagmanager.com, static.trbo.com, api-v4.trbo.com, pagead2.googlesyndication.com, and 7 more
dataLayer events seen
gtm.js, pageLoad, gtm.dom, gtm.elementVisibility, ec.view_promotion, OneTrustLoaded, OptanonLoaded, OptanonUpdate, gtm.load, gtm.triggerGroup
Where the data goes
Confirmed — a browser watched this site send measurement data to sgtm.stihl.com, not to Google. observed on stihl.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.
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 »
No third-party hosts were found in this container's tags.
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_195873122_10 private injects code from static.trbo.comDetected 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-MV96C4HG |
|---|---|
| Published version | 2 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-22 10:07:45 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-MV96C4HG |
| Body checksum | feb2c649d26023e9622ed1a4988a9d7739187fa24aaf6d9403eb220f3cd42bb4Evidence 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 »