GA4 Conversion Setup: The Complete Guide to Key Events

GA4 conversion setup starts with understanding one change: Google renamed “conversions” to “key events” in March 2024. The tracking works the same way. You mark important events as key events in your GA4 property, and those events appear in your conversion reports. The term “conversion” now only applies when a key event is imported into Google Ads for bid optimization. This guide walks you through setting up key events via the GA4 admin, Google Tag Manager, and enhanced conversions, then shows you how to verify everything in DebugView.

“The rename from conversions to key events confused a lot of teams, but the mechanics haven’t changed. What matters is that you’re tracking the 5-10 actions that actually indicate revenue, not just collecting page views and hoping the data tells a story.” Hardik Shah, Founder of ScaleGrowth.Digital

What’s the difference between key events and conversions?

A key event is any GA4 event you’ve marked as important to your business. A conversion is a key event that has been imported into Google Ads. Before March 2024, GA4 used “conversion” for both purposes, which caused confusion when GA4 conversion counts didn’t match Google Ads conversion counts. Google split the terminology to fix this.

Key event is a GA4 event marked as significant to your business. It appears in GA4 reports under the key events section and can be imported to Google Ads, where it becomes a “conversion.”

The practical impact: if you don’t run Google Ads, you only need to think about key events. The word “conversion” in your GA4 property now specifically refers to actions imported for ad campaign optimization. According to Google’s support documentation (2024), this change aligns the definition of “conversion” across GA4 and Google Ads so that both platforms report consistent numbers.

Concept	Where It Lives	Purpose	Limit
Key Event	GA4 only	Measure business-critical actions in GA4 reports	30 per property
Conversion	Google Ads (imported from GA4)	Optimize ad bidding and measure campaign ROI	No separate limit
Event	GA4	Track any user interaction (page view, click, scroll)	500 distinct names per property

You can mark up to 30 events as key events per GA4 property. That sounds like a lot, but most businesses need 8-15. If you’re marking 25+ events, you’re probably tracking micro-interactions that dilute your conversion data. Focus on actions that directly signal revenue or strong purchase intent.

How do you set up key events in the GA4 interface?

You can mark any existing event as a key event directly in GA4’s admin panel. No code required. This is the fastest method and works for events GA4 already collects (like automatically collected and enhanced measurement events) or events you’ve already set up through GTM. Here’s the step-by-step process:

1. Go to Admin > Events in your GA4 property. You’ll see the “Events” option under the “Data display” section.
2. Find the event you want to mark. The “Recent events” tab shows all events that have fired in the last 30 minutes. The “All events” list shows everything GA4 has collected. If you’re looking for form_submit or generate_lead, it needs to have fired at least once to appear here.
3. Click the star icon next to the event name. A filled star means the event is now a key event. In older documentation, this was a toggle switch labeled “Mark as conversion.”
4. Wait for data. Key event tracking only applies going forward. GA4 won’t retroactively apply the key event label to historical data. You’ll start seeing key event data within 24-48 hours.

You can also create new events directly in the GA4 interface. Go to Admin > Events > Create event. This lets you define a new event based on conditions applied to existing events. For example, you could create a qualified_lead event that fires when page_view fires on a specific thank-you page URL. Google’s in-GA Event Builder (expanded in 2025) lets you update trigger conditions, event names, and parameters without touching GTM or your site code. This method has limits. You can’t access the data layer, you can’t fire events based on element clicks, and you can’t pass custom parameters from forms. For anything beyond basic page-based conditions, use Google Tag Manager.

How do you set up conversion tracking with Google Tag Manager?

Google Tag Manager gives you full control over what fires, when it fires, and what data it sends. For most businesses, GTM is the right choice for conversion tracking because it handles click-based events, form submissions, scroll depth, and data layer interactions that GA4’s built-in event builder can’t. The process follows three steps: create a trigger, build a tag, test in Preview mode.

Step 1: Create a trigger

Triggers define when your event fires. Common conversion triggers include:

• Form submission trigger: Fires when a form is submitted. Filter by Form ID or Page URL to target specific forms. Use “Check Validation” to avoid counting failed submissions.
• Click trigger: Fires on specific button clicks. Filter by Click Text, Click URL, or Click ID. Good for “Buy Now” or “Request Demo” buttons.
• Page View trigger: Fires when a specific page loads. Use for thank-you pages or confirmation screens. Filter by Page Path containing /thank-you or /confirmation.
• Custom event trigger: Fires when your site pushes a specific event to the data layer. Use dataLayer.push({event: 'purchase_complete'}) in your site code, then trigger on that custom event name.

Step 2: Create a GA4 Event tag

