What Oriva does, from the visit to the delivered sale

Tracking goes through a subdomain of your site (t.yourstore.com), linked to Oriva by a DNS record. To the visitor's browser, it is not a third-party tool: the cookie that recognizes them is set by your domain. On arrival, Oriva captures the ad platforms' click IDs (fbclid, ttclid, gclid, gbraid, wbraid, msclkid), your affiliates' (aff_click_id, subid) and the UTM parameters, to tie each sale to the ad that brought it.

Attribution goes to the last click, within 30 days: an older click no longer counts.

Install Oriva on your site

Every conversion carries a unique identifier, your order reference. If the same sale arrives twice (page refresh, browser then server, a retry after a network outage), Oriva keeps it only once, and sends it only once to each platform.

If your Meta or TikTok pixel also sends the sale, give it the same reference: the platform then deduplicates on its side. The Health tab warns you if it sees the same order arrive by two different paths.

Without the visitor's consent to advertising, Oriva sets no advertising cookie, keeps no click ID and no personal data, and nothing goes to Meta, TikTok, Google Ads or OpenAI. The visit is counted, anonymously. Your cookie banner passes the visitor's choice to Oriva in a few lines, for Axeptio, Didomi, Cookiebot, tarteaucitron, Complianz and CookieYes.

The personal data you send (email, phone) is irreversibly hashed before it is stored, and the IP address is erased after 90 days. Data stored in the European Union.

Connect your cookie banner

For every sale, and for every platform, the log shows what was sent, when, and what the platform answered. When a send is rejected, the reason is translated into plain language, with what to do (“token expired, generate a new one”). A temporary error is replayed automatically, up to five times over about fifteen hours.

A tab that answers one question: are my sales reaching the platforms? Each destination has a status (active, needs attention, failing, awaiting conversions). And signals when something is wrong: tracking has stopped for 48 hours, DNS no longer answers, almost no visitors give consent, a destination is failing, too few sales carry an email, the same order arrives twice.

Counts, not scores: “38% of your purchases go out without an email”, never a mark out of 10 whose formula nobody knows.

A button sends a test call to Meta, TikTok, Google Ads or ChatGPT Ads and shows you their response, before your first sale rather than after. No fake sale is created. Google and ChatGPT Ads check the request without recording anything; Meta and TikTok use your test event code.

Revenue, spend and ROAS by day and by campaign, with the change against the previous period. One currency never mixes with another: if your spend is in euros and a sale in dollars, Oriva doesn't invent an exchange rate.

Spend is entered by hand, campaign by campaign: Oriva doesn't read your spend from Meta, TikTok, Google Ads or ChatGPT Ads yet.

Meta reports 40 sales, Oriva saw 25: the page shows both figures side by side, and explains why they differ. Meta also counts sales after a simple ad view and estimated conversions; Google attributes a sale to the day of the click; TikTok to the day the ad was viewed. Oriva only counts observed sales. The last two days are flagged as provisional, because the platforms are still completing them.

The platform's figure is entered by hand, along with the spend.

How long your visitors take to buy after their click, by campaign: the median delay, and the one under which 80% of sales happened. Enough to understand why the figures for the last few days keep rising after the fact.