gtm-diff

GTM drift detection compares your current live container state against a previously logged implementation baseline. This read-only diff surfaces any added, deleted, or modified elements across your tags, triggers, and variables to highlight unauthorized changes.

Auditing GTM changes before implementation involves running a diff against your last known baseline. This generates a report highlighting contextual modifications, additions, and deletions across tags, triggers, and variables to guide safe deployments.

Yes, you need an existing gtm-implementation-log.json file as a baseline to compare your live GTM container state against. Without this logged implementation record, there is no reference point to detect drift or generate a diff report.

Yes, performing a GTM container diff is strictly a read-only operation. It requires valid GTM API credentials to analyze the live state but makes absolutely no changes to your container, only generating a report of detected drift.

Container drift in Google Tag Manager happens when elements like tags, triggers, or variables are added, deleted, or modified outside your last logged implementation. It surfaces unauthorized or untracked changes that occurred between audits or deployments.