How to Track Conversions in GA4 (Key Events)

Okay, let’s take a breath together, because “conversion tracking” is one of those phrases that sounds far scarier than it actually is. You opened Google Analytics 4, went looking for the “conversions” you set up in the old Universal Analytics, and… they’re gone. Renamed. Rearranged. And now you’re staring at a menu wondering if you broke something. You didn’t, and figuring out how to track conversions in GA4 is far gentler than it looks. I promise.

So let me give you the honest, plain-language answer first, the kind you can act on today.

To track conversions in GA4, you collect the actions that matter as events (a purchase, a sign-up, a form submit, a call click), then you mark each of those events as a “key event” in the GA4 Admin panel — because Google renamed “conversions” to “key events” in 2024. You create those events using GA4’s automatic and enhanced measurement, a bit of gtag code, or Google Tag Manager, verify each one is firing correctly in DebugView, and (if you run ads) import them into Google Ads where they’re still called conversions. That’s the whole arc. Everything below is just us walking through it slowly so it actually sticks.

Grab something warm to sip, because we’re going to build a complete, trustworthy conversion-tracking setup from scratch — the terminology, the three setup methods, how to test without pulling your hair out, the privacy pieces you genuinely need to handle, and the small mistakes that quietly poison your data. By the end, that “conversions” menu won’t intimidate you one bit.

What does “conversion tracking” actually mean in GA4?

Let’s ground ourselves before touching a single setting, because understanding the mental model makes every step afterward feel obvious instead of arbitrary.

A conversion is simply a meaningful action you want people to take. It doesn’t have to be a sale. It can be a newsletter signup, a demo request, a completed contact form, a PDF download, a video watched to the end, a phone-number tap, or a free-trial start. You get to decide what “meaningful” means for your business — and honestly, that decision is more than half the work. If everything is a conversion, nothing is.

Here’s the piece that trips almost everyone up right now. In the old Universal Analytics you had “Goals.” When GA4 arrived, Goals became “Conversions.” Then in 2024, Google renamed conversions to key events inside GA4, while keeping the word “conversions” alive over in Google Ads. I know, I know — it’s a lot of renaming for one simple idea. So let me make it clean and quotable for you:

In GA4, a “key event” is an event you’ve flagged as important. When that same data flows into Google Ads, it’s called a “conversion.” They describe the same underlying action; the label just changes depending on which room you’re standing in.

Why does GA4 insist that everything be an event first? Because GA4’s entire foundation is different from the old page-view world. Universal Analytics thought in sessions and pageviews. GA4 thinks in events — every interaction, from a page load to a scroll to a purchase, is an event with a name and a little bundle of details called parameters. Once you internalize “in GA4, everything is an event,” the whole platform stops feeling mysterious. Conversions are just events wearing a special badge.

If you haven’t actually set up your GA4 property yet — or you’re not certain your base tracking is installed correctly — please start with our walkthrough on how to set up Google Analytics 4 first. Conversion tracking sits on top of a healthy foundation, and it’s so much less frustrating to build in the right order. That guide is the pillar this whole cluster hangs from, so it’s the natural home base.

What should you actually count as a conversion?

Before you touch any tracking code, spend ten quiet minutes deciding what deserves to be a key event. This is the strategy step everyone rushes, and rushing it is why so many accounts end up drowning in meaningless “conversions” that don’t inform a single decision.

A gentle way to think about it: work backward from money and momentum. What actions are closest to revenue, or closest to the relationship that eventually leads to revenue? Those are your true key events. Here are the usual suspects, so you can see yourself in the list:

• For an ecommerce store: purchases (the big one), plus “add to cart” and “begin checkout” as supporting signals that show you where people drop off.
• For a service business or agency: contact-form submissions, quote requests, phone-number clicks, and “book a call” completions.
• For a SaaS or app: free-trial starts, account signups, and key activation moments (like finishing onboarding).
• For a content site or creator: newsletter subscriptions, resource downloads, and maybe “read to the bottom” on a cornerstone article.

Notice I didn’t say “track every button click on your entire site.” You can, but you shouldn’t crown them all as key events. Keep your key events to the handful of actions that genuinely represent success. You can always track other events for context without marking them as key. Clarity here keeps your reports calm and your decisions sharp.

Macro versus micro conversions

