container audit
GTM-N66LXLD
87 tags, 9 custom scripts, 6 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 9 custom HTML tags carrying 4 KB of JavaScript. This runs on every page the container loads on.
- 6 third-party hosts reachable from its tags.
Tags87
Custom scripts9
Third parties6
Delivered598 KB
Versions136
What we observed
A real browser loaded bintercanarias.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
not observed loading
Measurement sent to
google-analytics.com — GoogleConsent
a consent banner was present and responded. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision.
Where the data goes
Nothing fired — we loaded the page and no tag library or measurement request ran, which usually means a consent banner held everything back. The container below still describes what would run once it does. observed on bintercanarias.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.
infoLoads JavaScript from another host (6)
6 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
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.google-analytics.com ×40fls.doubleclick.net ×10www.googleadservices.com ×9googleads.g.doubleclick.net ×4pixel.byspotify.com ×2tm.cdnwebcloud.com ×2
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_KF8K9 gallery injects code from analytics.tiktok.com · runs page-level globals__cvt_K8GSG gallery runs page-level globals__cvt_T9CP9 gallery injects code from www.clarity.ms · runs page-level globals__cvt_5RM3Q gallery injects code from connect.facebook.net, capi-automation.s3.us-east-2.amazonaws.com · runs page-level globals__cvt_96269335_578 private injects code from static.connect.travelaudience.comDetected 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-N66LXLD |
|---|---|
| Published version | 136 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:52:02 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-N66LXLD |
| Body checksum | a4803eed8ae1c81b884841d6be0b3a7faa44d355de0f2672cbc4f666ab675a7bEvidence 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 »