What is Google Tag Manager? A guide to tags, triggers, variables, and consent mode

Google Tag Manager is a free tag management system that allows the measurement and marketing codes (tags) added to a website to be installed and managed through a single web-based dashboard, without editing the site files each time. The container code is placed on the site once; tags such as Google Analytics 4, Google Ads conversions, or the Meta pixel are then installed, tested, and published through this dashboard.

This guide explains the tool’s basic concepts of tags, triggers, and variables, the role of the data layer, installation steps, configuring the GA4 tag, preview mode, publishing versions, consent mode, and common mistakes. In the Turkish interface, the tool is called “Google Etiket Yöneticisi”; the explanations are based on the Tag Manager Help Center.

What does Google Tag Manager do?

Google Tag Manager enables marketing and analytics teams to add tags without depending on a developer or theme files for every new measurement requirement. The Tag Manager overview pagestates that a container can replace the manually coded Google and third-party tags on a website.

In practice, this means the following: when a conversion tag is needed for a new advertising campaign, there is no need to open a theme file or install a plugin; the tag is prepared, tested, and published in the dashboard. Because all the tags are kept in one place, it is also easy to see which code is on the site and why. If a tag causes a problem, returning to the previous version takes just a few clicks.

The tool’s limitations should also be understood. Tag Manager manages measurement codes, but properly defining the events to be measured and interpreting the collected data are separate tasks. An incorrectly configured tag produces data just as misleading as faulty code added manually.

Understanding accounts, containers, and workspaces

In Google Tag Manager, the hierarchy consists of an account, a container, and a workspace. The account generally represents the company; Google’s help documentation states that a single account is sufficient for most organizations.

A container is the complete collection of tags, triggers, and variables configured for a particular website or application. A separate container is not needed for every page of the site; one container is enough for a website. The workspace is the section where changes to the container are kept in draft form. If several people work in the same container, each can use a separate workspace to work without disrupting the others’ changes.

Permissions are also assigned through this structure. Users who can add tags but cannot publish them can be defined; this keeps control of every change that goes live on the website with designated people. When working with an agency or freelancer, the container stays in the business’s account, and outside collaborators receive only the level of user access they need.

Tags, triggers, and variables: three basic concepts

The tag defines what will be done, the trigger defines when it will be done, and the variable defines which information will be used. According to Google’s triggers page, tags fire when an event occurs; the trigger monitors events such as form submissions, button clicks, or page views.

A good implementation also uses consistent naming. Tags whose names reveal their type and purpose, such as “GA4 – Event – form_gonderimi”, make maintenance easier as the container grows. Measurement IDs used repeatedly are also stored in a constant variable; if an ID changes, it can be updated in a single place.

What does the data layer (dataLayer) do?

The data layer is the JavaScript object through which the website passes information to Tag Manager in a structured and reliable way. Instead of extracting information from visible text on the page, the order value, product ID, or step completed by the user is written to this object, and variables read it from there.

The advantage of this approach is that measurement does not break when the design changes. When a button’s text or class name changes, triggers that read from the screen can stop working; events written to the data layer remain independent of the design. Platforms such as WooCommerce have plugins that pass ecommerce events to the data layer; on custom-built websites, this part is planned together with the developer.

For example, when an order is completed, the order number, total value, currency, and list of purchased products can be written to the data layer as a single event. Google Tag Manager uses a custom event trigger that captures this event to fire the GA4, Google Ads, and Meta tags simultaneously; each platform reads the information it needs from the same source. This also reduces discrepancies between the sales figures shown on different platforms.