Jornaya on your landing pages
In the verticals where LeadiD is a condition of purchase, a page without it is a page you can't sell from. LanderLab installs the Jornaya script for you from your Account Code and Campaign Key, and from then on every visitor session on the page gets a token that's saved with the lead and sent along with it.
It's built for lead sellers in regulated markets: auto and home insurance, Medicare, mortgage, solar, home services. These are the buyers who check the token before they accept a lead, or claw back the payout later when it's missing, after your media spend is long gone.
A Jornaya LeadiD token on every submit
Jornaya starts recording the session when the page loads. On submit, the LeadiD token is stored with the lead and sent along to your CRM, your lead platform or your buyer, next to the name and phone number.
On an A/B test you choose which variants carry it, so the variant you're testing doesn't quietly produce leads no buyer will take.
When the buyer asks for a LeadiD
Many buyers of insurance, Medicare, mortgage, solar and home services leads make a LeadiD a condition of purchase. Without the token, a lead can be rejected when you post it or returned later, after you've paid for the click. With it, a missing token is never the reason a lead is turned away.
The token rides through the integrations you already sell with, whether that's a ping-post platform, a lender's CRM or a webhook to the buyer's endpoint, so nothing extra sits between the form and the payout.
Run Jornaya next to TrustedForm
Some buyers want a LeadiD, some a TrustedForm certificate, some both. Switch on Jornaya and TrustedForm on the same page and every lead carries both records, so one form can sell to all of them without a second version of the page. With Workflows (beta) routing leads by state or vertical, each buyer receives the record it asked for.
Trace a returned lead to the click
A token proves the session; LanderLab's own fields tell you where it came from. Each lead also carries the page URL, the variant, the visitor's IP and the submit time, and hidden fields keep the UTMs, the gclid and the affiliate ID. When a buyer disputes a lead, you can find the source, the placement and the variant behind it, and cut the traffic that produces disputes.
