How to define RPV, conversion rate and AOV consistently for WooCommerce

How To Implement

• 1 Write the definitions in a one-page analytics spec before you touch any dashboard

  Put the formulas in plain English and in formula form. For most WooCommerce CRO reporting, a practical house standard is: RPV = Net sales / Sessions Conversion rate = Orders / Sessions AOV = Net sales / Orders Then write the exact meaning of each noun: Net sales means product revenue after refunds and coupons, excluding shipping and tax; Sessions means GA4 sessions; Orders means completed purchase transactions included in your chosen Woo status set. WooCommerce’s own Analytics definitions support the net-sales and AOV side of this, while GA4’s session and transaction metrics support the denominator choices.

• 2 Freeze the WooCommerce commercial settings that drive your order-side truth set

  In WP Admin → Analytics → Settings, review Excluded Statuses and Date Type. WooCommerce includes Processing, On hold, and Completed by default, excludes Pending payment, Cancelled and Failed by default, and lets you report Revenue and Orders by Date created, Date paid or Date completed; the default is Date paid. If you want a clean commercial baseline, Date paid is usually the safest match for paid-order reporting, but the important thing is that you document the choice and keep it identical everywhere.

• 3 Be explicit about checkout type, Draft orders and HPOS before reconciling order counts

  This technique is sitewide rather than template-specific, so the metric definitions do not change between classic shortcode checkout and Cart & Checkout Blocks. What does change is order behaviour: WooCommerce documents that Draft orders are created when customers start checkout with the block-based checkout experience, so Draft orders should never leak into your reported “orders” count. Also note that HPOS is enabled by default for new installs from WooCommerce 8.2 onward, and order data lives in dedicated Woo order tables when HPOS is authoritative; any custom export, plugin or script you use for reconciliation needs to support that storage model.

• 4 Validate the GA4 purchase implementation before you trust any revenue metric

  GA4’s recommended purchase event requires a transaction_id, and Google says that parameter helps avoid duplicate purchase events. For revenue, Google recommends setting value to the sum of (price * quantity) for all items and says not to include shipping or tax in that value; shipping and tax are separate optional parameters. GA4’s Purchase revenue metric is the sum of purchase revenue minus refunds, while Transactions counts completed purchases. That means the cleanest cross-platform match is to make your GA4 purchase payload reflect the same commercial basis you documented in Woo, then validate it against Woo before publishing any report.

• 5 If you use the official Woo extension, check the exact plugin area rather than guessing

  In the official Google Analytics for WooCommerce extension, GA4 is configured in WooCommerce → Settings → Integration → Google Analytics, with tracking options including Purchase Transactions, Add to Cart Events and Checkout Process Initiated. Woo also notes that purchase tracking with that extension requires a payment gateway that redirects to the thank you / order received page after payment. If you use WooCommerce Google Analytics Pro, its settings live in WooCommerce → Settings → Integrations → Google Analytics Pro, and Woo documents compatibility with Cart and Checkout blocks from WooCommerce 8.3 for that extension. Measurement note: before you sign off the dashboard, compare a sample of recent Woo orders against GA4 transactions to confirm that your live gateway flow actually fires the purchase event in your current checkout stack.

• 6 Build the shared formulas in GA4 only where they stay unambiguous

  GA4 now supports Calculated metrics under Admin → Custom definitions → Calculated metrics, but standard properties are limited to 5 calculated metrics. A practical setup is to create: RPV_session = {Purchase revenue} / {Sessions} AOV_reporting = {Purchase revenue} / {Transactions} and, if your team wants an explicitly order-based rate, Order conversion rate = {Transactions} / {Sessions}. This last formula is often the clearest replacement for the legacy ecommerce conversion rate because it is unambiguous and isolated from GA4’s wider key-event model. If your team instead wants “sessions with at least one purchase divided by sessions”, then use Session key event rate for purchase and label it exactly that way in the spec.

• 7 Put the master formulas in the Looker Studio data source, not inside random charts

  In Looker Studio, create data-source calculated fields rather than chart-specific fields, because data-source fields are available in any report that uses that source and can be reused in charts, controls and other calculated fields. The exact formulas are: RPV = SUM(Purchase revenue) / SUM(Sessions) Conversion rate = SUM(Transactions) / SUM(Sessions) AOV = SUM(Purchase revenue) / SUM(Transactions) Create them by editing the data source, clicking Add a field, naming the field, and saving the formula. This is the single best way to stop one tab, one scorecard or one copied chart from quietly using a different denominator.

• 8 Standardise the segmentation layer, not just the top-line formulas

  For session-based CRO views, use session-scoped dimensions with session-based metrics: Device category, Country, and Session default channel group are the clean defaults. Use First user default channel group only when you deliberately want first-touch acquisition analysis, because it answers a different question. For “new vs returning”, document the exact lens you mean: GA4 exposes New users and Returning users as user metrics, while New / established is a user dimension defined around users first seen within the last 7 days, so it is not a clean synonym for “returning”. If you need a reusable new-vs-returning split in reports, define that logic explicitly and keep the same logic in every report.

