How to Set Up Goals in Google Analytics (GA4)

Okay, let’s be honest for a second, because you’ve probably been clicking around your Google Analytics account looking for a “Goals” button that just isn’t there. So let me give you the real answer before anything else, the kind you can act on right away.

Here’s how to set up goals in Google Analytics today: the old “Goals” feature belonged to Universal Analytics, which Google has retired. In its replacement, Google Analytics 4 (GA4), goals are now called key events. You set one up by first defining the specific action that matters to you (a sign-up, a purchase, a form submission), making sure GA4 is collecting an event for that action, and then marking that event as a key event in your Admin settings. That’s the whole shift in a nutshell. Same intention you had all along, just a new name and a slightly different, honestly more flexible, way of doing it.

And here’s the part nobody tells you: this rename trips up almost everyone, so if you felt lost, it wasn’t you. Millions of people still search for “goals” out of muscle memory, and the tutorials they find are often written for the old system that no longer exists. I promise this gets easier once you see how the new pieces fit together, and by the end of this you’ll be able to set up a key event, verify it’s actually firing, and trust the numbers you see. Let’s walk through it together.

Grab something warm to drink, because we’re going to cover the whole thing calmly: why the change happened, what events and key events actually are, the exact steps to set one up (including the two most common scenarios), how to verify it’s working, the honest mistakes to avoid, and how all of this connects to the bigger picture of measuring your marketing. No jargon dumps, no fabricated benchmarks, just a clear path. Let’s dig in.

Why can’t you find “Goals” in Google Analytics anymore?

Let’s clear up the confusion first, because it’s the root of almost every frustration here. For years, Google Analytics ran on a system now called Universal Analytics (UA), and in that world you created things called Goals — a way to tell Analytics “this specific action counts as a success.” A goal might have been reaching a thank-you page, spending a certain amount of time on site, or triggering a particular event.

Then Google introduced a completely rebuilt platform: Google Analytics 4 (GA4), which is now the standard version everyone uses. Universal Analytics stopped processing new data, so those old Goal reports are no longer being fed. GA4 isn’t a facelift of the old tool; it’s a different measurement model from the ground up. And in that new model, the concept of a “Goal” doesn’t exist by that name at all.

So when you go hunting for the Goals menu and come up empty, nothing is broken and you haven’t missed a setting. The feature was intentionally replaced. In GA4, the thing you used to call a goal is now built out of two ideas working together: events and key events. Once those two clicks into place for you, the whole system suddenly makes sense — so let’s define them clearly.

What are events and key events in GA4?

Here’s the mental shift that unlocks everything: in GA4, every single interaction is an event. A page view is an event. A click is an event. A scroll, a video play, a file download, a form submission, a purchase — all events. Where Universal Analytics organized data into categories, sessions, and goals, GA4 sees the world as a stream of events, each one describing something a person did.

That sounds like a lot, and it would be overwhelming if every event mattered equally. It doesn’t. Most events are just useful background detail. Out of that whole stream, only a handful represent the actions you genuinely care about for your business — the ones that mean “this visit was a success.” A key event is simply a regular event that you’ve flagged as especially important. That’s the entire concept. You’re not building something new; you’re pointing at an event that already exists (or that you’ve set up) and saying, “This one counts.”

One more piece of honesty about the vocabulary, because Google has shuffled it recently. The actions you mark as important used to be labeled conversions inside GA4. Google renamed that in-platform term to key events, and now reserves the word “conversion” mostly for the advertising side (the actions you optimize ad campaigns around, especially in Google Ads). For your day-to-day setup work, the term you’ll click on and configure is key event. If a slightly older tutorial tells you to “mark an event as a conversion,” it’s describing this exact same action under the previous name.

So the map is simple. Everything is an event. The important events, the ones that are effectively your old “goals,” are key events. Setting up a goal in GA4 means getting an event to exist for the action you care about, then marking that event as a key event. Let’s do exactly that.

What should count as a goal (key event) for you?

Before you touch a single setting, pause and decide what you actually want to measure. This step gets skipped constantly, and it’s the one that determines whether your data is useful or just noise. A key event should represent a real, meaningful step toward your business’s success, not just any old click.

Think in terms of the actions that genuinely move things forward for you. Depending on what you do, a worthwhile key event might be:

• A completed purchase — the classic success action for any store.
• A form submission — a contact request, a demo booking, a quote inquiry.
• A sign-up or account creation — someone starting a free trial or joining your list.
• A newsletter subscription — a person opting in to hear from you again.
• A file download — a lead grabbing your guide, pricing sheet, or brochure.
• A key page reached — landing on a “thank you” or “order confirmed” page.
• An outbound click to something that matters — tapping your booking link or app-store listing.

A helpful way to think about it: separate your macro-conversions (the big wins, like a sale or a qualified lead) from your micro-conversions (the smaller steps that lead there, like viewing a pricing page or adding to cart). You can mark several key events, so it’s perfectly reasonable to track one or two macro actions plus a couple of the micro steps that predict them. Just resist the urge to mark everything — if all your events are “key,” then none of them really are, and your reports lose their focus.

