container audit
GTM-P6VNQ5J
10 tags, 1 custom scripts, 3 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 1 custom HTML tag carrying 0 KB of JavaScript. This runs on every page the container loads on.
- 3 third-party hosts reachable from its tags.
Tags10
Custom scripts1
Third parties3
Delivered445 KB
Versions15
What we observed
A real browser loaded kongcompany.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
googletagmanager.com — GoogleMeasurement sent to
google-analytics.com — GoogleConsent
a consent banner was present and we accepted it. Measurement fired beforehand but carried no identifier —
analytics_storage was denied, which is Consent Mode working as designed rather than a gap. 9 hosts appeared only after consent was granted. Google recorded gcs=G100 (all denied).Third parties contacted
25 hosts — cdn11.bigcommerce.com, microapps.bigcommerce.com, fonts.googleapis.com, cdn-4.convertexperiments.com, ajax.googleapis.com, code.rebillia.com, js.authorize.net, checkout-sdk.bigcommerce.com, and 17 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 kongcompany.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.
reviewNo consent signal in the container (1)
Nothing in this container sets, reads, or gates on a consent state.
WhyThe container itself neither sets a Consent Mode default, holds any tag back for consent, nor references a known consent platform. Either enforcement lives entirely outside GTM — where it cannot be audited from here — or tags fire regardless of what a visitor chose.
CheckIf a consent platform blocks scripts before GTM loads, this is fine — confirm that is actually the case. If not, tags are firing on a choice nobody recorded.
Seenseen in 52.1% of 46,522 containers measured
infoLoads JavaScript from another host (1)
1 piece 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
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_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-P6VNQ5J |
|---|---|
| Published version | 15 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:00:21 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-P6VNQ5J |
| Body checksum | 677dac079325de6d01ad7539c1ea404eab6759822f3f9043816df6841fe329d0Evidence 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 »