Version history · free

Every tag change, on the record.

Every create, edit and delete is recorded with who, when and what changed. Revert a bad edit or restore a deleted tag exactly as it was.

the problem

Why this breaks today.

✗

Nobody knows who changed the pixel.

When conversions drop, the first question is what changed. In a shared tag setup there is usually no answer.

✗

Deleted means gone.

Remove a tag by mistake and you are rebuilding it from memory, hoping you got the ID, the trigger and the consent category right.

how it works

How TracerKit handles it.

✓

A revision for every change.

Creating, updating, deleting or restoring a tag writes a revision: the user, the time, and the fields that changed, from the script source to its trigger and consent category.

✓

One-click revert.

Roll a tag back to any earlier revision. The rollback is itself recorded, so the history stays honest.

✓

Restore deleted tags.

A deleted tag keeps its history. Bring it back exactly as it was, configuration included.

questions

Asked and answered.

Is version history on the free plan?+

Yes. It is part of the Loader tier, alongside the tag manager itself.

What exactly is versioned?+

The tag's name, type, source or inline code, attributes, load strategy, placement, trigger and its config, consent category and the event it's expected to fire.

How is this better than tags in git?+

Git history only helps if someone notices the change. A merge that drops a tag looks like any other diff. Here a delete is an explicit, attributed action you can undo.

the terms behind it

more of what you get

Stop guessing whether your tracking works.

Tag management is free forever. Paid tiers start with a 14-day trial, no card.