How to Track Goals in GA4: Events & Key Events

Okay, let’s clear up the thing that trips up almost everyone first, because it’s the root of so much confusion: if you’re trying to figure out how to track goals in GA4 and you keep hunting for a “Goals” button like the one in the old Universal Analytics, you can stop looking. Google retired that model. In Google Analytics 4, everything is an event, and the handful of events that represent something valuable — a signup, a purchase, a lead form, a demo booked — are the ones you flag as key events (these were called “conversions” until a 2024 rename). So “tracking a goal” now means: send the event, then mark that event as a key event. That’s the whole shift in a sentence, and once it clicks, the rest gets so much calmer.

Here’s the part nobody tells you up front: the hardest thing about learning how to track goals in GA4 isn’t technical. It’s letting go of the old mental model. Once you stop looking for “Goals” and start thinking in events and key events, the tool actually becomes kind of elegant. I’m going to walk you through the whole thing the way I’d explain it to a friend over coffee — the model, the setup, how to create and mark the events you care about, how to verify they’re real, and how to do it all without stepping on anyone’s privacy. Let’s go.

Wait — why can’t I find “Goals” in GA4?

Because it isn’t there anymore, and that’s by design, not a bug you’re missing. Universal Analytics (the version Google sunset in 2023) had a dedicated “Goals” setup where you defined things like destination URLs or duration thresholds. GA4 threw that structure out and rebuilt measurement around a single unit: the event. A pageview is an event. A click is an event. A purchase is an event. Everything that happens on your site or app is an event with a name and some parameters attached.

So when someone asks how to track goals in GA4, the honest translation is: “How do I record the actions I care about as events, and then tell GA4 which of those events count as success?” That second part — flagging the valuable ones — is what key events do. And here’s a detail worth tattooing on your monitor: Google renamed “conversions” to “key events” in late 2024. If you’re reading an older tutorial that says “mark it as a conversion,” that’s the same action you now do under the label “key event.” The platform changes its vocabulary often, so always sanity-check the current wording in your own account before you follow any guide word-for-word — including this one.

How do I set up a GA4 property and data stream first?

You can’t track anything until GA4 is actually collecting data, so let’s lay the foundation. The structure goes: Account → Property → Data stream. The account is your top-level organization, the property is the specific site or app you’re measuring, and the data stream is the pipe that carries data in from a given platform (web, iOS, or Android).

Here’s the gentle walkthrough for a website:

• Create or open a property. In Admin, create a GA4 property (or pick an existing one). Set your reporting time zone and currency thoughtfully — changing them later doesn’t rewrite historical data, so get them right now.
• Add a web data stream. Under the property, add a Web data stream and enter your site URL. GA4 hands you a Measurement ID (it looks like G-XXXXXXX) and a snippet.
• Install the tag. Put the Google tag on every page — directly in your site’s <head>, through Google Tag Manager, or via your platform’s native GA4 field (WordPress, Shopify, Webflow and friends all have one). Pick one method and stick with it, so you don’t accidentally double-count.
• Confirm data is flowing. Open the Realtime report and load your site in another tab. If you see yourself show up, the stream is alive. If nothing appears after a few minutes, your tag isn’t firing — fix that before going further.

One quiet thing that matters: inside the web stream settings lives Enhanced measurement, a toggle that auto-collects a bunch of interactions for you. It’s usually on by default, and it’s the reason you already have useful events before you’ve built a single thing. Which is the perfect segue into understanding the four kinds of events you’ll be working with.

What are the four types of events in GA4?

This is the mental map that makes everything else make sense. GA4 events come in four flavors, and knowing which is which saves you from rebuilding something Google already gives you free.

• Automatically collected events. GA4 gathers these the moment the tag is installed — things like first_visit, session_start, and page_view. You don’t configure them; they just happen.
• Enhanced measurement events. Flip on that Enhanced measurement toggle and GA4 also captures scrolls, outbound clicks, site search, video engagement, and file downloads — no code required. Before you build a custom “scroll” event from scratch, check whether enhanced measurement already has you covered. It very often does.
• Recommended events. These are events with Google-defined names and parameters for common business actions — sign_up, purchase, generate_lead, login, and so on. They aren’t automatic; you have to implement them. But if you use Google’s exact naming, you unlock richer reporting and better compatibility down the road. When a recommended event fits your goal, use it instead of inventing your own name.
• Custom events. When nothing above matches what you need — say, “clicked the pricing-plan comparison” or “finished onboarding step 3” — you create a custom event with your own name and parameters.

