container audit
GTM-NHRV69X
40 tags, 10 custom scripts, 4 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 10 custom HTML tags carrying 2 KB of JavaScript. This runs on every page the container loads on.
- 4 third-party hosts reachable from its tags.
Tags40
Custom scripts10
Third parties4
Delivered408 KB
Versions53
What we observed
A real browser loaded vivosun.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
ssc.vivosun.com — the site's own host, and googletagmanager.comMeasurement sent to
ssc.vivosun.com — not Google, at /sst/g/collectMeasurement 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 — 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). Google recorded
gcs=G111 (all granted).Third parties contacted
22 hosts — widget.trustpilot.com, accounts.google.com, www.googletagmanager.com, chimpstatic.com, invitejs.trustpilot.com, utt.impactcdn.com, amplify.outbrain.com, www.redditstatic.com, and 14 more
dataLayer events seen
gtm.dom, gtm.load
Where the data goes
Confirmed — a browser watched this site send measurement data to ssc.vivosun.com, not to Google. observed on vivosun.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
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 »
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_NC6HJ gallery injects code from x.dwin1.com · runs page-level globals__cvt_5TP9K gallery injects code from x.dwin1.com__cvt_62570943_103 private injects code from x.goaffpro.com · runs page-level globals__cvt_62570943_16 private injects code from www.redditstatic.com · runs page-level globals__cvt_62570943_4 private injects code from amplify.outbrain.com · runs page-level globals__cvt_62570943_95 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-NHRV69X |
|---|---|
| Published version | 53 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:54:51 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NHRV69X |
| Body checksum | 3f8e7c94cd62d2ceaf5a13dd66d463d9d042bdcbcf2d53893ac22fbc61158283Evidence 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 »