Jornaya Integration

What This Integration Does

Connects your own Jornaya account (LeadiD, now part of Verisk Marketing Solutions) to Lead Distro AI so every incoming lead that carries a jornaya_leadid consent token is verified in real time at ingest. When a lead arrives with a token, Lead Distro AI calls Jornaya to confirm the token is authentic, pulls back the consent metadata Jornaya returns, and stores the result on the lead.

This is a bring-your-own-key integration. You connect your own Jornaya Audit/API key (LAK) and optional Account Code (LAC), and Jornaya bills your account directly for each verification. Lead Distro AI adds no markup.

What Is Jornaya (LeadiD)

Jornaya is a consent-tracking platform widely used in regulated lead verticals (insurance, mortgage, legal, home services). A small Jornaya script on the lead form records the consumer's interaction and the consent language they saw, and issues a LeadiD token: a UUID that uniquely identifies that form-fill event. The token is dropped into a hidden form field (historically named universal_leadid) and is passed along with the lead, most commonly under the field name jornaya_leadid.

On its own, a token is just an identifier. To turn it into proof you call Jornaya's authentication API, which confirms whether the token is genuine (Jornaya-issued, not expired, not over-queried, not tied to an opt-out) and returns metadata about the consent event. That verification step is what Lead Distro AI automates at ingest.

Why It's Helpful

• Proof of consent for TCPA. A verified LeadiD token is evidence that a real consumer saw your consent language and submitted the form at a specific time. It is one of the two consent records (alongside TrustedForm) that buyers in regulated verticals commonly require.
• Catch fake, expired, or recycled tokens. Jornaya flags tokens that were not actually issued by Jornaya, are too old, have been queried too many times, or are tied to a CCPA opt-out. Verifying at ingest keeps those leads out of your distribution flow.
• Protect your buyers and your return rate. Filtering non-authentic tokens before a lead is sold keeps low-quality and non-consented leads off your buyers' desks, which protects buyer trust and your reputation.
• Meet buyer requirements. Many buyers accept either a TrustedForm certificate or a Jornaya LeadiD token. Supporting both means you can take leads from any supplier's compliance stack.

How Lead Distro AI Integrates With Jornaya

The integration runs inside the ingest pipeline. The flow is automatic once set up:

• A supplier sends a lead that includes a jornaya_leadid field (the LeadiD token captured on the lead form). The raw Jornaya field name universal_leadid is also accepted as a fallback.
• Lead Distro AI confirms the value looks like a valid LeadiD token (a UUID) so a malformed value never burns a billed lookup.
• If your organization has a Jornaya API key connected, Lead Distro AI calls Jornaya's authentication API with the token and your Account Code.
• Jornaya responds with whether the token is authentic plus any consent metadata and warnings (for example token too old, over-queried, or opted out).
• Lead Distro AI stores the result on the lead under signal_data.jornaya, where it is visible on the lead detail page and fed into AI lead scoring as a quality signal.

Required vs Optional Tokens

Whether a failed verification rejects the lead is controlled by the jornaya_leadid field in your campaign's field mapping:

• Optional field (recommended for now). The token is verified and the result is recorded and passed to buyers, but a failed or unverified token does not block the lead. The signal is captured for scoring and for the buyer to evaluate.
• Required field. If the token is missing, malformed, or fails verification, the lead is rejected at ingest with a 400 and a clear reason. The rejection is logged to lead activity for audit. Use this once you have confirmed verification against your live Jornaya account.

Prerequisites

• A Jornaya (Verisk Marketing Solutions) account with API access.
• Your Jornaya Audit/API key (LAK) and, optionally, your Account Code (LAC).
• Lead forms running the Jornaya script so each submission produces a LeadiD token.
• Your supplier passing that token with the lead, ideally under the field name jornaya_leadid.

Step 1 — Connect Your API Key

• In Lead Distro AI, go to Settings → Integrations → Jornaya.
• Click the card to open the connection dialog.
• Paste your Jornaya Audit/API key (LAK).
• Optionally add your Account Code (LAC). Leave it blank if your key already scopes to a single account.
• Click Save. The key is stored on your organization and used only to authenticate calls to your own Jornaya account.

Step 2 — Map the Token Field

• Open the campaign that will receive leads with consent tokens and go to Field Mapping.
• Add the jornaya_leadid field (it is in the Compliance group of the field picker, or use the Quick Add compliance preset).
• Leave it optional to capture the token as a signal, or mark it required to reject leads with a missing or invalid token (see the status note above before requiring).
• If your supplier sends the token under a different key (for example universal_leadid), map that incoming key to jornaya_leadid.

Step 3 — Send a Test Lead

Send a test lead that includes a real jornaya_leadid token. Open the lead detail page and look for the Jornaya block under the lead's signals. You should see whether the token was verified, whether Jornaya reported it authentic, the token age if returned, and any warnings.

What Gets Captured

Pricing

Jornaya bills your own account directly for each token verification. Lead Distro AI adds no markup. Because a verification only happens when a lead arrives with a valid-looking token and your key is connected, you control spend by choosing which campaigns map the jornaya_leadid field.