TrustedForm vs Jornaya in 2026: Why One Is a Pre-Ping Quality Signal and the Other Is a Post-Buy Dispute Artifact
- Jornaya’s LeadiD token fires at form load, so session signals (time on page, field interaction, copy-paste flags) are attached to the lead BEFORE it posts. That is the only one of the two you can wire into pre-ping filtering inside LeadConduit or Ringba.
- TrustedForm certificates are stored on ActiveProspect’s servers from the moment they mint. Per ActiveProspect’s TrustedForm Certificate API docs, an unclaimed cert is accessible for up to 72 hours before it expires, and claiming is what extends retention (commonly 90 days, or longer on extended plans) and locks it in as your defensible record.
- Pay-per-call shops get more from TrustedForm (call certs, carrier mandates, dispute defense). High-volume form-fill buyers get more from Jornaya (pre-ping rejection lift). Multi-vertical buyers usually run both, with each doing a defined job.
- ActiveProspect closed its acquisition of Verisk Marketing Solutions in December 2025, putting both products under one corporate roof. No product consolidation has been announced. For 2026, plan for two distinct integration paths.
- The most expensive mistake we see in audits: buyers running both products and using neither as a pre-ping quality signal. Two consent line items, zero signal influencing bid logic.
Questions this article answers:
- Do I need both TrustedForm and Jornaya now that ActiveProspect owns both?
- Can a TrustedForm certificate be used as a pre-ping quality signal?
- What session signals does Jornaya LeadiD expose before the lead posts?
- Is Verisk LeadiD the same product as Jornaya LeadiD?
- What is a workable TrustedForm cert claim cadence for a high-volume stack?
- Should pay-per-call shops in final expense or Medicare use Jornaya at all?
Most TrustedForm vs Jornaya Comparisons Are Solving the Wrong Problem
Most trustedform vs jornaya content treats the two products as interchangeable TCPA vendors and ranks them on feature checklists. That framing misses the operator question entirely.
The real question is not which captures consent better. Both capture consent. The question is which signal your bid logic can actually USE before money changes hands, and which one only matters after a lead gets disputed.
Those are two different jobs. Jornaya’s LeadiD is a pre-ping quality signal you can score before you buy. TrustedForm’s certificate is a post-buy dispute artifact you reach for when someone challenges the lead. The mechanics force it. We’ll walk through why, and what that means for how you wire each one into Ringba, LeadConduit, or your own ping/post layer.
A quick note on the landscape: ActiveProspect closed its acquisition of Verisk Marketing Solutions (Jornaya’s parent) in December 2025. Both products now sit inside the same company. No product consolidation has been announced. For 2026 buying stacks, the integration paths are still distinct.
How TrustedForm Captures Consent, and What ‘Claiming’ Actually Does
TrustedForm is a consent-capture product from ActiveProspect that records the lead’s form interaction and issues a certificate URL pointing to that recording. The seller drops a JavaScript snippet on the landing page. The snippet captures the session. ActiveProspect mints the cert URL. The cert URL rides with the lead payload to the buyer.
Here is the part most operators get wrong, in either direction.
The cert is real from the moment it mints, and it lives on ActiveProspect’s servers. Per ActiveProspect’s Certificate API documentation, an unclaimed cert is accessible for up to 72 hours after creation. If you never claim, the cert expires and you lose access. Claiming is what associates the cert with your account, extends retention (commonly 90 days on standard plans, longer on extended retention), and gives you the durable, defensible record you can pull later if a lead gets disputed.
So the cert has some value before you claim, for about three days. After that, an unclaimed cert is gone for you. That is the economic trap: certs that age past the unclaimed window are paid-for evidence you no longer have access to.
What does claiming a TrustedForm certificate actually do?
Claiming is an API call that associates the cert with your account and triggers the retention window your contract specifies. Before the claim, you have a short window of access. After the claim, you have a durable record for the contracted retention period, and it is the artifact you can produce if a lead is challenged.
What happens if you don’t claim within the window?
You lose access to the cert. You paid the seller for a consent record that never became part of your defensible audit trail. In a high-volume stack, the math gets ugly fast:
This is why we treat TrustedForm as a dispute artifact, not a quality signal. By the time you have queried the cert for useful detail, the lead is already bought. The cert proves what happened. It cannot tell your bid logic whether to buy.
Per TCPAWorld, TrustedForm certifies over 1 billion opt-in leads annually. That scale is why claim cadence matters. Even a small unclaimed-cert percentage on a high-volume stack is real money.
How Jornaya LeadiD Captures Consent, and Why the Token Fires Before the Lead Posts
Jornaya LeadiD (which you’ll also see called Verisk LeadiD, and now operating under ActiveProspect since December 2025) works the opposite way. The LeadiD JavaScript token fires at form load, not form submit. Per Growform’s LeadiD documentation, a new LeadiD is generated per session, capturing the visitor’s interaction with the form from the moment the page loads.
That session data (time on page, field interaction sequence, pattern of edits, copy-paste flags, abandonment behavior) is attached to the LeadiD before the lead is ever submitted. By the time the lead posts to your ping/post waterfall, Jornaya already knows how it was filled out.
That is the entire operator story. You can query the LeadiD and get signal back about HOW the form was completed, which means your bid logic can decide whether to even ping for a buyer.
What session signals does Jornaya LeadiD expose before the lead posts?
The usable signals for filtering: time spent on the form, field-by-field interaction pattern, whether values were typed or pasted, abandonment-and-return behavior, and session-level red flags Jornaya surfaces in its scoring response. Operators use these to flag the classic thin-consent profile: short time on page, copy-pasted contact info, no field corrections. Those patterns line up with leadgen fraud signatures TrustedForm cannot see by design.
Is Verisk LeadiD the same product as Jornaya LeadiD?
Yes. Same product, different names floating around. Jornaya was acquired by Verisk years before ActiveProspect’s December 2025 acquisition of Verisk Marketing Solutions, so you’ll see Jornaya LeadiD, Verisk LeadiD, and now ActiveProspect-branded references all pointing at the same JavaScript token. No consolidation with TrustedForm has been announced.
The Timing Difference Is the Whole Decision
This is the thesis, said plainly: pre-ping signal versus post-buy artifact is the entire operator decision.
Jornaya gives you data before the buy. You can score it, filter on it, reject thin-consent leads before you pay. TrustedForm gives you a claimable record. You can defend with it, dispute with it, prove consent existed. Different jobs. Treating them as substitutes is the mistake.
Can a TrustedForm certificate be used as a pre-ping quality signal?
Not meaningfully. The cert URL arrives with the lead, but the rich detail behind it is only retrievable via the API. By the time you’ve called the API and parsed useful data back, you’ve added latency to a flow that needs to make a buy decision in milliseconds. Some buyers try to inline a pre-buy lookup in low-volume stacks. At scale, the latency and per-call cost make it a non-starter. The product is built for the post-buy job.
The expensive failure mode we see often: a buyer runs both TrustedForm and Jornaya because their sellers and downstream carriers each mandate one. They wire both products into LeadConduit. TrustedForm certs get claimed (sometimes). Jornaya LeadiDs are stored alongside the lead record. Neither is queried for pre-ping filtering. Both consent products are paid for. Neither is used as a quality signal. That is the most expensive mistake in a high-volume buying stack.
Wiring Each Into a Ringba or LeadConduit Buying Stack
The integration workloads are genuinely different. Plan for that.
Jornaya into a form-fill waterfall: The LeadiD attaches to the lead payload at form submit. Your ping/post layer (LeadConduit, a custom service, or LeadsPedia) reads the LeadiD, calls the Jornaya API for session signals, and applies rejection rules before pinging buyers. The rules belong to you. Short time-on-page plus copy-paste flag plus zero field corrections is one rejection profile we’d build first. Tune from there against your own conversion data.
TrustedForm into a form-fill waterfall: The cert URL rides with the lead payload. All certificates live on ActiveProspect’s servers from the moment they mint; per ActiveProspect’s Certificate API documentation, claiming is the API call that associates a cert with your account and extends its retention beyond the 72-hour unclaimed window. After your flow accepts the lead, a job (either in LeadConduit or your own scheduler) calls the claim API. The big operational decisions: when do you claim, and where do you store the resulting cert reference?
What is a workable TrustedForm cert claim cadence for a high-volume stack?
There is no single right answer, but the operator decisions look like this. Claim at lead receipt and you pay to retain certs for leads you may reject downstream. Claim only on sold leads and you risk the unclaimed window closing on leads stuck in pending review. A near-real-time claim on accepted leads, with a safety-net batch job that sweeps anything still pending before the 72-hour unclaimed window expires, is the shape most mature stacks settle into. Pick a cadence, document it, and audit the unclaimed rate monthly.
How do I read Jornaya signals inside a LeadConduit waterfall?
LeadConduit can call the Jornaya API as a step in the flow, before the buyer ping step. Configure the step to pull the session signals you care about, write them to lead fields, and put your rejection logic in a filter step that runs immediately after. The whole thing happens in the milliseconds before your buyers see the lead.
Should pay-per-call shops in final expense or Medicare use Jornaya at all?
Usually no. Jornaya is a form-load product. In a pure inbound call flow with no web form, there is nothing for the LeadiD JavaScript to fire on. TrustedForm has a call certification product that lives at the routing layer and attaches to the call record, which is what carriers and large agencies typically mandate in final expense and Medicare. If your supply has a click-to-call landing page in front of the call, Jornaya can still capture that form-load event, but the session signal is much thinner because the form never gets filled out.
When to Run TrustedForm Only, Jornaya Only, or Both
Here is the decision matrix by buyer profile.
| Buyer profile | Default answer | Why |
|---|---|---|
| Pay-per-call shop, low form-fill volume | TrustedForm only | Call certs, dispute defense, carrier mandates. Jornaya has nothing to attach to. |
| High-volume form-fill, shared-lead waterfall | Jornaya only | Pre-ping rejection lift pays for itself. TrustedForm adds cost without changing bid logic unless downstream mandates require it. |
| High-volume form-fill, exclusive leads to a single buyer | Whichever the buyer mandates | If they don’t mandate, default to Jornaya for the pre-ping signal. |
| Multi-vertical buyer (forms plus calls) | Both, with defined jobs | Jornaya as pre-ping filter on forms. TrustedForm as dispute artifact on everything. Measure both. |
| Seller or carrier mandates one specifically | The mandated one | Cost flows back through the rate. Negotiate accordingly. |
Do I need both TrustedForm and Jornaya now that ActiveProspect owns both?
In 2026, the answer is still driven by your buying stack, not the ownership structure. ActiveProspect has not announced product consolidation. Each product still requires its own integration path, its own retention/claim workflow, and its own line item. If your stack only buys form-fill leads on a single carrier mandate that accepts either cert, consolidate to one. If you sit across forms and calls and your downstream buyers are mixed, plan for both through 2026.
The consolidation question gets asked a lot post-acquisition. Our take: do not wait on a roadmap that has not been announced. Pick the right tool for your stack today. If ActiveProspect eventually merges the products, your contracts will roll into the new shape. Waiting is more expensive than picking.
Frequently Asked Questions
Do I need both TrustedForm and Jornaya now that ActiveProspect owns both?
Usually it still depends on your buying stack, not the ownership. ActiveProspect has not announced any merging of TrustedForm and Jornaya as of 2026, and the integration paths remain distinct: TrustedForm needs a claim API call, Jornaya needs a JavaScript token at form load. If your stack is single-vertical with one carrier mandate, consolidate to whichever they accept. If you cross forms and calls or your downstream buyers vary, plan to run both with each doing a defined job.
Can a TrustedForm certificate be used as a pre-ping quality signal?
Not in any practical high-volume way. The cert URL arrives with the lead, but pulling the rich detail behind it requires an API call that adds latency and per-call cost. By the time you have queried it, you have already paid for the lead, so the signal lands too late to influence bid logic. Treat TrustedForm as post-buy dispute defense, not pre-buy filtering.
What session signals does Jornaya LeadiD expose before the lead posts?
Time on page, field interaction sequence, copy-paste behavior, abandonment patterns, and session-level red flags surfaced by Jornaya’s scoring. Because the LeadiD JavaScript fires at form load, all of this is attached to the LeadiD by the time the lead is submitted. Your ping/post layer can query the Jornaya API for these signals before buyers see the lead, which is the basis for pre-ping rejection rules in LeadConduit or a custom flow.
Is Verisk LeadiD the same product as Jornaya LeadiD?
Yes, same product, different names you will see in the wild. Jornaya was rebranded as Verisk LeadiD after the Verisk Marketing Solutions deal years ago. As of December 2025, the product sits under ActiveProspect following the acquisition. The JavaScript implementation, the LeadiD token, and the API behavior described in Growform’s docs all refer to the same product.
What is a workable TrustedForm cert claim cadence for a high-volume stack?
Per ActiveProspect’s API docs, unclaimed certs are accessible for up to 72 hours; claiming extends retention and locks the cert as your durable record. Claiming at lead receipt costs you certs on rejected leads. Claiming only on sold leads risks letting the 72-hour window close on leads stuck in pending review. The shape most mature stacks settle into is a near-real-time claim on accepted leads plus a safety-net batch sweep before the 72-hour expiry. Pick a documented cadence and audit your unclaimed rate monthly so the line item does not silently grow.
Should pay-per-call shops in final expense or Medicare use Jornaya at all?
Usually no, because Jornaya is a form-load product and a pure inbound call flow has no form. TrustedForm’s call certificate product attaches to the call record at the routing layer and is what carriers typically mandate in those verticals. If your supply uses a click-to-call landing page upstream of the call, Jornaya can fire on that page, but the session signal is thin since the form is never filled out. Spend that budget on TrustedForm and on better call routing instead.
We’re media buyers and lead-gen operators sharing what we see in the field. This isn’t legal advice. TCPA consent capture and lead-buyer compliance is genuinely complicated and varies by state and vertical, so talk to an actual attorney before changing your consent flows or vendor contracts.
If your TrustedForm and Jornaya line items are showing up on your P&L but neither one is changing a pre-ping or post-buy decision, that is the conversation to have. Talk to our pay-per-call and lead-buying team about your specific vertical and volume, and ask about exclusive lead routing and consent-signal filtering for insurance, mortgage, home services, or your own buying stack. For deeper reading on how this wires into the rest of your stack, see our pieces on TrustedForm and Jornaya integration as quality signals, the 2026 TCPA lead buyer compliance checklist, and the enhanced conversions match-rate test for call tracking platforms.
