Documentation · Prynt Reveal

Prynt Reveal documentation

Reveal turns anonymous traffic into named companies — and, only from your own forms and logins, named people. One script, no cookies, consent-aware by default. Pick your platform below or read the reference pages.

Quickstart — From sign-up to live: three actions, no credit card, under five minutes including pasting the snippet. The first companies appear as soon as visitors browse from company networks.

The snippet

Copy it from the console (Websites → your site → Install); it already carries your public key and the verified domain. It loads asynchronously and never blocks rendering.

<script src="https://api.pryntid.com/cdn/prynt-reveal.umd.js" async
  onload="PryntReveal.reveal({publicKey:'pk_live_YOUR_PUBLIC_KEY',website:'example.com'})"></script>

That is the Reveal-only build (prynt-reveal.umd.js, about 14 kB, global PryntReveal): no device-intelligence code, nothing else to load. Sites that already run the Prynt agent (Prynt.load() for fraud and bot detection) keep the full bundle, where Reveal is PryntReveal.reveal() with the same options and the agent's visitor id attached:

<!-- Already running the Prynt device-intelligence agent? Use the full bundle instead: -->
<script src="https://api.pryntid.com/cdn/prynt.umd.js" async
  onload="Prynt.reveal({publicKey:'pk_live_YOUR_PUBLIC_KEY',website:'example.com'})"></script>

Using a bundler? npm install @pryntid/js and call reveal() from @pryntid/js/reveal once per page load; SPA route changes are followed automatically.

import { reveal } from '@pryntid/js/reveal';   // Reveal-only (~6 kB gzip)
// import Prynt from '@pryntid/js'; Prynt.reveal(…)  // full agent, when you also use Prynt.load()

const client = reveal({
  publicKey: 'pk_live_YOUR_PUBLIC_KEY',
  website: 'example.com',          // the verified website in the console
  // consent: () => cmp.allowed('analytics'),   // optional: CookieYes/Cookiebot/OneTrust/Klaro/TCF/GCM are auto-detected
  // forms: ['#demo-form'],                     // optional: email/name from your own forms (needs consent)
});

Check the installation

Open any page of your site with ?prynt_debug=1 to see a small panel with the loaded state, the key, the website, consent and where it came from, the detected consent manager, storage, GPC, whether a Content-Security-Policy blocked the beacon, and the last send. The same values come back from diagnose() in the browser console.

// In the browser console, on a page with the snippet installed:
PryntReveal.reveal({ publicKey: 'pk_live_YOUR_PUBLIC_KEY' }).diagnose()      // full bundle: Prynt.reveal(...)
// → { loaded: true, sdkVersion: "1.0.0", publicKey: "pk_live_ab…yz", website: "example.com",
//     endpoint: "https://api.pryntid.com", consent: true, consentSource: "cookiebot", cmpDetected: "cookiebot",
//     storage: "localStorage", gpc: false, cspBlocked: false, sessionId: "rvs_…", visitorId: null,
//     queued: 0, lastSend: { at: "…", status: 202, accepted: 1, error: null } }

// Or open any page with ?prynt_debug=1 to see the same values in a small panel.

In the console, Websites → Test Script fetches your page from our side and runs the seven install checks (snippet present, public key, website match, CSP script-src, CSP connect-src, consent manager, script position, www redirect) and shows the live pulse (last event, events and sessions in the last 24 h).

Reference

  • CSP and storage — the two hosts to allow, the one localStorage key, zero cookies, and exactly what is sent.
  • Consent — consent managers detected automatically, Global Privacy Control, the explicit option and what leaves the browser without consent.
  • Webhooks — signed deliveries and verification samples in Python, Node, PHP, Go and Ruby.
  • Limits — batch sizes, rate limits, field caps and plan limits.

API reference for the server side (/v1/reveal/*, secret key): see the OpenAPI document in the console under Developers. Visitors can opt out of identification on every site that uses Prynt at /legal/reveal-opt-out.

Next: Quickstart

Last updated 2026-11-03 · Limits · Visitor opt-out