container audit
GTM-TNKWVQSV
32 tags, 2 custom scripts, 1 third-party host — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 2 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
- 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.
Tags32
Custom scripts2
Third parties1
Delivered501 KB
Versions4
What we observed
A real browser loaded mercafacil.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
gtm.mercafacil.com — the site's own host, and googletagmanager.comMeasurement sent to
gtm.mercafacil.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 ×4 — 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).
Third parties contacted
24 hosts — cdn.prod.website-files.com, cdn.jsdelivr.net, app.optibase.io, ajax.googleapis.com, fonts.googleapis.com, d3e54v103j8qbb.cloudfront.net, d335luupugsy2.cloudfront.net, cdn.jetboost.io, and 16 more
dataLayer events seen
gtm.js, gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to gtm.mercafacil.com, not to Google. observed on mercafacil.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.
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
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_259203654_26 private injects code from snap.licdn.com__cvt_259203654_29 private injects code from connect.facebook.net · 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-TNKWVQSV |
|---|---|
| Published version | 4 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:11:40 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TNKWVQSV |
| Body checksum | e69054e10432cfafe9e35ae52d040b880cec4d55183ef57e94b297aa8db0f346Evidence 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 »