GTM Naming Conventions: Best Practices for Clean Containers | Adslytics | Adslytics

Google Tag Manager Setup & Audit How-To Guide

GTM Naming Conventions That Keep Your Container Sane

By Muhammad Farooq · January 16, 2026 · 6 min read
GTM Naming Conventions That Keep Your Container Sane

Why Naming Matters More Than You Think

A Google Tag Manager container with poor naming is a maintenance nightmare. When a tag is named "New Tag 4" or a trigger is called "Page View - Test", nobody knows what it does, whether it is still needed, or whether it conflicts with other tags. Multiply this across 50+ tags in a live account and debugging becomes extremely difficult.

A consistent naming convention is one of the most impactful quality improvements you can make to any GTM container — and it costs nothing but a few minutes of thought upfront.

The Core Pattern: [Type] - [Platform] - [Description]

The most widely adopted GTM naming format uses three segments separated by dashes:

  • [Type]: the category of the object (what kind of tag, trigger, or variable it is)
  • [Platform]: the platform or tool it sends data to (GA4, GADS, Meta, etc.)
  • [Description]: what it specifically does in plain language

Tag Naming Examples

Abbreviate the type as a prefix:

  • Tag - GA4 - Configuration
  • Tag - GA4 - Event - Purchase
  • Tag - GA4 - Event - Form Submission
  • Tag - GADS - Conversion - Lead Form
  • Tag - GADS - Remarketing
  • Tag - Meta - Pixel - Purchase
  • Tag - Meta - Pixel - Lead
  • Tag - LinkedIn - Insight Tag

Trigger Naming Examples

  • Trig - Pageview - All Pages
  • Trig - Pageview - Thank You Page
  • Trig - Event - Purchase
  • Trig - Event - Form Submitted
  • Trig - Click - CTA Button - Homepage
  • Trig - Scroll - 50 Percent
  • Trig - Timer - 30 Seconds

Variable Naming Examples

  • Var - DLV - Transaction ID (Data Layer Variable)
  • Var - DLV - Transaction Value
  • Var - DLV - Currency
  • Var - Cookie - GCLID
  • Var - JS - Page Path
  • Var - LT - Event Category Lookup (Lookup Table)
  • Var - Constant - GA4 Measurement ID

Tags With Exceptions or Variants

When a tag has an exception or is a variant of another:

  • Tag - GA4 - Event - Scroll 50pct - Blog Pages Only
  • Tag - GADS - Conversion - Purchase - Ecommerce
  • Tag - Meta - Pixel - ViewContent - Product Pages

Handling Multiple Accounts or Brands

If managing multiple websites or brands in one GTM account:

  • Tag - GA4 [BrandA] - Configuration
  • Tag - GA4 [BrandB] - Configuration

Additional Best Practices

  • Use title case consistently (not mixed case or all-lowercase)
  • Abbreviate platforms consistently: GA4, GADS, Meta, LI (LinkedIn), TT (TikTok), MS (Microsoft)
  • Add a note in the Description field of every tag explaining its purpose, date added, and who added it
  • Include version number in your GTM version names after publishing (e.g. "v1.4 - Added enhanced conversions")

Summary

A consistent naming convention makes your GTM container self-documenting and dramatically reduces time spent debugging or onboarding new team members. Establish your convention at the start of a project and enforce it with a simple style guide shared with all contributors.

For a fully organised GTM container audit, see our Google Tag Manager Setup and Audit service.

Need your GTM container cleaned up and documented? Contact Adslytics.

Need expert tracking setup?

Our Google Tag Manager experts have delivered 500+ tracking setups with a 98% success rate.

Get a Free Consultation →
← Back to Blog
Muhammad Farooq

Author

Muhammad Farooq GTM & Analytics Expert · Adslytics Founder

Tracking specialist with 10+ years of experience in Google Tag Manager, GA4, Server-Side Tracking, and Google Ads. Founder of Adslytics — a dedicated analytics agency with a 98% success rate across 232+ projects on Upwork.

Top Rated Plus LinkedIn Visit the author's profile →