container audit
GTM-WZSSDGQ
52 tags, 11 custom scripts, 6 third-party hosts — an ordinary container, near the middle of what we measure (median: 39 tags, 4 custom scripts).
- 11 custom HTML tags carrying 9 KB of JavaScript. This runs on every page the container loads on.
- 6 third-party hosts reachable from its tags.
Tags52
Custom scripts11
Third parties6
Delivered512 KB
Versions34
What we observed
A real browser loaded paklap.pk 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
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).
Third parties contacted
20 hosts — maxcdn.bootstrapcdn.com, static.cloudflareinsights.com, www.googletagmanager.com, apps.elfsight.com, static.elfsight.com, elfsightcdn.com, px.ads.linkedin.com, core.service.elfsight.com, and 12 more
dataLayer events seen
gtm.dom, gtm.load, gtm.js
Where the data goes
Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on paklap.pk 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.
reviewUniversal Analytics tags still shipped (4)
4 Universal Analytics tags are still in the container.
WhyUniversal Analytics stopped processing data in July 2023. These tags still download and execute on every matching page, and send to an endpoint that discards them.
CheckNothing is being collected from these. Confirm the equivalent GA4 tag exists, then delete them.
Seenseen in 23.2% of 46,522 containers measured
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 »
www.google-analytics.com ×30www.googleadservices.com ×3analytics.tiktok.com ×1connect.facebook.net ×1googleads.g.doubleclick.net ×1www.facebook.com ×1
Detected 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-WZSSDGQ |
|---|---|
| Published version | 34 — the identity of this configuration. It changes only when someone publishes. |
| Read at | 2026-08-23 18:23:10 UTC (a month ago) |
| Source | https://www.googletagmanager.com/gtm.js?id=GTM-WZSSDGQ |
| Body checksum | c310b1a80cabba7e2f4089d520817b2e8d795453e066a5711d328e18c3efb777Evidence 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 »