Market Comparison
AdPriva checks web traffic and records consent. It gives each page view a sealed, scored proof that anyone can re-check, and it turns submissions of consent forms you mark into sealed certificates. It does not serve ads.
This page compares AdPriva with the kinds of tools publishers already use. It describes categories of tools, not specific products.
By category
| Category | What it usually gives you | What AdPriva adds |
|---|---|---|
| Web analytics | Visit counts and reports inside your own account | A proof for each page view that a third party can look up, a score and verdict for each event, and batch roots anchored on Horizen |
| Bot-detection and invalid-traffic tools | A bot or invalid-traffic decision, shown in the vendor’s own reports | A public score and verdict for each event, and a receipt anyone can check against an on-chain root |
| Consent management platforms | A consent banner and a log of visitors’ choices | A sealed, anchored certificate for each submission of a form you mark. cert_v: 1 certificates can be verified offline |
| Blockchain advertising protocols | Ad delivery or payments recorded on-chain | AdPriva serves no ads. It puts one Merkle root per batch on-chain and nothing else |
Where AdPriva is different
- Each page view has its own receipt, which anyone can look up by proof id.
- Verdicts are published for each event, including automated traffic, instead of being filtered out silently.
- Batch roots are anchored on Horizen.
- The tag sets no cookies and uses no cross-site identifier.
Where AdPriva is narrower
- It does not block bots today. It runs in shadow mode.
- It records one view per page load. It has no click, conversion or custom events.
- It does not show a consent banner or manage visitors’ consent preferences. It witnesses forms that you mark.
- Public verdicts come from user-agent and IP checks. The behaviour and agent-identity results are kept private for now. See Proofs of Engagement.