Developer integration

Install after consent. Confirm from your server.

AdPriva works alongside your existing consent platform and forms. The tag observes the configured consent interaction after the required permission is granted. Your backend confirms the Evidence ID and links it to the lead using a pseudonymous reference.

Contact-field contents stay in your systems.

Read the docs

API integration available for pilot evaluation. See the documentation for supported endpoints and fields.

Confirm the Evidence ID from your server

POST /v1/evidence/EV-7F3A-91C2/confirm
Authorization: Bearer sk_test_…
Idempotency-Key: 7c1d…

{ "customer_reference": "a3f89c…12be" }
// HMAC-SHA256 of your lead ID, with a key only you hold

200 OK
{
  "outcome": "confirmed",
  "checks": "complete",
  "proof_policy": "pending",
  "chain_proof": "pending",
  "timestamp_proof": "unavailable"
}

Step 01

Load the tag after consent.

Use your existing consent-management platform to control when AdPriva loads. The tag starts observing the configured form only after the required permission is granted.

Didomi integration example

Illustrative structure.
Use your Console-generated snippet.

<script type="didomi/javascript"
  data-vendor="YOUR_VENDOR_API_ID"
  src="TAG_URL"
  data-site="SITE_KEY"
  data-consent-mode="didomi">
</script>

Consent-controlled loading: AdPriva loads only after the required consent is granted. Withdrawal stops further collection.
Test before launch: Use staging credentials to validate consent handling and form integration before production.

Step 02

Mark your consent form.

Use data-adpriva-role attributes to identify the consent wording, checkbox and submission action. Mark personal-data fields for exclusion, so AdPriva can capture the consent interaction without collecting contact details.

Consent form integration

<form data-adpriva-role="offer">
  <input
    name="phone"
    data-adpriva-role="personal-data"
  />

  <label>
    <input
      type="checkbox"
      data-adpriva-role="opt-in"
    />
    <span data-adpriva-role="consent-language">
      I agree to be called by Example Insurance.
    </span>
  </label>

  <button
    type="submit"
    data-adpriva-role="submit">
    Get my quote
  </button>
</form>

Simplified example. Validate the exact attributes and required markup against the current integration specification.

Key attributes

opt-in: Consent checkbox
consent-language: Consent wording displayed
personal-data: Field excluded from content collection
submit: Form submission action

See all supported attributes in the developer docs

Step 03

Confirm each Evidence ID.

When a lead is submitted, your backend confirms its Evidence ID and links it to the lead using a pseudonymous reference.

Your original lead reference and HMAC key stay in your systems.

Server-side confirmation

POST /v1/evidence/EV-7F3A-91C2/confirm
Authorization: Bearer sk_test_…
Idempotency-Key: 7c1d…

{
  "customer_reference": "a3f89c…12be"
}

200 OK
{
  "outcome": "confirmed",
  "checks": "complete",
  "proof_policy": "pending",
  "chain_proof": "pending",
  "timestamp_proof": "unavailable"
}

Confirm the Evidence ID from your backend, not from the browser.
Use an HMAC-based reference so the original lead identifier does not need to be sent.
Use idempotency keys to handle retries safely.

API example based on the current page. Validate endpoint, response fields and confirmation behavior against the implemented API before publication.

Step 04 · For lead buyers

Check the evidence before accepting a lead.

Use the Evidence ID received with a lead to request an evidence check from your backend.

AdPriva returns the check outcome and the status of the associated proofs, so your system can decide whether to accept, review or hold the lead.

Check an Evidence ID

POST /v1/evidence/EV-7F3A-91C2/check?wait_ms=300
Authorization: Bearer sk_test_…

200 OK
{
  "outcome": "passed",
  "results": "provisional",
  "chain_proof": "pending"
}

Example based on the current page. Confirm the endpoint and response schema against the implemented API.

Understand the response

Awaiting evidence
The event has not arrived yet. Retry or hold the lead according to your policy.
Provisional
The configured checks have run, but some required proofs may still be pending.
Final
The proofs required by the configured policy are attached and their status can be evaluated.

A passed technical check does not establish that consent is legally valid.

Connect evidence to your workflow.

Link from your CRM

Store the Evidence ID alongside each lead, so your team can open its associated evidence in AdPriva through the supported access controls.

https://console.adpriva.com/evidence/{evidence_id}

Stay informed with webhooks

Use supported webhook events to keep your systems informed as evidence records and their associated processing states change.

Explore webhook documentation

Build with AdPriva.

Tell us about your forms, consent platform and existing infrastructure. We’ll explore how AdPriva can fit your technical environment.

Explore a pilot

Who it’s for: Developers and technical teams working with lead forms, consent platforms, CRMs or lead-buying systems.
What you get: Pilot access, integration guidance and direct collaboration with the AdPriva engineering team.
What happens next: We’ll review your technical stack, discuss integration requirements and identify a suitable pilot together.