Write down your shortlist before you go further. Being deliberate here is what separates analytics that guides real decisions from a dashboard nobody looks at twice. Once you know the exact action you want to capture, you’re ready to make sure GA4 has an event for it.

How do you set up a goal (key event) in GA4, step by step?

Here’s the honest reality that trips people up: how you set up your key event depends on whether GA4 is already collecting an event for your chosen action. There are two common paths, and I’ll walk you through both. First, though, a quick note on access.

Make sure you have the right permissions

To create or mark key events, you need an appropriate role — generally an Editor (Marketer) role or above at the property level. If you don’t see the options described below, or they appear greyed out, that’s usually a permissions issue, and you’ll want whoever administers your Analytics account to grant you access. This is worth checking first so you’re not troubleshooting a “missing” feature that’s really just locked.

Path 1: The event already exists (mark it as a key event)

This is the happy path, and it’s more common than you’d think. GA4 automatically collects some events on its own, and if you have Enhanced Measurement turned on (it usually is by default), it also captures things like page views, scrolls, outbound clicks, site searches, and file downloads without any extra work. So the action you care about may already be sitting in your event list. To mark an existing event as a key event:

• In GA4, go to Admin (the gear icon).
• Under the property settings, open Events (sometimes shown as “Key events” and “Events” areas within the data-display or events section).
• Find the event that represents your action in the list of events GA4 has collected.
• Toggle the “Mark as key event” switch next to that event.

That’s it. From that moment on, GA4 will count that event as a key event and surface it in your reports as an important action. One caveat worth naming plainly: GA4 has to have seen the event at least once for it to appear in this list. If your action is brand new or rarely happens, the event might not be there yet, which leads us to the second path.

Path 2: The event doesn’t exist yet (create it, then mark it)

Sometimes the action you care about isn’t captured automatically, or you want to define it more precisely — say, only counting a form submission that lands on a specific confirmation page. In that case you create a new event first, then mark it. GA4 lets you build an event from existing events without editing your website’s code, using a feature usually labeled “Create event”:

• In Admin → Events, click Create event (or “Create custom event”).
• Give your new event a clear, descriptive name (for example, something like generate_lead or newsletter_signup — lowercase with underscores is the GA4 convention).
• Set the matching conditions that define when it should fire. A very common pattern is: when the event name is page_view and the page location contains /thank-you. That tells GA4 to create your new event whenever someone reaches your thank-you page.
• Save the event, then wait for it to fire at least once (visit the thank-you page yourself to trigger it), after which it will appear in your events list.
• Finally, follow Path 1 above: find your new event and toggle “Mark as key event.”

For more complex or precise tracking — like capturing a button click that has no page change, or passing extra detail such as a plan name or value — many people use Google Tag Manager to send a custom event to GA4, then mark that event as a key event the same way. That’s a deeper setup than we need to cover here, but it’s good to know the door is open when your needs grow. The pattern never changes: get the event to exist, then flag it as key.

Whichever path you took, don’t stop here. An untested key event is a guess, and guessing is exactly what we’re trying to leave behind. Verifying is the step that turns “I think it’s set up” into “I know it’s working.”

How do you verify your key event is actually working?

This is where careful people separate themselves from frustrated ones, so please don’t skip it. GA4 gives you a couple of honest ways to confirm your event fires before you rely on the numbers, and both are worth your five minutes.

Use DebugView for a live, precise check

DebugView (found in the Admin area) shows you events streaming in from a device you’ve put into debug mode, almost in real time and in exact detail. It’s the closest thing to watching your tracking work with your own eyes. You enable debug mode (for example, with Google’s Tag Assistant or the GA Debugger browser extension), then perform your action — submit the form, reach the thank-you page — and watch the event appear in DebugView within moments. If you see it, you know it’s firing. If you don’t, you’ve caught the problem now instead of a month from now when a report looks suspiciously empty.

Check the Realtime report

The Realtime report shows activity on your site over roughly the last half hour. Trigger your action, then look for your event (and your key event) appearing there. It’s less granular than DebugView but quick and reassuring for a sanity check. Seeing your key event tick up in real time is a genuinely satisfying little moment, and it confirms the whole chain is connected.

Give the data a little patience

One honest heads-up: while DebugView and Realtime are nearly instant, your standard GA4 reports are not. Data can take up to a day or so to fully process and appear in the regular reports. So if you set up a key event and it’s not showing in your main reports immediately, that’s usually normal processing time, not a broken setup — especially if you already saw it fire in DebugView or Realtime. Verify live first, then let the standard reports catch up. This one bit of patience saves a lot of unnecessary panic.

Because tools and menu labels in Google Analytics do get refreshed from time to time, it’s always worth confirming the exact current wording and click path in the official Google Analytics Help documentation as you go. Treat this guide as the method and the map; treat Google’s own help center as the live source of truth for any button that may have been renamed since.

What are the mistakes that quietly ruin your goal tracking?

Let me save you some of the bruises I’ve watched people collect, because these are the sneaky ones that don’t announce themselves until your data is already messy.

