You do not need a new dashboard. You need a fifteen-minute Monday routine of seven specific numbers, each pulled from the right tool, that catches marketing problems on day one instead of day twenty-eight. 67% of data professionals do not trust their analytics data for business decisions (Precisely, 2025), and the difference between teams that catch problems early and teams that find them at quarter-end is almost always cadence, not tooling.
This is the routine. Seven numbers. Fifteen minutes. Every Monday before 9am.
A Fifteen-Minute Reporting Routine That Catches Tracking Failures Early
The routine works on any WooCommerce stack and any team size. It is built on one principle: each number comes from the tool that owns the truth for that question, and the gaps between the numbers are themselves diagnostic. We covered why those gaps exist in The Single Source of Truth Problem: Why WooCommerce Stores Have Three Versions of Every Number — this piece is the operational version of that conversation.
Open seven tabs. Pull each number. Eyeball the gaps. Decide one thing per number. Close the laptop.
Number 1: WooCommerce Orders, Last 7 Days
Where to pull: WooCommerce → Analytics → Orders → date range “Last 7 days.”
What good looks like: A number you recognise. Compare it to the same week last month, and to the same week last year if you have history. WooCommerce records orders server-side from the WordPress database — no browser, no ad blocker, no cookie. This is your absolute count of paid checkouts, full stop.
The decision it enables: Is volume up, flat, or down? Everything else this morning gets read against this baseline. If volume cratered last week, the rest of the routine is figuring out why.
Number 2: WooCommerce Gross Revenue, Same Period
Where to pull: Same WooCommerce Analytics screen.
What good looks like: Revenue scales with orders, with average order value (AOV) inside its normal band. If revenue grew faster than orders, AOV is up — usually a pricing or product-mix shift. If revenue grew slower than orders, AOV is down — promotional discounting, smaller-cart customers, or a mix shift toward lower-priced SKUs.
The decision it enables: Compare AOV to the previous four-week average. Anything outside ±10% is a flag worth following up on by Tuesday — not Monday morning. Note it and move on.
Adjust for returns: Average ecommerce return rate is 17.9% (NRF, 2024), so the gross revenue number is overstated by roughly that amount in steady state. If returns spiked last week — outside the 15-20% normal band — that is its own signal worth catching.
Number 3: GA4 Ecommerce Revenue (Reconciliation Check)
Where to pull: GA4 → Reports → Monetization → Ecommerce purchases → same 7-day window.
What good looks like: A number that is lower than WooCommerce. GA4 underreports WooCommerce revenue by 15-50% (industry analysis, 2025) due to ad blockers (31.5% of users globally per Statista, 2024) and browser privacy restrictions. Healthy stores typically see GA4 in the 50-85% range relative to WooCommerce.
The decision it enables: Calculate the ratio (GA4 ÷ WooCommerce). Below 50% is a tracking architecture problem — read Your Looker Studio WooCommerce Dashboard Is Sampling — And You Do Not Know It for one common cause and follow up by mid-week. Above 95% is suspicious in the other direction (likely duplicate tracking firing without deduplication).
Number 4: Google Ads — Spend, Conversions, ROAS
Where to pull: Google Ads → Campaigns → date range “Last 7 days,” columns Spend / Conversions / Conv. value / ROAS.
What good looks like: Spend within ±15% of your weekly target. Conversions and ROAS in the same band as your trailing four-week average.
The decision it enables: Last week’s number is necessarily incomplete. Google Ads conversion lag for considered-purchase WooCommerce products typically runs 7-21 days (Google Ads Help, 2025) — clicks from last Tuesday may convert this Friday and back-attribute. Track each week’s number again the following Monday to see how much it grew, and treat the second view as the decision point, not the first.
If conversions look ugly today, mark a calendar entry to re-check next Monday before you change anything in the campaign.
Number 5: Meta Ads — Spend, Purchases, ROAS
Where to pull: Meta Ads Manager → Campaigns → date range “Last 7 days,” columns Spend / Purchases / Purchase ROAS.
What good looks like: Same shape as Google Ads — spend within target, ROAS within band. The reconciliation question with Meta is different from Google: Meta tends to over-attribute (its 7-day-click-1-day-view default attribution window is generous), so its purchase count is usually higher than the WooCommerce orders that genuinely came from Meta.
The decision it enables: Compare Meta-reported purchases to your WooCommerce orders attributed to Meta as the source (UTM source = facebook or meta). If Meta is reporting more than 2× the WooCommerce-attributed orders, your CAPI deduplication or attribution window is the issue.
Number 6: Tracking Health Ratio (GA4 ÷ WooCommerce)
Where to pull: Calculator. Take Number 3 (GA4 revenue) and divide by Number 2 (WooCommerce gross).
What good looks like: A ratio between 0.65 and 0.85. That band reflects healthy GA4 reporting on a typical WooCommerce store with 30%-ish ad blocker exposure plus normal Safari ITP attrition.
The decision it enables:
- Below 0.50 — tracking is broken. Multiple hops in the chain are likely failing simultaneously. Audit before Wednesday.
- 0.50 to 0.65 — under-tracking, but recoverable. Common causes: missing GA4 enhanced ecommerce setup, WooCommerce hook on a custom checkout, consent banner blocking events.
- 0.65 to 0.85 — healthy. Move on.
- Above 0.95 — duplicate tracking. Server-side and client-side likely posting without deduplication. Audit event_id usage.
Number 7: Smart Bidding Learning Phase Status
Where to pull: Google Ads → Campaigns view → “Bid Strategy Status” column. (If the column is hidden, add it from Columns → Modify columns.)
What good looks like: Most campaigns showing “Eligible” or a clean status. Smart Bidding requires 30-50 monthly conversions per campaign to exit the learning phase confidently (Google Ads Help, 2025) — below that threshold the algorithm never converges.
The decision it enables: Any campaign showing “Learning” beyond two weeks, or “Limited by conversions,” is a signal that conversion volume is too low for the bidding strategy you have selected. Read Your WooCommerce Store Is Stuck in Google Smart Bidding’s Learning Phase Forever if this number stays red week after week — the structural fix is upstream of the bidding panel.
The Routine on a Single Page
Tabs in this order: WooCommerce Analytics, GA4 Monetization, Google Ads Campaigns, Meta Ads Manager. Two values per tab plus the calculator. Bad data costs organisations an average of $12.9 million per year (Gartner, 2025) — and at the SMB scale, the cost is mostly the marketing decisions you would not have made if the numbers had been right.
The routine is not a tool. It is a cadence. We deliberately did not build it around a paid dashboard product, because the moment a routine depends on a paid tool, agencies running it across many clients hit the per-project pricing trap we covered in Looker Studio Pro Charges $9 Per User Per Project — and Every WooCommerce Client You Manage Is a Separate Project. Pull the numbers from the source. Eyeball the gaps. Decide and move on.
Why Three of These Numbers Get Better With Server-Side Capture
The routine works on any architecture. But three of the seven numbers — GA4 reconciliation (Number 3), paid-ad conversions (Numbers 4 and 5), and tracking health (Number 6) — get materially more accurate when WooCommerce events are captured server-side and routed through a first-party server before reaching GA4, Google Ads, and Meta CAPI.
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 WooCommerce purchase hooks server-side and sends events via API to Transmute Engine, which routes the same conversion simultaneously to GA4, Facebook CAPI, Google Ads Enhanced Conversions, and BigQuery — bypassing ad blockers, Safari ITP, and consent-banner ordering bugs in one move. The Monday numbers stop lying to themselves.
Key Takeaways
- Seven numbers, fifteen minutes, every Monday before 9am. Cadence beats tooling.
- WooCommerce is your source of truth for revenue and orders. GA4 is for pattern detection, not absolute counts.
- Healthy GA4-to-WooCommerce ratio is 0.65 to 0.85. Below 0.50 is broken; above 0.95 is duplicate tracking.
- Google Ads numbers for last week are incomplete. 7-21 day conversion lag — re-check the same week next Monday before deciding.
- Smart Bidding “Learning” beyond two weeks is a tracking volume problem, not a bidding problem.
- Three of the seven numbers improve materially with server-side first-party capture. The routine itself works regardless.
Frequently Asked Questions
Because WooCommerce is the source of truth — it records orders server-side at the database level, with no browser, no ad blocker, and no cookie in the path. GA4 underreports WooCommerce revenue by 15-50% on average due to ad blockers (31.5% of users) and browser privacy restrictions. Use WooCommerce for the absolute number, GA4 for the pattern, and the gap between them as a tracking health metric in its own right.
If GA4 matches WooCommerce within 5%, that is suspicious — not in the way you would expect. 31.5% of users globally run ad blockers, so GA4 should be missing some portion of orders. A near-perfect match usually means you have duplicate tracking firing somewhere (server-side and client-side both posting the same event without deduplication), or a small sample where statistics are noisy. Investigate before celebrating.
Google Ads conversion lag for considered-purchase products typically runs 7-21 days. Customers who clicked your ad last Tuesday may convert next Friday, and Google Ads attributes the conversion back to last Tuesday’s click — so the number you see Monday morning for last week will continue rising for two to three weeks. Track the same week’s number again the following Monday to see how much it grew, and use the second view for decisions, not the first.
Tracking health is the ratio of GA4 ecommerce revenue to WooCommerce gross revenue for the same period. Healthy WooCommerce stores typically see GA4 reporting 50-85% of WooCommerce revenue, depending on traffic mix. Below 50% is a tracking architecture problem — GA4 is missing more than half your data. Above 95% is the duplicate-tracking case mentioned above. Aim for 65-85%; investigate anything outside that band.
Yes. The routine works on any WooCommerce stack — it is a cadence, not a tool. Server-side first-party tracking makes three of the seven numbers more accurate (GA4 reconciliation, paid ad conversions, tracking health) by eliminating browser-side data loss before it happens, but the routine itself catches problems regardless of architecture. Start with the cadence; upgrade the data foundation when the routine surfaces a recurring gap you cannot close any other way.
Save this page. Run the seven numbers next Monday. If three of them do not reconcile within 20%, that is a tracking architecture problem worth a closer look. Start at seresa.io.
