container audit
GTM-WW62942
This container ships 54 hand-written scripts (31 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.
- 6 third-party hosts reachable from its tags.
- 556 published versions — each one live for every visitor the moment it was published.
Tags312
Custom scripts54
Third parties6
Delivered543 KB
Versions556
What we observed
A real browser loaded koronapay.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 — GoogleThird parties contacted
3 hosts — mc.yandex.ru, www.googletagmanager.com, hdrc.yandex.net
dataLayer events seen
gtm.js, gtm.dom, gtm.load
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on koronapay.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 (8)
8 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 (6)
6 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
reviewdocument.write (5)
5 pieces of custom code call document.write.
Whydocument.write blocks the HTML parser while it runs, and browsers ignore it entirely once the page has finished parsing — so an async-loaded tag using it can silently do nothing.
CheckIf these tags fire on page load they are costing render time; if they fire later they may not be working at all. Worth confirming the tag still does what it was added to do.
Seenseen in 18.4% 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 (50)
"gtm.elementUrl" is read by 50 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 (1)
1 piece 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
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 »
app.appsflyer.com ×28mc.yandex.ru ×8koronapay.com ×5cc.cdn.civiccomputing.com ×1web.telegram.org ×1www.google-analytics.com ×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-WW62942 |
|---|---|
| Published version | 556 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-12 23:00:21 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WW62942 |
| Body checksum | fa19c27c79c856733cb2b226a75bdb7805afb1e2cfd9ff19b181b5422daa8577Evidence 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 »