GA4 Key Events vs Conversions: What Ecommerce Teams Should Configure in 2026

30 Sept

Google Analytics 4 (GA4) no longer uses “conversions” the way older help articles describe. Google renamed that concept to key events, and reserved conversions for actions you share with Google Ads for campaign measurement and bidding. For UK ecommerce teams, that changes what you mark in Admin, what appears in standard reports, and what you optimise paid media against.

In this blog, we’ll break down the difference, show what Shopify and ecommerce brands should configure in 2026, and flag traps that inflate revenue or starve bidding of signal.

What are key events and conversions in GA4?

A key event is any GA4 event you mark as especially important to your business. When a user triggers that event, GA4 records a key event and surfaces it in standard Analytics reports (traffic acquisition, engagement, monetisation, and so on).

A conversion, in today’s Google language, is an important action you create from Analytics data (often from a key event) so you can measure and optimise ad campaigns consistently in Google Ads and in GA4’s Advertising section. Google Ads conversions do not replace your standard GA4 reports — they sit alongside them for media performance.

In short:

Key events = “this mattered for the business” inside Analytics.
Conversions = “this mattered for Ads bidding and campaign reporting.”

GA4 automatically marks purchase as a key event. That is why ecommerce revenue can appear even before you touch Admin — provided your purchase event (and item parameters) are firing correctly.

Why the distinction matters for ecommerce

Getting this wrong usually shows up as:

Purchase tracked, micro-goals ignored — newsletter sign-ups or account creations never appear as key events.
Too many key events — noise in reports, and confused Ads optimisation if everything is also shared as a conversion.
Ads and Analytics disagree — media optimises to Ads conversions while ecommerce reads GA4 key events with no shared definition.

A clean split lets merchandising watch behaviour in GA4 while paid media bids on conversions that drive profitable orders.

What ecommerce teams should mark as key events

Start from recommended ecommerce events, then decide which ones deserve key-event status.

Usually keep as key events:

purchase (already automatic) — completed orders and revenue.
High-intent micro-goals that you actively improve, such as generate_lead, sign_up, or a custom newsletter_subscribe if that is a real growth lever.
Sometimes begin_checkout or add_to_cart — only if you use them as intentional optimisation targets (for example, a cart-recovery programme), not as vanity metrics.

Usually leave as ordinary events (not key events):

view_item, view_item_list, select_item, view_promotion — vital for product insight, rarely worth key-event volume.
Navigation and engagement spam (click, scroll, page_view).

For Google Ads conversions (built from Analytics events / key events):

Prefer purchase (and value-based bidding where possible) as the primary conversion.
Add secondary conversions carefully (for example, begin checkout) only when you have enough volume and a clear bidding strategy — secondary actions can dilute Smart Bidding if they are easier than a real sale.

Limits still apply: you can mark a limited number of additional key events per property (higher on Analytics 360). Treat that quota like shelf space — only stock what you will actually manage.

How to configure this in GA4 (practical steps)

Confirm ecommerce collection first. In Admin → Data display → Events (or your Events report), check that view_item, add_to_cart, begin_checkout, and purchase fire with value, currency, transaction_id, and an items array where required.
Mark key events. Open Admin → Data display → Events, find the event, and toggle Mark as key event. You can also mark an event as a key event before it arrives so GA4 treats it correctly from first collection.
Review key-event counting. For each key event, check whether you count once per session or every time the event fires. Purchases should align with unique transaction_id values so duplicates do not inflate revenue.
Create Ads conversions deliberately. From GA4 (or Google Ads), create conversions based on the key events you want for bidding. Manage Google Ads conversion settings carefully so primary vs secondary roles match your strategy.
Align reporting language. In team docs and Looker Studio, label columns “GA4 key events” vs “Google Ads conversions” so stakeholders stop comparing unlike numbers.

Ecommerce example: a DTC fashion brand

A UK DTC fashion brand marked add_to_cart, begin_checkout, view_item, and purchase as key events and imported them all into Ads. Campaigns chased cheap add-to-carts; reported “conversions” rose while revenue stalled.

They reset to: key events = purchase + newsletter_subscribe; Ads primary = valued purchase; Ads secondary (observation) = begin_checkout; product insight stayed in Explorations — not as key events. Bidding re-centred on revenue within weeks.

Limitations and caveats

Consent Mode and blockers still reduce observed events; Ads modelled conversions are not raw GA4 key-event counts.
Key events cannot fix a broken ecommerce dataLayer.
Document change dates when you remake key events — history will not rewrite itself cleanly.
Meta, TikTok, and affiliate “conversions” are unaffected by Google’s rename; keep those definitions separate.

Final Thoughts

In 2026, ecommerce teams should treat key events as the Analytics layer of “what success looks like,” and conversions as the Ads layer of “what we bid and report against.” Keep purchase clean, be selective with micro-goals, and only promote events to Ads conversions when they support a real optimisation strategy.

Need help aligning GA4 key events with Google Ads conversions for your Shopify or ecommerce stack? Reach out to our team at info@taggurus.co.uk or book a meeting — we’ll help you build a conversion-ready, privacy-aware setup that matches how your store actually sells.