English
Deutsch
PolskiUnlike the other tools here, this one does not work on its own. It reads from the Google Tag Manager REST API v2 and therefore asks for a Google sign-in. The permission requested is tagmanager.readonly — read-only, so nothing can be changed through it.
What it fetches stays in this tab: the evaluation runs in the browser, and nothing is sent to lukaswojcik.com. The OAuth Client ID below is prefilled and can be replaced with a different one.
Connect directly to the Google Tag Manager REST API v2 using OAuth 2.0. Fetch version headers and deeply search through hundreds of container versions for tags, scripts, triggers, or variables without manual file exports.
Change history of one element: after signing in, a single tag, trigger, variable, template, folder, client, transformation or zone can be entered by name, ID or GTM URL. The tool lists every version in which it was created, changed, renamed, removed or restored, with version number, version name and notes, dates, field-by-field differences, changes to referenced triggers and variables, and unpublished changes in workspaces.
Earlier overview of the unification: Google Tag and Tag Manager Merge: Destinations, the gtm init Trigger and What the Loading ID Decides.
Background to the migration: Google Tag Manager and gtag.js Merge: What Changes in 2026. The October overview explains container optimization, gtag.config events and a controlled migration.
Update — 19.10.2026: The search covers the selected tag, trigger, variable, template and folder lists in the returned versions. It is not a search of every container-wide setting or permission. Google-delivered runtime can change without a new version; no result for gtag.config does not rule out that runtime event. The optional optimization requires a separate review of central settings and destination tags. Permissions are not versioned and are not restored by a version rollback.
October changes in context · Google release notes · Optimization and permissions