TrustedForm Certificate
TrustedForm witnesses lead-form sessions and issues claimable certificates. Powerful for bought leads; first-party programs need the same evidence without the certificate workflow.
TrustedForm operates by embedding a script on lead-generation forms. Each submission generates a certificate — a URL referencing a session replay, page snapshot, timestamps, and metadata — which the lead seller passes to buyers.
The operational catch is claiming: certificates must be claimed (retained) by the buyer within a limited window (commonly 90 days on standard terms) or the underlying evidence becomes unavailable. Claimed certificates can then be stored for the multi-year retention TCPA defense requires.
Limits worth understanding: a certificate documents what one form did during one session. It does not certify that the consent language was legally sufficient, that the consumer was the number's actual subscriber, or that downstream texting stayed within the consent's scope. For first-party consent capture (your own forms, your own subscribers), per-record session evidence with hash-locked storage — the OptInFix model — covers the same evidentiary ground without per-lead certificate economics.
Frequently asked questions
Related glossary terms
Lead certification is third-party documentation attached to a purchased lead proving when, where, and how the consumer's consent was captured — the mechanism lead buyers use to defend TCPA claims on bought data.
Jornaya LeadiD (now part of Verisk) assigns a unique token to each lead-form interaction. Buyers use the token to verify the lead's origin, age, and consent context — an audit-trail alternative to TrustedForm's certificate model.
Session replay records the exact UI interactions during an opt-in (mouse, scroll, clicks, form fields) so the consent moment can be re-watched as evidence in a TCPA dispute.