hello@datascale.de+49 89 921 35 623tracked cookie-free · /openDEEN

Search services, integrations and blog posts.

DatascaleResourcesChecksTag manager

Check · C03 · Tracking core

Tag manager

A central tag manager decouples tracking changes from your release cycle.

What we check

Looks for a central tag manager (GTM, Zaraz, Tealium, Adobe Launch, Segment).

Why it matters

A central tag manager decouples tracking changes from your release cycle.

Common causes

  • All pixels are hardcoded individually, grown historically across several agencies.
  • A tag manager exists but loads from a first-party subdomain and is not recognisable as one in the HTML, then the finding is a false positive.
  • The CMS plugin manages the tags, without versioning and without permission separation.
  • The container was installed for a test and never published, the snippet points to an empty workspace.

The fix

Set up GTM, Zaraz, Tealium, or Segment, centralise and version your tags.

Matching template

GA4 and Google Ads Consent Mapping

Documents which data flows from GA4 to Google Ads and which signal governs each flow.

Get the worksheet →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →
What does a failing "Tag manager" check mean?

A central tag manager decouples tracking changes from your release cycle. Set up GTM, Zaraz, Tealium, or Segment, centralise and version your tags.

How do you fix a failing "Tag manager" check?

Set up GTM, Zaraz, Tealium, or Segment, centralise and version your tags.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.