container audit
GTM-NF8FQF6
104 tags, 25 custom scripts, 8 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 25 custom HTML tags carrying 16 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- 8 third-party hosts reachable from its tags — more than 70% of the 46,522 containers we have measured.
duplicate-ads-conversionis uncommon — under 4% of the containers we have measured have it. That is context rather than a verdict: a server container is rarer still and is a sign of a mature setup. What it means is in the finding itself.
Tags104
Custom scripts25
Third parties8
Delivered560 KB
Versions171
What we observed
A real browser loaded senec.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
senec.com — the site's own host, at /modules/contrib/google_tag/js/gtm.js rather than the default path, and googletagmanager.comMeasurement sent to
google-analytics.com — GoogleThe container is self-hosted; the measurement still goes to Google. The first-party path that a tagging server provides is not being used for the data itself.
Consent
a consent banner was present and we accepted it. Nothing measured until it was granted — no analytics or advertising hit left the page beforehand, and 13 fired afterwards. That is the outcome consent is meant to produce. 10 hosts appeared only after consent was granted. Google recorded
gcs=G111 (all granted).Third parties contacted
25 hosts — static.cloudflareinsights.com, unpkg.com, static.elfsight.com, www.googletagmanager.com, core.service.elfsight.com, static.hotjar.com, www.google.com, ad.doubleclick.net, and 17 more
dataLayer events seen
gtm.js, loadgtm-hubspot, loadgtm-facebook, loadgtm-bing-ads, loadgtm-linkedin, loadgtm-outbrain, loadgtm-reddit, loadgtm-adform, loadgtm-hotjar, loadgtm-google-analytics, loadgtm-stackadapt, loadgtm-google-ads, +8 more
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on senec.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 (7)
7 pieces 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
reviewSame Google Ads conversion defined more than once (1)
1 conversion action is defined by more than one tag.
WhyA conversion ID plus label identifies one action. Two tags carrying the same pair can report the same conversion twice, inflating conversion counts and the ROAS that bidding runs on.
CheckCheck whether both tags can fire on the same page. If they can, your Ads reporting is overstating this action and automated bidding is optimising against it.
Seenseen in 3.8% of 46,522 containers measured
infoUses browser storage (23)
23 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
infoLoads JavaScript from another host (2)
2 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 ×28www.googleadservices.com ×13senec.com ×6schema.org ×2analytics.tiktok.com ×1googleads.g.doubleclick.net ×1static.hotjar.com ×1widget.moin.ai ×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_K8GSG gallery runs page-level globals__cvt_12147080_753 private 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-NF8FQF6 |
|---|---|
| Published version | 171 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 17:53:48 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-NF8FQF6 |
| Body checksum | 73a0937d64bfb41777178cd7730f9bafd38df5e7191a7486040ea0f30040d14bEvidence 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 »