AdLintBack to Check Reference
GTM·Google Tag Manager·warning

Inconsistent Data Layer Variable Naming

Data Layer Variables in this container use mixed naming patterns. Some use `dot.notation`, others `camelCase`, others `snake_case`. The dominant pattern accounts for less than 80% of variables, which means the dataLayer is being read inconsistently across the container.

CL
By Christopher LandaverdeCreator of AdLint · ad-tech tracking specialistUpdated

Why It Matters

A consistent naming pattern for Data Layer Variables is a leading indicator of dataLayer governance discipline. When variables mix `ecommerce.value`, `ecommerceValue`, and `ecommerce_value`, three things break down. First, developers cannot predict the right path when adding a new tag and end up creating a new variable instead of reusing an existing one (see `duplicate-datalayer-paths`). Second, the dataLayer spec implied by GTM stops matching the dataLayer pushed by the site, because the site team and the GTM team have different mental models. Third, every audit takes longer because the auditor has to mentally normalize names before they can see what is actually configured. The threshold of 80% is chosen because some legacy variables will always exist; the goal is a clearly-dominant convention, not perfect uniformity.

How To Fix It

  1. Decide the canonical convention. The default in modern GTM implementations is dot-notation matching the GA4 ecommerce spec: `ecommerce.value`, `ecommerce.currency`, `ecommerce.items.0.item_id`.
  2. In GTM, open Workspace → Variables → User-Defined Variables and identify variables that do not match.
  3. For each non-matching variable, create a new variable with the canonical name and update tag references.
  4. Archive the non-matching variables once nothing references them.
  5. Document the convention in your team's GTM governance doc so new variables follow it by default.

Example

Configuration
Inconsistent:
  ecommerce.value (dot-notation)
  purchaseValue (camelCase)
  transaction_total (snake_case)

Consistent:
  ecommerce.value
  ecommerce.currency
  ecommerce.transaction_id
For Your Client Report

Data Layer Variable naming inconsistency in this GTM container. Less than 80% of variables follow a single naming convention. Industry-standard GTM governance, the dominant convention is dot-notation matching the GA4 e-commerce specification. Naming inconsistency correlates with duplicate variable creation, audit friction, and dataLayer spec drift between the site and the container. Fix: adopt the GA4 dot-notation convention, rename non-matching variables, and document the convention in team governance materials. Source: developers.google.com/analytics/devguides/collection/ga4/ecommerce.

Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.

References

  1. [1]Google Analytics 4. E-commerce events naming reference

Audit your own files for this check

AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.

Run a free audit