Publishers
AdPriva gives you a receipt for every page view on your site, with a verdict on whether it looks like a person. You can share the receipts with partners and auditors. They can re-check them without having to trust your numbers or ours.
What you get
- A proof for every page view. AdPriva’s server seals each view event with an HMAC. The signature is the proof id.
- A score and a verdict for every proof. Each view proof gets a validity score from 0 to 100 and a verdict such as
human,uncertainorabusive_bot. See Proofs of Engagement. - Reports in the console. The console shows your own sites only: the verdict mix, bot rate over time, traffic sources and pages, geography and devices. See Engagement Analytics & Reporting.
- Portable Verification Certificates. Signed JSON files that list your scored proofs for a date range. You download them from the console’s Explorer page.
- Public verification. Every batch of proofs is anchored on Horizen. Anyone with a proof id can look it up in the Explorer and check it against the on-chain root.
- Consent certificates (optional). Sealed evidence of what a visitor agreed to on a web form you mark. See Consent Certificates — Quickstart.
How it works
- Install. Add your domain in the console and paste one script tag with your consent mode, or install the WordPress plugin. See Tag installation.
- Capture. About one second after a page loads, the tag sends one view event with aggregate interaction counts and a one-time nonce. In the
tcformanualconsent mode, it waits for the visitor’s consent first. - Seal and score. The server refuses a replayed event, seals the event as a proof and scores it.
- Anchor. Every 5 minutes, new proofs are grouped into a batch, and the batch’s Merkle root is anchored on Horizen.
- Report and verify. You see your proofs and verdicts in the console. Anyone with a proof id can re-check it in the Explorer.
What AdPriva does not do today
- It does not block bots. AdPriva runs in shadow mode. Verdicts are recorded and published, but no traffic is blocked or dropped because of them.
- It does not record clicks or conversions as proofs. The tag sends one view event per page load. Clicks and scrolls are only counted inside that event.
- It does not decide your lawful basis. The tag does not show a consent banner. It can wait for the consent your own banner collects: set its consent mode to
tcf(IAB TCF v2 banners) ormanual(any other consent tool), and it sends nothing until the visitor consents. Without a consent mode it starts at page load. Whether you need consent is your decision as the controller. See GDPR, ePrivacy, CCPA.
Compared with self-reported analytics
| Self-reported analytics | AdPriva | |
|---|---|---|
| Who records the event | Your own analytics account | AdPriva’s server, from the event the tag sends |
| Checking a single event | Not possible from outside | Anyone can look it up by proof id |
| Bot verdict | Not shown per event | A score and a verdict on every view proof |
| Tamper evidence | None | HMAC seal, and each batch’s membership anchored on Horizen |
| Cookies | Often | None |