In GTM, go to Tags > New > GA4 Event. Select your GA4 Configuration tag (or enter your Measurement ID directly). Set the event name using Google’s recommended naming: generate_lead for form submissions, purchase for transactions, sign_up for account creation. Add event parameters like value, currency, and any custom parameters you need.

Step 3: Test in Preview mode

Click Preview in GTM to open Tag Assistant. Navigate your site and perform the conversion action. Verify the tag fires (it’ll show under “Tags Fired” in the debug panel). Check the event parameters in the tag detail view to confirm data is correct. Once confirmed, submit and publish your GTM container version. After publishing, go back to GA4 > Admin > Events and mark your new event as a key event. The event needs to fire at least once before it appears in the events list.

What are enhanced conversions and when do you need them?

Enhanced conversions send hashed first-party customer data (email address, phone number, or mailing address) alongside your conversion events. Google matches this hashed data against its logged-in user base to attribute conversions that cookies miss. Advertisers who implement enhanced conversions typically see a 5-15% increase in reported conversions (Google, 2025).

Enhanced conversions is a GA4 and Google Ads feature that supplements standard conversion tracking by sending hashed first-party user data to improve attribution accuracy, especially for cross-device and delayed conversions.

You need enhanced conversions if:

• You run Google Ads and optimize toward conversions or ROAS targets
• Your customers research on mobile and convert on desktop (cross-device behavior)
• You operate in a market where cookie consent rates are below 70% (most of Europe)
• Your conversion window exceeds 7 days (B2B sales cycles, high-value purchases)

There are two setup methods as of 2026: Method 1: GA4 Admin panel. Go to Admin > Data Streams > your web stream. Under “Events,” you can activate enhanced conversions and configure which user-provided data fields to collect. This method works without GTM and is the fastest path for simple setups. Method 2: Google Ads Data Manager. Introduced in 2024 and fully scaled in 2025, the Data Manager lets you connect CRMs like Salesforce or HubSpot directly to Google Ads. This is the preferred method for businesses with complex CRM workflows because it handles the data hashing and matching server-side, without requiring front-end code changes. After implementation, allow 30 days before evaluating impact. The conversion model needs time to build sufficient match data. Check your conversion action table in Google Ads for a “Reporting status” of “Recording conversions” to confirm the setup is working.

Which ecommerce events should you track as key events?

GA4 has a set of recommended ecommerce events that unlock built-in reports like the purchase journey funnel, product performance, and revenue attribution. Using Google’s exact event names is critical because GA4’s ecommerce reports only populate with these specific names.

Event Name	When It Fires	Mark as Key Event?	Required Parameters
purchase	Transaction completes	Yes (always)	transaction_id, value, currency, items[]
begin_checkout	User starts checkout	Yes	value, currency, items[]
add_to_cart	Product added to cart	Optional (micro-conversion)	value, currency, items[]
view_item	Product page viewed	No	value, currency, items[]
add_payment_info	Payment details entered	Optional	value, currency, payment_type, items[]
add_shipping_info	Shipping details entered	Optional	value, currency, shipping_tier, items[]

At minimum, mark purchase and begin_checkout as key events. The purchase event is your revenue signal. The begin_checkout event lets you calculate checkout abandonment rate. If your checkout abandonment exceeds 70% (the Baymard Institute 2024 average of 70.19%), you know where to focus optimization. Every ecommerce event requires an items array with at least item_id and item_name. Without this array, GA4’s product-level reports stay empty. This is the single most common mistake in ecommerce GA4 setups.

How do you create custom events for lead gen and SaaS?

If you’re not running an ecommerce store, your conversion events won’t match Google’s recommended ecommerce names. Lead generation and SaaS businesses need custom events tailored to their funnel. The recommended approach: use Google’s recommended event names where they exist, and create truly custom events only for business-specific actions.

Lead generation events

• generate_lead (Google recommended): Fire this when a visitor submits a contact form, request-a-quote form, or demo request. Mark as key event. Pass value and currency if you assign a lead value.
• contact (Google recommended): Fire when a visitor initiates a phone call, opens a chat widget, or clicks a “Call Us” button. Mark as key event for businesses where phone leads matter.
• schedule (custom): Fire when a visitor books a meeting via Calendly, HubSpot, or similar. Not a Google recommended event, so name it with snake_case and a descriptive prefix like meeting_scheduled.

SaaS events

• sign_up (Google recommended): Fire on account creation or trial start. This is your top-of-funnel conversion.
• tutorial_complete (Google recommended): Fire when a user finishes onboarding. Tracks activation, not just registration.
• first_value_achieved (custom): Fire when a user reaches their “aha moment.” Define this based on your product’s activation metric. For a project management tool, this might be “created first project with 3+ tasks.”

