Tag management

Connect your tag manager and check tracking

Connect a client's Google Tag Manager to their Maven workspace with Google sign-in, choose their containers, and ask Maven to check their tags, pixels and conversion tracking.

Maven manages tracking through each client's own tag manager: Google Tag Manager (GTM) or Piwik PRO Tag Manager. You connect it once per workspace and choose the client's containers or site. Maven can then check the client's tags, pixels and conversion events, and prepare container changes for you to review. Maven never publishes a container change you haven't approved. See Review and approve staged changes.

Connect GTM#

  1. Select the client's workspace, open Sources and select Add a source.
  2. Search for Google Tag Manager and select Connect Google Tag Manager.
  3. Sign in with a Google account that has access to the client's GTM account, and approve access.
  4. When Maven lists the Account / Container options, tick every GTM container used by this workspace. All the containers share this one Google connection.
  5. Confirm your selection.

Maven asks Google for permission to read containers, edit containers and container versions, and publish. It needs these so it can stage changes in GTM and, once you approve, publish them. Approval always happens in Maven first.

If someone at the client owns the GTM account, use Copy shareable connect link and send it to them instead. See Connect a client's sources.

Connect Piwik PRO Tag Manager#

If the client uses Piwik PRO, connecting Piwik PRO also gives Maven access to its Tag Manager. There is no separate tag-manager connection.

  1. Select the client's workspace, open Sources and select Add a source.
  2. Search for Piwik PRO and connect it.
  3. Choose the client's Piwik PRO site.

Maven stages tag, trigger and variable changes in Piwik PRO Tag Manager the same way it does in GTM, and publishes only after you approve them.

After connecting#

After connecting, Maven syncs a snapshot of each container. To pull the latest version at any time, use Sync now on the source in Sources.

Check the client's tracking#

Ask from Claude, ChatGPT or another AI tool connected to Maven. If you haven't connected one yet, see Connect your AI tools.

  • For a quick health check, ask for the daily brief: "Give me today's tracking-health and budget-pacing brief for Acme." It lists tracking issues, one per pixel or event, labelled broken, degraded or stalled, with what changed and what to check. See Tracking health and the daily brief.
  • For a full review or a fix, describe the work as a tagging request, for example "Audit Acme's GTM container and fix any tags that aren't firing" or "Add a LinkedIn conversion for the demo form". Your assistant submits it with the request tool (kind: "tagging"). Maven then prepares the change, stages it, and runs QA.

Requests are processed asynchronously, so you can come back to them later. Ask your assistant for the request's status at any time.

What happens next#

When a tagging request is ready, it pauses at a review checkpoint with the staged changes and QA evidence. Nothing goes live until you approve it. Continue with Review and approve staged changes.

FAQ#

Does Maven change our GTM container without asking? No. Preparing a request stages changes and runs QA, but never authorizes publication. Only your explicit approval does.

Do we need to give Maven a GTM admin login? No. You connect with Google sign-in. You can disconnect at any time by removing the source in Sources.

Which ad platforms can Maven send conversions to server-side? Google Ads, Meta, LinkedIn and ChatGPT ads. See Server-side conversions and consent.

Last updated 2026-11-05