Your Looker Studio WooCommerce dashboard shows $142,000 in revenue last month. Your WooCommerce orders page shows $157,000. Your payment processor shows $159,000. All three are measuring the same business. GA4 applies data sampling above 10 million events, and Looker Studio reports built on GA4 inherit this sampling silently—producing estimates instead of exact figures (Google Analytics Help, 2025). Most WooCommerce store owners discover this problem after it has already corrupted a budget decision.
And You Do Not Know It
There’s a yellow triangle indicator in Looker Studio that appears when sampling is active. It’s easy to miss. Most users ignore it. The report looks authoritative regardless—same charts, same formatting, same numbers presented with the same confidence whether GA4 sampled 100% of your events or 30% of them.
What Data Sampling Actually Means
Sampling is what happens when GA4 has more events than it wants to process for a given query. Instead of analyzing all your data, it analyzes a representative subset—then projects the results to the full dataset. The output is an estimate, not an exact count.
GA4 applies sampling in Explorations above 10 million events (Google Analytics Help, 2025). Looker Studio dashboards connected to GA4 inherit this threshold. At scale, the gap between sampled estimates and real revenue figures widens—and for a WooCommerce store doing meaningful volume, 10 million events isn’t that far away when you’re tracking pageviews, scroll depth, add-to-cart, checkout steps, and purchases across all sessions.
67% of data professionals say they cannot trust their analytics data for business decisions (Precisely/Drexel Data Integrity Trends Report, 2025). Sampling is one of the primary reasons.
Translation: the revenue number in your Looker Studio dashboard is GA4’s best guess, not your actual figure. And your best guess and your actual figure are not the same number.
You may be interested in: Your WooCommerce CLV Is Fiction Because GA4 Only Sees 60% of Customers
The Three Layers That Break GA4 WooCommerce Reporting
Sampling isn’t the only problem. GA4-sourced Looker Studio dashboards carry three compounding issues that make the revenue number unreliable for finance-level decisions.
Layer 1: Data Sampling
At scale, GA4 analyzes a subset of events and projects results. The projection is statistical—accurate-ish in aggregate, but wrong at the order level. Revenue figures, in particular, don’t project cleanly from a sample. A $10,000 order that doesn’t make it into the sample pulls the projected revenue figure down; a cluster of high-value orders in the sample skews it up.
Layer 2: Processing Latency
GA4 revenue data carries processing latency of 24–48 hours, with retroactive model adjustments for up to 72 hours (Google Analytics Documentation, 2025). Your Looker Studio dashboard showing yesterday’s revenue is showing an early estimate. The final figure may be adjusted retroactively—but your dashboard doesn’t automatically update to reflect it, and the date range you’re looking at shows the original processed number.
Layer 3: Identity Fragmentation
GA4 CLV and revenue cohort data reflects only around 60% of customers due to identity fragmentation and privacy restrictions (Seresa Analysis, 2025). Ad blockers (31.5% of users globally, Statista 2024), Safari’s ITP restrictions, and consent rejections mean GA4 never sees the full picture. The orders in your dashboard are the orders GA4 tracked—not all the orders that happened.
Stack all three: a dashboard built on sampled data, with processing lag, covering only 60% of your actual customers. The revenue figure in Looker Studio can be 20–30% below your real WooCommerce total.
You may be interested in: Your Facebook Ad Click Opens in One Browser But Your Customer Buys in Another
The Finance Meeting Problem
Here’s where this becomes a credibility issue, not just a data issue. Marketing presents the Looker Studio dashboard in the monthly review. Finance pulls the WooCommerce report. The numbers don’t match. Leadership asks which one to believe.
That question has a correct answer—WooCommerce orders are the ground truth—but having to answer it erodes confidence in marketing’s reporting infrastructure. Poor data quality costs organizations an average of $12.9 million annually (Gartner, 2025). For growing WooCommerce stores, the cost is more immediate: budget misallocated based on a dashboard that’s estimating, not measuring.
The fix isn’t to switch out of Looker Studio. Looker Studio is an excellent reporting interface. The problem is the data source, not the tool.
What Unsampled Data Actually Looks Like
BigQuery is GA4’s own export layer, and it behaves completely differently from GA4’s reporting API. Every event exported to BigQuery is written at the row level—one row per event, with no sampling thresholds, no projection, no estimates. If 1,847 purchases happened, there are 1,847 purchase rows in BigQuery. Full stop.
Looker Studio connected directly to BigQuery is 100% unsampled. Every order, every session, every event—at exact figures, with no sampling triangle to ignore.
BigQuery also eliminates the processing latency issue. Events written to BigQuery via streaming insert are available in seconds, not hours. No retroactive adjustments. No early-estimate revenue figures that shift overnight.
The architecture change: instead of GA4 → Looker Studio (sampled estimates), it becomes WooCommerce → BigQuery → Looker Studio (exact figures). The Looker Studio interface stays the same. The data source changes. The charts look identical. The numbers are real.
How Transmute Engine Gets You There
Transmute Engine™ is a first-party Node.js server that runs on your subdomain (e.g., data.yourstore.com). The inPIPE WordPress plugin captures WooCommerce purchase events at the hook level and sends them via API to the Transmute Engine server, which routes every event simultaneously to BigQuery via Streaming Insert API, GA4 via Measurement Protocol, Facebook CAPI, Google Ads Enhanced Conversions, and more. Your BigQuery dataset gets every order, every event, at exact figures—unsampled and without processing lag. Connect Looker Studio to BigQuery instead of GA4 and your dashboard reconciles with your payment processor for the first time.
Key Takeaways
- GA4 samples above 10 million events: Looker Studio dashboards built on GA4 inherit this sampling silently—displaying estimates flagged only by a small yellow triangle most users ignore.
- Three compounding issues break GA4 WooCommerce reporting: Sampling thresholds, 24–72 hour processing latency with retroactive adjustments, and identity fragmentation covering only ~60% of actual customers.
- WooCommerce orders are always the ground truth: If your Looker Studio revenue doesn’t match your WooCommerce orders page, the dashboard is wrong—not WooCommerce.
- BigQuery exports are 100% unsampled: Every event at the row level, no thresholds, no projections, available in seconds via streaming insert.
- The fix is the data source, not the reporting tool: Looker Studio stays. Switch the connection from GA4 to BigQuery and the dashboard becomes exact revenue, every order, zero sampling.
Yes. Looker Studio dashboards connected to GA4 inherit GA4’s sampling thresholds. GA4 samples data above 10 million events in Explorations, and Looker Studio reports using the GA4 data connector are subject to the same limits. When sampling is active, Looker Studio displays estimated figures rather than exact counts—indicated by a yellow triangle warning that is easy to miss.
Three compounding issues cause the gap: GA4 data sampling projects revenue from a subset of events rather than counting every order; GA4 processing latency means revenue figures carry 24–72 hour delays with retroactive adjustments; and identity fragmentation means GA4 never captures all orders due to ad blockers and privacy restrictions. The WooCommerce orders page and payment processor are correct. The Looker Studio figure is an estimate.
Connect Looker Studio to BigQuery instead of GA4. BigQuery exports every event at the row level with no sampling thresholds—one row per event, exact figures, available in seconds via streaming insert. The Looker Studio interface stays identical; only the data source changes. To populate BigQuery with complete WooCommerce event data, you need server-side tracking that captures purchase events at the WooCommerce hook level and routes them to BigQuery via Streaming Insert API.
BigQuery export is the primary unsampled path available to GA4 users. The GA4 reporting API and Looker Studio’s GA4 connector both inherit GA4’s sampling thresholds at scale. BigQuery export bypasses the sampling layer entirely, writing events at the row level as they occur. For WooCommerce stores, pairing BigQuery with server-side event capture ensures every order is in the dataset before Looker Studio reads it.
If your Looker Studio WooCommerce dashboard doesn’t reconcile with your payment processor, sampling is likely the first place to look—and BigQuery is the fix. GA4 gives you filtered light through a prism. BigQuery gives you the full spectrum. For stores ready to build Looker Studio dashboards on exact, unsampled first-party data, visit seresa.io.
