Revision Control¶
Revisions track versions of your Tag Manager configuration. Each revision captures the complete state of tags, rules, actions, and settings at a point in time.
How Revisions Work¶
Every Tag Manager application maintains a revision history:
- Draft revisions are editable -- you make changes here
- Finalized revisions are locked and immutable -- they serve as deployment snapshots
- Deployed revisions are the finalized revisions currently running on each environment
Creating and Editing Revisions¶
When you make changes in the Tag Manager dashboard (adding tags, modifying rules, etc.), you are working on the current draft revision.
To create a new draft revision:
- Navigate to Tag Manager > Revisions
- Click Create New Revision
- The new revision starts as a copy of the currently deployed configuration
- Make your changes
- When ready, finalize the revision to lock it
Finalizing a Revision¶
Finalizing a revision locks it so it cannot be modified. This ensures that what you test is exactly what gets deployed.
- Navigate to Tag Manager > Revisions
- Select the draft revision
- Click Finalize Revision
- The revision is now locked and ready for deployment
Finalized revisions cannot be edited
If you need to make changes after finalizing, create a new revision.
Deploying a Revision¶
To deploy a finalized revision to an environment:
- Navigate to the target Environment (e.g., Production)
- Select the finalized revision to deploy
- Click Deploy
The environment immediately begins serving the new revision's configuration.
Rollback¶
To rollback to a previous configuration:
- Navigate to the environment
- Select an earlier finalized revision from the revision history
- Deploy that revision
The rollback is instant because the previous revision's configuration is preserved and unchanged.
Revision History¶
The revision list shows:
| Column | Description |
|---|---|
| Revision Number | Sequential identifier |
| Status | Draft, Finalized, or Deployed |
| Created By | Team member who created the revision |
| Created At | Timestamp |
| Deployed To | Which environments run this revision |
Best Practices¶
- Finalize before deploying -- always finalize a revision before deploying to production
- Test in staging first -- deploy to a staging environment before production
- Keep revisions focused -- each revision should represent a logical set of changes
- Document changes -- use descriptive notes when finalizing revisions
- Don't skip rollback testing -- verify that rollback works by deploying a previous revision in staging
Continue to Team Management for managing team access and permissions in Tag Manager.