Skip to main content

Trusted Form - RTB Integration

Amanda Cross
Updated

TrustedForm is a platform that issues independent certificates of authenticity for the leads you generate. TrustedForm lets you provide proof of consent for each lead you generate—for your own use or to sell—documenting exactly when and where proof of consent was obtained. With Ringba, you can ping TrustedForm's API to get information about the call from the certificate in real-time.

There are two versions of the TrustedForm Integration: Call Flows for static calls that don't bid dynamically, and another version for RTB Calls that do. This article will show you how to implement the RTB Version of the TrustedForm integration.

Note: Please contact your Account Manager or our support team to activate TrustedForm RTB Integration for your Ringba account.

Note that TrustedForm requires a phone number to retrieve a certificate. To accommodate this requirement, your publisher must:

  • include the exposeCallderID tag equal to yes, and
  • populate the Caller ID

For more information on how to expose the caller ID, see How do I allow the RTB client to see the caller ID?

Trusted Form Credentials - Account Level

In the sidebar menu Settings > Account Settings > Manage Account Settings, you find the Trusted Form Settings.

  • API Key: Add the API key provided by TrustedForm.
  • Certificate ID: The tag name that you will receive from publisher that contains the Certificate ID. In the following example is a URL parameter that we created for this ID, so this field would have as a value tag:User:trusted_form_cert. You can name it whatever you like, but you must first create a URL parameter and communicate the tag name to your publisher so they can send it to you.

     

Note: Once you set the above fields and save, go to the desired campaign to enable the feature.

TrustedForm Credentials - Campaign Level

  1. Open the RTB-enabled campaign you want to integrate with TrustedForm and click the Real Time Bidding tab.
  2. Choose a value for the Trusted Form Cert ID:
    • Disabled: The campaign does not claim TrustedForm certificates.
    • Enabled: Ringba claims the Cert ID with TrustedForm to verify its authenticity.
    • Required: Ringba will not return a bid unless a Cert ID was provided and authenticated.
    When you select Enabled or Required, additional fields appear to configure how the integration works.
  3. Choose a value for the Trusted Form Integration Method:
    • Claim: claim a certificate to verify its legitimacy, view it online, access its data via our API, and refer to the snapshot that was taken of the page as seen by the consumer.
    • Verify: meant to be used by lead buyers purchasing leads using the "ping/post" model. This API gives buyers access to that data with the intention that it will be called when the buyer is evaluating a ping request from a seller. This is also known as "Ping API".
  4. Choose a value for the Trusted Form Settings:
    • Account Settings: the integration uses the credentials configured at the account level. See the procedure in the previous section of this article.
    • Override: choose this value to override the credentials. Fields appear where you enter the API token and Cert ID Tag Name for this campaign.

  5. Share your RTB URL with your publisher and ask them to send you the required parameter and its value.

     

Example with a GET request:

https://rtb.ringba.com/v1/production/12345.json?CID=14061571951&trusted_form_cert=value&exposeCallerId=yes

Note: As explained in this article, the name of the Certificate ID parameter depends on how you configure the tag name. In this article we used trusted_form_cert for all examples but you can choose whatever parameter name works for you business.

Related articles