• Still hunting for “Goals.” The single most common one. Stop looking for the old menu; you want key events now. This alone resolves half the confusion.
• Marking everything as a key event. If ten events are all “key,” your reports lose all focus. Reserve the flag for actions that truly signal success.
• Never verifying. Setting up an event and assuming it works is how you discover, weeks later, that it never fired. Always confirm in DebugView or Realtime.
• Panicking about processing delay. Not seeing your key event in the standard reports within minutes doesn’t mean it’s broken. Check live first, then give the reports up to a day.
• Vague or duplicate event names. Names like event1 or three slightly different “signup” events make your data a puzzle. Use clear, consistent, lowercase-with-underscores names.
• Ignoring permissions. If the toggles are greyed out, you likely need a higher role. That’s a five-minute fix with whoever admins the account, not a bug.
• Forgetting the action has to fire once. An event won’t appear in your list until GA4 has actually seen it. Trigger it yourself to bring it to life.

None of these are hard to avoid once you know they exist. The theme running through all of them is the same: be deliberate about what you measure, and verify before you trust. Do that, and your key event data becomes something you can actually make decisions on.

A quick, honest word on privacy

Because you’re setting up tracking, it’s worth a genuine moment on privacy — and I want to be clear this is a practical function note, not legal advice. When you measure actions people take on your site, you’re collecting data about real humans, and that carries responsibility. Depending on where you and your visitors are, you may have obligations around consent banners, cookie choices, honoring “do not track”-style signals, and how you configure data retention and IP handling in GA4.

The healthy mindset is to collect what you genuinely need to make better decisions, be transparent about it in a clear privacy policy, and respect the choices people make. GA4 includes consent-related settings and controls precisely so you can measure responsibly. For anything touching your specific legal obligations, please talk to a qualified professional who knows your jurisdiction and business — that’s outside what any article can responsibly promise. Measure with care, and you’ll build trust as well as data.

How do key events connect to the rest of your measurement?

Setting up your first key event is a milestone, but it’s really one piece of a bigger, satisfying picture. A single key event tells you an action happened; the real magic comes when you understand it in context — and that context is what turns raw tracking into actual insight you can act on.

If you’re just getting your Analytics account off the ground, or you want to make sure the foundation under these key events is solid, start with our complete walkthrough on how to set up Google Analytics 4 — that’s the pillar this article grows out of, covering property creation, data streams, and the settings that make everything downstream work. Think of it as building the house before you decorate the rooms.

From there, two directions naturally open up. Once your key events are firing, you’ll want to see them in the fuller reporting context of your funnels and campaigns, which is exactly what our guide on how to track conversions in GA4 is built for. And if you’re ready to zoom all the way out and connect these individual actions to the metrics that actually reflect business health, our piece on how to track your marketing KPIs ties your key events into a coherent picture of what’s working. Each one builds on the setup you just completed here.

The point is that a key event isn’t the finish line — it’s the first honest data point in a system you’ll keep refining. And that system is what lets you stop guessing and start knowing.

Where does SocialBlaze fit into all this?

Let me be completely straight with you, because honesty is the whole spirit of this article: SocialBlaze is a social media management tool, not Google Analytics. It won’t set up your GA4 key events, run DebugView, or track what happens on your website — for the website side of things, GA4 (and the guides above) is exactly what you want. So why bring it up at all? Because your measurement story has two halves, and they’re better together.

GA4 answers what people do once they land on your site: which actions they take, where they drop off, which key events they complete. But those visitors arrive from somewhere, and for a huge number of businesses, social media is a major source of that warm, interested traffic. SocialBlaze lives on that side of the story — it gives you social analytics across Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Threads, Bluesky, Mastodon, Tumblr, and X, so you can see which posts are earning attention and sending people your way.

Put the two together and you get a fuller loop: SocialBlaze helps you understand and improve the social content that drives people toward your site, and GA4 tells you what those people do once they get there and complete your key events. One tool for the journey to your door, one for what happens inside. Neither replaces the other, and that’s exactly the point — honest complements, each doing the job it’s genuinely good at. Keep your social presence steady and measurable, keep your GA4 key events sharp, and you’ll finally see the whole path instead of guessing at the middle.

Let’s put it all together

So take a breath, because you actually have the whole thing now. “Goals” in Google Analytics aren’t missing — they’ve been reimagined. In GA4, the action you care about is captured as an event, and when you flag that event as important, it becomes a key event (the concept Google briefly called a conversion inside the platform). To set one up, you decide on the meaningful action, make sure an event exists for it (either one GA4 already collects, or one you create), and then toggle “Mark as key event” in your Admin settings. Then you verify it’s firing with DebugView or the Realtime report, and you give the standard reports a little patience to catch up.

None of it is flashy, but all of it is true, and true is what lets you make real decisions instead of hopeful guesses. Pick one meaningful action this week — I’d start with your single most important one, like a sign-up or a purchase — set it up as a key event, and watch it fire in Realtime. That one small win builds the confidence for all the measurement that follows. You’ve got this, and I’m genuinely rooting for you.