GTM Naming Convention Violations
Why It Matters
Naming conventions are governance, not configuration. And governance is what separates a container that can be audited in 30 minutes from one that takes a day. The most widely-adopted convention in the GTM community uses prefix-based naming: tags as <Platform> - <Event> (e.g. GA4 - Purchase, Google Ads - Lead), triggers as <Type> - <Description> (e.g. Custom Event - purchase, Click - CTA Button), and variables as <Type> - <Source> (e.g. DLV - ecommerce.value, CJS - User Agent). The benefit is searchability: filtering by GA4 - shows every GA4 tag instantly, and the same prefix tells reviewers what platform owns the data. AdLint flags this check when more than 40% of tags, triggers, or variables deviate from a detectable convention. Not because the names are "wrong," but because inconsistency is a leading indicator of governance issues that show up later as duplicate tags, conflicting triggers, and audit findings that take longer to remediate than they should.
How To Fix It
Pick a convention. The default in the GTM community:
<Platform> - <Event>for tags,<Type> - <Description>for triggers,<Type> - <Source>for variables. Write it down in a one-page document.Rename existing tags in batches by platform. Start with the most-modified tags (typically GA4 and Google Ads). Renaming is non-destructive in GTM. Version history preserves the old name.
After renaming, update related triggers and variables to follow the same convention.
For larger containers, consider creating a Naming Convention workspace solely for renames so the audit trail is clean.
Publish, then re-run AdLint to confirm the finding clears.
Document the convention in your team's GTM governance doc so new tags follow it by default.
Example
Inconsistent:
GA4 Event
ga4-purchase
Purchase (GA4)
Consistent:
GA4 - Page View
GA4 - Purchase
GA4 - Add to CartThat more than 40% of tags, triggers, or variables in this GTM container do not follow a detectable naming convention. While GTM does not enforce names, inconsistent naming is the highest-correlated indicator of governance debt that produces downstream duplicate tags, conflicting triggers, and prolonged audit cycles. Industry-standard GTM governance recommends prefix-based naming (e.g. <Platform> - <Event> for tags). Fix: adopt and document a naming convention, rename existing assets in batches, and treat naming as a publish-gating governance check. Source: support.google.com/tagmanager/answer/6103693.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.