tagora
container audit

GTM-MTNB8CT

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

Tags0
Custom scripts0
Third parties0
Delivered315 KB
Versions1

What we observed

A real browser loaded planet-liebe.com 2 months 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 www.planet-liebe.com — the site's own host, at /jc/gtm.js rather than the default path
Measurement sent to google-analytics.com — Google

The 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 Quantcast answered its own API. 3 measurement hits left the page before it was granted, carrying a client id (whether that is permitted depends on jurisdiction, and this was not a European visit). 10 hosts appeared only after consent was granted. 3 advertising hosts were contacted before anything was granted.
Third parties contacted 25 hosts — imagesrv.adition.com, pl-live-data.nbg1.your-objectstorage.com, cdn.h5v.eu, cmp.inmobi.com, visit-server.inmobi-choice.io, region1.analytics.google.com, stats.g.doubleclick.net, www.google.de, and 17 more
dataLayer events seen gtm.dom, gtm.load

Where the data goes

Not observed — on the page we loaded, measurement went to Google and nowhere else. observed on planet-liebe.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.

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.

planet-liebe.com

What this audit describes

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

ContainerGTM-MTNB8CT
Published version1 — the identity of this configuration. It changes only when someone publishes.
Read at2026-08-23 17:49:21 UTC (2 months ago)
Sourcehttps://www.googletagmanager.com/gtm.js?id=GTM-MTNB8CT
Body checksum144f678436d0f9c3572676b2ae9a3107648ea3a10ef30778f4f9b030787e224c
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 2 months 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-MTNB8CT

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 »