Engagement Analytics & Reporting
AdPriva’s reports are built from proofs, and every proof can be looked up on its own. This page lists the reports in the console and the export you can hand to a partner or auditor.
Console reports
All reports cover your own organization’s sites only, for the date range you choose.
| Page | What it shows |
|---|---|
| Dashboard | Total proofs, batches and batches confirmed on-chain (the console calls batches “snapshots”), traffic flagged, the validity mix and bot rate over time, and proofs against anchored proofs over time |
| Traffic Quality: Overview | The validity distribution and the bot rate by traffic source |
| Traffic Quality: Events | One row per proof: time, site, type, score, verdict, the reasons behind the verdict, and a link to verify it |
| Traffic Quality: Sources | Traffic sources (referrers) and top pages |
| Traffic Quality: Geo | Country, device class, browser and OS |
| Traffic Quality: Funnel | The proof lifecycle: sealed, scored, batched, anchored on Horizen |
| Traffic Quality: Consent | Consent certificates: granted against denied, and a breakdown by consent form |
| Traffic Quality: Delta | A comparison of AdPriva’s verdicts with another vendor’s, for organizations that send that vendor’s verdicts to AdPriva |
| Explorer | Your proofs and batches, with filters, and the certificate export described below |
The dashboard also shows a money protected figure. It is a rough estimate: the number of abusive_bot proofs multiplied by $0.50. It is not a measured loss.
For the definitions of the validity mix and the bot rate, see Attention & Engagement Metrics.
WordPress
The AdPriva WordPress plugin shows a summary in wp-admin: KPI cards, a human against bot breakdown, and a trend chart over the last 7, 30 or 90 days, with a link to the full console.
Portable Verification Certificates (PVCs)
From the console’s Explorer page you can download a PVC for a date range. It is a JSON file that contains:
- your organization’s scored proofs in that range, each with its proof id, type and verdict;
- the range and the time the certificate was made;
- the batch’s Merkle root and anchor transaction, when all the proofs fall in one batch;
- a SHA-256 digest over the content and an HMAC signature.
The digest is SHA-256 over the file’s JSON with the sha256 and hmac fields left out, keys sorted at every level, and no whitespace. The console recomputes it before it hands you the file, and anyone can do the same to catch accidental changes. The HMAC uses AdPriva’s own key, so only AdPriva can check it. To check the contents independently, look up the proof ids on the public Explorer.
Checking a number yourself
Any proof in a report can be checked independently. Look it up by its id on the Explorer or through the public API, take its Merkle inclusion receipt, and recompute the batch root. The API Reference has the algorithm.