Why consent capture matters
Under TCPA, a buyer needs to prove the consumer agreed to be contacted. TrustedForm (a certificate of the form session) and Jornaya LeadiD (a token recording the lead event) are the two standard proofs buyers expect attached to a lead.
How I capture and pass consent
- Embed the TrustedForm and Jornaya scripts on the form correctly, so the cert/token actually generate
- Capture the certificate URL and LeadiD token at submission
- Attach both to the lead payload posted to every buyer (Boberdoo, direct, etc.)
- Retain the record for audit and dispute resolution
On the platform I built, the consent layer meant loading the TrustedForm and Jornaya scripts correctly inside a dynamic, multi-step form, capturing the certificate and LeadiD at submission, and preserving that consent (alongside TCPA, DNC, and Do-Not-Sell flags) on the lead as it routes to each buyer.
Concretely: the TrustedForm bootstrap script and the Jornaya LeadiD script load on the page, so each form session generates a certificate and a token. At submission I read the TrustedForm certificate URL and the Jornaya LeadiD off the form and store them on the lead record itself, so every lead keeps its own consent proof and a disputed lead can be pulled up with it later. Both then travel in the payload to each buyer, mapped to whatever field names that buyer expects, for example trustedFormCertURL and universalLeadID, so the buyer can independently verify and retain the certificate on receipt.
1:1 consent
For verticals like Medicare, consent now has to be specific to each buyer (1:1), not a blanket partner list. That changes how consent is captured and which buyer can receive a given lead.
FAQ
- Do you capture both TrustedForm and Jornaya?
- Yes. Both, attached to the lead payload for each buyer.
- Can you prove consent on a disputed lead?
- That's the point, the certificate and token are retained so a disputed lead can be verified.