container audit

GTM-MT54VMN

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

4 third-party hosts reachable from its tags.
854 published versions — each one live for every visitor the moment it was published.

Tags116

Custom scripts43

Third parties4

Delivered510 KB

Versions854

What we observed

A real browser loaded snapptrip.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 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). Google recorded gcs=G1 (no consent signal).

Third parties contacted 12 hosts — sentry.pinsvc.net, www.googletagmanager.com, ssl.widgets.webengage.com, 11b5650c0.webengage.co, wsdk-files.webengage.com, mc.yandex.ru, s1.mediaad.org, c.webengage.com, and 4 more

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 snapptrip.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 (1)

1 piece 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

infoUses browser storage (3)

3 pieces of custom code read or write localStorage or sessionStorage.

WhyBrowser storage persists across visits and is not covered by cookie consent tooling, so it is easy to overlook when auditing what you keep on a visitor's device.

CheckConfirm nothing personal is being kept there, and that it is covered by your privacy notice.

Seenseen in 23.3% of 46,522 containers measured

infoConsent configuration detected (1)

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 »

mc.yandex.ru ×2 www.google-analytics.com ×2 s1.mediaad.org ×1 www.googleadservices.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.

snapptrip.com

What this audit describes

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

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

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 »