Whenever you set up GA4 or Google Ads, you inevitably encounter "Google Tag." Yet many people wonder: "How is it different from Google Tag Manager (GTM)?" or "There are so many similar-looking IDs like G-XXXXX and GTM-XXXXX that I get confused." This article clearly explains what Google Tag is, how it differs from GTM, and the specific steps for implementation.
Google Tag is a JavaScript code (script tag) that you place on your website to connect with Google services like GA4 (Google Analytics 4) and Google Ads, collecting user behavior data. It was previously known as the "Global Site Tag (gtag.js)" but was rebranded as Google Tag in 2023.
The key feature of Google Tag is its ability to manage multiple Google services through a single tag. With the old Global Site Tag, you had to write separate code for GA4 and Google Ads individually. With Google Tag, you only need to include one tag ID in the script, and subsequent service integrations can be completed through the UI in the GA4 or Google Ads management interface. This allows even non-technical staff to easily configure cross-service integrations.
Once Google Tag is installed, basic user behavior events such as page views, scrolls, outbound clicks, site search, video engagement, and file downloads are automatically collected. These work in conjunction with GA4's Enhanced Measurement feature, meaning that simply installing Google Tag correctly gives you the essential data needed for basic web analytics.
Through Google Tag, you can configure foundational measurement settings from the GA4 or Google Ads management interface, including internal traffic definitions, cross-domain measurement, referral exclusion settings, and session timeout adjustments. An important caveat: changes to Google Tag settings affect all connected Google services. For example, if you configure internal traffic exclusion in Google Tag, it will be reflected not only in GA4 but also in Google Ads data.
Google Tag and GTM (Google Tag Manager) are often confused because of their similar names, but their roles are entirely different. Understanding this distinction is the first step to building a proper measurement environment.
Google Tag is the "measurement executor" that actually collects data on your website and sends it to Google's servers. Measuring GA4 page view data or Google Ads conversion data is Google Tag's job. Google Tag can be placed directly on a website and used standalone, but it can only manage tags for Google services (GA4 and Google Ads). It cannot manage tags for non-Google tools such as Meta Ads pixels or heatmap tools.
GTM, on the other hand, is a "tag management system." Think of it as a "toolbox" that centrally manages and deploys various tags—including Google Tag, GA4, Google Ads, Meta Ads pixels, Yahoo! Ads, heatmap tools, and more. GTM itself does not have any data measurement capability. You configure Google Tag and other tags within GTM, controlling when, on which pages, and which tags should fire.
To summarize the relationship: Google Tag is "the code that actually performs measurement," and GTM is "the system that manages and deploys that code." When using GTM, you select "Google Tag" as a tag type within the GTM management interface. In September 2023, the former "GA4 Configuration Tag" in GTM was renamed to "Google Tag," so this name now appears in the GTM interface as well. If you are not using GTM, you place Google Tag's code directly in your website's HTML to perform measurement.
Multiple IDs appear around Google Tag, which is a common point of confusion. Let's clarify what each ID means.
"G-XXXXXXX" is a GA4 Measurement ID, issued when you create a GA4 data stream; passing this ID to Google Tag enables data transmission to GA4. "AW-XXXXXXX" is a Google Ads Conversion ID, issued when you create a conversion action in Google Ads. "GT-XXXXXXX" is a Google Tag-specific ID; it is issued simultaneously when you create an ID in GA4 or Google Ads and serves to manage the linking between multiple services. Finally, "GTM-XXXXXXX" is a GTM (Google Tag Manager) Container ID, issued when you create a container in GTM and included in the GTM container snippet.
A common mistake is entering "G-XXXXXXX" in the Tag ID field when configuring a "Google Tag" tag type in GTM. The correct ID to pass to the Google Tag tag type is "GT-XXXXXXX." No error is displayed at save time, and it may appear to work in the preview, but data will not be reflected in GA4. When using a GA4 Measurement ID, always double-check that you have selected the correct tag type.
There are two main methods for installing Google Tag: placing the code directly in HTML or configuring it through GTM. Let's look at the advantages and steps for each.
To place Google Tag directly in HTML, obtain the installation code from the GA4 management interface. Go to "Admin," open "Data Streams," select the target web stream, and the Google Tag script code will be displayed under "View tag instructions." Paste this code into the head element of every page on your website. After installation, verify in GA4's "Realtime" report that your access is being tracked.
This method is simple and straightforward, suitable when you only use GA4 or when your site structure is simple. However, if you plan to add Google Ads or other tags in the future, or need to manage multiple tags, GTM-based installation is recommended.
Installing Google Tag via GTM is the method officially recommended by Google. From the GTM management interface, click "Add a new tag," select "Google Tag" as the tag type, enter your GA4 Measurement ID (G-XXXXXXX) as the Tag ID, and set the trigger to "All Pages." Verify the setup in Preview Mode (Tag Assistant), and if everything works, click "Publish."
There are many advantages to installing via GTM: all tags including Google Ads conversion tags and Meta Ads pixels can be centrally managed from the GTM interface; Preview Mode allows pre-deployment verification; version control enables safe operations; and advanced measurement configurations like custom events and e-commerce tracking can be flexibly implemented. Google's official documentation also recommends GTM as the first choice for deploying measurement tags.
Direct placement works when you only use GA4 with no plans to add more services, when your site is small and tag management is simple, or when you want to avoid the learning curve of GTM. GTM-based installation is suitable for most cases: when you use Google Ads or other ad platforms alongside GA4, when tags may increase over time, when multiple people manage tags, or when you need advanced measurement like custom events or e-commerce tracking. Considering future scalability, setting up via GTM from the start is the safest approach.
There are several important considerations when installing Google Tag.
The most common issue is double-counting. If Google Tag is placed directly in HTML while also being deployed through GTM, a single page view gets counted twice. Unify your approach by using only one method. When migrating from direct HTML placement to GTM, you must remove the directly placed code from HTML at the same time you start deploying via GTM.
As mentioned earlier, Google Tag manages multiple Google services in a cross-cutting manner. Therefore, changes to Google Tag settings (internal traffic exclusion, cross-domain settings, etc.) affect all connected services. You may intend to change only GA4 settings but inadvertently impact Google Ads as well. When making changes, it is critical to determine whether you are modifying a Google Tag-level setting or a service-specific setting.
Google Tag (or the GTM container snippet) must be installed on every page you want to track. If you only install it on certain pages, access data from other pages will not be captured. When using a CMS like WordPress, use the theme's template files or plugins to ensure installation across all pages.
The predecessor of Google Tag, the "Global Site Tag (gtag.js)," was introduced in 2017. In the Global Site Tag era, code had to be written separately for each service—GA4, Google Ads, etc.—which was a high barrier for non-technical staff.
With the current Google Tag, you only need to include the tag ID in the script once, and subsequent integrations like Google Ads linking or cross-domain setup can be completed entirely through the UI in the GA4 or Google Ads management interface. This change makes it possible to configure cross-service integrations without technical knowledge. It is also designed to smoothly accommodate data quality improvements and new features. For sites that already have the Global Site Tag installed, it automatically functions as Google Tag, so no code replacement is needed.
Google Tag is the measurement code that sends data to Google services such as GA4 and Google Ads. GTM (Google Tag Manager), on the other hand, is the management system for centrally managing various tags including Google Tag. Despite their similar names, their roles are different—Google Tag is configured "inside" GTM in a parent-child relationship.
There are two installation methods: direct HTML placement and GTM-based deployment. Considering future scalability and tag management efficiency, GTM-based installation is recommended. When installing, be sure to avoid double-counting, verify the scope of setting changes, and ensure installation on all pages.
To further leverage the measurement data accurately collected through Google Tag, combine it with a cross-media analytics tool like NeX-Ray to visualize and comparatively analyze advertising performance across multiple channels—Google Ads, Yahoo! Ads, Meta Ads, and more—all in one place. Build your data-driven marketing on a foundation of accurate tag configuration.
A beginner-friendly guide to tag managers. Learn the differences between GTM (Google Tag Manager) and YTM (Yahoo! Tag Ma...
A practical guide to Tag Manager (GTM) with 5 essential tag configuration patterns: GA4 basic tracking, Google Ads conve...
A beginner-friendly guide to GTM tags, triggers, and variables. Learn the role of each component, commonly used tag type...
