WooCommerce conversion tracking that respects consent

Most WooCommerce tracking plugins fire the purchase event from the browser on the thank-you page – where ad blockers, closed tabs and reloads lose or duplicate it. Omea Consent Pro counts WooCommerce events on the server and sends them to your platforms only with the visitor’s consent.

Set it up

1. Check the server-side events Go to Omea Consent › Conversions. In Server-side events, the three WooCommerce rows – order received, checkout started, product added to cart – are on by default.
2. Make them conversions Click Make conversion next to purchase (and begin_checkout or add_to_cart if you want them). The Pro setup suggests these for you.
3. Map each platform Edit the conversion and fill in Send to ad platforms – for example GA4 purchase, Meta Purchase, TikTok CompletePayment, Snap PURCHASE, and your Google Ads conversion label.
4. Turn on the Conversions APIs Optionally switch on each platform’s server-side API in its card under Integrations, so purchases arrive even with ad blockers.
5. Test an order Place a test order in a private window after accepting all cookies, and check each platform’s test or debug view.

The three WooCommerce events

Event	WordPress action	Value
purchase	Order received	Order total
begin_checkout	Checkout started	Cart total
add_to_cart	Product added to cart	–

They’re on by default when WooCommerce is active. An event reaches your ad platforms only when a conversion with the same name exists – that’s what Make conversion creates.

Once per order

Each purchase has the event ID wc-order-<order id> and fires once per order. A reloaded thank-you page doesn’t count twice, and because the browser pixel and the Conversions API use the same ID, each platform de-duplicates them.

How server events reach the pixels

A purchase is recorded on the server, then handed to the pixels on the page:

• If the event happens while the page is being built (the order-received page), it’s printed straight into that page.
• If it happens on a request that redirects or runs in the background (an AJAX add-to-cart), it rides along to the next page in the omea_conv_pending cookie for up to 10 minutes – only with Marketing consent.

Consent

• Browser pixels and tags send the event only if the visitor consented to that platform’s category.
• Conversions APIs check the visitor’s consent on the server before sending.
• For orders completed later – for example when you mark an order paid in the admin – Omea uses the consent recorded on the order at checkout, or sends nothing.

Customer data

For Meta, TikTok, Snap and LinkedIn, the server-side event includes the customer’s billing details hashed with SHA-256 – email, phone, name and address fields as each platform supports – so the platform can match the purchase. GA4 gets the purchase through the Measurement Protocol, and Google Ads can use enhanced conversions.