English
Deutsch
PolskiSave tool
Paste a GTM JSON export to audit tag and trigger naming conventions. Supported prefixes: [GA4], [FB], [GTM], [AW], [UET], [Custom].
GTM Naming Convention Auditer
Articles that explain this
OTHER TOOLS
- GTM Container History & Deep Search Engine
- GTM Duplicates Analyser
- GTM DataLayer Variable Path Flattener
- GA4 Event Parameter Generator
- DataLayer Inspector & Validator
- Server-Side GTM – Cloud Run Cost Estimator
- JSON Beautifier
- Text & Code Diff
- GA4 gcd Parameter Decoder
- DateConverter – Unix Epoch Timestamp & ISO
RELATED ARTICLES
- Tutorial: Agreeing a GTM Naming Convention and Enforcing It on an Existing Container
- Tutorial: Finding the Container Version in Which a Tag Changed
- Tutorial: Turning a Nested dataLayer Object Into Durable GTM Variables
- Google Tag and Tag Manager Merge: Destinations, the gtm init Trigger and What the Loading ID Decides
- GTM Integrations for Claude Code: Three MCP Servers, Their Tool Count and Their Context Cost
- GA4 E-Commerce Enhanced Tracking in SPAs without DataLayer Race Conditions
- gtag(‘set’) in practice: handing a User ID to a Google tag that has already loaded
- Tutorial: Migrating E-Commerce Analytics from Client-Side to Server-Side GTM
- Tutorial: Using Claude Code to Prepare and Review Google Tag Manager Changes
- Server-Side GTM on GCP Cloud Run: Architecture, Auto-Scaling, and Cost Optimization