What Are Tags in Google Analytics? A Plain-English Guide (With Steps)

The short version: "Tags in Google Analytics" almost never means what people think it means. Most of the time you're talking about Google Tag Manager tags, UTM tags on your links, or the base tracking snippet that sends data to GA4 in the first place. Learn which one you need and you'll stop wasting afternoons in the wrong settings menu.

If you want to go deeper on this: why google analytics is now called ga4.

Why this question is more confusing than it should be

I get asked this at least once a month by a client who's just been told by an agency that their "tags aren't firing" and has no idea what that means or whether it's their fault. It isn't a stupid question. Google has, over the years, used the word "tag" for at least three different things, and the interface doesn't do much to sort it out for you.

Here's the breakdown that nobody explains clearly enough:

• The GA4 tracking tag - the snippet of code (or the Google Tag Manager setup) that connects your website to your Google Analytics property in the first place.
• Google Tag Manager tags - individual pieces of tracking code that fire when something happens on your site, like a button click, a form submit, or a video play.
• UTM tags - the bits of text you add to the end of a link so Google Analytics knows exactly where a visitor came from.

Three completely different tools, one shared word. If you've been nodding along in meetings pretending you know which one someone means, you're not alone.

The GA4 tracking tag: the one everyone sets up once and forgets

This is the base layer. Without it, nothing else on this page matters, because Google Analytics never even knows your website exists. If you check what data Google Analytics collects about your visitors, all of it depends on this snippet being installed and running on every page.

There are two ways to install it:

• gtag.js directly in your site code - a chunk of JavaScript you paste into the header of every page, usually via your theme settings or a plugin.
• Through Google Tag Manager - you install one small GTM container snippet once, and then the GA4 configuration tag lives inside GTM rather than in your website code.

I push nearly every client toward the second option. Here's why, told through a real example: a coaching client I worked with in 2023 had her developer hard-code the GA4 snippet into her WordPress header.php file directly. Fine, until she wanted to add a Meta Pixel and a LinkedIn Insight tag six months later. Every single addition meant a support ticket, a wait, and a small risk of someone breaking the whole header. With GTM, she'd have added both in under ten minutes herself, no developer, no ticket, no downtime. That's not a small convenience. Over a year it was probably four or five days of her life she got back. If you're still deciding between the two, our guide on whether you need to add Google Analytics code to every page walks through the exact placement rules either way.

Running several sites? Here's how many Google Analytics accounts you can set up.

Google Tag Manager tags: the ones that do the work

This is what most people mean when a marketer or developer says "we need a new tag." Inside Google Tag Manager, a tag is a piece of code that fires under specific conditions, called triggers. The three parts work together like this:

• Tag - the code that runs (send this event to GA4, fire this ad conversion pixel, load this chat widget).
• Trigger - the condition that has to be true for the tag to fire (someone clicked a button with the class "book-call", someone scrolled 90% down the page, someone spent 30 seconds on the pricing page).
• Variable - a piece of information the tag or trigger needs, like the URL of the page, the text on a clicked button, or a form field value.

Here's a step-by-step example I set up for a client selling an online course, tracking clicks on their "Enrol Now" button:

1. In Google Tag Manager, go to Variables and turn on the built-in variable "Click Text" and "Click Classes" so GTM can see what's being clicked.
2. Create a new Trigger, type "Click - All Elements," set it to fire on "Some Clicks," and set the condition Click Text equals "Enrol Now."
3. Create a new Tag, type "Google Analytics: GA4 Event," pick the existing GA4 configuration tag, name the event something clear like enrol_button_click.
4. Attach the trigger you just built to that tag.
5. Click Preview, test it on the live site in the debug window, confirm the event fires exactly once per click, then Submit and publish the container.

That whole process took about 12 minutes the first time I did it, and about 4 minutes once I'd done it fifty times. Once it's live, that event shows up in GA4 under Reports, then Engagement, then Events, and you can build it into a conversion inside a few clicks.

The uncomfortable bit that most guides skip over: for a lot of small businesses, none of this is necessary anymore. GA4's Enhanced Measurement feature, switched on by default in every new property, already tracks page views, scrolls, outbound clicks, site search, video engagement, and file downloads automatically, without a single custom tag. I've seen agencies bill clients for £600 worth of "custom event tagging" that recreated tracking GA4 was already doing for free the moment the property was created. Before you or anyone else builds a single custom tag, check Admin, then Data Streams, then your web stream, then Enhanced Measurement, and see what's already switched on. Nine times out of ten, half the "tagging project" someone's quoting you for is redundant.

UTM tags: the ones you're probably already half-using wrong

UTM tags are the third meaning, and they're the simplest to understand but the easiest to mess up in practice. They're the little bits of text tacked onto the end of a URL, like this:

www.example.com/webinar?utm_source=linkedin&utm_medium=social&utm_campaign=january_launch

