Our method
Every Oriva guide rests on pages we read, cited at the bottom with their date, and on tests run on real accounts. When we could not check a fact, we do not write it: we write that we could not check it.
What do we check before writing?
Facts about a platform come from its documentation, its help center or its terms, read on the page itself. When a platform contradicts itself from one page to another, we say so instead of choosing. Pages that only display in JavaScript are read in a browser, not guessed from a summary.
Setup guides describe screens we went through. When we could not read a label, we leave it generic rather than guess it.
How do we talk about other tools?
Every comparison says what the other tool does better, and a “Who doesn't need Oriva?” section names the cases where it is the right choice. Its prices carry the date we read them; when a price is not published, we write that it is not published and we quote no estimate.
We do not write that a tool “does not have” a feature we have not seen missing: “not listed on the pages read” is not “does not exist”.
Which figures do we publish?
A platform's figure is always attributed to the platform, with its link (for example Meta's on cost per result). A figure measured at a customer is only published with their written agreement and the method that produced it. We do not publish a result we cannot explain.
Dates and corrections
Who writes?
The guides are signed “the Oriva team”. The site puts no one forward, by choice: what should be trusted is the sources cited at the bottom of each guide and, in your account, the log of every send. The About page lists the commitments the product already keeps. The site's publisher and its host are named in the legal notice (in French).
Try Oriva for free.
14 days to connect your site and watch your sales reach your platforms.
Start free trial