WooCommerce says $10,000 in revenue. GA4 says $6,000. Facebook claims credit for $8,000. Google Ads says $4,500. All from the same month. Which number goes in your board report? The answer: WooCommerce is right, and every other platform is telling you a different version of a partial story. GA4 underreports WooCommerce ecommerce revenue by 15-50% (Seresa/Industry analysis, 2025), and the gap is getting worse. A structured weekly reconciliation report takes 15 minutes and tells you exactly how much each platform is missing.
Why Every Platform Shows a Different Number
This isn’t a bug. It’s physics. Each platform measures conversions differently because each platform has a different job—and different blind spots.
WooCommerce records every completed transaction server-side, through your payment processor. It doesn’t care about browsers, cookies, or consent banners. An order is an order.
GA4 relies on a JavaScript tag that fires in your visitor’s browser. 31.5% of global users run ad blockers that block GA4’s tracking script entirely (Statista, 2024). Safari’s ITP limits cookies to 7 days. Visitors who deny consent are invisible. GA4 doesn’t miss some of your revenue—it structurally cannot see it.
Facebook Ads uses its own attribution model with a default 7-day click, 1-day view window. It takes credit for conversions that happened up to 7 days after someone clicked your ad—even if they came back through a Google search. 68% of multi-touch attribution models over-credited digital channels in 2025 (MarTech Series).
Google Ads uses yet another attribution model. And here’s the part that catches most store owners off guard: GA4’s data-driven attribution requires 400+ monthly conversions to function—below that, it silently falls back to last-click (Google Analytics Help, 2025). Most WooCommerce stores don’t hit that threshold.
You may be interested in: Google Ads Shows 85 Conversions, GA4 Shows 60
The Cost of Not Reconciling
When you don’t reconcile, you’re making budget decisions on incomplete data. And you’re not alone—73% of marketers report significant attribution challenges since iOS 14.5 (Direct Agents, 2025).
Here’s what goes wrong. Your Facebook ROAS looks terrible because Facebook can only see 60% of the conversions it actually drove. So you cut Facebook spend. Revenue drops. You blame the algorithm. But the algorithm was working—your tracking wasn’t.
Or the opposite: Google Ads claims a 5x ROAS because it’s attributing conversions that Facebook also claims. You increase spend based on inflated numbers. Actual return doesn’t match.
67% of data professionals don’t trust their data for making decisions (Greenbook/Precisely, 2025). The problem isn’t the data itself—it’s that nobody is comparing the data against reality.
The 15-Minute Weekly Reconciliation Report
Revenue reconciliation means comparing what actually happened (WooCommerce) against what each platform says happened (GA4, Facebook, Google Ads). The goal isn’t to make the numbers match—they won’t. The goal is to know your tracking gap per platform so you can make informed decisions.
Step 1: Pull Your WooCommerce Numbers
Go to WooCommerce → Reports → Orders → This Week. Note three numbers: total orders, total revenue, and total refunds. This is your source of truth. WooCommerce records transactions server-side through your payment processor—no browser dependencies, no tracking gaps.
Step 2: Pull GA4 Numbers for the Same Period
In GA4, go to Reports → Monetization → Ecommerce purchases. Match the exact same date range. Note: total purchase events, total revenue, and transactions. Compare against WooCommerce.
Calculate your GA4 tracking gap: (WooCommerce orders – GA4 transactions) ÷ WooCommerce orders × 100 = tracking gap percentage.
A 30% gap means GA4 is blind to nearly one-third of your actual sales. That’s typical for stores without server-side tracking.
Step 3: Pull Ad Platform Numbers
For each ad platform (Facebook Ads Manager, Google Ads), pull conversions and attributed revenue for the same date range. Calculate each platform’s tracking gap against WooCommerce the same way.
Then calculate your adjusted ROAS: Actual WooCommerce revenue attributed to that channel ÷ ad spend. This is your real return—not the inflated or deflated number the platform reports.
Step 4: Build Your Tracking Gap Scorecard
Create a simple spreadsheet with one row per platform. Columns: Platform, Reported Orders, WooCommerce Orders, Tracking Gap %, Reported Revenue, Actual Revenue, Reported ROAS, Adjusted ROAS.
Track this weekly. When the tracking gap suddenly widens—say from 30% to 55%—something broke. Maybe a plugin update killed your GA4 tag. Maybe Facebook’s pixel lost its connection. Weekly reconciliation catches silent failures within 7 days instead of letting them compound for months.
You may be interested in: Bad Data Costs $12.9 Million Per Year
What a Healthy Tracking Gap Looks Like
Zero gap is unrealistic. Different attribution models, consent frameworks, and counting methods guarantee some discrepancy. Here’s what to expect:
GA4 tracking gap: 15-30% is normal for stores with standard client-side tracking. Above 40% signals a configuration issue or an unusually high ad-blocker audience. Below 15% suggests server-side tracking is already working.
Facebook Ads: Expect over-attribution. Facebook will often claim more conversions than WooCommerce shows for that channel because of its view-through attribution and cross-device modeling. A healthy ratio is Facebook claiming 80-120% of the conversions you can actually attribute to Facebook traffic.
Google Ads: Expect 20-40% tracking gap similar to GA4, since both depend on browser-based measurement. Google Ads Enhanced Conversions can reduce this gap by matching hashed customer data server-side.
Closing the Gap With Server-Side Tracking
Reconciliation tells you how big the gap is. Server-side tracking actually closes it. When events are captured on your server—not in the visitor’s browser—ad blockers, consent denials, and Safari’s cookie limits stop being data killers.
Transmute Engine™ runs as a first-party Node.js server on your subdomain, capturing WooCommerce events via the inPIPE plugin and routing them simultaneously to GA4, Facebook CAPI, Google Ads, and BigQuery. Your tracking gap shrinks because data flows through your own infrastructure—not through browsers where it can be blocked.
With BigQuery streaming, reconciliation becomes real-time. Your WooCommerce transaction data and your platform tracking data live in the same warehouse. Instead of pulling numbers manually from four dashboards, you query one source.
Key Takeaways
- WooCommerce is your source of truth. It records every transaction server-side, regardless of browser behavior or ad blockers.
- GA4 underreports revenue by 15-50%. Ad blockers (31.5% of users), Safari ITP, and consent denials make this structural, not fixable with configuration alone.
- Calculate your tracking gap percentage weekly. (WooCommerce orders – platform orders) ÷ WooCommerce orders × 100.
- Adjust your ROAS using actual WooCommerce revenue, not platform-reported revenue—this changes budget decisions.
- A sudden gap increase means something broke. Weekly reconciliation catches silent tracking failures within 7 days.
WooCommerce records every completed transaction server-side through your payment processor. GA4 relies on browser-based JavaScript that fails when visitors use ad blockers (31.5% globally), deny cookie consent, or close their browser before the thank-you page loads. The result: GA4 consistently underreports WooCommerce revenue by 15-50%.
Trust WooCommerce (or your payment processor) as your source of truth for actual revenue. WooCommerce records completed transactions server-side regardless of browser behavior. Use GA4 and ad platforms for channel attribution and traffic analysis, but always calibrate their numbers against WooCommerce actuals.
Weekly. A 15-minute weekly check reveals your tracking gap percentage per platform, catches silent failures early, and prevents compounding data loss. Monthly reconciliation misses failures that can quietly run for weeks—by then you’ve lost data you can never recover.
Server-side tracking significantly reduces the gap by capturing events on your server before they reach browsers where they can be blocked. It recovers data lost to ad blockers and browser restrictions. Some gap will always remain due to platform attribution differences, but server-side tracking typically closes 60-80% of the discrepancy.
Stop guessing which platform is right. Start reconciling weekly. See how Seresa closes the tracking gap at the source →
