GTM Controller

Privacy tests before GTM publishes

Tagmaps tests new versions against your privacy requirements, then blocks, notifies users, or publishes based on the results.

View plans How it works
Input
GTM update
Decision
Policy verdict
Action
Block or publish

Candidate version

northledger.com · v24

Not published

EU

GDPR

Pass

UK

UK GDPR

Pass

California

CCPA · GPC

Fail

Colorado

CPA

Pass

GPC signal ignored on /checkout

Live container remains on v23. The owner receives the failed test and remediation guidance.

Automate policy checks in your publish workflow

Your team keeps using GTM as normal. Tagmaps adds the testing, decisioning, and publishing controls before production.

Test before production

Tagmaps loads your live website, but with a preview version of GTM. Tagmaps uses a real browser, loading your site from a variety of international locations, testing against privacy laws before your changes go live.

Choose how much to automate

Start in read-only mode, then add human publishing within Tagmaps. Once you're ready, enable automated publishing for versions that pass the tests.

Keep the audit trail

Each test stores its results, letting you compare changes over time.

How it works

From candidate to controlled publish

Configure the connection once. Tagmaps watches for the next candidate and applies the same repeatable process every time.

  1. 01

    Connect the container

    Log in to your Google account and select which containers are in scope.

  2. 02

    Assign the test plan

    Select the tests you want to run for each GTM container.

  3. 03

    Test the GTM version

    Tagmaps detects a new GTM version, loads it in a real browser as a preview on your live website, and records the results.

  4. 04

    Act on the verdict

    Tagmaps can be read-only, allow human publish from the product, or automate the publish too. A version that fails tests is never published by Tagmaps.

Everything needed to review the decision

The Controller keeps technical evidence and publishing actions together instead of splitting them across GTM, spreadsheets, and one-off scan reports.

01

Version-to-version comparison

Review the tags, cookies, storage, and network requests the tested version adds or changes.

02

Regional privacy tests

Tests execute from the locations relevant to your policy, such as in the EU vs California.

03

User notifications

One or more users are notified of the outcomes, showing how to fix this version before it goes live.

04

Optional publisher controls

Tagmaps can prevent human users from publishing directly from GTM, ensuring only tested versions ever reach production.

Control your tag manager

View plans Free trial