Naming rules for custom events: use snake_case, start with a letter (not a number), keep names under 40 characters, and don’t prefix with ga_ or google_ (these are reserved). Bad example: FormSubmit_ContactUs_v2. Good example: contact_form_submit.

How do you debug and verify your conversion tracking?

DebugView is GA4’s real-time event inspector. It shows every event firing from a debug-mode device, including event names, parameters, and user properties. Standard GA4 reports take 24-48 hours to process, so DebugView is the only way to verify tracking immediately after setup. To enable debug mode, use one of these methods:

1. Google Analytics Debugger Chrome extension: Install the extension from the Chrome Web Store. Toggle it on, then visit your site. DebugView in GA4 Admin will start showing your events within 15-30 seconds.
2. GTM Preview mode: When you click “Preview” in Google Tag Manager, debug mode activates automatically for your browser session. Events from that session appear in DebugView.
3. URL parameter: Add ?debug_mode=true to any page URL on your site. This works without extensions and is useful for testing on mobile devices.

What to check in DebugView:

• Event appears: Does your conversion event show up when you perform the action? If not, your trigger isn’t firing.
• Event parameters: Click on the event to expand its parameters. Check that value, currency, transaction_id, and custom parameters are populated with the right values.
• Key event badge: Events marked as key events display a flag icon in DebugView. If the flag is missing, go to Admin > Events and re-check the star toggle.
• No duplicates: Verify the event fires once per action, not multiple times. Duplicate firing inflates your conversion count and corrupts ROI calculations.

After DebugView confirmation, wait 24-48 hours and check your standard reports under Reports > Engagement > Key events. If events appear in DebugView but not in standard reports, the most likely cause is a filter or data freshness delay.

What are the 8 most common GA4 conversion setup mistakes?

We’ve audited over 120 GA4 properties at ScaleGrowth.Digital. These are the mistakes that show up in more than half of them.

1. Not marking events as key events. Events fire, data collects, but nothing is marked as a key event. The conversion reports stay empty. This happens when teams set up events in GTM but forget the second step in GA4 Admin.
2. Tracking too many key events. Marking 25+ events as key events dilutes your data. Your “All key events” report becomes meaningless when it includes newsletter signups, video plays, and PDF downloads alongside purchases. Stick to 8-15 high-signal actions.
3. Missing the items[] array on ecommerce events. The purchase event fires, revenue appears in your totals, but product-level reports are empty. The items array is required for GA4 to populate ecommerce-specific reports.
4. Not passing value and currency parameters. Without value and currency on your key events, GA4 can’t calculate revenue attribution. Google Ads can’t optimize for ROAS. Always send a monetary value with your primary conversion events.
5. Duplicate event firing. A form submission fires the conversion event twice because both GA4’s enhanced measurement form tracking and a custom GTM tag trigger on the same action. Disable enhanced measurement’s form interaction tracking if you’ve built custom form tracking in GTM.
6. Ignoring Consent Mode. For businesses serving EU/EEA users, Consent Mode v2 is mandatory. Without it, you lose conversion data from users who decline cookies. With Consent Mode, Google’s behavioral modeling recovers a portion of those conversions. According to Google (2025), Consent Mode recovers an average of 65% of ad conversions that would otherwise be lost.
7. Not linking GA4 to Google Ads. Key events in GA4 don’t automatically appear in Google Ads. You need to link the accounts (Admin > Product Links > Google Ads), then import specific key events as conversions in Google Ads. Without this link, your Smart Bidding has no conversion signal.
8. Expecting retroactive data. Marking an event as a key event doesn’t apply backward. If you marked generate_lead as a key event today, you won’t see last month’s form submissions in the key events report. Set up tracking before you need the data, not after.

Pro tips from our analytics practice

• Set up a “conversion health” check in Looker Studio. Create a Looker Studio dashboard that shows daily key event counts for your top 5 conversions. If any line drops to zero, your tracking broke. You’ll catch issues in 24 hours instead of finding out at month-end.
• Use event-scoped custom dimensions for lead quality. Pass a lead_quality parameter (hot, warm, cold) or lead_source (organic, paid, referral) with your generate_lead event. Register these as custom dimensions in GA4 Admin. This lets you segment conversion data by quality, not just quantity.
• Test conversions on staging before production. Create a separate GA4 data stream for your staging environment. Verify all conversion events fire correctly there first. When you push to production, you know the tracking works. We do this for every client engagement at ScaleGrowth.Digital.
• Document your conversion map. Maintain a spreadsheet listing every key event: event name, trigger condition, expected parameters, who owns it, and when it was last verified. Without documentation, tracking breaks silently when developers ship site changes.