Five parameters exist: source, medium, campaign, term, and content. Source and medium are the two that change your reports, because GA4 uses them to decide which channel group a visitor lands in. Get sloppy with these and your channel data becomes useless. I've audited accounts where the same email newsletter was tagged four different ways over a year, once as "email," once as "Email," once as "newsletter," and once with no tag at all, which meant a full quarter of newsletter traffic showed up under "Unassigned" or "Direct" instead. Nobody noticed until a board report claimed email marketing was underperforming, when a third of its traffic was just mislabelled and hiding in the wrong bucket.

The fix is boring but works: build a shared spreadsheet with your exact source and medium values written down, always lowercase, no spaces, and make everyone who sends a campaign link use it. Google's own Campaign URL Builder will generate the link for you, but it won't stop someone typing "FB" one week and "facebook" the next, so the discipline has to come from your team, not the tool.

How tags connect to the reports you look at

None of this matters if it doesn't change a decision. Here's roughly how the three types feed into what you see:

• Your GA4 tracking tag determines whether you see any data at all, and it's the foundation behind figures like what Google Analytics means by "active users", since that number only exists because the base tag is sending signals every time someone opens your site.
• Your GTM tags determine which specific actions (clicks, form fills, video plays) show up as events, and which of those you can promote to Key Events (what used to be called conversions in Universal Analytics) so they surface in your main reports rather than getting buried.
• Your UTM tags determine whether the traffic driving those events gets credited to the right channel, which matters enormously if you're comparing, say, a TikTok push against a LinkedIn one. If you're chasing engagement from platforms like TikTok, it's worth reading why some TikTok accounts get more likes than others alongside your tagging setup, because none of that engagement data means anything in GA4 if the links back to your site aren't tagged consistently.

A quick word on the tools involved

Google Tag Manager is free, and you don't need a developer to run it day to day once it's installed, though I'd still get one to do the initial container install correctly. It sits alongside a handful of other tools worth knowing about, and if you're not sure which ones are worth your time versus which ones are just noise, our rundown of Google Analytics tools every business owner should know covers that ground, including which add-ons are useful and which ones just add another login to manage.

It's also worth mentioning that tagging discipline isn't unique to Google Analytics. If you run YouTube alongside your website, the same "label things consistently or your data lies to you" rule applies to YouTube channel keywords too. Different platform, same habit: whatever labelling system you build, someone on your team will eventually skip it unless it's written down somewhere everyone can see.

Common mistakes I see on real accounts

• Firing the same GA4 configuration tag twice because it's been added both directly in the site code and again through GTM, which double-counts every single pageview and quietly inflates every report by roughly double until someone catches it.
• Building custom tags for things Enhanced Measurement already tracks, wasting hours and sometimes agency fees on duplicate data.
• Never publishing the GTM container after making changes. Preview mode shows the tag working, everyone celebrates, nobody clicks Submit, and three weeks later the "fix" was never live.
• Inconsistent UTM casing, splitting one channel's traffic into three or four separate rows in reports.
• Naming events something meaningless like "Event 1" or "click_thing" instead of something you'll still understand in six months, like form_submit_contact_page.

Where to start if you've never touched any of this

If you're setting this up from nothing, here's the order that avoids the most rework:

1. Confirm your GA4 property exists and the base tag (via GTM ideally) is firing on every page, checked using GA4's Realtime report while you browse your own site.
2. Check Enhanced Measurement in your Data Stream settings and switch on the events you want, before building anything custom.
3. Write down, in a shared document, the two or three most valuable actions on your site you're not yet tracking, like a demo booking or a PDF download, and build one GTM tag for each.
4. Mark those as Key Events in GA4 so they show up front and centre in your reports rather than buried in the general Events list.
5. Standardise your UTM naming with your team before your next campaign, not after you've noticed the data's a mess.

None of this needs a developer, a big budget, or a week. It needs about two hours of focused work and a willingness to check what's already switched on before you build something new on top of it.

Related: the data analytics page.

Related reading: how many times can you take the google analytics certification exam.

Frequently asked questions

Is a Google Analytics tag the same as a Google Tag Manager tag?

No. The GA4 tracking tag is the base code that connects your site to Analytics, while a Google Tag Manager tag is one of potentially dozens of separate pieces of code, including that base connection, that fire based on specific triggers you set up.

Do I need Google Tag Manager if I already have Google Analytics installed?

Not strictly, but it makes almost everything easier because you can add and edit tags yourself without touching your website's code, which matters the moment you want to track a button click, add a Meta Pixel, or install any other marketing tool.

Why does GA4 show fewer "conversions" than I expected even though I set up tags?

This usually happens because the events were fired and recorded correctly but were never marked as Key Events in GA4's admin settings, so they're sitting in the general Events report instead of the conversions view you're checking.

What happens if I use the wrong UTM source and medium on a campaign link?

The traffic still arrives and gets counted, but it lands in the wrong channel group in your reports, which can make a working channel look like it's underperforming simply because its traffic is mislabelled somewhere else.

If you're curious about traffic quality versus traffic volume, I've covered that too.

Where to check the details

• the ICO's guidance on cookies and similar technologies