GA4 Renamed Your Conversions to Key Events — Did Your Reporting Break?
Quick Answer: GA4 renamed all conversions to key events in March 2024 while Google Ads kept its own conversions metric — creating a terminology split that silently breaks cross-platform reporting (Google, 2024). Looker Studio dashboards referencing the old metric show blanks. WooCommerce tracking plugins still say ‘conversions’ when they mean key events. Year-over-year comparisons require manual remapping. The fix is auditing your GA4 property, updating report dimensions, and verifying Google Ads conversion imports pull from the correct source.
In this article
- Did GA4 rename conversions to key events?
- What is the difference between GA4 key events and Google Ads conversions?
- Why do my GA4 and Google Ads conversion numbers not match?
- How does the key events rename affect WooCommerce tracking plugins?
- Did the key events rename break year-over-year GA4 reporting?
- How should WooCommerce stores reconfigure after the key events change?
- Should I mark all GA4 events as key events?
- Does server-side tracking handle the key events rename automatically?
Did GA4 rename conversions to key events?
Yes — GA4 renamed all conversions to key events in March 2024 (Google, 2024), but Google Ads kept its own “conversions” metric with a completely separate definition. The same purchase event now has a different name in each platform, even though both track the same underlying action.
The rename wasn’t cosmetic. Google separated the concepts because GA4’s analytics-side measurement and Google Ads’ campaign-side optimisation serve different purposes. A GA4 key event tracks whether something important happened on your site. A Google Ads conversion tracks whether an ad drove a specific business outcome. Same event, different counting logic, different names.
For WooCommerce store owners who’d spent years building dashboards, importing GA4 data into Google Ads, and training teams on a shared vocabulary, the rename broke assumptions that were baked into every layer of their reporting stack. The terminology split means “conversions” now refers to Google Ads only — and saying it in a GA4 context points to a metric that no longer exists.
GA4 renamed all conversions to key events in March 2024 while Google Ads kept its own conversions metric — creating a cross-platform terminology split that breaks shared reporting (Google, 2024).
What is the difference between GA4 key events and Google Ads conversions?
GA4 key events are analytics-side metrics counting user interactions you’ve marked as important, while Google Ads conversions are campaign-side metrics used for bidding optimisation — they count the same event differently by design (Google, 2024).
GA4 key events use data-driven attribution across the entire user journey within GA4’s lookback window. Google Ads conversions use the attribution model and conversion window configured in your Google Ads account — typically last-click within 30 days for search campaigns. The same purchase, attributed by two different models, produces two different numbers.
Counting method adds another layer. GA4 can count one key event per session or every occurrence. Google Ads counts one conversion per click or every conversion per click, depending on your setting. A customer who buys twice in one session from one ad click might show as one GA4 key event and two Google Ads conversions — or the reverse, depending on configuration.
Related: GA4 Key Events vs Google Ads Conversions: Why Your Numbers Never Match
Why do my GA4 and Google Ads conversion numbers not match?
GA4 key events and Google Ads conversions use different attribution models, different counting windows, and different deduplication logic — and since the rename, they’re no longer even called the same thing (Google Ads Help, 2024). Cross-platform reporting dashboards break silently when they try to compare what look like the same metric.
Before the rename, store owners could at least point to “conversions” in both platforms and understand they were measuring the same concept even if the numbers differed slightly. Now the concept itself is split. GA4 reports key events. Google Ads reports conversions. A dashboard that pulls both into one table is comparing metrics with different names, different definitions, and different counting rules.
The practical impact is decision-making confusion. A WooCommerce store sees 85 key events in GA4 and 112 conversions in Google Ads for the same week. Which one is right? Neither is wrong — they’re measuring differently. But without understanding why the numbers diverge, store owners either distrust their data entirely or pick the higher number to feel better about performance.
How does the key events rename affect WooCommerce tracking plugins?
Many WooCommerce tracking plugins still reference “conversions” in their GA4 configuration interfaces and documentation, confusing store owners on 43.5% of the web’s websites that run WordPress (W3Techs, 2024) into thinking their plugin sends GA4 conversions when the platform now calls them key events.
The plugins still work — the underlying event structure hasn’t changed. A purchase event fired by a WooCommerce tracking plugin arrives in GA4 exactly as it did before. But the plugin’s settings page says “conversion tracking” while GA4 calls it “key event tracking.” Store owners looking at the plugin, then at GA4, see different language and wonder whether something is misconfigured.
Documentation compounds the problem. Tutorials written before March 2024 walk store owners through “setting up conversions in GA4” — steps that no longer match the current interface. The GA4 admin panel now says “key events” where it used to say “conversions,” and every pre-rename tutorial, video, and support thread is now technically incorrect.
Related: GA4 Renamed Conversions to Key Events and Your WooCommerce Tracking Plugin Did Not Update
Did the key events rename break year-over-year GA4 reporting?
Yes — Looker Studio reports built before March 2024 that reference the “conversions” metric now show blanks or zeros for post-rename data, and 56% of businesses still use single-touch attribution models with legacy reporting setups vulnerable to exactly this breakage (CaliberMind, 2025).
The issue is metric continuity. Pre-rename data used the “conversions” dimension. Post-rename data uses “key events.” A Looker Studio chart tracking monthly conversions over 18 months shows a solid line through February 2024, then drops to zero — not because conversions stopped, but because the metric name changed and the report didn’t.
Fixing it requires editing every Looker Studio report, Data Studio connector, and BigQuery query that references the old metric. For a store with three or four custom dashboards, that’s an afternoon. For a store that hasn’t touched its reporting setup since initial configuration, it’s an unpleasant surprise when the Q4 year-over-year comparison comes back showing a 100% drop in “conversions.”
Looker Studio reports referencing the old conversions metric show blanks for post-March 2024 data — year-over-year comparisons require manually remapping to key events (Google, 2024).
How should WooCommerce stores reconfigure after the key events change?
WooCommerce stores should audit their GA4 property to confirm purchase events are marked as key events, update Looker Studio reports to use the key events metric, and verify that Google Ads conversion import pulls from the correct source (Google Analytics Help, 2024).
Start with the GA4 property. Open Admin → Key Events and confirm that purchase, add_to_cart, and begin_checkout are listed. If they show as regular events, toggle them to key events — otherwise they won’t appear in your key events reports or be importable into Google Ads.
Next, check your Looker Studio reports. Any chart or scorecard referencing the “conversions” metric needs updating to “key events.” Create a calculated field that merges pre-rename and post-rename data for year-over-year continuity if historical comparison matters.
Finally, verify the Google Ads link. In Google Ads, navigate to Goals → Conversions → Summary and confirm the imported GA4 key events are mapped correctly. If you’re importing from GA4, the conversion actions should reference key events, not the deprecated metric.
Related: Why Your WooCommerce Analytics Are Showing Zero Conversions (When You Have Orders)
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
Should I mark all GA4 events as key events?
No — marking every event as a key event inflates your count and dilutes bidding signals if you import GA4 key events into Google Ads (Google Ads Help, 2024). Only events that represent genuine business value should be key events.
For a WooCommerce store, the key events worth marking are: purchase, add_to_cart, begin_checkout, and any lead generation form submissions. Page views, scroll depth, and outbound clicks are useful analytics events but should not be key events — they don’t represent a business outcome worth optimising ad spend against.
The risk of over-marking is real. If you import 15 key events into Google Ads, Smart Bidding optimises for all of them — diluting its focus across page views and scroll events alongside actual purchases. The question isn’t which events are important. It’s which events represent enough business value to steer your ad spend.
| Event | Mark as Key Event? | Import to Google Ads? | Reason |
|---|---|---|---|
| purchase | Yes | Yes (primary) | Direct revenue — the core conversion |
| begin_checkout | Yes | Yes (secondary) | High-intent signal for bidding |
| add_to_cart | Yes | Optional | Mid-funnel intent, useful for audience building |
| page_view | No | No | Too broad — dilutes bidding signals |
| scroll | No | No | Engagement metric, not a business outcome |
Does server-side tracking handle the key events rename automatically?
Server-side tracking that sends events directly to GA4’s Measurement Protocol and Google Ads’ conversion endpoint uses the correct event structure for each platform, bypassing the naming confusion entirely (Google Analytics Help, 2024). The event is labelled correctly at the API level.
When a WooCommerce purchase fires server-side, the tracking system constructs two separate payloads: one for GA4’s Measurement Protocol (where the event registers as a key event) and one for Google Ads’ conversion endpoint (where it registers as a conversion). The terminology split is handled at the infrastructure layer — the store owner never needs to reconcile the two.
For WooCommerce stores, tools like Transmute Engine send purchase events as properly structured GA4 key events and simultaneously as Google Ads conversions through a managed first-party endpoint. Each platform receives data in its own format, with the correct event names and parameters, without manual reconfiguration when platform naming changes.
The broader point matters: platform-side naming changes shouldn’t break your measurement. When events are structured correctly at the API level, a UI rename in GA4 is a documentation update, not a reporting emergency.
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
Key Takeaways
- GA4 renamed conversions to key events in March 2024: Google Ads kept its own conversions metric, creating a terminology split across platforms.
- The numbers won’t match by design: GA4 key events and Google Ads conversions use different attribution models, counting windows, and deduplication logic.
- WooCommerce plugins haven’t caught up: Many still say “conversions” in their settings when they mean GA4 key events, causing configuration confusion.
- Year-over-year reports broke silently: Looker Studio dashboards referencing the old metric show zeros for post-rename data.
- Server-side tracking bypasses the confusion: Events structured at the API level use the correct naming for each platform automatically.
Yes. GA4 renamed all conversions to key events in March 2024. Google Ads kept its own conversions metric with a separate definition. The same purchase event now has different names in each platform — a key event in GA4 and a conversion in Google Ads — even though both track the same underlying action.
GA4 key events are analytics-side metrics counting user interactions you’ve marked as important, while Google Ads conversions are campaign-side metrics used for bidding optimisation. They use different attribution models, counting windows, and deduplication logic, so the numbers will not match even for the same event.
GA4 key events and Google Ads conversions use different attribution models, different counting windows, and different deduplication logic. Since the rename, they are no longer even called the same thing, making cross-platform reporting dashboards break silently when they try to compare what appear to be the same metric.
Many WooCommerce tracking plugins still reference conversions in their GA4 configuration interfaces and documentation. This confuses store owners into thinking their plugin is sending GA4 conversions when the platform now calls them key events. The plugin still works, but the terminology mismatch causes configuration errors.
Yes. Looker Studio reports built before March 2024 that reference the conversions metric now show blanks or zeros for post-rename data. Year-over-year comparisons require manually mapping the old dimension to the new one, which many WooCommerce store owners have not done.
WooCommerce stores should audit their GA4 property to confirm purchase events are marked as key events, update Looker Studio reports to use the key events metric, and verify that Google Ads conversion import pulls from GA4 key events rather than the deprecated conversion metric.
No. Marking every event as a key event inflates your count and dilutes bidding signals if you import GA4 key events into Google Ads. Only purchase, add_to_cart, begin_checkout, and form submissions that represent genuine business value should be key events.
Server-side tracking that sends events directly to GA4’s Measurement Protocol and Google Ads’ conversion endpoint uses the correct event structure for each platform, bypassing the naming confusion entirely. The event is labelled correctly at the API level regardless of what the GA4 interface calls it.