Measurement for WooCommerce
In short
WooCommerce measurement depends on the checkout, payment flow, extensions and consent setup. Server-side events reduce reliance on a thank-you page or browser pixel, but need compatible hooks, reliable delivery and deduplication. They do not bypass consent requirements.
Start with a test order and follow its event through the actual checkout. These guides cover classic and Block checkout, the timing of consent and the difference between received events and attributed purchases.
Checkout, event delivery and consent checks for WooCommerce.
What this covers
- 01Why conversions go missing, and whereRead
- 02What you can still measure after a consent refusalRead
Every article in this cluster
Common questions
Why is WooCommerce underreporting conversions?
Check scripts, payment redirects, checkout-hook compatibility, event delivery and consent exclusions. Reconcile identifiers as well as totals. Server-side capture can address some failures but does not guarantee complete measurement.
Do I need server-side tracking or the Conversions API?
They are related but not the same. The Conversions API is one destination for server-side events; server-side capture is the practice of recording them at all. Do the second first, then decide where to send them.
What can I record without consent?
That depends on your jurisdiction and on what the record is used for, and it is a question for your counsel rather than for a blog. What is technically possible and what is lawful are different questions, and conflating them is how a measurement project becomes a legal one.
See it on your data
Loyalz joins ad spend to settled order lines, so the numbers in these articles are columns rather than a spreadsheet you rebuild every month.
Book a demo