Here’s a tiny table to keep them straight when you’re deciding how to track a goal in GA4:

Event type	Who sets it up	Reach for it when…
Automatic	GA4, on its own	Never — it’s already there (pageviews, sessions)
Enhanced measurement	You, with one toggle	You want scrolls, outbound clicks, downloads, site search
Recommended	You, using Google’s names	Your goal is a common action (sign_up, purchase, generate_lead)
Custom	You, naming it yourself	Nothing else matches your specific action

The practical rule: climb this list from the top before building anything. Reinventing an event Google already collects is the most common way people waste an afternoon here.

How do I actually create the event I want to track?

You’ve got three honest paths, and the best one depends on your setup and comfort level. None is “more correct” — they’re just different doors into the same room.

Option 1: Create an event in the GA4 interface. This is the no-code route. In Admin, under Events, there’s a Create event option that lets you build a new event out of an existing one using conditions. For example, you can say “when a page_view happens and the page location contains /thank-you, create an event called lead_submitted.” It’s perfect for destination-style goals — the GA4 equivalent of the old “thank-you page” goal — and you never touch code. The catch: it can only build from data GA4 already receives, so the underlying signal has to exist first.

Option 2: Use Google Tag Manager (GTM). If you want to fire an event on a specific button click, form submission, or scroll depth without bugging a developer every time, GTM is your friend. You set up a trigger (e.g., “click on the element with ID book-demo“) and a GA4 event tag that sends an event name and parameters when that trigger fires. GTM is the sweet spot for marketers who want control and flexibility but don’t want to redeploy the site for every change.

Option 3: Send the event with gtag in code. If you (or a developer) are comfortable in the codebase, you can fire events directly. The shape looks like this:

• gtag('event', 'generate_lead', { currency: 'USD', value: 50 });

That single line sends an event named generate_lead with a currency and a value attached. This route gives you the most precision — you control exactly when it fires and what data rides along — but it also means changes live in your deploy cycle. Choose it when the action lives deep in your app logic, like “completed checkout step 3 with these items.”

Whichever door you pick, a word on naming: be consistent and descriptive, use lowercase with underscores (book_demo, not Book Demo or bookDemo), and lean on Google’s recommended names whenever one fits. Future-you, staring at a list of 40 events, will be grateful you were disciplined now.

How do I mark an event as a key event (the “conversion”)?

This is the step that turns a plain event into a tracked goal, so let’s be precise. Sending the event just records that something happened. Marking it as a key event tells GA4, “this one matters — count it as success and surface it in the conversion-style reporting.” Here’s the walkthrough:

• Let the event fire at least once. GA4 generally needs to have seen the event before it appears in your events list. So trigger it yourself — submit the test form, click the button — and give it a little time.
• Go to Admin → Events (or Key events). You’ll see a list of every event GA4 has recorded, each with a toggle labeled Mark as key event (older screens say “Mark as conversion” — same switch).
• Flip the toggle on for the event that represents your goal. From that moment forward, GA4 counts it as a key event. Note that it generally counts going forward, not retroactively, so don’t panic that yesterday’s data looks empty.
• If the event doesn’t exist yet, you can pre-register a key event by name in the Key events section, and GA4 will start counting it once an event with that exact name arrives.

A gentle discipline note: not everything should be a key event. If you flag fifteen things as “key,” nothing is actually key, and your reporting turns to mush. Pick the few actions that genuinely represent business value — the ones you’d tell your boss about — and mark those. A tidy set of three to six meaningful key events beats a sprawling list every time. If you want the bigger-picture thinking on choosing what deserves to be measured, our guide on how to set up conversion tracking walks through the strategy side so your GA4 setup actually maps to goals that matter.

How do I add parameters and values so the data is useful?

An event that just says “it happened” is fine. An event that also says “here’s the context” is where the real insight lives. Parameters are the extra details you attach to an event, and they’re what let you slice and understand it later.

Say someone submits a lead form. The bare event generate_lead tells you a lead came in. Add parameters and suddenly you know so much more:

• value and currency — an estimated worth of that lead (e.g., value: 50, currency: 'USD'), which powers GA4’s revenue-style reporting.
• A descriptive parameter like form_location: 'pricing_page' or plan_interest: 'pro', so you can see which forms and intents drive the best leads.

