GA4 Conversion Tracking: How to Set Up Events That Match Your Business Goals

The short answer

GA4 ships with default events: page_view, scroll, click, file_download, video_engagement. Useful as a starting point, useless as a measurement strategy. The events that matter for your business (form submissions, leads, calls, signups, purchases) almost always need to be configured by you.

This post is the playbook I use to set up conversion tracking that actually maps to business outcomes, on a small or mid-sized site, without a developer team.

The mental model: events, key events, conversions

GA4 changed the vocabulary in a way that confuses everyone. Here's what the terms actually mean.

• Event. Anything tracked. A page view, a scroll, a button click, a form submission. Hundreds of events fire in a typical session. Most aren't important.
• Key Event. An event you've flagged as a meaningful business outcome. Form submits, leads, purchases. Used to be called 'Conversions' in older GA4 documentation. Functionally the same thing.
• Conversion (in Google Ads, not GA4). When GA4 sends a Key Event over to Google Ads, it shows up as a conversion there. The two terms overlap but live in different products.

The workflow: define what counts as a business outcome, fire events for those outcomes, mark them as Key Events, then verify they flow to Google Ads (and any other linked platform) correctly.

The 5-event baseline I configure on most properties

For most service businesses, e-commerce sites, and lead-driven SaaS properties, this is the baseline I set up. Adjust based on your actual conversion paths.

1. generate_lead

Fires on every form submission that captures contact info. Use the GA4 recommended event name 'generate_lead' so the data stays portable across properties and integrations. Include parameters for the form name (contact, demo request, newsletter, etc.) and a value if the lead has an estimated dollar value.

2. phone_call_click (or call_tracking_event)

Fires when a user clicks a tel: link or completes a call through a tracked phone number. If you use call tracking software (CallRail, WhatConverts, etc.), wire its webhook into GA4 so calls become events. For a small business with phone-driven conversions, this single event often represents 30-50% of total leads.

3. sign_up

Fires on account creation, newsletter signup, free trial start, or any other low-friction conversion. Distinct from generate_lead because the user isn't necessarily a sales-qualified lead, but the action is meaningful enough to track.

4. purchase

For e-commerce, fires on order completion. Include the standard GA4 e-commerce parameters: transaction_id, value, currency, items array. If your platform (Shopify, WooCommerce, etc.) has GA4 integration built in, use it. If you're hand-rolling, follow the GA4 Enhanced Ecommerce documentation. This is the highest-stakes event on any property that runs it.

5. engaged_session_qualified (custom)

A custom event for sites where the primary conversion is hard to track (long sales cycles, multi-touch B2B, etc.). Fires when a session hits a threshold of engagement: time on site over 2 minutes, 3+ pageviews including a service or pricing page. Treats meaningful exploration as a soft conversion, useful for ad bidding when no direct conversion fires.

How to wire events: GA4 directly vs. Google Tag Manager

Two main paths to fire custom events. Both work. They have different trade-offs.

Option A: GA4 directly via gtag

If your site loads the GA4 tag directly (not via GTM), you fire custom events with gtag('event', 'event_name', { ...params }). Simple. Works fine for low-complexity setups. Falls apart fast when you have multiple tracking pixels, A/B testing tools, and analytics platforms competing for tag firing.

Option B: Google Tag Manager (GTM)

GTM is a tag-management container that lets you configure tracking from a UI without code changes. For anything beyond a single GA4 setup, GTM is the right answer. Add Meta Pixel, LinkedIn Insight Tag, conversion linker, and consent management without touching your codebase.

I default to GTM on every new engagement. The learning curve is real (a day or two for a marketer with no GTM experience) but pays for itself within weeks once you stop emailing developers every time you need to add a tracking pixel.

Conversion values: when to bother, how to set them

Every Key Event can carry a value. The value flows downstream into reports, Google Ads bidding, and any platform GA4 sends data to. If you don't set values, those reports show blanks where revenue or estimated revenue should be.

