The New Google Tag Explained Simply: What It Is and Why It Replaces Old gtag
7 min read · AstraLoop Studio
Open the Admin section of Google Analytics or Google Ads and you'll find an entry called "Google tag." Or maybe a consultant told you to "install the Google tag," and you wondered: is that the same as the old Analytics code? Is it Google Tag Manager? Do you need to remove what you already have?
Fair questions, because Google has changed the rules. The Google tag is the unified version of the old gtag.js (the "global site tag"), and it changes how your site talks to Google's products. Here it is with no unnecessary jargon, aimed at the practical needs of anyone running a small or mid-sized business: what changes, and how to manage multiple destinations with a single tag.
What the Google tag is, in plain terms
The Google tag is a single snippet of code you place on your site once, and it can send data to multiple Google products at the same time: Google Analytics 4, Google Ads, Campaign Manager 360, Merchant Center. Previously, every product wanted its own piece of code. Now one is enough.
Technically, it's still the gtag.js library: the name "Google tag" is how Google unified and rebranded that mechanism. What changes is the logic, not the nature of the thing: one single tag, identifiable by an ID that starts with G-, AW-, or GT-, acting as the single entry point for measurement.
What changes compared to the old gtag
Here's the difference that matters: before, to add a new product (say, Google Ads conversion tracking alongside Analytics) you had to go into the site's code and paste a second snippet. Now you add a "destination" from the interface, without touching the site at all.
| Aspect | Old approach | Unified Google tag |
|---|---|---|
| Code on the site | One per product | A single, reusable one |
| Adding a product | Edit the site's code | Add a destination from the interface |
| Risk of double counting | High (duplicate tags) | Reduced |
| Consent management | Fragmented, tag by tag | Centralized on the tag |
| Who can make changes | Needs a developer | Marketing can often handle it |
Less code scattered around means fewer errors, fewer duplicate tags, and more solid tracking. And solid tracking is the condition for everything else to work: without clean data, tracking conversions becomes a pointless exercise, and campaigns end up optimizing against the wrong signals.
Careful: the Google tag is NOT Google Tag Manager
This is the most common misunderstanding, and it's worth clearing up right away since the names sound alike.
- Google tag (gtag.js): this is the tag itself. A single piece of code that creates a direct channel between your site and Google's products. Its IDs start with G-, AW-, or GT-.
- Google Tag Manager (GTM): this is a system for managing tags. A container (ID starting with GTM-) from which you deploy and update many different tags, including third-party ones (for example, the Meta pixel), without touching the code every time.
In practice: the Google tag is a single tool, GTM is the control room. If you already use Google Tag Manager, you generally don't need to paste the gtag.js by hand, because you manage it from inside GTM. If you have a simple setup with few tags, the Google tag on its own can be enough.
One tag, multiple destinations: how it actually works
The key concept of the new model is the destination. A destination is an account on a Google product that shares configuration with your tag and receives its data. Today there are four possible destinations:
- a Google Analytics 4 web data stream;
- a Google Ads account;
- a Floodlight configuration (Campaign Manager 360 and Display & Video 360);
- a Merchant Center conversion source.
A concrete example. You've installed the GA4 tag (ID G-XXXX) and now want to track Google Ads conversions. You don't install a second code: you add the Google Ads account as a destination of the tag that's already there. From that moment on, the same snippet on the site sends data to both Analytics and Ads.
The ID prefixes tell you where the tag comes from:
| ID prefix | Where it comes from | What it's for |
|---|---|---|
| G- | Google Analytics 4 | Measures site traffic |
| AW- | Google Ads | Tracks advertising conversions |
| GT- | "Native" Google tag | Generic multi-product tag |
| GTM- | Google Tag Manager | A container, not a tag (see above) |
| DC- | Floodlight | Display and video campaigns (CM360 and DV360) |
One useful heads-up: when you change the Google tag's settings, the change applies to all connected destinations. Handy, but worth keeping in mind if you share the same tag across different projects or accounts.
Where you manage it and what you can configure
The Google tag is managed from the interfaces of the products that use it: Google Analytics, Google Ads, and Campaign Manager 360. In GA4 you'll find it in Admin, inside the web data stream settings ("Google tag settings"). From there, without touching the code, you can:
- add or remove destinations;
- configure domains for cross-domain measurement;
- define internal traffic to exclude and unwanted referrals;
- adjust session duration;
- manage consent signals.
The consent piece in particular is decisive today: if you advertise to users in the European Economic Area, the tag is where you connect the Consent Mode v2 signals. And if you're starting your measurement from scratch, it's worth laying solid foundations: here's how to set up GA4 from scratch without skipping steps.
If your tracking is a patchwork of tags added over the years and you're not sure the data is clean, tell us about it: we'll tell you what to fix to get reliable conversions flowing into campaigns and your CRM.
Why this matters if you run a small or mid-sized business
It's easy to think this is a technical detail. In reality, how the tag is installed decides the quality of the data your whole marketing runs on. Three concrete reasons.
1. Fewer errors, more reliable data
A single tag reduces the classic problems: conversions counted twice, events that never fire, pages with no tracking at all. Wrong numbers lead to wrong decisions about where to put your budget.
2. Campaigns that optimize better
Google Ads' automated strategies (Smart Bidding) learn from the conversion data the tag sends. If the signal is clean and complete, the algorithm pushes toward the right audience. You can strengthen it with enhanced conversions, which use first-party data to recover conversions that would otherwise be lost.
3. The bridge to actual sales
The tag isn't the finish line. It's the first link in a chain that, if built well, reaches all the way to the CRM. You can feed offline CRM conversions back into Google Ads (a closed deal, a signed quote), so the algorithm optimizes not for clicks but for real customers. That's how tracking becomes part of a true customer acquisition system, not just a visit counter.
How to install it: three ways
- By hand in the code: paste the snippet into the header of your site or theme. Suited to those with code access and a simple setup.
- Through the platform: many CMSs and e-commerce platforms (WordPress, Shopify, and similar) have a field where you paste the ID, or a dedicated integration, with no file editing required.
- Through Google Tag Manager: you use the "Google Tag" tag inside GTM. This is the recommended route if you manage multiple tags or want to centralize everything in one interface.
For high volumes or precision and privacy needs, there's also server-side tracking, which moves data collection to an intermediary server. It's a more advanced level, but worth knowing about once tracking becomes strategic.
Common mistakes to avoid
- Double tagging: having the gtag.js snippet pasted by hand and the same ID loaded via GTM. Result: everything counted twice.
- Installing a second code for Google Ads instead of adding it as a destination to the GA4 tag that's already there.
- Ignoring consent: without Consent Mode configured, data from Europe stays incomplete.
- Mixing up GTM- with G-: they're different things, and combining them creates setups that don't work.
- Not verifying: after installation, always check with Tag Assistant or the real-time preview that the tag actually fires.
In short
The Google tag retires the "one code per product" logic. One snippet, one ID, multiple destinations managed from the interface: fewer errors and more reliable data for Analytics, Google Ads, and everything else. It isn't Google Tag Manager (that's the control room), and it doesn't replace your cookie banner: it's the channel that carries data into the Google ecosystem. If you want the full picture, start from our complete guide to conversion tracking, of which this article is one piece.
Frequently asked questions
Are the Google tag and Google Tag Manager the same thing?
No. The Google tag (gtag.js) is a single tag that sends data to Google, with an ID starting with G-, AW-, or GT-. Google Tag Manager is a system for managing multiple tags from one interface, with an ID starting with GTM-. If you use GTM, you typically deploy the Google tag from within it.
Do I need to remove the old gtag.js or the global site tag?
If you already have a working tag with a single ID, it has often been updated automatically to the new logic. What matters is not having the same ID loaded twice (for example, by hand and via GTM), since that causes double counting.
What do the G-, AW-, and GT- prefixes mean?
They indicate where the tag originated: G- from Google Analytics 4, AW- from Google Ads, GT- is the generic Google tag format. GTM-, on the other hand, is the Tag Manager container, which is a different thing.
Can I use a single tag for Analytics and Google Ads?
Yes, and that's the main advantage. You add the Google Ads account as a destination of the GA4 tag that's already installed, and the same code sends data to both, without pasting a second snippet onto the site.
Does the Google tag handle cookie consent?
The tag is where you connect consent signals (Consent Mode v2), but it doesn't replace the banner or the consent management platform (CMP). You still need a solution to request and record user consent.
Is it better to install it by hand or with Google Tag Manager?
For simple setups, installing by hand or through your CMS works fine. If you manage multiple tags, including third-party ones, or want to change configurations without touching the code, it's worth moving to Google Tag Manager.
Want tracking that actually fuels campaigns and sales instead of giving you random numbers? Request an analysis of your setup and let's see together where to start.