Feature Snapshot
Summary:
Lead Matching When Viewing A Certificate is the process of verifying that the email/phone in a TrustedForm certificate matches the email/phone provided for a lead.
Key Benefits:
- Confirms that the certificate corresponds exactly to the lead’s originally submitted data.
- Enhances fraud prevention by ensuring certificates and leads truly belong together.
- Protects consumer privacy by keeping sensitive form data masked until a valid match is made.
Typical Use Cases:
- Revealing form field values input by a consumer if they are currently hidden for security purposes.
How Lead Matching When Viewing A Certificate Works
When you open a TrustedForm certificate in your browser, the sensitive form input fields (for example, email and phone number) are initially hidden (displayed as a series of asterisks) if lead matching has not been performed. To verify the certificate against the lead data, you manually enter the contact details that the lead submitted. TrustedForm then applies its lead matching process by hashing these inputs and comparing them against the stored hashes from the consumer’s session. If there is a match, the certificate reveals the actual values, thereby confirming that the certificate is valid and that the lead data authentically corresponds with the certificate. This process provides both an immediate visual confirmation and technical validation that the certificate and lead belong together.
What is Lead Matching When Viewing A Certificate?
It is the process of validating the consumer’s contact details against the hashed values captured during the web session, ensuring that the sensitive inputs stored in the certificate indeed belong to the lead.
Why is Lead Matching Important?
It prevents lead fraud and builds trust by ensuring that the certificate data is accurate and the lead has genuinely provided those contact details. This safeguards businesses from compliance issues and protects consumer privacy until proper consent is verified.
How Do I Use It?
View a certificate where the form inputs are hidden, and then enter the exact email address and/or phone number submitted by the lead. Once submitted, if the input details correctly hash and match the stored fingerprints, the hidden data will be revealed.
How Fast is the Lead Matching API Operation?
The operation typically processes in near‑real‑time—approximately one second—allowing quick verification during certificate review.
Step‑by‑Step Instructions
-
Access the Certificate:
Open the TrustedForm certificate URL in your browser. Navigate to the session replay or certificate details area where the form inputs are hidden. -
Enter Contact Details:
Type the lead’s email address and/or phone number exactly as originally submitted into the provided input fields. -
Review the Outcome:
Once a match has been made, the certificate will prompt you to refresh the page to reveal the form input values, confirming that the certificate data is authentic.
Expected Result:
The certificate display form field values to display the true email address and/or phone number, verifying that it correctly corresponds to the lead’s submitted details.
Troubleshooting
| Symptom / Error | Likely Cause | Resolution |
|---|---|---|
| Sensitive form inputs remain masked after submission | The entered email/phone does not exactly match the certificate data; potential formatting issues or typos. | Re‑verify the submitted details ensuring no extraneous spaces or incorrect punctuation exist. |
Frequently Asked Questions (FAQ)
Q: Do I have to perform lead matching for every certificate I view?
A: Not necessarily. For leads generated on verified domains or through automated processes, lead matching may occur automatically. Manual matching is most useful for certifcates that were manually retained or failed automated lead matching.
Q: What happens if the email or phone number I submit does not match the certificate data?
A: If no match is detected, the certificate’s form field values will remain hidden. In such cases, review the entered details for accuracy and consult your lead vendor if discrepancies persist.
Q: Can I share a certificate that has not been lead matched?
A: When sharing via the “Share URL”, the certificate’s hidden state remains intact until a successful lead matching operation is performed. The form field values will only be visible when proper contact details are provided.
Glossary
| Term | Definition |
|---|---|
| Lead Matching | The process of comparing a lead’s submitted contact details (e.g., email and/or phone) against hashed fingerprints stored in the certificate to confirm authenticity. |
| Certificate | A TrustedForm record capturing consumer events on a web form, including hidden and masked sensitive data, generated during the consumer’s visit. |
| Fingerprints | Securely hashed representations of the consumer’s contact details captured during the web session; used for matching with the provided values. |
| Masked Certificate | A certificate where sensitive form input values (like email and phone) are hidden (typically with asterisks) until lead matching is successfully performed. |
| Session Replay | A visual recreation of the consumer’s interaction with a web form, reconstructed from the data (HTML, keystrokes, mouse movements) captured by TrustedForm. |
Comments
0 comments
Please sign in to leave a comment.