GTM Naming Convention Generator
Build consistent naming rules for your GTM tags, triggers, and variables — then export a style guide for your team
Convention Settings
Live Preview
Tags 8
Triggers 6
Variables 8
GA4 Event Name Validator
Check if your custom event name follows GA4 requirements: snake_case, max 40 characters, starts with a letter, no reserved names.
Bulk Name Generator
Paste your raw element names (one per line) and select the type — get properly formatted names instantly.
Why Naming Conventions Matter in GTM
A GTM container with 50+ tags, 30 triggers, and 40 variables can quickly become unmanageable without consistent naming. When multiple team members contribute to the same container, naming chaos leads to duplicate tags, broken tracking, and hours wasted searching for the right element.
A well-defined naming convention acts as a shared language for your analytics team. It makes containers self-documenting, simplifies audits, and reduces errors when updating or debugging tracking setups.
Benefits of Consistent Naming
Instant Searchability
Find any tag in seconds by typing the platform name or event type. No more scrolling through hundreds of vaguely named elements.
Team Onboarding
New team members understand the container structure immediately. The convention serves as built-in documentation.
Easier Debugging
When something breaks, clear names help you trace the issue back to the right tag, trigger, or variable in minutes instead of hours.
Clean Audits
Tools like our GTM Container Linter flag naming inconsistencies. Consistent names mean cleaner audit reports.
Variable Prefix Reference
| Prefix | Variable Type | Example |
|---|---|---|
dlv | Data Layer Variable | dlv - ecommerce.value |
cjs | Custom JavaScript | cjs - getUserTimezone |
js | JavaScript Variable | js - document.title |
cookie | 1st Party Cookie | cookie - userId |
url | URL Variable | url - hostname |
const | Constant | const - GA4 Measurement ID |
aev | Auto-Event Variable | aev - Click Classes |
regex | Regex Table | regex - pageType from URL |
lookup | Lookup Table | lookup - country from hostname |
dom | DOM Element | dom - nav menu item |
GTM Naming Best Practices
- Pick one convention and stick to it across the entire container
- Include the platform/vendor as the first component of tag names
- Use descriptive prefixes for variables (dlv, cjs, cookie, etc.)
- Document your convention in a shared style guide
- Use GA4 snake_case for event names:
form_submit - Organize elements into GTM folders by vendor or function
- Mix naming styles within the same container
- Use spaces in GA4 event names (use underscores instead)
- Leave GTM default names like “Untitled Variable”
- Use abbreviations that only you understand
- Start GA4 event names with numbers or reserved prefixes
- Exceed 40 characters for GA4 custom event names
Related Articles
Frequently Asked Questions
There is no single “best” convention. The most important thing is consistency. The most popular format is [Platform] – [Type] – [Detail] with dash delimiters and Title Case. Choose a format that works for your team size and container complexity, then document it and enforce it.
No. GA4 event names must use snake_case (lowercase with underscores, e.g. form_submit). GTM element names (tags, triggers, variables) typically use Title Case with dash or pipe delimiters. They serve different purposes and have different technical constraints.
In GTM, click on any tag, trigger, or variable name to edit it inline. There is no bulk rename feature, so rename elements one at a time. Start with the most used elements first. Create a new container version after renaming to keep a clean history.
GA4 reserves certain event names including: ad_click, ad_impression, app_remove, app_store_subscription_cancel, first_open, in_app_purchase, session_start, user_engagement. You also cannot use the prefixes “firebase_”, “ga_”, or “google_” for custom events. Use the validator above to check.
Most teams use lowercase prefixes for variables (dlv, cjs, cookie) because it makes them visually distinct from the descriptive part of the name. For example, “dlv – Page Category” clearly separates the type prefix from the description. This is the approach recommended by Analytics Mania and widely adopted in the industry.
Review your convention when adding a new platform or tool, onboarding new team members, or during quarterly container audits. The convention should evolve with your needs but changes should be documented and applied consistently across existing elements.