weballin DIGIWIKI
Clear explanations of SEO, AI search, content, advertising and analytics, with practical context.
19 terms
Tagging/tracking
Google Tag Manager is a tag management system that allows marketers to directly add, edit, and version manage tags such as GA4, Google Ads, and remarketing pixels without distributing developer code. It consists of three elements: tag, trigger, and variable, and speed and data quality can be improved with a server-side container.
Tagging/tracking
In GTM, a tag is a unit that defines 'what to execute'. When trigger conditions are met, tasks such as sending GA4 events, tracking Google Ads conversions, and calling Meta pixels are performed. Most marketing tools can be added without code using Google's official templates and community templates.
Tagging/tracking
A trigger defines ‘when to execute a tag’ in GTM. Precisely control when tags are fired by combining event types (pageview, click, form submission) and filter conditions (specific URL, CSS class, data layer value). Accurately designing filters is the key to data accuracy.
Tagging/tracking
GTM variables read or calculate values for tag parameters and trigger conditions. They include built-in and user-defined types.
Tagging/tracking
The data layer is a JavaScript object (array) that structures and delivers web page events, products, and user data to GTM and GA4. The developer generates an event with dataLayer.push(), and GTM connects this data to the tag and delivers it to GA4 and advertising pixels.
Tagging/tracking
A data-layer variable reads a specified value from GTM’s data model for use in a tag or condition.
Tagging/tracking
dataLayer.push adds events and data for GTM to process.
Tagging/tracking
The GTM container is the highest management unit that contains tags, triggers, and variables. When one snippet code (GTM-XXXXXX) is inserted into the site, all settings in the container are applied. There are web container (client side) and server container (server side) types, and it supports version management and rollback.
Tagging/tracking
GTM Preview tests workspace changes before publication and shows event-level tags and values in Tag Assistant.
Tagging/tracking
Tag Assistant is Google's official tool that automatically diagnoses the installation status and errors of Google tags (GA4, GTM, Google Ads) on web pages. There are two methods: a web version (tagassistant.google.com) and a Chrome extension, and tag firing in real time are checked in conjunction with the GTM preview session.
Tagging/tracking
Google tag is an integrated tag that connects all Google tools such as GA4 and Google Ads with one snippet. As an evolution of the existing gtag.js, when you use GA4 configuration tags in GTM, Google tags work internally. ‘Integrating the Google ecosystem with one tag’ is the core goal.
Tagging/tracking
gtag.js is an official JavaScript library that is inserted directly into HTML to transmit data to Google tools such as GA4 and Google Ads. This is a method where the developer manages tags directly with code without GTM, initializing them with gtag('config', 'G-XXXXXXXX') and sending events with gtag('event', ...).
Tagging/tracking
GA4 Configuration tag is the name of a former GTM tag type. It was replaced by the Google tag in 2023, and existing configuration tags were upgraded automatically. Check current setups using the Google tag terminology.
Tagging/tracking
A GA4 event tag in GTM configures an event name, parameters, destination, and firing conditions.
Tagging/tracking
A Custom HTML tag executes HTML and JavaScript through GTM. Review the vendor code and firing conditions before using it.
Tagging/tracking
A custom event trigger fires GTM tags when a data-layer event and its conditions match.
Tagging/tracking
Cross-domain measurement connects GA4 journeys as users move between domains.
Tagging/tracking
Server-side tagging processes incoming data in a server container and forwards it to configured destinations.
Tagging/tracking
Client-side tagging runs tags in a user’s browser and sends data to measurement services. Collection depends on implementation, consent state, browser behavior, and network conditions.