GTM & tracking glossary

Plain-language definitions of the Google Tag Manager and analytics terms that matter for a healthy container: tags, triggers, variables, the data layer, Consent Mode v2, server-side tagging and more.

Google Tag Manager (GTM): Google Tag Manager is a free tag management system that lets you deploy and update tracking tags — analytics, advertising, and marketing scripts — on a website or app without editing the site's code each time. Tags live in a container that GTM loads on your pages.
Container: A GTM container is the bundle of all the tags, triggers, and variables for one website or app, identified by an ID like GTM-XXXXXX. Publishing a container pushes your current configuration live to every page the GTM snippet loads on.
Tag: A tag is a snippet of code GTM runs when its trigger fires — for example a GA4 event, a Google Ads conversion, or a Meta pixel. Tags are how data leaves your site for an analytics or advertising platform.
Trigger: A trigger is the condition that tells a tag when to fire: a page view, a click, a form submission, or a custom event pushed to the data layer. A tag with no trigger never runs, and a trigger scoped too broadly makes a tag fire where it shouldn't.
Variable: A variable is a reusable, named value GTM resolves at runtime — a page URL, a clicked element, a cookie, or a value read from the data layer. Variables keep configuration out of individual tags so it can be reused and changed in one place.
Data layer (dataLayer): The data layer is a JavaScript object (dataLayer) that passes structured information from your website to Google Tag Manager — page category, user status, ecommerce details, and so on. A clean, consistent data layer is the foundation of reliable tracking.
GA4 configuration tag (Google tag): The GA4 configuration tag — now called the Google tag — initialises Google Analytics 4 and sends the base configuration for a property. A healthy container has exactly one per Measurement ID; duplicates double-count your traffic.
Measurement ID: A Measurement ID (format G-XXXXXXXXXX) identifies a specific GA4 data stream — it's the ID your GA4 tags send data to. Using the wrong one, such as a development ID in production, sends data to the wrong property.
Consent Mode v2: Consent Mode is Google's framework for adjusting how tags behave based on a user's consent choices, using signals such as analytics_storage and ad_storage. Version 2 added ad_user_data and ad_personalization and is required for sites serving users in the EEA.
Consent gating: Consent gating means configuring tags to fire only when the user has granted the relevant consent, so tracking respects GDPR and ePrivacy rules. In GTM it's done with consent settings and consent-aware triggers, not by firing tags before consent is given.
Enhanced Measurement: Enhanced Measurement is a GA4 feature that automatically collects common events — page views, scrolls, outbound clicks, site searches, video engagement, and file downloads — without extra tags. Adding manual tags for the same events double-counts them.
Server-side tagging: Server-side tagging runs a GTM container in a server environment instead of the user's browser, so tag requests are processed on infrastructure you control. It improves data control, page performance, and resilience to ad blockers, at the cost of setup and hosting.
Preview mode: Preview mode (Tag Assistant) is GTM's debugging tool: it connects to your site and shows, in real time, which tags fired, which triggers matched, and what values the variables resolved to. It's the fastest way to confirm a container behaves as intended.
Workspace: A workspace is an isolated area in GTM where you make and test changes before publishing. Workspaces let several people work on the same container at once without overwriting each other.
Container version: A container version is a saved snapshot of your entire configuration. Publishing a version makes it live; keeping clear version notes is part of good governance and makes it easy to roll back a bad change.
Tag sequencing: Tag sequencing lets you specify that one tag fires before or after another — for example ensuring a configuration tag runs before the event tags that depend on it. It prevents race conditions where a tag fires before its prerequisites are ready.
Naming convention & governance: A naming convention is a consistent scheme for naming tags, triggers, and variables (for example 'GA4 - Event - Purchase'). Combined with folders and version notes, it's what keeps a container maintainable as it grows — collectively called governance.
Cross-domain measurement: Cross-domain measurement tells GA4 to treat visits across two or more of your own domains as a single session. Without it, moving between your domains creates self-referrals and splits one user journey into several sessions.
Tag redundancy: Tag redundancy is having more tags than you need doing the same job — duplicate GA4 tags, paused-but-not-deleted tags, or several tags on the same trigger. Redundancy inflates data, slows pages, and makes a container harder to maintain.
Orphaned trigger or tag: An orphaned element is a trigger attached to no tag, or a tag with no trigger. Both are dead weight: the trigger does nothing, and the tag either never fires or was left behind after a change.
Container health score: A container health score is a 0–100 measure of how clean, consistent, and correctly configured a GTM container is. Tagwise calculates one for any container you upload, so you can see at a glance whether your setup needs attention and what to fix first.

Upload your GTM export and get a professional health score in seconds. Not affiliated with Google. The assessment runs in your browser — no account needed, nothing stored.

Start free assessment