Description
Oriva for WooCommerce connects your shop to your Oriva account. Oriva is a conversion-tracking service: it receives your sales and passes them on to the advertising platforms you connect, and keeps a journal of every delivery so you can see what arrived and why something did not.
The plugin is free. Oriva is a paid service, after a 14-day free trial that asks for a card. You need an Oriva account to use the plugin: without one it does nothing.
What it does
- Sends each paid order from your server, not from the thank-you page. A buyer who never comes back from the bank’s page, a payment confirmed later by the gateway, a reloaded confirmation page: the sale is still sent, once.
- Puts Oriva’s browser tracker on your pages, on a sub-domain of your own site, so that it is first-party.
- Follows your visitors’ consent. A sale is sent to the advertising platforms, with its buyer data (a hashed email and phone number, the IP address and browser), only for visitors who accepted advertising cookies through your cookie banner. Without their consent the sale is still counted in your Oriva account, but it is not sent to the platforms and nothing that identifies the person is sent at all.
- Never slows or breaks your checkout. Nothing is sent while the order is being placed: the order is only flagged, and a background task does the sending, retrying on its own if Oriva cannot be reached.
- Works with the classic and the block checkout, and with High-Performance Order Storage.
Your cookie banner
The plugin understands banners that follow WordPress’s WP Consent API (Complianz, CookieYes, Cookiebot and others). With another banner, you wire it to Oriva with two lines of code that your Oriva account explains. With no banner, no sale is sent to the advertising platforms, which is the safe default: the sales are still counted in your Oriva account. A setting lets you declare consent for everyone: only use it if that is true for your site.
What you need
- An Oriva account, a domain added in it, and a DNS record for
t.your-domainthat Oriva shows you (the browser tracker needs it). - WooCommerce 8.0 or later.
External services
This plugin is a client of Oriva, a conversion-tracking service operated by Oriva (https://www.orivaforge.com). It does nothing, and contacts nobody, until an administrator connects the site to an Oriva account. It sends the following, to the following places, at the following times.
1. Oriva, https://www.orivaforge.com
- When an administrator clicks “Connect to Oriva”: the address of the site, the address of the plugin’s own admin page, a random value and the hash of another random value (to make the connection safe), and the versions of the plugin, WordPress and WooCommerce. Then, to finish the connection, a one-time code and the random value it belongs to. What comes back is the keys of your Oriva domain.
- For every paid WooCommerce order, from your server: the order number, the amount and the currency. Only for a visitor who accepted advertising cookies: a visitor identifier, the buyer’s email address and phone number (each hashed with SHA-256 by the plugin before it is sent), the IP address and the browser of the buyer as recorded on the order, and the address of the shop.
Why: to count the sale, and to let Oriva pass it on to the advertising platforms you connect in your Oriva account (Meta, TikTok, Google Ads, ChatGPT Ads). The plugin never contacts those platforms itself.
2. Your tracking address, https://t.your-domain
A sub-domain of your own site that you point, with a DNS record, to Oriva’s collector. After the connection, your visitors’ browsers send it the pages they view and the events your pages raise. The plugin reads your cookie banner’s marketing choice (the wp_consent_marketing cookie) and passes it on. Oriva’s collector sets a first-party visitor cookie (or_vid) on your domain only for visitors who accepted advertising cookies; the plugin sets a session cookie (oriva_ads) that records the visitor’s last choice so that the server can honour it when an order is created.
The tracker’s code is included in the plugin (the assets folder) in readable form; nothing is loaded from another site.
Terms and privacy
- Terms of service: https://www.orivaforge.com/en/terms
- Privacy policy: https://www.orivaforge.com/en/privacy
Screenshots
Installation
- Install and activate the plugin.
- Open WooCommerce > Oriva and click “Connect to Oriva”.
- Sign in to Oriva, choose your domain, and confirm. You come back to your site.
- Add the DNS record
t.your-domainthat Oriva shows you.
If the button cannot work (a firewall, a staging site), paste your keys by hand in the “Connect manually” section of the same page.
FAQ
-
Does it cost anything?
-
The plugin is free. It needs an Oriva account, and Oriva is a paid service after a 14-day free trial.
-
Does it send anything before I connect it?
-
No. Until an administrator connects the site, the plugin contacts nobody and loads nothing on your pages.
-
What does it send to Oriva?
-
See the “External services” section below. In short: the pages your visitors view, and each paid order with its amount and currency; for visitors who accepted advertising cookies, also a hashed email and phone number, the buyer’s IP address and browser, and a visitor identifier.
-
The sale is counted in your Oriva account, but it is not sent to the advertising platforms, and nothing that identifies the buyer is sent at all. Add a banner, or use the setting that declares consent for every visitor if that is true for your site.
-
I already use Meta’s own plugin or a pixel. Will sales be counted twice?
-
Possibly. Oriva’s Health tab shows when the same sale reaches it from two places. If you pasted the old WooCommerce snippet from Oriva’s documentation on your thank-you page, remove it: the plugin replaces it.
-
Does it work with bank transfer and cheque payments?
-
By default an order is sent when it becomes paid (processing or completed). A setting lets you send those orders when they are placed instead.
-
Does it work with the block checkout and High-Performance Order Storage?
-
Yes, both are declared and tested.
-
What happens to my orders if I deactivate or delete the plugin?
-
Nothing is deleted from your orders. Deleting the plugin removes its settings and cancels its queued sends. The key stays active in your Oriva account until you revoke it there.
-
My ad campaigns do not show on my sales. What can I check?
-
Oriva reads the ad click identifier (
gclid,fbclid,utm_parameters and similar) from the address the visitor lands on. If that address redirects before the page loads (from www to the bare domain, a missing trailing slash, http to https), some hosts remove these parameters during the redirect (their cache), and the sale arrives without a campaign. The plugin cannot put back what the host removed.Use, as the address of your ads, exactly the one your site serves: with or without www, and with the trailing slash it ends up on. To check, open your ad’s address with
?gclid=testat the end: if the parameter is still in the address bar once the page has loaded, nothing was lost. If it disappears, ask your host whether its cache or protection removes tracking parameters, and whether that can be turned off or your domain excluded. -
Where do I get help?
-
Write to us from your Oriva account (the Help page), or use the support forum of this plugin.
Reviews
ഈ പ്ലഗിന് റിവ്യൂകൾ ഒന്നുമില്ല.
Contributors & Developers
“Oriva for WooCommerce” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Oriva for WooCommerce” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
0.1.6
- New: the plugin’s admin page and order notes are translated into French.
0.1.5
- Change: WordPress now checks that WooCommerce is installed and active before it activates the plugin (“Requires Plugins” header).
0.1.4
- Fix: the translation text domain is the plugin’s directory slug, oriva-for-woocommerce.
0.1.3
- Fix: the tracker’s script files carry the plugin version in their name, so a hosting cache that ignores the query string cannot keep serving an old copy after an update.
0.1.1
- Fix: the browser tracker now follows the consent setting, so “Always granted” also applies to page views on a site without a cookie banner.
0.1.0
- First version: connection to an Oriva account, the browser tracker, and paid orders sent from the server with retries, for the classic and the block checkout.