FAQs

General

How is AdPriva different from analytics or bot-filtering tools?

Those tools give you numbers you have to take on trust. AdPriva gives every page view its own receipt:

  • a proof, sealed with an HMAC by AdPriva’s server;
  • a public validity score and verdict (human, uncertain or abusive_bot);
  • an anchor: the proof’s batch root is written to the Horizen blockchain.

Anyone with a proof id can re-check it on the public Explorer, without an account.

Is blockchain used for everything?

No. Proofs are sealed and stored off-chain. Every 5 minutes, new proofs are grouped into a batch, and only the batch’s Merkle root is anchored on Horizen.

How does AdPriva detect bots?

The public score and verdict come from two checks on the ingest server: what the client says about itself in its user agent (L0), and whether it connects from a datacenter or cloud network (L1). A separate scoring service also checks whether the behaviour looks like a person’s (L2) and whether the client carries a valid signature as a declared agent (L3). Those two run in shadow mode: their result is kept privately and does not change the public verdict yet. See Proofs of Engagement. Replayed events are refused, because every event carries a one-time nonce.

Does AdPriva block bots?

Not today. AdPriva runs in shadow mode: every proof is scored and its verdict is published, but nothing is blocked or dropped because of a verdict. The tag never blocks anything on your pages.

Is AdPriva compliant with privacy rules?

AdPriva is built to collect little: no cookies, no cross-site identifiers, aggregate interaction counts only, and nothing that identifies a visitor in the public record. Whether a given use is compliant depends on how the publisher uses it. See GDPR, ePrivacy, CCPA and Data-Processor Posture.

Publishers

How do I add AdPriva to my site?

  • Any website: add your domain in the console, then add one script tag. See Tag installation.
  • WordPress: install the AdPriva plugin from WordPress.org and click Connect with AdPriva. The plugin registers your site and loads the tag for you.

What do I get?

  • A proof, a validity score and a verdict for every page view.
  • Traffic reports in the console: verdict mix, bot rate over time, traffic sources, pages, geography and devices.
  • Portable Verification Certificates: signed JSON files you can download from the console and share with partners or auditors.
  • Optional consent certificates for your web forms. See Consent Certificates — Quickstart.

Can I use AdPriva alongside my existing stack?

Yes. The tag is headless. It renders nothing, sets no cookies and does not change your pages.

Visitors

Does the AdPriva tag track me?

The tag sets no cookies and uses no cross-site identifier. It sends aggregate counts (how long the page was in the foreground, how many scrolls and clicks, pointer speed), a low-detail device snapshot, the page path and the referrer. It never records keystrokes or what you type into forms. AdPriva’s server also sees your IP address and user agent; the raw values are emptied after 30 days. See Consent & Privacy Model.

Do I need to install anything?

No. There is nothing for visitors to install or sign up for.

Will the tag slow down pages?

The tag loads asynchronously, is under 10 KB compressed, and renders nothing.

Developers

How do I integrate AdPriva?

There is no SDK package. You use:

  • the tag on your pages;
  • the public API at https://api.adpriva.com/public/... to look up proofs and certificates, with no credentials;
  • the signed-in API (a JWT from POST /auth/login) to read your own organization’s proofs.

See the API Reference.

What does a proof look like?

A JSON record with an opaque proof id, type, status, creation time, validity score, verdict, and, once batched, a Merkle inclusion receipt and the Horizen references. Batches anchored before 2026-09-28 also carry a zkVerify reference. See Proofs of Engagement.

How are proofs verified?

Take the proof’s Merkle inclusion receipt, recompute the batch root, and compare it with the Anchored(merkleRoot) event in the Horizen transaction. The API Reference has the exact algorithm.

Can I export proofs for an audit?

Yes. Download a Portable Verification Certificate for a date range from the console’s Explorer page. It lists your scored proofs by id, type and verdict, and carries a SHA-256 digest and an HMAC over its content.