Your WooCommerce dashboard says $10,423. GA4 says $6,891. Facebook Ads claims $8,200 in revenue. Google Ads reports $4,540. 67% of data professionals do not trust their analytics data for business decisions—up from 55% the year before (Precisely/Drexel, 2025). For WooCommerce store owners, that distrust starts right here: four dashboards, four numbers, none of them matching.
Here’s the answer: WooCommerce is correct. Your WooCommerce order total is the only revenue number recorded at the moment of payment, server-side, by your own infrastructure. GA4, Facebook Ads, and Google Ads are all measuring something adjacent to revenue—not revenue itself. The fix isn’t making them agree. The fix is giving each platform a specific job.
Why Your Dashboards Will Never Agree—And That’s Normal
Four dashboards show four numbers because they measure four fundamentally different things. The moment you expect them to agree, you’ve set yourself up for a recurring Monday morning crisis that no amount of tag troubleshooting will solve.
Bad data costs organizations an average of $12.9 million per year (Gartner, 2025). Not because the data is wrong—but because people apply the wrong data source to the wrong decision. Understanding why each number exists is the first step to stopping that leak.
Here’s what each platform is actually measuring:
- WooCommerce: Completed, payment-confirmed transactions recorded server-side by your own WordPress installation. No browser required. No JavaScript. No consent banner.
- GA4: Behavioral events sent from the user’s browser—subject to ad blockers, Safari ITP, browser privacy settings, and consent rejections. GA4 sees what the browser reports, not what your payment processor confirmed.
- Facebook Ads: Conversions attributed to any user who saw or clicked a Facebook ad within the attribution window, regardless of what actually drove the sale. A customer who saw your ad seven days ago and came back via Google? Facebook may claim that purchase.
- Google Ads: Conversions attributed to Google-assisted clicks within its window. Same multi-touch counting problem, different platform.
These aren’t errors. They’re design choices. Each platform measures what it’s built to measure—and, naturally, what makes its own value proposition look most compelling.
Why GA4 Specifically Underreports Your Revenue
GA4’s gap deserves its own section because it’s the one store owners find most alarming. You completed 50 orders. GA4 shows 32. Where did 18 go?
GA4 underreports WooCommerce ecommerce revenue by 15–50% depending on your audience’s browser and privacy preferences (Seresa/Industry Analysis, 2025). The causes stack up fast:
- Ad blockers: 31.5% of global users have ad blockers installed (Statista, 2024), and most block GA4’s tracking script from firing entirely.
- Safari ITP: Apple’s Intelligent Tracking Prevention limits first-party cookies to 7 days and fragments sessions for Safari’s significant browser share.
- Consent rejection: In the EU, 40–70% of users reject cookie banners. When they do, GA4 receives nothing.
- GA4 misconfigurations: 73% of GA4 implementations have silent misconfigurations causing 30–40% data loss (SR Analytics, 2025)—most owners discover them at month-end when the numbers look wrong.
None of this is fixable with tag tweaks. It’s structural. GA4 runs in browsers that are actively restricting it.
You may be interested in: Validate WooCommerce Events Before They Reach GA4
The Reporting Hierarchy: Give Each Tool a Specific Job
The question isn’t which number is right. The question is which number is right for which decision. Here’s the framework that ends the Monday confusion:
WooCommerce = Revenue truth. Use for finance, invoicing, monthly targets, and year-over-year comparisons. This is your ground truth for whether the business made money. It’s recorded server-side, payment-confirmed, immune to browser restrictions.
GA4 = Behavioral trends. Use for user journeys, landing page performance, checkout funnel drop-off, and traffic pattern analysis. Don’t use GA4 to measure revenue. Do use it to understand what users did before they bought—understanding you’re likely working with 70–85% of the full behavioral picture.
Ad platforms (Facebook, Google Ads) = Directional ROAS only. Use for relative campaign performance, creative testing, and bid optimization signals. Never use ad platform revenue numbers as your actual revenue. 73% of marketers report significant attribution challenges since iOS 14.5 (Direct Agents, 2025)—and ad platform revenue inflation is the most visible symptom.
When each tool has a defined job, the discrepancy stops being a problem. Of course Facebook shows a higher number than WooCommerce—it’s counting view-through attributions from three weeks ago. That’s what it’s designed to do. Now you know what to do with that information: use it to compare campaigns against each other, not against your bank statement.
How to Reconcile Numbers When You Actually Need To
Sometimes you need to report across all platforms—a consolidated dashboard for an investor, a monthly marketing review, or an end-of-year analysis. Here’s how to approach it cleanly:
Start with WooCommerce revenue as your denominator. This is the actual revenue you’re trying to attribute. Everything else is an attribution attempt at that same pool of revenue.
Add a platform-claimed column for context: GA4-attributed revenue, Facebook-attributed revenue, Google-attributed revenue. These will sum to more than your WooCommerce total—that’s normal, it’s the double-counting built into multi-touch attribution across competing platforms.
Calculate your attribution gap: WooCommerce total minus GA4-attributed revenue equals the purchases that happened but weren’t captured behaviorally. For most WooCommerce stores, this runs 15–50%. That gap represents real customers making real purchases—they just did it invisibly to browser-based tracking.
Don’t try to make the gap zero. The gap is real. Your job is to minimize it over time through better data capture—while making good decisions with what you have today.
You may be interested in: Zapier Is Not a Tracking Pipeline
The Long-Term Fix: A Single Canonical Record
The reporting hierarchy framework solves the Monday morning confusion. But it doesn’t solve the underlying problem: you’re running paid media decisions on incomplete behavioral data.
The long-term answer is a single, immutable event log—every WooCommerce transaction, every key user action, streamed to a data warehouse you own. BigQuery streaming from a first-party server is the infrastructure that makes all your other dashboards interpretable. When every event is confirmed delivered from your own server, you have a canonical record to check any other platform against.
This is what Transmute Engine™ is built for. It’s a first-party Node.js server that runs on your subdomain (e.g., data.yourstore.com)—not a plugin, not a third-party script. The inPIPE WordPress plugin captures WooCommerce events and sends them via API to your Transmute Engine server, which streams them simultaneously to GA4, Facebook CAPI, Google Ads Enhanced Conversions, and BigQuery. Every event confirmed delivered. Every transaction recorded in a warehouse you own—before it goes anywhere else.
For a detailed comparison of your BigQuery integration options, see Every WordPress to BigQuery Tool Compared.
Key Takeaways
- WooCommerce is the only revenue source of truth—server-recorded, payment-confirmed, immune to browser restrictions and ad blockers.
- GA4 underreports revenue by 15–50% due to ad blockers (31.5% of global users), Safari ITP, and consent rejection—this is structural, not a configuration error.
- Ad platform revenue numbers are attribution claims, not transaction records—use them to compare campaigns, not to measure how much money you made.
- The fix is a reporting hierarchy, not reconciliation—WooCommerce for revenue, GA4 for behavior, ad platforms for directional ROAS.
- BigQuery via first-party server-side tracking is the long-term canonical record—every event confirmed delivered, from your own subdomain, giving you data all other dashboards can be checked against.
Use WooCommerce revenue for financial reporting. WooCommerce records each transaction server-side at the moment of payment, making it your ground truth. GA4 only captures browser events and misses 15–50% of purchases due to ad blockers, Safari ITP, and consent rejection. GA4 is useful for behavioral analysis—not as your official revenue figure.
Facebook attributes conversions to any user who saw or clicked an ad within its attribution window—typically 7-day click, 1-day view. A customer who clicked a Facebook ad two weeks ago and returned via Google search may still be counted. Ad platform revenue figures represent attribution claims, not transaction records. Use them to compare campaigns against each other, not against your actual bank balance.
Stream every WooCommerce transaction to a data warehouse you control—BigQuery is the most accessible option for WordPress stores. A first-party server-side tracking solution captures each event before it reaches any third-party platform, giving you an immutable record to check other dashboards against. This is the infrastructure that makes discrepancies interpretable instead of confusing.
No—and it shouldn’t. Server-side tracking significantly closes the GA4 underreporting gap by bypassing ad blockers and browser restrictions. But ad platform attribution will always differ from transaction records because it uses multi-touch attribution models. The goal is accurate behavioral data and a canonical transaction record, not identical numbers across all platforms.
The attribution gap is the difference between confirmed WooCommerce transactions and the purchases captured by behavioral tools like GA4. For most stores, this runs 15–50%. It’s caused by ad blockers (31.5% of global users), Safari’s 7-day cookie limit, consent rejection, and GA4 misconfigurations. The gap represents real customers making real purchases who were simply invisible to browser-based tracking scripts.
WooCommerce is correct. Your other dashboards are doing their jobs too—just different jobs. Once each tool has a role in your reporting stack, the confusion stops. If you want to close the behavioral data gap at the same time, Transmute Engine is built for exactly that.