Two honest caveats here. First, if you want to report on a custom parameter as a breakdown or filter, you usually have to register it as a custom dimension (for text) or custom metric (for numbers) in Admin — otherwise it’s collected but not easily visible in standard reports. Second, and this is the big one: never put personal data in a parameter. No names, no email addresses, no phone numbers, no anything that identifies a human. GA4’s terms forbid it, and it’s just the right thing to do. Send plan_interest: 'pro', never email: '[email protected]'. We’ll come back to privacy properly in a minute, because it deserves real attention.

How do I verify my event is actually tracking? (DebugView + Realtime)

Please, please don’t skip this part. The most painful analytics mistake is building a whole dashboard on an event that was quietly firing twice, or not at all. Verifying first is the difference between data you can trust and data that embarrasses you in a meeting. GA4 gives you two tools for this.

Realtime is your quick gut-check. Open the Realtime report, then go do the action on your site — click the button, submit the form. Within a few seconds you should see your event tick up in the event-count card. If it shows, the signal is reaching GA4. If it doesn’t, something upstream is broken.

DebugView is your precision instrument, and it’s wonderful. When you enable debug mode (via the GA4 Debug extension, GTM’s Preview mode, or a debug parameter), DebugView shows a live, second-by-second stream of events from your session, including every parameter attached. This is how you confirm not just that generate_lead fired, but that it fired once, with the right value and the right form_location. It’s the closest thing to watching the data with your own eyes.

Here’s a verification checklist I’d run every single time before trusting a new key event — genuinely, save this one:

• Fires at all? The event appears in Realtime or DebugView when you perform the action.
• Fires once? One action produces exactly one event — not zero, not two. Double-firing is shockingly common with layered tags.
• Right name? The event name matches exactly what you intend to mark as a key event (spelling and case).
• Right parameters? Your value, currency, and custom parameters show up with correct values in DebugView.
• Only on success? It fires on the real completion (actual form submit), not just a button hover or page load.
• Marked as key event? The toggle is on, and the event is showing up as a key event after a little data has accumulated.
• Not polluted by you? You’ve filtered or excluded internal/developer traffic so your own testing doesn’t inflate the numbers.

If every box is checked, breathe out — you’ve actually tracked your goal in GA4, verified and honest. If a box fails, fix it before you report anything. Accurate setup is the whole ballgame; a confident number built on a broken event is worse than no number at all.

Where does the data show up in reports and Explorations?

Once your key event is verified and collecting, it starts flowing into a few places — with a little patience, because standard reports typically take up to 24–48 hours to fully populate (Realtime and DebugView are the only truly instant views).

• Reports → Engagement → Events and Conversions/Key events. Here you’ll see counts for every event and a dedicated view for your key events over time.
• The Reports snapshot and Realtime cards surface key events so you can glance at momentum.
• Explorations are where GA4 gets genuinely powerful. This is a free-form canvas where you build funnels, path analyses, and segment comparisons. Want to see how many people who triggered view_pricing went on to sign_up? Build a funnel exploration. Want to know which traffic source brings the leads that actually convert? Segment it here.

If the standard reports feel overwhelming at first — and they do for everyone, you’re not alone — our walkthrough on how to read analytics reports breaks down what each view is actually telling you so you stop squinting and start understanding. And once you can read the numbers, the next skill is drawing honest conclusions from them, which is its own craft; our guide to how to interpret marketing data is the companion piece that keeps you from fooling yourself with a pretty chart.

What about attribution and lookback windows?

Here’s a nuance that quietly changes your numbers, so it’s worth understanding rather than ignoring. When a key event happens, GA4 has to decide which marketing touchpoint gets the credit. That decision is attribution, and GA4 lets you choose a model (data-driven and last-click are common options) in the attribution settings. Switch the model and the same conversions can get redistributed across channels — so if two reports disagree, check whether they’re using different attribution models before you panic.

The lookback window is the related idea: how far back GA4 looks to find the touchpoints that led to a conversion. A longer window gives more credit to earlier interactions; a shorter one favors recent ones. Neither is “right” universally — it depends on how long your buying cycle is. The honest takeaway: attribution is an interpretation, not a law of physics. Two reasonable setups can tell slightly different stories from the same events, and that’s okay as long as you know which lens you’re looking through. Don’t treat any single attributed number as absolute truth; treat it as one defensible view.

How do I handle consent and privacy the right way?

