Getting Started with Claiming

A TrustedForm Certificate (aka Cert) is all the information necessary to document a consumer's interaction with a mobile app, web page, or Facebook page. In it, we store metadata about the consumer's visit, an event log of their interactions with a webpage or mobile app, screenshots (mobile only) of the interactions, and a playback (web only). It's this Cert which documents that prior, express written consent was obtained before you contact a lead.

Claiming the certificate...

  1. Verifies the legitimacy of the Certificate
  2. Stores the Certificate for future reference and
  3. Provides programmatic access to the information shown on the Certificate

TrustedForm certificates are tamper-proof. In the event of a TCPA complaint, you can easily view the certificate and video replay, and share the certificate with your legal team.

How Do I Claim a Certificate?

Now that you know what a Certificate is and why it's important to claim them prior to contacting a lead, you're probably wondering how to do that.

Claiming Through LeadConduit

If you have a LeadConduit account, you can claim TrustedForm Certificates automatically by adding the TrustedForm enhancement step to your flow. When you use LeadConduit to claim Certificates, it enables you to limit what you claim based on the criteria you define (e.g. geography, fraud checks, and more). You can find out more about claiming through LeadConduit in the article, Claiming TrustedForm Certificates in LeadConduit

Claiming Through the API

Claiming Certificates with the API is as simple as sending an authorized POST HTTP request to https://cert.trustedform.com along with the Cert ID as part of the path. That's really all there is to it.

Example:

Copy
Copied
curl -X "POST" "https://cert.trustedform.com/3620bba4adb82a5cd65146de6ce6a93f38111e18" \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json' \
     -u 'API:19836a19a4e2f6349d9b8763a930f654'

You can find your API key on the Settings tab in your account.

Lead Fingerprinting

Fingerprinting allows you to determine "that information collected on the web form matches the lead data received with the TrustedForm certificate." To test if an email or phone number is associated with a Certificate during claiming, you will send the values you want to check with keys such as phone, phone_1, email2, etc. The naming doesn't matter. The response will then return with SHA1 versions of those values in either a matching or not_matching array in the claim response.

Example:

Copy
Copied
curl -X "POST" "https://cert.trustedform.com/3620bba4adb82a5cd65146de6ce6a93f38111e18" \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json' \
     -u 'API:19836a19a4e2f6349d9b8763a930f654' \
     -d $'{
  "phone_1": "123.123.1231",
  "email1": "user@example.com",
  "email_2": "another_user@example.com"
}`

Page Scanning

Page scanning gives you the ability to determine if certain language appears in the text of a web page or not. It can also be used to show language that shouldn't appear on the page, but does.

Here's an example:

Copy
Copied
curl -X "POST" "https://cert.trustedform.com/3620bba4adb82a5cd65146de6ce6a93f38111e18" \
     -H 'Accept: application/json' \
     -H 'Content-Type: application/json' \
     -u 'API:19836a19a4e2f6349d9b8763a930f654' \
     -d $'{
  "scan": [
    "Submit the {{*}} a claim",
    "TrustedForm"
  ],
  "scan!": [
    "Win a free iPhone",
  ]
}'

In this example, we use scan for language we want to ensure shows up, but use scan! to ensure other language doesn't.

Conclusion

In the end, claiming is about ensuring your company has documented consent to contact consumers, and TrustedForm makes it easy to do that through its API, or by using it in conjunction with with LeadConduit.

You can find detailed information about fingerprinting, page scanning, and more in the Claiming API docs.