container audit
GTM-TPXQHXR
This container can hand execution to 17 third parties — more than 96% of the 46,522 containers we have measured. Each serves code it controls, which can change at any time.
- 32 custom HTML tags carrying 40 KB of JavaScript — more than 80% of the 46,522 containers we have measured. This runs on every page the container loads on.
- Measurement runs through a server container on its own domain — the mark of a mature setup, and rarer than the tooling vendors imply.
inner-htmlis uncommon — under 6% 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.
Tags85
Custom scripts32
Third parties17
Delivered579 KB
Versions76
What we observed
A real browser loaded icanotes.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
a.icanotes.com — the site's own hostMeasurement 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
Cookiebot answered its own API. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. no new hosts appeared after granting — either the tags are ungated, or they fire regardless and record the decision. Google recorded gcs=G111 (all granted).Third parties contacted
25 hosts — pro.fontawesome.com, fonts.gstatic.com, fonts.googleapis.com, platform-api.sharethis.com, ta.gaconnector.com, www.bigmarker.com, track.gaconnector.com, js.hs-scripts.com, and 17 more
dataLayer events seen
gtm.js, gtm.dom, gtm.formInteract, gtm.load, cookie_consent_preferences, cookie_consent_statistics, cookie_consent_marketing
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on icanotes.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.
reviewHardcoded http:// URL (4)
4 pieces of custom code reference a plain http:// address.
WhyOn an https:// page the browser blocks or upgrades these. Blocked means the tag quietly stops working; upgraded only works if that host also serves https.
CheckCheck whether the hosts below still respond over https, and update the URLs.
Seenseen in 12.8% of 46,522 containers measured
reviewWrites cookies directly (2)
2 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
reviewWrites innerHTML (1)
1 piece of custom code assign to innerHTML.
WhyAssigning innerHTML parses the string as HTML. If any of it comes from the URL, the page or a cookie, that is a script-injection route into your own site.
CheckCheck whether the assigned value is a fixed template or built from something a visitor can influence.
Seenseen in 5.7% of 46,522 containers measured
infoLoads JavaScript from another host (4)
4 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 (3)
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
infoUses browser storage (2)
2 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
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.icanotes.com ×87schema.org ×23www.youtube.com ×9testdrive.icanotes.com ×2www.clickcease.com ×2agent.marketingcloudfx.com ×1api.ipify.org ×1insight.adsrvr.org ×1js.adsrvr.org ×1monitor.clickcease.com ×1portal.smartrecognition.com ×1px.ads.linkedin.com ×1snap.licdn.com ×1www.facebook.com ×1www.instagram.com ×1www.linkedin.com ×1www.pinterest.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_57SF4 gallery injects code from x.cookiebot.com, x.cookiebot.eu__cvt_55X8C gallery injects code from x.pagesense.io, x.pagesense.cn__cvt_MQDKZ gallery injects code from www.clarity.ms · 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-TPXQHXR |
|---|---|
| Published version | 76 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:12:09 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-TPXQHXR |
| Body checksum | 4ac151c85d08d3be50d60d93c31e2b2ddba85480040a50d38c07f9709cb17d6eEvidence 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 »