Jornaya certifies that a consumer filled in a form and saw your disclosure, and hands the buyer a LeadiD token as the evidence. Like TrustedForm, it is only worth anything if the token reaches a field on the lead and stays there. A token that lands in an unmapped POST parameter is a consent record you paid for and discarded.
First, the name. Jornaya was acquired by Verisk and folded into Verisk Marketing Solutions. As of today jornaya.com redirects to verisk.com, and the old documentation domain redirects into Verisk help. Your sellers will still say "Jornaya" and "LeadiD" on the spec sheet, and the field names have not changed, but do not expect to find a standalone Jornaya site to read.
Integrations on demand. We are not a Verisk partner and there is no connector to switch on. Our team wires the token capture and the verification step as scoped work, quoted per setup.
What arrives
A LeadiD token: an identifier generated by a script on the seller's form while the consumer was filling it in. It travels as one more field on the post, commonly named leadid_token or universal_leadid, though the seller's spec is what decides.
The token is a pointer to a recorded consent event, not the event itself. It becomes evidence when you verify it against Verisk and store the result.
Where it belongs in VICIdial
Write it to a lead custom field at creation, in the same non_agent_api.php call that creates the record:
non_agent_api.php?function=add_lead
&phone_number=&list_id=
&vendor_lead_code=<seller lead id>
&dnc_check=Y&campaign_dnc_check=Y
with the token, the verification outcome and the timestamp you verified at written alongside. The timestamp matters as much as the token - a consent record with no evidence of when you checked it is weaker than one with.
It also runs the other way
The verification call is the outbound direction, and it happens on ingestion rather than mid-call: your endpoint receives the post, calls Verisk to verify the token, and only then creates the lead. A token that fails verification should stop the record before it reaches the hopper, not after an agent has dialled it.
This is the same shape as the TrustedForm claim. Where a live transfer is in play, the verified consent token is what makes the transfer saleable to a buyer who demands proof - see live transfer on a buyer API response.
Gotchas
Jornaya and TrustedForm are not alternatives. Plenty of sellers attach both. Buyers who accept only one of them are a reason to keep both fields rather than picking a favourite at mapping time.
One token, one consent event. Do not carry a token across a re-post or a deduplicated record. It documents one person filling in one form once.
Verify before you dial, not after. The cheapest outcome for a bad token is that no agent ever calls the number.
The field name is the seller's choice. Two sellers in the same vertical will name it differently. The mapping is per-seller and is part of the setup, not a one-time configuration.
Retention outlives the buying relationship. Keep it on the dialer, which you will still have long after the seller is gone.
Related: consent and TCPA certification and our TCPA guidance.