• For e-commerce purchases, the actual transaction value. Easy. Fire it on order completion.
• For lead-form submissions, the estimated value of an average lead. Calculate it from your historical close rate and average deal size: (close rate) x (average deal size) = expected value per lead. Use that as the static value parameter.
• For phone calls, the same logic as leads. If 1 in 4 calls becomes a customer with an average $1,200 deal, the value per call is $300.
• For engaged_session_qualified events, leave value blank or use a small token value (like $1) to signal the event matters without inflating revenue numbers.

Common mistakes I see most often

1. 1Firing the conversion on the form page load instead of the form submission. Conversion count inflates dramatically and matches form-page traffic, which is the giveaway.
2. 2Double-counting because both the form's native event AND a custom GTM event fire on the same submission, and both are flagged as Key Events.
3. 3No conversion value set, so revenue and ROAS calculations downstream are silently empty.
4. 4Conversion values set in the wrong currency, especially on multi-region properties where GA4 reports in USD but the source value comes through in EUR or GBP.
5. 5Phone call tracking forgotten entirely on a phone-driven business. The site shows 5 form submissions a month and the team thinks marketing isn't working, when in reality 80 untracked phone calls are coming in.

Where this connects to CRO

Good conversion tracking is a prerequisite for CRO. Without it, you're optimizing on guesses. With it, you can measure whether a page change actually moved the conversion rate, by how much, and whether it sustained.

Once your events are clean and your Key Events are dialed in, the CRO beginner's guide is the natural next read.

Getting started

If you're setting up conversion tracking for the first time or cleaning up an existing setup, here's the order.

1. 1Map your business outcomes. Write down every action a user can take that matters. Form submits, calls, signups, purchases.
2. 2Pick the recommended GA4 event name for each (generate_lead, phone_call_click, sign_up, purchase, etc.). Use the official names so data stays portable.
3. 3Decide on a value for each. For lead events, calculate (close rate) x (average deal size).
4. 4Wire each event in GA4 directly or in GTM. GTM is the better default for anything beyond single-tag setups.
5. 5Test every event in DebugView. Don't flag as Key Event until you've seen it fire correctly.
6. 6Flag the events as Key Events in Admin > Events. Confirm they appear in the Key Events list.
7. 7Verify Key Events flow to Google Ads if linked. Check the conversion list in Ads, ensure the GA4 conversion appears.
8. 8If you want help setting this up the right way the first time, reach out. Conversion tracking is part of every analytics engagement I run.

A clean conversion tracking setup pays for itself ten times over in better decisions. For the outdoor and DTC brands I work with, this is usually the first thing we fix, because every paid-channel decision downstream depends on it. Sloppy tracking compounds the other way. Spend the half day to wire it correctly. The reports you build on top will actually tell the truth.

Frequently asked questions

What's the difference between an event and a Key Event?

An event is anything tracked: page views, clicks, scrolls, custom actions. A Key Event is an event you've flagged as a business outcome. Same data, different attention. Key Events are what GA4 reports on by default and what flows to Google Ads as conversions.

Should I use the recommended GA4 event names or custom names?

Use the recommended names (generate_lead, sign_up, purchase, etc.) wherever possible. They map to GA4 reports automatically and stay portable across properties and integrations. Use custom names only when no recommended name fits the action.

Do I need GTM, or can I just use GA4 directly?

Direct GA4 is fine for the simplest setups. GTM is the right answer for anything more complex, especially if you're running multiple tracking pixels, A/B testing tools, or consent management. For most businesses, GTM is worth the small upfront learning cost.

How do I track phone calls in GA4?

Two paths. The simple version: track tel: link clicks as a phone_call_click event. The accurate version: use call tracking software (CallRail, WhatConverts) that assigns a unique number per source and fires a webhook into GA4 when calls actually complete. The second approach is much more reliable, especially on mobile where users dial numbers without clicking links.

Keep reading