Lead Fingerprinting

While a consumer is filling out a form hosting our JavaScript, TrustedForm collects a set of fingerprints that uniquely and anonymously identify the consumer using his or her email address and or phone number. The fingerprints are stored on the Certificate issued during that consumer's page visit.

When the advertiser receives the certified lead, a new set of fingerprints can be easily generated from the email addresses and phone numbers. Then those fingerprints can be verified against those collected on the certificate. If the fingerprints do not match, then the advertiser will be warned so appropriate action can be taken.

What does it mean when fingerprints match?

When fingerprints match it means that the information collected on the form matches the lead data received with the certificate — the lead and the certificate belong together. This prevents a certificate from being sent with a lead other than the one generated at the time the certificate was issued.

Why don't fingerprints match?

  • The fingerprints generated on the form do not match the fingerprints provided during the claim API call.
  • No fingerprints were generated on the form. This can happen if there were no pre-populated form fields or if the consumer didn't interact with the form.
  • The fingerprints provided by the advertiser during the claim API call weren't properly generated. See the API documentation.
Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request


You must be logged in to comment.