One little framework that’ll serve you well: separate your macro conversions from your micro conversions. A macro conversion is the real goal — the purchase, the signed contract, the paid subscription. A micro conversion is a smaller step along the way — adding to cart, watching a demo, subscribing to your list. Both are worth tracking, but only your macro conversions usually deserve to drive your ad bidding and your headline reporting. Micro conversions are your breadcrumbs; macro conversions are the destination. Knowing which is which keeps you from optimizing your whole marketing budget toward newsletter signups when what you actually need is sales.

How do you create the event behind a conversion?

Here’s the reassuring truth: you have three routes, and you’ll often use a mix. Let’s go from easiest to most flexible, so you can stop at whichever level covers your needs.

Route 1: Events GA4 already collects for you (automatic and enhanced measurement)

GA4 is genuinely helpful out of the box. The moment your tag is installed, it starts collecting automatically collected events like first_visit and session_start without you lifting a finger. On top of that, a feature called Enhanced Measurement (you’ll find it toggled on in your data stream settings) quietly tracks things like page views, scrolls, outbound link clicks, site searches, video engagement, and file downloads.

Why you should care: some of your conversions might already exist as events and you just need to go mark them. For example, if a “file download” counts as a conversion for you and Enhanced Measurement is on, that file_download event is probably already collecting. Before you write any custom code, open your Events report and see what’s already flowing in. It’s a lovely little shortcut, and it costs you nothing to check.

Route 2: Custom events with gtag (a little code)

When the action you care about isn’t captured automatically — say, a specific “Request a Quote” button, or a purchase with its value — you can send a custom event yourself using the gtag function that comes with your Google tag. It looks roughly like this in your site’s code, fired at the moment the action happens:

• A named event, like generate_lead or sign_up or purchase.
• Optional parameters that add detail, like value and currency for a purchase, so you can measure revenue, not just count.

Google recommends using its recommended event names where one fits your action (like purchase, sign_up, generate_lead), because GA4 understands those special names and unlocks richer reporting around them. If nothing fits, you can invent your own clear, lowercase, underscore-style name — just keep it consistent and human-readable so future-you isn’t confused. The gtag route is perfect when you (or a developer) can drop a snippet at the exact moment an action completes, like on a thank-you page or inside a button handler.

Route 3: Google Tag Manager (the flexible favorite)

For most people who don’t want to edit site code every time something changes, Google Tag Manager (GTM) is the happy place. Instead of hardcoding events, you set up triggers (like “when someone clicks a button with this text” or “when the thank-you page loads”) and GTM sends the GA4 event for you — no code deploy required each time. It’s especially wonderful for tracking clicks, form submissions, and multi-step flows without bugging a developer.

GTM has a real learning curve, so I won’t cram it into a paragraph and pretend it’s simple. If this route is calling to you, walk through our dedicated guide on how to use Google Tag Manager — it’s the gentle, click-by-click companion for setting up triggers and tags properly, and it pairs perfectly with everything here.

Which route should you pick? Here’s a simple way to decide:

Your situation	Best route	Why
The action is a page view, scroll, download, or outbound click	Enhanced Measurement	It’s likely already tracked — just go mark it
You have a developer and a precise code moment (like a thank-you page)	gtag custom event	Direct, reliable, great for passing values
You want to track clicks and forms without editing code repeatedly	Google Tag Manager	Flexible triggers, no deploy each time
Ecommerce with product and revenue detail	gtag or GTM ecommerce events	Structured data for real revenue reporting

How do you mark an event as a conversion (key event) in GA4?

This is the step that turns an ordinary event into a tracked conversion, and it’s delightfully quick once the event itself exists and has fired at least once.

Here’s the walk-through, in the order you’ll actually do it:

• Fire the action once yourself. Complete the form, click the button, make a test purchase — whatever the event represents — so GA4 has seen the event name at least once. New events can take a little time to appear in the interface, so don’t panic if it’s not instant.
• Go to Admin → Events (under the property’s data display settings). You’ll see a list of every event GA4 is collecting.
• Find your event and toggle “Mark as key event.” That single toggle is the whole magic. From that moment on, GA4 counts it as a key event and starts reporting it as such.
• Prefer to set it up ahead of time? There’s also a Key events section in Admin where you can create a key event by name before it’s ever fired — handy when you know the event name in advance and want everything ready.

And that’s genuinely it. No code for this part — just a toggle. The heavy lifting was creating a clean, reliable event; flagging it as key is the easy victory lap. Once it’s marked, your key event will show up in the reports, in your Advertising workspace, and become available to import into Google Ads.

