Google Tag Manager (GTM)

Google Tag Manager (GTM) is Google’s tag management system: it lets you set up and manage measurement and advertising code on a website or app without editing the site’s code each time. You add 2 GTM snippets to every page once, then add, change or pause tags in the Tag Manager web interface.

What is Google Tag Manager?

Once GTM is installed, your website or app can communicate with the Tag Manager servers. You build tags, set triggers that fire them when certain events happen, and create variables that simplify your configuration. The full set of tags, triggers and variables for one site or app is called a container. A container can replace all other manually coded tags on a site, including tags from Google Ads, Google Analytics, Floodlight and third parties (Tag Manager Help, Introduction to Tag Manager, accessed November 2026).

Most companies need only one GTM account, with one container per website or app. There are 5 container types: Web, iOS, Android, AMP and Server. A web container is named after the site’s top-level URL; you do not need a container for each page (Tag Manager Help, Create an account and container, accessed November 2026).

Tags, triggers and variables

Sources: About Tags, About triggers and Variables, Tag Manager Help, accessed November 2026.

Google Tag Manager vs. the Google tag (gtag.js)

The Google tag (gtag.js) is a single snippet that sends data to Google Ads and GA4, and it can only send data to Google services. To measure custom events with gtag.js, you need to be comfortable editing JavaScript on your site. GTM takes 2 snippets and manages both Google and third-party tags from its interface. Google notes that you can start with the Google tag and migrate to GTM later (Tag Manager Help, Google Tag Manager vs. gtag.js, accessed November 2026).

If you only need page views and a few Google Ads conversions, the Google tag is enough. Once you also track forms, calls, and Meta or TikTok tags, GTM saves time because you stop waiting on a developer for every change.

Preview before you publish

Preview and debug mode lets you browse your site as if the current container draft were published. The site connects to Tag Assistant, so you can see which tags fired, in what order and with what data. The debug interface appears only in the browser that enabled preview, or for people you share the preview link with; regular visitors do not see it (Tag Manager Help, Preview and debug containers, accessed November 2026).

Example: tracking a lead form with GTM (hypothetical)

A real estate project has a sign-up form that redirects to a /thank-you/ page. In GTM:

1. Create a Page View trigger where Page URL contains “/thank-you/”.
2. Attach it to 2 tags: a GA4 generate_lead event tag and a Google Ads conversion tag.
3. Click Preview, submit a test form, check that both tags show as Fired, then Publish.

Next month GA4 records 120 leads and Google Ads spends VND 36 million. CPA is VND 300,000 per lead. Without tracking, you would have no number to compare against other channels.

Frequently asked questions

If I use GTM, do I still need Consent Mode?

Yes, if your site shows a cookie consent banner. GTM is where tags live; Consent Mode controls how those tags behave before a user consents. Tag Manager Help has a whole section on managing consent with Consent Mode.

What is server-side GTM?

Besides web containers, GTM offers server containers: measurement data is processed on a server you control rather than in the user’s browser (Google for Developers, An introduction to server-side tagging, accessed November 2026). For when to switch, see our guide to server-side tracking and marketing analytics.

If you need an audit of the tags, triggers and conversions you send to Google Ads and Meta, contact Adtek.