TrustedForm is a platform that issues independent certificates of authenticity for the leads you generate. TrustedForm Certify allows you to 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 shows you how to implement the Call Flows version of the TrustedForm Integration.
Note: Please contact your Account Manager or our support team to activate TrustedForm Call Flows Integration for your Ringba account.
TrustedForm Call Flows Node
Navigate to the Call Flow you want to integrate with TrustedForm and select the Trusted Form node.
- Node Name: Enter the name of the node. This name identifies the node in the call reporting.
- API Key: Add the API key provided by TrustedForm.
-
Certificate ID: Enter the name of the tag your publisher provides to contain the Certificate ID. In the example above, we created a URL parameter for this ID, so this field has a value of tag:User:trusted_form_cert. If you create a URL parameter, you can choose the name you want to use and communicate that name to your publisher.
- Timeout (sec): The amount of time Ringba waits for a response from TrustedForm API before failing.
- Integration Method: The method TrustedFrom uses to authenticate the call. Important: As of December 12, 2023, Claim is the only available Integration Method, so it is selected by default. This method provides 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.
- Vendor: Optional vendor parameter to be stored along with the claiming certificate record. We only support tag macros for this field. Example: "tag:User:VendorWebsite".
- Reference: Optional parameter of your choice to link a claimed certificate with an ID of yours. We only support tag macros for this field. Example: "tag:User:VendorName".