It’s Monday morning. You open three tabs: GA4, Facebook Ads Manager, Google Ads. Same store, same week. Three completely different conversion numbers staring back at you. 68% of multi-touch attribution models over-credited digital channels in a 2025 analysis of 1,000+ ad accounts (MarTech Series, 2025). Every platform is inflating its own score—and most WooCommerce stores don’t know it.

Here’s the short answer: all three numbers are correct, and none of them are the truth. Each platform counts conversions through its own self-serving attribution model. Your WooCommerce order count is the only number that reflects reality.

Which Conversion Number Do You Put In Your Report?

You use WooCommerce as your revenue truth, each platform’s number to understand that platform’s self-reported efficiency, and a metric called tracking gap per platform to measure how healthy your data actually is. That’s the complete framework. The rest of this article explains why the gap exists—and how to close it.

Why Every Platform Shows a Different Number

Attribution isn’t a measurement—it’s an argument. Each platform argues that it deserves credit for your conversions, using its own rules for how far back to look and what counts as an interaction.

73% of marketers report significant attribution challenges since iOS 14.5 (Direct Agents, 2025)—and that was before consent mode, GA4’s forced migration, and the latest browser restrictions layered on top.

Three things cause the discrepancy:

• Attribution windows: The time period a platform uses to claim credit after a click or view. Facebook’s default is 7-day click / 1-day view. Google Ads uses 30-day click. GA4’s data-driven model uses lookback windows that vary by conversion type. The same purchase can be claimed by all three simultaneously.
• What counts as an interaction: Facebook includes view-through conversions—credit given when someone saw your ad but never clicked it, then bought later. GA4 only counts what its tracking script captures. Google Ads includes assisted conversions if you’re looking at the right report.
• Tracking coverage: GA4 depends on a JavaScript tag loading in the user’s browser. If an ad blocker stops it, if a consent banner is rejected, or if Safari has expired the cookie—that conversion disappears from GA4 entirely. Facebook CAPI and Google Enhanced Conversions receive server-side signals, which is why they often show higher numbers than GA4.

You may be interested in: GA4 Last-Click Attribution Is Hiding Your Best Marketing Channel

Why Facebook Always Shows the Highest Number

Facebook’s attribution model is designed to show you its value. That’s not cynicism—it’s architecture.

By default, Facebook Ads Manager reports on 7-day click / 1-day view attribution. The view-through component is the key. If someone sees your Facebook ad on Monday but never clicks it, then buys your product on Wednesday via a Google search, Facebook claims that purchase. Google claims it too. GA4 may or may not see it at all.

The average WooCommerce customer touches a brand 9.5 times before converting (Direct Agents, 2025). Last-click attribution captures only the final touch. Every other platform claims the sale too—through its own window.

When you see Facebook showing 180 conversions against GA4’s 120, the gap is usually explained by view-through attribution. Facebook saw the customer earlier in the journey. It’s not wrong to claim that—but it’s not the same as what GA4 is counting, and neither matches your WooCommerce order count.

Why GA4 Shows the Lowest Number

GA4 is the most conservative counter—not because it’s more accurate, but because it has the most obstacles between an event firing and a conversion being recorded.

Three structural problems suppress GA4’s conversion count in WooCommerce stores:

• Ad blockers: 31.5% of global users block JavaScript trackers. GA4’s tag doesn’t load. The purchase event never fires. The sale disappears.
• Consent rejection: In the EU, 40–60% of users reject analytics cookies. GA4 in consent mode fires only a minimal ping, not a full purchase event. Every rejected consent banner is a missing conversion.
• Attribution model threshold: GA4 Data-Driven Attribution requires a minimum of 400 monthly conversions to activate (Google Analytics Help, 2025). Below that threshold—where most WooCommerce SMBs operate—it silently falls back to last-click. No warning. No notification. Your attribution model just quietly stops working.

GA4’s 400-conversion threshold for data-driven attribution is the most underreported problem in WooCommerce analytics. Most stores never hit it—and GA4 never tells them it’s fallen back to last-click.

