The same WooCommerce purchase shows three different conversion counts in GA4 — depending on which section you check. Google renamed conversions to “key events” in 2024 to reduce confusion with Google Ads. Instead, it created a three-way measurement split: GA4 Reports uses session-based attribution, Explorations uses user-based attribution, and the Advertising workspace uses data-driven attribution. 73% of marketers already report significant attribution challenges since iOS 14.5 (Direct Agents, 2025). The rename made it worse for WooCommerce stores — and most tracking plugins haven’t caught up.

The Rename That Nobody Explained to WooCommerce Store Owners

Here’s what happened: Google decided that the word “conversion” meant different things in GA4 and Google Ads. In GA4, a conversion was any event you marked as important. In Google Ads, a conversion is a specific action tied to ad attribution with its own attribution windows and models. Same word, different meaning, constant confusion.

Google’s fix? Rename GA4 conversions to “key events.” Now GA4 has key events and Google Ads has conversions. Two different terms, two different attribution systems, two different numbers for the same purchase.

14.2 million websites use GA4 worldwide (BuiltWith, 2025). Every single one now deals with this naming split.

But the real problem isn’t the rename. It’s what the rename revealed: WooCommerce tracking plugins like GTM4WP, Conversios, and PixelYourSite still reference “conversions” in their documentation and interfaces. Store owners configuring these plugins don’t realize the GA4 backend now treats these differently. The terminology mismatch creates a silent gap between what your plugin sends and what GA4 reports.

Three Reports, Three Numbers, One Purchase

This is the part that catches WooCommerce store owners off guard. You check your GA4 Reports section and see 47 purchases. You open Explorations and see 52. You switch to the Advertising workspace and see 43. Same store, same time period, same purchase event.

Each GA4 workspace applies a different attribution method — meaning the same WooCommerce purchase generates three different conversion counts depending on where you look.

Here’s the breakdown:

• Reports section: Uses session-based attribution. Credits the traffic source that started the session where the purchase happened. Last-click within the session wins.
• Explorations: Uses user-based attribution. Credits the traffic source at the user level across sessions. Can show more conversions because it counts across the full user journey.
• Advertising workspace: Uses data-driven attribution. Google’s algorithm distributes credit across multiple touchpoints. Often shows fewer conversions per channel because credit is split.

Now add Google Ads to the mix. Google Ads applies its own attribution window (default 30 days for clicks) and its own data-driven model. So you have a fourth number. 67% of data professionals already don’t trust their data for decision-making — up from 55% the previous year (Precisely/Drexel, 2025). Four conflicting numbers for one purchase event explains why.

You may be interested in: Facebook Says 85 Sales, Google Says 60, WooCommerce Says 50

The Hidden Gap: Funnel Events Your Plugin Doesn’t Mark

Here’s the thing most WooCommerce store owners miss entirely: GA4 automatically marks the purchase event as a key event. That’s it. The rest of your e-commerce funnel — add_to_cart, begin_checkout, add_payment_info, add_shipping_info — are not key events by default.

Translation: GA4 tracks your purchases as key events out of the box, but your entire funnel leading up to that purchase? Invisible in key event reports unless you manually mark each one.

If you haven’t manually marked add_to_cart and begin_checkout as key events, your GA4 conversion reports show the finish line but not the race.

Most WooCommerce tracking plugins send these events to GA4 correctly. The events show up in your Events report. But they don’t appear in your key event metrics, can’t be used for Google Ads conversion optimization, and won’t count toward the attribution models that determine your ROAS.

The fix is straightforward: go to Admin > Events in GA4, find each funnel event, and toggle “Mark as key event.” But if nobody told you this step existed — and most plugin documentation still references the old “conversion” terminology — you’d never know to look.

Why the Numbers Between GA4 and Google Ads Will Never Match

Even after marking all the right key events, WooCommerce store owners discover something frustrating: GA4 key event counts and Google Ads conversion counts still don’t match.

This isn’t a bug. It’s by design.

GA4 attributes a key event to the last non-direct traffic source within its attribution model. Google Ads attributes a conversion to the ad click within its attribution window. If a customer clicks your Google Ad on Monday, browses organically on Wednesday, and purchases on Friday, GA4 might credit “organic” while Google Ads credits the ad click from Monday.

81% of high-performing marketing teams rely on advanced analytics platforms (Gartner, 2026) — partly because native tools like GA4 and Google Ads can’t agree on a single number.

The attribution disagreement is structural. GA4 and Google Ads are different products with different measurement philosophies. No plugin, no configuration change, and no amount of debugging will make them show the same number. The question isn’t how to make them match. The question is how to make sure both receive accurate, consistent data to work with.

You may be interested in: GA4 Data-Driven Attribution Is a Black Box: How to Take Control

Fixing the Data Quality Problem at the Source

The attribution disagreement between GA4 and Google Ads is a platform-side problem you can’t control. But the data quality feeding both platforms? That’s entirely within your control.

Client-side tracking — the JavaScript-based method most WooCommerce plugins use — has a fundamental reliability problem. 31.5% of users globally run ad blockers (Statista, 2024), blocking GA4’s tracking script entirely. Safari’s ITP limits cookies to 7 days. These gaps mean GA4 and Google Ads aren’t just disagreeing on attribution — they’re working with incomplete data to begin with.

When both GA4 and Google Ads receive incomplete event data, the attribution disagreement becomes noise on top of noise.

Server-side tracking solves the data quality layer. Events are captured on your server and sent directly to GA4’s Measurement Protocol and Google Ads Enhanced Conversions API — bypassing browsers entirely. Both platforms receive the same complete event data. The attribution models still disagree, but at least they’re disagreeing about the same set of purchases.

Transmute Engine™ handles this by running a first-party Node.js server on your subdomain. The inPIPE WordPress plugin captures WooCommerce events and sends them via API to your Transmute Engine server, which formats and routes them simultaneously to GA4, Google Ads, and other destinations — all from your own domain.

Key Takeaways

• GA4 “key events” replaced “conversions” in 2024 — but Google Ads still uses “conversions” with different attribution, creating a permanent number mismatch between the two platforms.
• Three GA4 workspaces, three different numbers: Reports (session-based), Explorations (user-based), and Advertising (data-driven) each count the same purchase differently.
• Only purchase is a key event by default. Manually mark add_to_cart, begin_checkout, and other funnel events in Admin > Events or they won’t appear in key event reports or Google Ads optimization.
• GA4 and Google Ads will never show the same number — they use different attribution models and windows by design. Focus on data consistency, not number matching.
• Server-side tracking ensures both platforms receive complete, identical event data — eliminating the most common source of discrepancies caused by ad blockers and browser restrictions.

Your GA4 data and Google Ads conversions will never agree — but they should at least disagree about the same complete dataset. See how Seresa makes that happen.