Documentation · Prynt Reveal

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.

1. Create the account and add your website

  1. Sign up at app.pryntid.com/signup?product=reveal with your work email — the Free plan needs no card (100 companies a month, 1 website, 7-day history).
  2. Your website is created from your email's domain (with a personal address the console asks for it once) together with a public key restricted to https://<domain> and https://www.<domain>. Subdomains are covered.
  3. Nothing to verify by hand: the first visit with the snippet, from your own domain over https, verifies the website. A DNS TXT record or a meta tag stays available under **Reveal → Settings** for sites that cannot run the snippet yet.

2. Install the snippet

Copy the snippet from **Websites → your site → Install**: it already carries your public key and domain. Paste it in the <head> of every page, or follow the guide for your platform (WordPress, WPCode, Google Tag Manager, Webflow, Shopify, Next.js and more).

<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>

It loads asynchronously, sets no cookies and stores one localStorage key only after consent. In Europe it starts consent-off: read Consent before going live.

3. Check the installation

Open any page with ?prynt_debug=1 and look for loaded: true, the right website and lastSend.status: 202. Then, in the console, **Websites → Test Script** fetches your page from our side and runs the install checks; the live pulse shows the last event and the sessions of the last 24 hours.

// 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.

4. See your first companies

**Reveal → Companies** lists the accounts identified on your sites with the confidence, the resolution method and the reasons behind each match, the pages they read and an intent score. Visits from home broadband, mobile carriers, hosting providers, VPNs and Tor stay anonymous — they are not companies — and never spend a credit.

Each company spends one credit per website per calendar month; repeat visits that month are free. See Credits.

5. Add people from your own forms (optional)

Reveal links a person to a visit only from evidence you collect yourself. Capture the email of your own forms on submit (with consent) or call identify from your server after a login:

// Read the email of YOUR OWN forms on submit (sent only with consent). true = every form, or CSS selectors:
PryntReveal.reveal({ publicKey: 'pk_live_YOUR_PUBLIC_KEY', website: 'example.com', forms: ['#demo-form'] });
# After a login or a form on YOUR server: link the person to the browser session (first-party evidence)
curl -X POST https://api.pryntid.com/v1/reveal/identify \
  -H "Authorization: Bearer sk_live_YOUR_SECRET_KEY" -H "Content-Type: application/json" \
  -d '{"sessionId": "rvs_…", "email": "[email protected]", "name": "Ann Lee", "consentRef": "signup-terms-v3"}'

# → 200 {"status": "VERIFIED_PERSON", "person": {"id": 81, "status": "verified", "displayName": "Ann Lee",
#        "identifiers": [{"kind": "email", "verified": true, "masked": "a***@acme.com"}],
#        "evidence": [{"type": "login", "consentRef": "signup-terms-v3", "collectedAt": "2026-11-03T10:02:11Z"}], …}}

First-party people are included on every plan, Free included. Reveal never infers a person from an IP address, a device or a third-party database.

Next steps

  • Alerts: connect Slack (Starter and up) or HubSpot, signed webhooks, n8n and Zapier (Growth and up) under **Reveal → Integrations** — webhook verification samples.
  • Focus: set your ICP, hot pages and segments so alerts fire only for accounts that matter.
  • Server side: pull companies, people and sessions with the API (Scale and up).
  • Before launch: CSP and storage, Consent and Limits.

Next: CSP and storage

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