This isn’t the boring footnote — in many places it’s the law, and it’s always the decent thing to do. Tracking goals in GA4 means collecting data about real people, so let’s do it respectfully and lawfully.

• Get consent before you track, where it’s required. Under regulations like the GDPR, you generally need a lawful basis — often explicit consent — before setting analytics cookies or collecting behavioral data from visitors in those regions. A proper cookie consent banner that genuinely blocks tracking until the visitor agrees isn’t optional there; it’s the baseline. Decline-friendly by default is the respectful posture.
• Use Consent Mode. Google’s Consent Mode lets your tags adjust their behavior based on whether a visitor has consented — collecting full data when they have, and only limited, cookieless signals when they haven’t. If you operate anywhere with consent requirements, wiring up Consent Mode (usually alongside your consent-banner tool) is how you keep GA4 honest and compliant at the same time.
• Never collect PII. I said it above and I’ll say it again because it’s that important: no names, emails, phone numbers, or other personal identifiers in event parameters or user properties, ever. Beyond being against GA4’s terms, it’s a trust violation waiting to happen.
• Mind data retention and anonymization. GA4 has a data-retention setting that controls how long user-level data is kept (commonly 2 or 14 months) — set it to match your policy rather than leaving it on autopilot. Lean on built-in protections like IP anonymization/handling and only collect what you genuinely need. Less data, held for less time, is less risk.

None of this makes you track less effectively — it makes you track sustainably, without a compliance headache or a betrayed-visitor headache down the road. Good measurement and good ethics really are the same habit: taking the people behind the numbers seriously. (And a quick, honest disclaimer: I’m sharing general best practices here, not legal advice — for your specific obligations, check the current rules for your regions and, when in doubt, ask a professional.)

A quick, honest note on what GA4 does and doesn’t cover

Since we’re being straight with each other: GA4 is a website and app analytics tool. It’s brilliant for understanding how people move through your site and whether they complete the goals you’ve set up there. What it does not do is measure your performance on social platforms — your Instagram reach, your LinkedIn engagement, your TikTok views. For that you need social analytics (which is exactly what SocialBlaze is for). The two are complementary: GA4 tells you what happens when social traffic lands on your site, and a social analytics tool tells you what’s happening on the platforms themselves. Use both, and don’t expect either one to do the other’s job. Clarity about each tool’s lane saves you a lot of confused reporting.

And remember the theme that runs through this entire guide: verify the current interface yourself. Google reorganizes GA4’s menus and renames features regularly — “conversions” became “key events,” settings migrate between Admin sections, toggles move. Anything I’ve described could be labeled slightly differently by the time you read it. That’s not a reason for anxiety; it’s just the nature of a tool that evolves. Trust the model (events become key events, verify before you believe), use the current labels you see on screen, and you’ll stay oriented no matter how the furniture gets rearranged.

Frequently asked questions

Does GA4 still have “Goals” like Universal Analytics did?

No. GA4 removed the old Goals feature entirely. Instead, every action is recorded as an event, and you flag the important ones as key events (which Google called “conversions” until a 2024 rename). So the modern equivalent of setting a goal is creating the right event and then marking it as a key event in Admin.

What’s the difference between an event and a key event in GA4?

An event is any recorded interaction — a pageview, a click, a scroll, a purchase. A key event is simply an event you’ve flagged as representing business value, so GA4 counts it as success and features it in conversion-style reporting. Every key event is an event, but only the meaningful few should be marked as key events.

Why isn’t my new key event showing up in reports yet?

Usually patience or timing. Standard reports can take up to 24 to 48 hours to fully populate, and key events generally count going forward from when you flip the toggle, not retroactively. Check Realtime and DebugView for instant confirmation that the event is firing, and make sure the event name matches exactly what you marked as a key event.

Do I need Google Tag Manager to track goals in GA4?

No, it’s optional. You can create many events right inside the GA4 interface with no code, or fire them directly with a gtag call in your site’s code. Google Tag Manager is a popular middle ground that gives marketers flexible control over triggers without redeploying the site, but it’s a convenience, not a requirement.

Do I have to worry about privacy and consent when tracking in GA4?

Yes, and you should take it seriously. In many regions you need a lawful basis — often explicit consent via a cookie banner — before collecting analytics data, and tools like Google’s Consent Mode help your tags respect those choices. Never put personal data like names or emails into events, set a sensible data-retention period, and check the current rules for your regions rather than treating this as optional.