WooCommerce: your orders sent server-side

WooCommerce doesn't stop scripts from running on the order confirmation page, so the Oriva script runs there normally. It only lacks what only WooCommerce knows: the order amount, currency and reference, and the buyer's email and phone number. The PHP snippet provides them. The email is hashed before it even appears in the page, the phone number before it is saved. With them, Meta, TikTok, Google Ads and OpenAI recognize the person who clicked your ad more reliably.

1. The script: with a plugin like WPCode (“Insert Headers and Footers”), paste the Oriva script into your site's header. Avoid pasting it straight into header.php: a theme update would erase it.
2. The order snippet: paste the PHP code Oriva gives you into your child theme's functions.php, or into a snippets plugin. It relies on woocommerce_thankyou, the hook WooCommerce fires on the confirmation page.
3. The DNS setting, the same for every site.

No: Oriva takes the event identifier from the WooCommerce order number, so going back to the confirmation page never counts the same sale twice. If your Meta or TikTok pixel receives the same number as its event identifier, the platform deduplicates on its side too. A declined payment is never sent.

Connect your cookie banner to Oriva: without the visitor's consent, nothing goes to Meta, TikTok, Google Ads or OpenAI. The code for Complianz and CookieYes, the two most common plugins on WordPress, is on the Any website page. With CookieYes, the plugin must be linked to the CookieYes web app: without that, it does not emit the events Oriva needs.

It doesn't trigger affiliate postbacks, for the same reason as on Shopify: it sends the purchase from the browser. If you pay affiliates, also send those sales through the server API.