tagora
container audit

GTM-MHWQVV8

This container ships 46 hand-written scripts (21 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.

Tags61
Custom scripts46
Third parties3
Delivered541 KB
Versions23

What we observed

A real browser loaded elis.com 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 google-analytics.com — Google
Consent a consent banner was present and responded. 3 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).
Third parties contacted 17 hosts — cdn.jsdelivr.net, unpkg.com, service.mtcaptcha.com, static.axept.io, www.googletagmanager.com, client.axept.io, api.axept.io, fonts.axept.io, and 9 more
dataLayer events seen gtm.js, axeptio_update, gtm.dom, gtm.load, gtm.click, axeptio_activate_piano_analytics, axeptio_enable_piano_analytics, axeptio_activate_youtube, axeptio_enable_youtube, axeptio_activate_gmaps, axeptio_enable_gmaps, axeptio_activate_newrelic, +8 more

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on elis.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.

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 »

www.googleadservices.com ×3googleads.g.doubleclick.net ×1www.google-analytics.com ×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_52128311_297 private injects code from tag.aticdn.net · runs page-level globals
__cvt_MQDKZ gallery injects code from www.clarity.ms · 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.

elis.com

What this audit describes

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

ContainerGTM-MHWQVV8
Published version23 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 17:46:24 UTC (2 months ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-MHWQVV8
Body checksum42288b5bdabb839e28505f8a350cdf8f3f127c78c30ccc4e5596861fef48fbcd
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-MHWQVV8

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 »