Measurement for WooCommerce
In short
WooCommerce stores lose more conversion data than Shopify ones, for structural reasons: no native server-side event stream, a plugin layer that varies per store, and checkout flows that differ. The fix is first-party capture on the server, where an ad blocker and a consent refusal cannot reach it.
Two thirds of e-commerce is not on Shopify, and almost every measurement guide is written for Shopify. This cluster is for the other two thirds.
Measurement for the two thirds of e-commerce that is not on Shopify.
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?
Browser-side pixels are blocked, consent is refused, the thank-you page is sometimes skipped by payment redirects, and any plugin that alters checkout can break the event. Server-side capture removes the first three causes entirely.
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