Ringba makes it easy to integrate with Jornaya's TCPA Guardian to pull information about which leads provided TCPA consent to help you avoid non-compliant calls and mitigate the risk of TCPA litigation by having proof of consent in the event of a complaint.
There are two versions of the Jornaya 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 Call Flows Version of the Jornaya Integration.
Note: Please contact your Account Manager or our support team to activate Jornaya Call Flows Integration for your Ringba account.
Jornaya Call Flows Node
Use the following steps to integration Jornaya with your Call Flow:
- Navigate to the Call Flow you want to integrate Jornaya with and select the Jornaya node.
After enabled, a new node named Jornaya appears in your Call Flows list. - Toggle on the Credentials switch so you can input all the required information. The fields that you need to fill out are the ones described below:
- Account Code (LAC): Your Jornaya Account Code.
- Audit Key (LAK): The Audit Key for this query.
- Agency Code: This parameter allows a company that is an AOR or LMS for a client to perform queries on behalf of that client and identify itself accordingly by passing in its own Account Code.
- Entity Code: The tag name that your publisher will pass the Entity Code value. Ringba supports only tag macros in this field. An example is [tag:User:EntityCode].
-
Lead ID: The tag name that your publisher will pass the Jornaya Lead ID value. Ringba supports only tag macros in this field. An example is [tag:User:JleadId].
Tip: Make sure that you set it both Entity Code and Lead ID tags as a URL parameter. If you want to know more about it see URL Parameters - Time out (sec): The number of milliseconds the request can take before it times out.
- Test Mode: Enables Test Mode for requests.
- Save it as a draft, or publish it.
An example of a Call Flow using Jornaya's response for routing decisions.
