GA4 Conversion Tracking: What Businesses Actually Need to Measure

Events and key events

In GA4, every action is an event. Not every event is a conversion. GA4 calls conversions key events. The distinction matters because key events are what flow into your conversion reports and what you can import into Google Ads. Marking too many events as key events dilutes your conversion data.

A good rule is to mark an event as a key event only if it represents a real business outcome. Page scrolls, video plays and outbound clicks are events worth collecting for context, but they are not conversions.

Lead generation measurement

For a lead business, the key events are usually form submission and phone call of meaningful duration. Everything else is supporting context. If you mark a button click as a key event, your conversion reports fill with clicks that never became leads.

Form submissions

Track form submissions as a dedicated event, not as a generic page view of a thank you page. Send the event through the data layer after the form validates so it only fires on real submissions. Include details like form ID or form name as parameters so you can compare forms later.

Calls

If you use call tracking, send a call event with the call duration as a parameter. Set your key event to fire only when the call exceeds a threshold that means a real conversation. Short or abandoned calls should be events for context, not conversions.

Ecommerce actions

For an online store, GA4 ecommerce tracking covers the full funnel: view item, add to cart, begin checkout and purchase. The purchase event is the key event. The earlier steps are events that show where the funnel leaks, but they should not be marked as conversions.

• view_item and add_to_cart show interest and where people drop off.
• begin_checkout shows intent to buy.
• purchase is the only ecommerce key event for most stores.

Purchases

The purchase event should carry transaction ID, value and currency at minimum. The transaction ID is what lets you deduplicate against other platforms like Meta. Without it, the same order can be counted multiple times across your stack.

Meaningful business actions

The test for whether something is a key event is simple. Would you change your marketing spend based on this action alone? If yes, it is a key event. If it only provides context, leave it as an event. This keeps your conversion reports focused on what drives decisions.

Micro actions vs real conversions

Micro actions like email signups, brochure downloads or account creations can matter, but they are not the same as a sale or a qualified lead. Track them as events and review them in exploration reports. Resist the urge to mark them as key events unless you genuinely optimize for them.

Event naming

Use clear, consistent event names. GA4 has recommended events for common actions like purchase and generate_lead. Sticking to these makes reporting and imports easier than inventing custom names. If you do use custom names, document them so the setup stays understandable over time.

Data quality

GA4 data quality depends on the events being sent correctly. Test each key event in debug mode and confirm it appears with the right parameters. A purchase event missing its value is far less useful than one sent correctly, and you may not notice the gap until you try to report on revenue.

Avoiding unnecessary event tracking

Every event you add is more data to maintain and more chances for something to break. Start with the few events that map to real outcomes and add more only when you have a specific question to answer. Tracking everything up front usually means none of it is trustworthy.