Why Google Ads and GA4 Never Match: The WooCommerce Gap Explained
Quick Answer: Google officially identifies 9 separate reasons why Google Ads and GA4 show different conversion counts for the same events (Google Analytics Help, 2024). For WooCommerce stores, the gap is even wider: payment gateway redirects, plugin-based tag firing, and consent rejection compound the standard attribution differences. GA4 missed 29% of visits in one controlled test (SealMetrics, 2025). The fix isn’t choosing one platform over the other — it’s sending the same server-verified order event to both, so the only remaining difference is the attribution model.
In this article
- Why do Google Ads and GA4 show different conversion numbers for the same WooCommerce store?
- What is the main attribution difference between Google Ads and GA4?
- Why does Google Ads usually show more conversions than GA4?
- How does the conversion counting method differ between Google Ads and GA4?
- How much conversion data does GA4 miss compared to Google Ads?
- How does Consent Mode affect the gap between Google Ads and GA4 conversion data?
- Do conversion lookback windows cause discrepancies between Google Ads and GA4?
- How do WooCommerce payment gateway redirects make the discrepancy worse?
- Should WooCommerce stores trust Google Ads or GA4 conversion numbers?
- Can server-side tracking eliminate the gap between Google Ads and GA4?
Why do Google Ads and GA4 show different conversion numbers for the same WooCommerce store?
Google Ads and GA4 use fundamentally different attribution models, counting methods, and data collection mechanisms, with Google officially identifying 9 separate reasons the two platforms show different conversion counts (Google Analytics Help, 2024). These aren’t bugs — they’re architectural decisions baked into how each platform was built. GA4 was designed as a cross-channel analytics tool that credits the last touchpoint. Google Ads was designed as an advertising platform that credits the ad. Same event, different rules, different numbers.
Google officially identifies 9 separate reasons why Google Ads and GA4 report different conversion counts for the same events (Google Analytics Help, 2024).
For WooCommerce stores, the standard discrepancy gets worse. WordPress plugin-based tag firing means your pixel, GA4 tag, and conversion linker may each load at different moments — or not at all — depending on caching, consent banners, and plugin conflicts. The gap you see between Google Ads and GA4 is the standard attribution difference plus whatever your WooCommerce setup adds on top.
What is the main attribution difference between Google Ads and GA4?
GA4 uses cross-channel last-click attribution by default — crediting the last touchpoint before conversion — while Google Ads uses data-driven attribution that distributes credit across multiple touchpoints using machine learning, so the same conversion gets counted differently in each platform. GA4 defaults to cross-channel last-click; Google Ads defaults to data-driven attribution (Dataslayer, 2024).
Translation: a customer clicks your Google Ad on Monday, returns via an email link on Wednesday, and buys. GA4 credits the email (last click). Google Ads credits the ad (it participated in the path). Neither is wrong — they’re answering different questions. GA4 asks “what was the final touchpoint?” Google Ads asks “which of my ads contributed to this sale?”
Related: Google Quietly Moved Conversion Management Out of Google Ads and Into GA4
Why does Google Ads usually show more conversions than GA4?
Google Ads counts view-through conversions by default, applies conversion modelling for unconsented users, and can count every conversion per click rather than one per session — three mechanisms that consistently inflate Google Ads numbers above what GA4 reports. Google Ads applies conversion modelling for unconsented users while GA4 does not offer equivalent modelling (Google Analytics Help, 2024).
Google Ads applies conversion modelling for unconsented users while GA4 does not offer equivalent modelling — the gap widens as consent rejection rates increase (Google Analytics Help, 2024).
View-through conversions are the biggest surprise for most store owners. A user sees your display ad, doesn’t click it, then visits your store directly and buys. Google Ads counts that as a conversion. GA4 doesn’t — it never saw the ad impression because it only tracks on-site activity. For WooCommerce stores running display or YouTube campaigns, this single difference can account for a 15–25% gap.
How does the conversion counting method differ between Google Ads and GA4?
Google Ads can be set to count every conversion from a single click (so one user buying twice counts as two), while GA4 typically counts one conversion per event name — setting the GA4 counting method to “Once per session” is the only way to align the two. This is a configuration difference, not a data collection difference, and it’s one of the easiest discrepancies to fix.
Check your Google Ads conversion action settings: if counting is set to “Every” and your GA4 key event counts once per session, the numbers will never match. For WooCommerce purchase events, “Every” usually makes more sense (you want to count each order), but both platforms must use the same method, or you’re comparing quantities measured in different units.
| Factor | Google Ads | GA4 |
|---|---|---|
| Default attribution | Data-driven (multi-touch) | Cross-channel last-click |
| View-through conversions | Counted by default | Not tracked |
| Conversion modelling | Applied for unconsented users | Not equivalent |
| Counting method | Configurable (Every / One) | Typically one per session |
| Date assignment | Date of original click | Date conversion happened |
| Data collection | Client-side + modelling + Enhanced | Client-side JavaScript only |
How much conversion data does GA4 miss compared to Google Ads?
GA4 relies entirely on client-side JavaScript and missed 29% of visits in a controlled side-by-side test (SealMetrics, 2025), while Google Ads supplements client-side data with modelled conversions, Enhanced Conversions, and view-through tracking — creating a structural gap where GA4 consistently underreports. The 29% isn’t a worst case; it’s what happens when ad blockers, browser privacy features, and consent rejection all work as designed.
For WooCommerce stores, the client-side dependency is particularly painful. Every WordPress caching plugin, every consent management platform, and every ad blocker interacts with GA4’s JavaScript tag. A misconfigured caching layer can serve stale pages without the GA4 tag. A strict consent banner can block GA4 entirely until a user opts in. Google Ads’ conversion tag faces the same obstacles, but its server-side modelling and Enhanced Conversions partially compensate — GA4 has no equivalent recovery mechanism.
How does Consent Mode affect the gap between Google Ads and GA4 conversion data?
In regions with 30–50% consent rejection rates (TrackBee, 2025), Google Ads applies conversion modelling to estimate unconsented conversions while GA4 does not have equivalent modelling, creating an inherent gap that grows larger the higher the consent rejection rate. If half your visitors reject cookies, Google Ads estimates what those visitors would have done and adds modelled conversions. GA4 records nothing for them.
The practical effect for WooCommerce stores selling into the EU, UK, or any market with GDPR-style regulation: your GA4 purchase count could be 30–50% below your actual order count purely from consent rejection, while Google Ads’ modelled count sits closer to reality. The irony is that GA4 looks broken while Google Ads looks right — but the “right” number is partly estimated, not measured.
Related: Why Google Ads, Meta, and GA4 Show Different Conversion Numbers for the Same WooCommerce Sale
Do conversion lookback windows cause discrepancies between Google Ads and GA4?
Google Ads assigns conversions to the original click or impression date using a lookback window (up to 90 days for clicks), while GA4 assigns them to the date the conversion actually happened — so the same event appears on different dates in each platform. A customer who clicked your ad on October 1st and bought on October 15th shows up as an October 1st conversion in Google Ads and an October 15th conversion in GA4.
This means day-level and week-level comparisons between the two platforms will never match, even if the total numbers eventually converge. For WooCommerce stores with longer consideration cycles — furniture, electronics, B2B products — the lookback window difference can make monthly reports look wildly inconsistent until you account for the date-shifting effect.
How do WooCommerce payment gateway redirects make the discrepancy worse?
When a WooCommerce customer completes checkout through PayPal, Klarna, or a bank redirect, the browser leaves your domain and may not return to the thank-you page — GA4’s client-side tag never fires while Google Ads may still credit the conversion via modelling or Enhanced Conversions. Google Ads averages 11% signal loss while platforms without server-side backup lose significantly more (GrowWithBA via WebTonic, 2025).
This is WooCommerce-specific pain. Shopify handles most payment flows within its own domain. WooCommerce’s flexibility — supporting dozens of payment gateways via plugins — means the checkout flow regularly leaves your site. Every redirect is a chance for GA4 to lose the conversion entirely: the customer pays on PayPal’s domain, PayPal redirects back, but the browser drops the session, the thank-you page doesn’t load, or the GA4 tag fires before the WooCommerce order is confirmed in the database.
Should WooCommerce stores trust Google Ads or GA4 conversion numbers?
Neither platform shows the complete truth — the most reliable conversion count comes from your WooCommerce order database itself, and the role of tracking tools is to match as closely as possible to that server-side record rather than to each other. Your WooCommerce orders table is the single source of truth: a row exists in wp_wc_orders for every completed sale, regardless of what any tracking platform recorded or missed.
The right question isn’t “which platform is correct?” but “how far is each platform from my actual order count?” Pull your WooCommerce completed orders for a week, compare against Google Ads’ reported conversions and GA4’s key events for the same period. The gap between each platform and your real orders tells you how much signal each one is losing — and that’s the number worth fixing.
Related: Should I use GA4 or Google Ads conversions?
Can server-side tracking eliminate the gap between Google Ads and GA4?
Server-side tracking sends the same verified WooCommerce order event directly to both Google Ads and GA4 from the server, bypassing ad blockers, consent restrictions, and payment gateway redirect losses — reducing the discrepancy to only the attribution model difference, which is typically small and predictable. Server-side tracking recovers 20–40% of missed conversions (Releva AI via WebTonic, 2025) by removing the client-side JavaScript dependency entirely.
The mechanism is direct: when a WooCommerce order reaches “completed” status, the server sends that event to both GA4’s Measurement Protocol and Google Ads’ offline conversion import (or Enhanced Conversions API). Both platforms receive the same order ID, the same revenue, the same timestamp. The only remaining difference between their reported numbers is how each platform attributes the conversion — and that difference is small, predictable, and documented.
For WooCommerce stores that want a single server-side pipeline feeding both platforms, Transmute Engine sends the same server-verified order event directly to GA4 and Google Ads — the order either happened or it didn’t, and both platforms receive identical data, bypassing the client-side tag fragmentation that causes most of the gap.
Key Takeaways
- The gap is structural, not a bug: Google identifies 9 reasons Ads and GA4 differ — attribution model, counting method, consent modelling, view-through tracking, lookback windows, and more.
- Your WooCommerce orders are the truth: compare each platform’s count against your actual order database, not against each other.
- WooCommerce compounds the problem: payment gateway redirects, plugin-based tags, and caching layers add WooCommerce-specific signal loss on top of the standard discrepancy.
- Server-side tracking closes the data gap: sending the same verified event from your server to both platforms reduces the discrepancy to the attribution model difference alone.
Google Ads and GA4 use fundamentally different attribution models, counting methods, and data collection mechanisms, with Google officially identifying 9 separate reasons the two platforms will never show identical numbers for the same transactions.
GA4 uses cross-channel last-click attribution by default — crediting the last touchpoint before conversion — while Google Ads uses data-driven attribution that distributes credit across multiple touchpoints using machine learning, so the same conversion gets counted differently in each platform.
Google Ads counts view-through conversions by default, applies conversion modelling for unconsented users, and can count every conversion per click rather than one per session — three mechanisms that consistently inflate Google Ads numbers above what GA4 reports.
Google Ads can be set to count every conversion from a single click (so one user buying twice counts as two), while GA4 typically counts one conversion per event name — setting the GA4 counting method to ‘Once per session’ is the only way to align the two.
GA4 relies entirely on client-side JavaScript and missed 29% of visits in a controlled side-by-side test, while Google Ads supplements client-side data with modelled conversions, Enhanced Conversions, and view-through tracking — creating a structural gap where GA4 consistently underreports.
In regions with 30-50% consent rejection rates, Google Ads applies conversion modelling to estimate unconsented conversions while GA4 does not have equivalent modelling, creating an inherent gap that grows larger the higher the consent rejection rate.
Google Ads assigns conversions to the original click or impression date using a lookback window (up to 90 days for clicks), while GA4 assigns them to the date the conversion actually happened — so the same event appears on different dates in each platform.
When a WooCommerce customer completes checkout through PayPal, Klarna, or a bank redirect, the browser leaves your domain and may not return to the thank-you page — GA4’s client-side tag never fires while Google Ads may still credit the conversion via modelling or Enhanced Conversions.
Neither platform shows the complete truth — the most reliable conversion count comes from your WooCommerce order database itself, and the role of tracking tools is to match as closely as possible to that server-side record rather than to each other.
Server-side tracking sends the same verified WooCommerce order event directly to both Google Ads and GA4 from the server, bypassing ad blockers, consent restrictions, and payment gateway redirect losses — reducing the discrepancy to only the attribution model difference, which is typically small and predictable.
References
- Google Analytics Help (2024). Why conversion counts differ between Google Ads and GA4. Source
- Google Ads Help (2024). Understanding conversion count differences. Source
- Dataslayer (2024). 8 key reasons for data discrepancies between Google Ads and GA4. Source
- SealMetrics (2025). Data loss in analytics: Incapto case study. Source
- TrackBee (2025). How much revenue are you losing to bad tracking. Source
- WebTonic (2025). E-commerce attribution statistics. Source