GA4 Events vs. Key Events vs. Conversions: A Clear Explanation

Google Analytics 4 is built entirely on events. Every page view, scroll, click and purchase is recorded as an event with parameters. That flexibility is powerful, but it has also created confusion, especially after Google renamed what GA4 used to call "conversions." Today, GA4 uses the term key events for the actions you mark as important in Analytics, while conversions refers to the actions counted for optimization and reporting in Google Ads. Getting this straight is the first step to clean reporting.

Events: the raw building blocks

In GA4, an event is any recorded interaction. Events come in four broad groups:

• Automatically collected events such as first_visit and session_start.
• Enhanced measurement events that you can switch on in the data stream settings, such as scrolls, outbound clicks, site search, video engagement and file downloads.
• Recommended events with names and parameters defined by Google for common scenarios, such as generate_lead, sign_up, add_to_cart and purchase.
• Custom events that you define yourself for interactions not covered elsewhere.

Each event can carry parameters: extra details such as the form name, the product category or the value of a purchase. To use a custom parameter in standard reports you generally register it as a custom dimension or metric.

Key events: what matters to your business

A key event is simply an event you have flagged as especially important. Marking an event as a key event changes how GA4 treats it: it appears in key event reporting, it can be used in attribution and path analysis, and it shows in acquisition reports as a key event count and rate.

What makes a good key event? It should represent a meaningful step toward business value. Typical examples:

• Completed purchase
• Submitted lead or demo request form
• Account or trial sign-up
• Booked appointment

Things that usually should not be key events include page views of the home page, scrolls or generic button clicks. They are useful diagnostics, but flagging them as key events inflates numbers and dilutes attribution.

Conversions: what Google Ads optimizes toward

In Google Ads, a conversion action is what bidding strategies optimize for and what campaign reports count. You can import GA4 key events into Google Ads as conversion actions, or use the Google Ads tag directly. Either way, the Ads side decides which actions are "primary" (used for bidding) and which are "secondary" (observed only).

This separation is helpful once you understand it. Analytics can track a broader set of key events for analysis, while Google Ads bids only on the most valuable actions. A newsletter sign-up might be a key event in GA4 but a secondary action in Ads, so it does not pull bidding toward cheaper, less valuable outcomes.

Side-by-side comparison

Why the numbers rarely match

It is normal for GA4 key event counts and Google Ads conversion counts to differ, even for the same underlying action. Common reasons include:

1. Attribution model and scope. Ads credits conversions to ad clicks and, depending on settings, views; GA4 reports can apply different models and include all channels.
2. Date attribution. Ads reports conversions on the date of the ad interaction, while GA4 typically reports on the date of the event itself.
3. Counting method. Ads can count one or every conversion per click; GA4 key events can be configured to count once per event or once per session.
4. Consent and modeling. Each product models unobserved conversions in its own way.
5. Lookback windows. Conversion windows set in Ads may differ from GA4's attribution settings.

Rather than forcing them to match, decide which source answers which question, and reconcile both against your own backend order or CRM data at regular intervals. Our attribution and measurement guide covers this.

Designing a clean event plan

A written measurement plan prevents most GA4 messes. Keep it in a shared spreadsheet with these columns:

• Event name (use recommended names where possible, lowercase with underscores)
• Trigger description (what exactly causes it to fire)
• Parameters and their expected values
• Key event? (yes/no, with reasoning)
• Imported to Ads? Primary or secondary?
• Owner and date added

Naming conventions

GA4 event names are case-sensitive, so Form_Submit and form_submit become two separate events. Pick one convention and document it. Prefer one event with a descriptive parameter (generate_lead with form_name) over a separate event for every form.

Values

Wherever possible, send a value and currency with key events. Even an estimated value for leads, agreed with sales, lets you compare channels by value rather than by raw counts.

Track broadly, flag narrowly: many events, few key events, fewer primary conversions.

Testing before you trust

Use GA4's DebugView and your tag manager's preview mode to confirm that each event fires once, with the right parameters, under the right conditions. Check what happens when consent is declined. After launch, compare daily counts with backend data for a week before relying on the numbers in reports or bidding. Teams considering more robust collection may also want to read about server-side tagging concepts.

A quick audit of an existing property

If you inherited a GA4 property, open the events report and sort by event count. Look for near-duplicates with different capitalization, events that fire on every page view, and key events that do not represent real business value. Then check which key events are imported into Google Ads and which are set as primary. Cleaning up even a few of these issues usually makes reporting noticeably clearer.

Quick FAQ