container audit
GTM-KF4MHDR
213 tags, 0 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 third-party host reachable from its tags.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
Tags213
Custom scripts0
Third parties1
Delivered586 KB
Versions124
What we observed
A real browser loaded fh-ooe.at 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
st.fh-ooe.at — not GoogleMeasurement 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 — 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). 1 host appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
21 hosts — webcache-eu.datareporter.eu, www.googletagmanager.com, www.youtube-nocookie.com, www.clarity.ms, connect.facebook.net, snap.licdn.com, sc-static.net, px.ads.linkedin.com, and 13 more
dataLayer events seen
cookie_consent_statistic_enabled, cookie_consent_marketing_enabled, gtm.js, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to st.fh-ooe.at, not to Google. observed on fh-ooe.at 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.
infoOne variable that a great deal depends on (93)
"gtm.triggers" is read by 93 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 (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
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 »
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_8664348_149 private injects code from sc-static.net, tr.snapchat.com · runs page-level globals__cvt_8664348_342 private injects code from snap.licdn.com__cvt_8664348_372 private injects code from connect.facebook.net · runs page-level globals__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-KF4MHDR |
|---|---|
| Published version | 124 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:37:37 UTC (2 months ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-KF4MHDR |
| Body checksum | 2dac9a36157c9d229122f9fcbffcdd094999dbb5dfe35ed054fbff8aa8bea9abEvidence 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 »