A quick word on counting and values

Two small settings worth knowing so your numbers mean what you think they mean. First, GA4 lets you choose how a key event is counted — once per event or once per session — which matters if someone might trigger the same action twice in one visit. Second, if your conversion has a monetary value (like a purchase), make sure you’re passing that value as a parameter so GA4 can report actual revenue rather than a bare count. A “purchase” with no value tells you that it happened; a “purchase” with a value tells you what it was worth. Always reach for the second one when money is involved.

How do you test conversions before trusting the data?

Please, please don’t skip this part. I’ve watched people build a whole reporting dashboard on top of an event that was firing twice, or firing on the wrong page, or not firing at all — and then make real budget decisions on numbers that were quietly wrong the entire time. Testing is the difference between data you can trust and a pretty chart built on sand.

Your best friend here is DebugView, a real-time debugging tool built right into GA4.

How to use DebugView

• Turn on debug mode for your own browsing session. If you’re using GTM, its Preview mode enables debug automatically. If you’re using gtag directly, you can enable debug with the Google Analytics Debugger browser extension or a debug configuration.
• Open Admin → DebugView in GA4. You’ll see a live timeline of events streaming in from your debug session — just yours, not your whole audience, which makes it clean and readable.
• Perform the action. Click the button, submit the form, complete the checkout. Watch for your event to appear in the timeline within a few seconds.
• Click the event and inspect its parameters. Is the name right? Are the values and currency correct? Is it firing exactly once, not three times? This is where you catch the sneaky problems while they’re still cheap to fix.

Do this for every single conversion you set up. It takes a couple of minutes per event and it will save you from the special heartbreak of discovering, a month later, that your most important number was never real. Once an event passes its DebugView check and you’ve marked it as a key event, then you can trust it. Not before.

One more reassurance: it’s normal for conversion data in your standard reports to lag by a day or so while GA4 processes it. DebugView shows you real time; the polished reports take their time. So if your test event shows up in DebugView but not yet in the main reports, that’s usually just processing, not a broken setup. Give it 24 hours before you worry.

How do you see conversions once they’re set up?

Once your key events are flowing, GA4 gives you a few lovely places to actually look at them, and knowing where to look saves so much aimless clicking.

• Reports → Engagement → Conversions (your key events report) shows each key event and how often it’s happening over time. This is your at-a-glance scoreboard.
• The Advertising section helps you see how different channels and campaigns contribute to your key events, including attribution — which touchpoints deserve credit for the conversion.
• Explorations (the free-form analysis area) let you slice conversions by any dimension you like — source, device, landing page, audience — when you want to answer a specific question like “which blog post drives the most signups?”

And here’s where conversion tracking gets truly powerful: pairing it with funnels. A single conversion number tells you how many people converted, but a funnel shows you where the others dropped off along the way — added to cart but didn’t check out, started the form but abandoned it. That “where did they leave?” insight is often worth more than the conversion count itself, because it tells you exactly what to fix. When you’re ready to see the whole journey and not just the finish line, our guide on how to set up conversion funnels in GA4 is your next stop — it’s the natural companion to everything you’ve built here.

How do you send GA4 conversions to Google Ads?

If you run paid ads, this is where all your careful tracking pays for itself. When you import a GA4 key event into Google Ads as a conversion, you let your ad campaigns optimize their bidding toward the outcomes that actually matter — real purchases and leads — instead of shallow clicks.

The high-level flow, so you know what you’re aiming for:

• Link your GA4 property to your Google Ads account in the GA4 Admin under Product Links. This connection is what lets the two platforms share data.
• In Google Ads, import your GA4 key events as conversion actions. Once linked, your marked key events become available to bring in.
• Choose which imported conversions to optimize toward. You usually don’t want every micro conversion driving your bidding — pick the macro ones that represent genuine business value.

Remember that terminology hand-off we talked about? This is where it matters in practice. What you carefully marked as a “key event” in GA4 arrives in Google Ads wearing its “conversion” name tag. Same action, same data, different room. Now your ad spend can chase real results instead of vanity clicks, which is the entire point of tracking conversions in the first place.

What about privacy and consent when tracking conversions?

This part matters, and I want to be straight with you: I’m not a lawyer, and nothing here is legal advice. But there are a few privacy principles that are just good, responsible practice — and increasingly, they affect whether your tracking even works.

