Track WooCommerce conversions with PureMetrix

In PureMetrix, a WooCommerce conversion is a Purchase event that your server sends when the order confirmation page appears. You can add funnel steps and campaign data on top.

Enable purchase tracking

Install the PureMetrix plugin on your shop and connect it (the one-click connection also sets up the keys WooCommerce needs).
Open PureMetrix > Settings and check under Plugin integrations that WooCommerce is detected and switched on.
Under Connection & Site Credentials, make sure the Private Ingest Key (Server Events) is filled in—purchase tracking needs it.
Place a test order in a private browser window.
Check in PureMetrix that the order shows up with its revenue and number of items.

Sending the purchase from your server matters because ad blockers often stop browser tracking right after payment.

See where buyers drop off

Track product, cart, and checkout page views if you want to find out where people abandon their purchase. Guide: reduce abandonment.

Campaigns

Add UTM parameters to links in ads and emails, then compare purchases by campaign. Revenue attribution.

Test orders from your team

Excluding a user role only stops page tracking. The Purchase event is sent from the server for every order, so test orders count as purchases too. Keep test orders few and note them.

Not an accounting tool

Check your actual money in WooCommerce. Use PureMetrix to answer marketing questions, such as which channels and campaigns bring buyers.

Funnel events that matter

At minimum: which landing pages lead to product views, add-to-cart clicks if you send them, and purchases with revenue. Because PureMetrix sends the purchase from your server when the confirmation page appears, it still counts when buyers pay on an external payment page—as long as they return to your confirmation page. On a test day, compare the order count with WooCommerce before you rely on the dashboard in meetings.

Exclude shop managers and administrators from page tracking so their restocking visits do not look like customer demand.

Campaign results

Break down purchases by UTM campaign and landing page. A low average order value from a coupon campaign can still be fine if your margin holds—look at revenue together with AOV, not just conversion rate.

The essentials for shop tracking

Connect PureMetrix, exclude shop roles from page tracking, check that the WooCommerce integration is on, test one order per payment method, then tag your paid landing pages. Only after that is it worth discussing advanced funnels.

If you send add-to-cart events, use them to tell demand problems apart from checkout problems. If you do not, “landing page to purchase” still answers most weekly questions.

Coupon and wholesale noise

Staff coupons and wholesale payment methods distort the conversion rate. Leave those orders out of your analysis, even though the Purchase event is still recorded.

Subscriptions and renewals

Automatic WooCommerce subscription renewals usually do not pass through the confirmation page, so they are not counted as purchases. Decide whether analytics should count only the first purchase, and write it down so nobody blames PureMetrix for “missing” renewals that never happened in the shop front end.

Bundle and composite products

Bundles can make item counts confusing while revenue stays correct. Check how WooCommerce counts bundles before building custom item events. PureMetrix purchase revenue is usually enough to decide where to spend on marketing; leave product catalogue analysis to WooCommerce.

Test a bundle order from start to finish after template changes—customised confirmation pages break more often with complex product types.

Gift cards and store credit can make revenue look low compared with actual demand—take those payment types into account when judging campaign return on ad spend (ROAS).

Manual orders and in-store sales

Orders your staff enter manually never pass through the shop front end, so PureMetrix does not count them. That is usually fine: PureMetrix revenue reflects online shop orders, and you reconcile in-store (POS) sales in WooCommerce only.

Plugins that create draft orders can produce junk orders; make sure those never lead to the confirmation page, where a purchase would be recorded.

If you use a plugin to edit checkout fields, test a purchase again after every change; a broken required field can silently stop all sales.

Pre-order and backorder flows

Pre-orders may take payment differently. PureMetrix records each order once, when the buyer sees the confirmation page—check that this happens at checkout, so pre-order campaigns do not stay invisible until shipping day.

Once a month, compare a sample of ten orders between WooCommerce and PureMetrix before the numbers go into management reports.

Write down how a shop conversion is counted, who is responsible, and when it will next be reviewed, so PureMetrix reports stay in line with how your team actually works.

Compare new and returning customers in WooCommerce reports; PureMetrix shows where your visitors come from, not how loyal your customers are.

Note coupon-driven spikes in your weekly notes; otherwise a higher conversion rate looks like a product success when it was really a discount.