• 9 Add a Woo reconciliation view and only reconcile after data has settled

  Use WooCommerce’s Analytics exports or report CSVs as the order-side check, because Woo lets you download report tables to CSV and control the included statuses and date basis from Analytics → Settings. GA4, meanwhile, warns that data processing can take 24–48 hours, and WooCommerce 10.5 adds an Analytics Updates setting with Scheduled imports every 12 hours or Immediately for faster refreshes. A safe operating rule is: do not judge metric drift from same-day data. Reconcile on a stable lookback window after GA4 and Woo Analytics have both finished processing.

How To Measure

Pitfalls

• Myth: “GA4 has one standard conversion rate just like old Universal Analytics.” It does not. GA4 exposes Session key event rate and User key event rate, and those are different from an explicitly defined orders per session formula. If you do not name the exact formula, people will compare unlike-for-like numbers.
• Myth: “Average purchase revenue per active user is the same thing as RPV.” It is not. That metric is user-based and uses active users as the denominator, while session-based RPV uses sessions.
• Mistake: mixing Woo “Total Sales” with GA4 purchase revenue. Woo Total Sales includes taxes and shipping, while Woo Net Sales excludes them and subtracts returns and coupons. Google recommends excluding shipping and tax from the purchase event value, and GA4 keeps shipping and tax as separate parameters. If you blend those revenue bases, your AOV and RPV will drift even when tracking is otherwise correct.
• Mistake: using session metrics against first-user acquisition dimensions without saying so. Session default channel group and First user default channel group are both valid, but they answer different questions. Use one deliberately; do not swap them across tabs and still call the KPI the same thing.
• Mistake: trusting same-day reconciliation. GA4 says processing can take 24–48 hours, and Woo Analytics imports are also scheduled or immediate depending on settings. Daily noise is normal; persistent drift after settlement is the real problem.
• Mistake: assuming every paid order will appear in GA4 if Woo has it. Woo’s official free GA extension says purchase tracking requires a gateway that returns users to the Woo thank-you page. If your gateway flow, consent setup or extension support is incomplete, Woo can record the order while GA4 misses the purchase event.
• Edge case: block checkout Draft orders. Woo documents that Draft orders are created in block-based checkout. If someone exports Woo orders carelessly, Draft can pollute order counts even though it should not be treated as a purchase.
• Edge case: Woo core Order Attribution is not a substitute for GA4 session history. Woo’s Order Attribution Tracking is last-click, session-scoped, and Woo says it cannot be used to track visitors across sessions. It is useful for order metadata and order-side diagnostics, but it is not the same model as user-based GA4 acquisition reporting.

Examples

FAQs

Sources & Further Reading

• Analytics and Sales Reports Documentation – — WooCommerce’s primary definitions for Gross Sales, Total Sales, Net Sales, Orders, Average Order Value, plus Analytics → Settings for excluded statuses, date type and update behaviour. Date: date not stated on page; current documentation accessed June 2026.
• Order Statuses Documentation – — Official Woo definitions for core order statuses and the note that Draft orders are created with block-based checkout. Date: date not stated on page; search result showed publication in 2024.
• High-Performance Order Storage Documentation – — Official HPOS documentation, including the note that HPOS is enabled by default for new installs from WooCommerce 8.2 and the admin path for storage settings. Date: date not stated on page; search result showed publication in 2022.
• Google Analytics for WooCommerce Documentation – — Official setup path for the free Woo GA extension, purchase tracking options, gateway redirect caveat, and consent-related discrepancy note. Date: date not stated on page; search result showed publication in 2024.
• WooCommerce Google Analytics Pro Documentation – — Official setup path for the Pro extension and Woo’s note that the extension supports Cart & Checkout Blocks from WooCommerce 8.3. Date: date not stated on page; search result showed publication in 2015 with later updates.
• About Analytics sessions – — Google’s official definition of sessions, session timeout, session estimation, and the note that standard reports, Explorations and Looker Studio use HLL++ for session counts. Date: date not stated on page.
• Understand user metrics – — Google’s definitions of Total users, Active users, New users and Returning users, which is essential when deciding whether RPV is session-based or user-based. Date: date not stated on page.
• Analytics dimensions and metrics – — Google’s master list for Session key event rate, User key event rate, Purchase revenue, Transactions, Returning users, Device category, Country, and traffic-source dimensions. Date: date not stated on page.
• Recommended events – — Google’s official purchase event requirements, including transaction_id, shipping, tax, customer_type, and the instruction that value should exclude shipping and tax. Date: last updated 2026-06-03 UTC.
• About calculated fields – — Official Looker Studio guidance on data-source versus chart-specific calculated fields and why data-source fields are reusable across reports. Date: last updated 2026-06-15 UTC.
• Add, edit, and troubleshoot calculated fields – — Official step-by-step instructions for creating data-source and chart-specific calculated fields in Looker Studio. Date: last updated 2026-06-15 UTC on the page footer; search result highlighted 2026-04-23 update history.
• Create calculated metrics – — Official GA4 instructions for creating calculated metrics, including the 5 calculated metrics per standard property limit. Date: date not stated on page.

About This Page

• Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
• Last Reviewed: 17 Jun 2026
• Last Updated: 17 Jun 2026