Markitech / Google Tag Manager AI / GTM Publishing Workflow
A GTM publishing workflow with approvals built in
Every publish shown as a readable diff, approved before it goes live, and checked after.
Updated November 4, 2026 · Markitech team
Most tracking incidents are self-inflicted: someone publishes a workspace with unrelated changes or no notes, and nobody notices until the numbers move.
Markitech works in named workspaces, shows the full change list in plain language, publishes only after approval, and checks key events after the publish.
How to do it
- Create a named workspace per change.
- Make changes and generate a readable change list.
- Review and approve in chat.
- Publish with a version name and notes.
- Check key events and conversions after publish.
- Keep a history of what changed and why.
Common mistakes
- Publishing the Default Workspace with leftover edits.
- Versions with no names or notes.
- No post-publish check of conversions.
- Many people publishing without a review step.
Ask Markitech
Related questions
Key terms
Approved by you, every time
Markitech proposes each change in chat and holds it until you approve. Nothing is published, created or changed in your accounts without that approval.
Part of the Google Tag Manager AI guide.
GTM Publishing Workflow questions
Can anyone on my team approve?
Approvals happen in your Markitech account; nothing is published without an explicit approval.
Does it support server containers?
Yes, the same workflow applies.