Markitech / Google Tag Manager AI / GTM Debugging
GTM debugging: find what broke after the last publish
Diff versions, trace the trigger chain and get a proposed fix, instead of clicking through Preview for an hour.
Updated November 4, 2026 · Markitech team
When conversions drop right after a publish, the answer is usually in the version diff: a trigger changed from a custom event to a page view, a variable path moved, or a consent setting flipped.
Markitech compares the before and after versions, lists every change, and explains which one most likely caused the drop, then prepares a workspace that restores it.
How to do it
- Identify the publish that preceded the drop.
- Diff the previous and current versions: tags, triggers, variables and consent.
- Trace the affected tag's trigger and variables against the live data layer.
- Check consent defaults and tag consent requirements.
- Prepare a fix workspace and review the diff.
- Publish after approval and confirm counts recover.
Common mistakes
- Debugging only in Preview, which misses consent and timing issues on real traffic.
- Fixing the symptom with a second tag instead of the broken trigger.
- Publishing a fix without a version note.
- Not checking downstream platforms after the fix.
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 Debugging questions
Can it roll back a version?
Markitech can prepare a workspace that restores the previous configuration, and publishes it after your approval.
Does it need site access?
No. It reads the container and platform data; the data layer itself is set by your site.