After creating a Google Tag Manager account and installing the container snippet, most beginners stare at the interface wondering what everything does. The GTM dashboard has several sections, each serving a specific purpose in the tag management workflow. This article walks through every major section so you know exactly where to go for any task.
The Workspace Overview
When you log into Google Tag Manager and select a container, you land on the Workspace Overview. This is your home base. It shows a summary of all changes you have made since the last published version.
The overview displays three counts: new tags, new triggers, and new variables added in the current workspace. If these numbers are all zero, it means either you have not made any changes yet or all changes have already been published.
The “Submit” button in the top right is how you publish changes. Nothing you configure in GTM takes effect on your live website until you submit and publish. This is a crucial safety feature. You can experiment freely knowing that nothing affects your live site until you explicitly push it.
Tags: What Gets Executed
Tags are the core of GTM. Each tag represents a piece of code that gets executed on your website. Common examples include Google Analytics tracking codes, advertising conversion pixels, and custom HTML scripts.
To create a tag, click “New” in the Tags section. You will see two areas to configure:
Tag Configuration defines what the tag does. GTM provides built-in templates for common services like Google Analytics 4, Google Ads, Floodlight, and others. For services without a built-in template, you can use the “Custom HTML” tag type to paste any JavaScript code. For more on why GTM is better than hardcoding, see our comparison.
Triggering defines when the tag fires. Every tag needs at least one trigger. Without a trigger, the tag exists in your container but never executes.
The tag editor also shows advanced settings where you can configure tag firing priority, tag sequencing (ensuring one tag fires before or after another), and consent settings for privacy compliance.
Triggers: When Tags Fire
Triggers define the conditions under which a tag should execute. They are event-based, meaning they listen for specific things happening in the browser.
GTM provides several built-in trigger types:
Page View triggers fire when a page loads. You can configure them to fire on all pages, specific pages (based on URL), or based on other conditions. This is the most common trigger type and is used for analytics tracking that should run on every page.
Click triggers fire when a user clicks an element. You can target all clicks or only clicks on links. Click triggers support filtering by element ID, class, URL, or text content, allowing you to track specific button clicks or navigation actions.
Form Submission triggers fire when a user submits a form. This is essential for tracking lead generation forms, sign-up forms, and contact forms.
Scroll Depth triggers fire when a user scrolls to a specified percentage of the page. This helps measure content engagement, distinguishing between visitors who leave immediately and those who read your entire article.
Timer triggers fire after a specified time interval. These are useful for measuring active time on page or implementing delayed actions.
Custom Event triggers fire when your website’s code pushes a specific event to the data layer. This is the most flexible trigger type and is how you track custom interactions like video plays, tab switches, or dynamic content changes.
Each trigger has conditions that determine exactly when it fires. A Page View trigger might be configured to fire only when the Page URL contains “/checkout,” ensuring the tag runs only on checkout pages.
Variables: Dynamic Data
Variables provide dynamic values that tags and triggers can use. They make your GTM setup flexible and maintainable.
GTM has two types of variables:
Built-in variables are provided by GTM and include common values like Page URL, Page Hostname, Click URL, Click Text, and Form ID. You need to enable the ones you want to use, as most are disabled by default for performance.
User-defined variables are custom variables you create. Common types include:
- Data Layer Variables that read values pushed to the data layer by your website code
- JavaScript Variables that execute custom JavaScript and return a value
- Constant Variables that store fixed values like tracking IDs, useful for referencing in multiple tags without hardcoding
- Lookup Tables that map one value to another, like mapping page URLs to custom page names
Variables become powerful when combined with triggers. Instead of creating separate tags for each page, you can create one tag that uses a variable for the page name, and the variable resolves to the correct value on each page.
Folders: Organizing Your Container
As your GTM container grows, folders help you stay organized. You can group tags, triggers, and variables into logical folders like “Analytics,” “Advertising,” “Custom Tracking,” or by business area like “Marketing” and “Engineering.”
Folders have no functional impact. They do not affect how tags fire or how triggers work. They are purely organizational, but that organization becomes essential when you have dozens or hundreds of items in your container.
Version Management
Every time you publish changes, GTM creates a new version. The Versions section shows your complete publishing history, including who published each version, when it was published, and what description was provided.
This history is your safety net. If a newly published change causes problems, you can instantly revert to any previous version. The revert takes effect immediately, no code deployment required.
Best practices for version management include writing clear descriptions for each version (not “updated tags” but “added checkout funnel tracking for Q1 campaign”), and reviewing changes before publishing by clicking into the version to see exactly what was added, modified, or removed.
Admin Settings
The Admin section manages account-level and container-level settings. Key areas include:
User Management controls who has access to your GTM account and what they can do. Permission levels range from read-only access to full publishing rights. For teams, set up appropriate permissions so marketers can create and test tags but only designated team members can publish to production.
Container Settings let you configure the container name, usage context, and additional settings.
Environments allow you to create separate versions of your container for development, staging, and production. This is valuable for testing tag configurations on non-production sites before pushing them live.
Understanding these sections gives you the foundation to use GTM effectively. The interface is designed to be navigated sequentially: create variables to hold your data, create triggers to define when things should happen, and create tags that use those variables and triggers to execute the right code at the right time. For a complete setup guide, see our GTM setup guide.