You may be interested in: Facebook Says Your ROAS Is 5x But You Cannot Pay Your Suppliers

Why Google Ads Lands in the Middle

Google Ads typically reports somewhere between GA4 and Facebook—lower than Facebook because it doesn’t default to view-through, higher than GA4 because its Enhanced Conversions receive server-side signals directly.

Google Ads Data-Driven Attribution requires 600+ conversions per month (Google Ads Help, 2025). At lower volumes it uses last-click or another rules-based model. It also gives credit across the Google ecosystem—Search, Display, YouTube, Shopping—so a single customer’s journey can be split across multiple Google touchpoints before the sale is attributed to the keyword or campaign you think drove it.

Google Ads showing 95 when Facebook shows 180 is normal. It reflects how much earlier in the funnel Facebook is claiming credit versus Google, which typically claims credit closer to the final purchase intent moment (Search).

The Resolution Framework: Three Numbers, Three Jobs

Stop trying to reconcile the numbers. They’re not measuring the same thing. Use each number for its intended purpose:

• WooCommerce orders = revenue truth. This is the only source of record for actual completed purchases. Use it for revenue reporting, supplier payments, and business decisions.
• Platform conversion numbers = self-reported efficiency. Use Facebook’s number to evaluate Facebook’s performance relative to itself over time—not against GA4. Use Google Ads’ number to evaluate Google Ads. These numbers tell you how each platform thinks it’s doing, which matters for budget allocation within that platform.
• Tracking gap per platform = data health metric. Calculate: ((WooCommerce orders − platform conversions) / WooCommerce orders) × 100. A 20% gap means the platform sees 80% of real conversions. Track this weekly. If the gap widens suddenly, your tracking has a problem. If it narrows after a change, your fix worked.

WooCommerce is the only platform in this system that doesn’t benefit from overclaiming. Its order count is what actually happened—use it as your anchor.

How Server-Side Tracking Changes the Gap

Here’s the underlying issue: GA4 undercounts because it relies on a JavaScript tag that users can block. Facebook and Google show higher numbers partly because they receive server-side signals that bypass those blocks—and partly because they’re counting different things.

The gap between your platforms can be reduced by routing purchase events directly to each platform’s server API. When Transmute Engine™ sends a purchase event to Facebook CAPI and Google Enhanced Conversions simultaneously—from your own first-party server on your subdomain—both platforms receive the signal regardless of what happens in the user’s browser. GA4 via Measurement Protocol gets the same event. The result: smaller, more consistent gaps across all three platforms, and a WooCommerce order count that’s easier to reconcile with each platform’s report.

Transmute Engine™ is a dedicated Node.js server that runs first-party on your subdomain (e.g., data.yourstore.com). The inPIPE WordPress plugin captures purchase events from WooCommerce hooks and sends them via API to the Transmute Engine server, which routes them simultaneously to GA4, Facebook CAPI, Google Ads Enhanced Conversions, and BigQuery. You don’t need GTM. You don’t need a developer. And your gaps get smaller—without changing how you report.

Key Takeaways

• All three platform numbers are correct within their own models—they’re just not measuring the same thing, with the same rules, over the same window.
• Facebook shows more because it defaults to view-through attribution—credit for ads users saw but never clicked. This is real signal, but it inflates topline conversion counts significantly.
• GA4 shows less because it relies on client-side JavaScript that ad blockers, consent rejection, and Safari ITP can all prevent from firing.
• Use WooCommerce as your revenue truth, platform numbers for within-platform efficiency, and tracking gap per platform as your data health score.
• Server-side tracking reduces the gap by routing purchase events directly to each platform’s server API—bypassing the browser entirely and giving each platform more of the signal it needs to report accurately.

Stop choosing which number looks best in your report. Build a framework: WooCommerce for revenue truth, platform numbers for channel efficiency, tracking gap for data health. Then use server-side tracking to close the gap across all three. See how Transmute Engine reduces tracking gaps for WooCommerce stores at seresa.io.