container audit

GTM-M2DJ97R

49 tags, 2 custom scripts, 2 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).

2 custom HTML tags carrying 3 KB of JavaScript. This runs on every page the container loads on.
2 third-party hosts 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.

Tags49

Custom scripts2

Third parties2

Delivered461 KB

Versions47

What we observed

A real browser loaded bomba.md 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 — Google

Measurement sent to gtm.bomba.md — not Google

Measurement 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 ×3 — read from the measurement id, not the hostname

Consent a consent banner was present and we accepted it. Measurement fired beforehand but carried no identifier — analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 10 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).

Third parties contacted 25 hosts — cdn-cookieyes.com, code.jquery.com, log.cookieyes.com, cdn.jsdelivr.net, www.googletagmanager.com, analytics.ahrefs.com, directory.cookieyes.com, connect.facebook.net, and 17 more

dataLayer events seen gtm.js, gtm.dom, gtm.load, gtm.click

Where the data goes

Confirmed — a browser watched this site send measurement data to gtm.bomba.md, not to Google. observed on bomba.md 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 (3)

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

infoLoads JavaScript from another host (2)

2 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

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 »

analytics.ahrefs.com ×1 www.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_KDQSW gallery injects code from cdn-cookieyes.com

__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals

__cvt_NBJ5G gallery runs page-level globals

__cvt_PH34Q gallery runs page-level globals

__cvt_T9LCB gallery injects code from x.iadvize.com, x.twilio.com · runs page-level globals

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.

bomba.md

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-M2DJ97R`
Published version	`47` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:42:23 UTC (2 months ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-M2DJ97R`
Body checksum	`f0f6ed4177f6df3fcf874ed1137ed58c9e0cb1c203009a6e2a5156ba238271f2` Evidence 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.

Re-audit GTM-M2DJ97R

Check another container

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 »