container audit

GTM-P4642V3F

This container is published but empty — no tags, so nothing fires.

Tags0

Custom scripts0

Third parties0

Delivered315 KB

Versions2

What we observed

A real browser loaded dpd.pt 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 — Google

Measurement sent to google-analytics.com — Google

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 3 fired afterwards. That is the outcome consent is meant to produce. 7 hosts appeared only after consent was granted. Google recorded gcs=G111 (all granted).

Third parties contacted 11 hosts — www.dpd.com, cdn.consentmanager.net, chatbot.alturing.eu, d.delivery.consentmanager.net, www.googletagmanager.com, www.google.com, ad.doubleclick.net, www.google-analytics.com, and 3 more

dataLayer events seen initialData, default_consent, cmpEventLoadedLayerOpen, cmpEventLoadFinished, cmpEvent, 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 dpd.pt 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.

No findings were raised for this container.

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 »

No third-party hosts were found in this container's tags.

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.

dpd.pt

What this audit describes

Containers change. These findings describe one specific artifact, and you can re-fetch it to check this reading.

Container	`GTM-P4642V3F`
Published version	`2` — the identity of this configuration. It changes only when someone publishes.
Read at	2026-08-23 17:59:23 UTC (a month ago)
Source	`https://www.googletagmanager.com/gtm.js?id=GTM-P4642V3F`
Body checksum	`c964017fa6103140e5b32fd5e33a4719f41e454f809f39c7dc975a327925f642` Evidence 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.

Re-audit GTM-P4642V3F

Check another container

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 »