AdPriva Tag
One line of code and your site’s traffic becomes verifiable — privacy-first, no ads.
The AdPriva Tag is a lightweight, headless JavaScript snippet that publishers embed on their sites. It renders nothing: it captures privacy-safe behavioural signals and emits cryptographic engagement proofs, without cookies, trackers or hidden identifiers.
Why Use the Tag?
- Simple integration → One script, as easy as an analytics snippet.
- Headless → Renders no UI; it instruments traffic, it does not serve ads.
- Proof generation → Sends one view event per page load, which AdPriva seals as a view proof.
- Privacy-first → No cross-site tracking or personal data sharing.
Installation
Add this snippet before </body>:
<script async src="https://cdn.adpriva.com/tag.js" data-consent-mode="tcf"></script>
- There is no site key. The tag identifies your site by its hostname, so add the domain in the console first.
async→ the tag never delays your page or your ad calls.data-consent-mode→tcformanual: the tag sends nothing until the visitor consents;off: it starts at page load. A missing attribute meansofftoday; always set it. See Consent modes.- Loaded from
cdn.adpriva.com, the tag sends toingest.adpriva.com. Older embeds oncdn.adpriva-ads.comsend toserver.adpriva-ads.comand keep working. See Content Security Policy.
Proof Integration
- View proofs → one per page load, sent about one second after the page loads (or after consent, in the
tcfandmanualconsent modes), with a behavioural feature vector attached. - Explorer logging → All proofs are verifiable in the AdPriva Explorer.
- Console dashboard → Track verified traffic and validity verdicts in real time.
What the tag sends
Engagement events (view) carry three small objects. Consent events carry none of them.
behavior: the behavioural feature vector (schema v1). Aggregate statistics only. It feeds the behavioural layer (L2) of the validity verdict.
| Field | Meaning |
|---|---|
v | Schema version (1) |
dwell_ms | Foreground dwell time in milliseconds; time in a background tab is excluded |
interacted | Whether any scroll, click or pointer activity happened (false means an instant bounce) |
scroll_n | Number of scroll events |
scroll_cadence_ms | Mean time between scrolls (null with fewer than 2) |
scroll_cadence_cv | How regular the scrolling was: coefficient of variation of the intervals (null with fewer than 2) |
click_n | Number of clicks |
click_entropy | How varied the click timing was, from 0 (perfectly uniform, bot-like) to 1 (varied, human-like); null with fewer than 2 clicks |
ptr_n | Number of pointer-velocity samples |
ptr_v_mean, ptr_v_max | Mean and maximum pointer speed in pixels per millisecond (null with fewer than 2 samples) |
auto_webdriver | navigator.webdriver is true |
auto_headless | The browser looks headless |
auto_flags | Bitmask of other automation hints: missing languages, no plugins, no reported CPU cores, a Chrome user agent without the Chrome runtime |
behavioral: interaction summary. Mouse-move and touch counts, maximum scroll depth (0–1), the last 10 intervals between clicks, and the last 50 relative pointer movements. Absolute screen coordinates never leave the page. The server does not use or store this object today.
environment: device snapshot. Screen and viewport size, platform string and colour depth. These are low-detail values. The server uses only the platform value, to classify the device type, and does not store the snapshot. They are not used to recognise a returning visitor.
The tag also sends the page path and the referrer with engagement events.
What is never sent: keystrokes (there is no keyboard listener), the values of any form field, absolute pointer positions, cookies, or any cross-site identifier. Each object has a fixed list of allowed keys, and the tag’s tests fail if anything outside that list is emitted.
Privacy & Compliance
- No cookies and no cross-site identifiers.
- Consent modes: with
tcformanual, nothing is observed or sent before consent, and a withdrawal stops the tag at once. The one exception is a consent form the publisher opts in to record-only evidence: its submission is recorded with no signals. - Designed for GDPR, ePrivacy and CCPA.
- Only aggregated behavioural signals, a low-detail device snapshot, the page path and the referrer leave the page.
The AdPriva Tag turns any site into verifiable, privacy-first traffic — proof-backed and headless.