Glossary · Term

Jornaya

A consent-capture and lead-verification service producing a LeadiD token that documents the origin of a lead.

Definition

Jornaya's LeadiD records the session that produced a lead, including timestamps, page interactions, and consent language shown. It functions similarly to TrustedForm and is often required by regulated verticals as evidence of consented collection. Networks operating in insurance, mortgage, or financial verticals typically maintain both.

Why it matters

Buyers in regulated verticals increasingly refuse to pay for leads that do not present a valid Jornaya token, and disputed leads without a verifiable record are functionally worthless in an audit. The token capture has to happen at the source and be preserved through every hop.

How it fails in practice

Tokens are captured client-side but not correctly attached to the post payload, and the buyer receives leads with the field missing or malformed. The buyer rejects those leads for compliance; the source continues sending them; the network loses two weeks of billable inventory before the drop is noticed.

See jornaya in your operation.

A 30-minute working session to map how this term shows up in your platforms, workflows, and reporting — and where it is currently exposed.