container audit
GTM-TW4RMC9
10 tags, no hand-written scripts, 2 third-party hosts — smaller than 75% of the 46,522 containers we have measured, and carrying none of the hand-written JavaScript most of them do.
- 2 third-party hosts reachable from its tags.
duplicate-ga4-configis uncommon — under 5% 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.
Tags10
Custom scripts0
Third parties2
Delivered420 KB
Versions24
What we observed
A real browser loaded agrofoto.pl 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
Cookiebot 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. 1 host appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
15 hosts — www.googletagmanager.com, fonts.googleapis.com, code.createjs.com, static.hotjar.com, www.google-analytics.com, connect.facebook.net, consent.cookiebot.com, pagead2.googlesyndication.com, and 7 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on agrofoto.pl 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.
reviewSame GA4 property configured more than once (1)
AW-776384692 is configured by 2 separate tags.
WhyEach config tag initialises the property independently, so a single page view can be counted once per tag. Sessions, users and conversion rates all inherit the error.
CheckIf more than one of these fires on the same page you are double-counting. Compare against a known-good day, or check for a step change in traffic when the second tag was added.
Seenseen in 4.8% of 46,522 containers measured
infoConsent configuration detected (2)
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_8278980_20 private injects code from x.cookiebot.com, x.cookiebot.euDetected 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-TW4RMC9 |
|---|---|
| Published version | 24 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:13:42 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TW4RMC9 |
| Body checksum | 18952aaa9982d699ea8a4c1e56bf056be52ace32fed3c89f71118867b5983e55Evidence 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 »