Here’s the honest guidance, by function:

• Never send personally identifiable information (PII) into GA4. Google’s own policies prohibit it. That means no email addresses, names, phone numbers, or anything that identifies a specific person in your event parameters or user properties. If you need to pass along form details, strip out the personal stuff first. A conversion event should record that a lead happened and its value — not who the person is.
• Respect consent. In many regions you’re required to get a visitor’s permission before setting analytics or advertising cookies. Google offers Consent Mode, which adjusts how tags behave based on whether a user has consented — so your tracking honors their choice. If you serve visitors in regions with strict privacy laws, this isn’t optional nicety; it’s part of doing tracking properly.
• Use a consent banner that actually controls your tags. A banner that just looks pretty but doesn’t genuinely gate your analytics and ad tags isn’t doing its job. The banner and your tag setup need to be wired together so “decline” means decline.
• Be transparent in your privacy policy. Tell people what you collect and why. It builds trust, and it’s usually required anyway.

The reassuring reframe: privacy-respecting tracking and useful tracking are not enemies. You can measure conversions beautifully while never touching an individual’s personal data — because for optimization, you care about patterns and totals, not identities. Track the what, not the who, and you’ll sleep better and stay on the right side of both Google’s rules and your visitors’ trust.

What are the mistakes that quietly wreck your conversion data?

Let me hand you the bruises I’ve collected so you can skip them. These are the sneaky ones that don’t announce themselves.

• Marking too many events as key events. When everything’s a conversion, your reports turn to noise and you can’t tell what actually matters. Keep your key events few and meaningful.
• Never testing in DebugView. The single most common cause of “my numbers look weird.” An untested event is a guess, not data. Always verify before you trust.
• Double-firing events. A tag that fires twice — because it’s in two places, or a trigger is too loose — inflates your conversions and quietly lies to you. DebugView catches this if you look.
• Forgetting to pass values. Counting purchases without their value means you know how many but not how much. For anything revenue-related, always send the value and currency.
• Ignoring the processing delay. Panicking that an event “isn’t working” when it simply hasn’t finished processing into the standard reports yet. Check DebugView for real-time truth; give reports a day.
• Letting PII slip into parameters. An email address accidentally captured in a URL or form field can violate Google’s policy and your users’ trust. Audit what your events actually send.
• Setting it and forgetting it. Your site changes — buttons move, forms get redesigned, thank-you pages get renamed — and tracking silently breaks. Re-check your key events every few months, especially after a site update.

Where does social media fit into your conversion picture?

Here’s an honest boundary I want to draw clearly, because I’d rather be useful than oversell. GA4 is your tool for website and app conversions — what happens on your own property. It’s brilliant at that, and nothing here replaces it.

But a huge slice of the journey happens before someone ever lands on your site — on social media, where they first discover you, engage with your posts, and decide whether to click through. GA4 can tell you a visitor arrived from Instagram or LinkedIn, but it can’t tell you which posts earned that click, how your audience is growing, or which content is quietly driving people toward you across every network. That’s a different measurement job entirely.

This is exactly where SocialBlaze complements your GA4 setup rather than duplicating it. SocialBlaze handles the social side — scheduling and auto-publishing your posts, and giving you unified analytics across Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, and more — so you can see which content is building the audience that eventually converts on your site. Think of it as two halves of one clear picture: SocialBlaze shows you what’s working on social to bring people in; GA4 shows you what they do once they arrive. Neither replaces the other, and together they close the loop.

Let’s put the whole system together

Take a breath, because you actually have the whole thing now. Tracking conversions in GA4 isn’t one scary switch — it’s a calm, repeatable sequence. You decide what genuinely counts as success. You make sure that action exists as an event, using Enhanced Measurement, a gtag snippet, or Google Tag Manager. You test it in DebugView until you trust it. You mark it as a key event with a single toggle. And if you run ads, you link GA4 to Google Ads and import that key event so your budget chases real outcomes.

Along the way you keep your key events few and meaningful, you pass values when money’s involved, you respect consent and never touch PII, and you re-check everything after site changes so nothing breaks in silence. That’s the entire system — not flashy, but true, and true is what keeps working long after the confusing rename fades from memory.

You’ve got this. Go pick your first key event tonight, fire it once, and watch it appear in DebugView. That little moment of “oh — there it is” is where the intimidation ends and the confidence begins.