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 mititage 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 RTB Version of the Jornaya Integration.
Note: Please contact your Account Manager or our support team to activate Jornaya RTB Integration for your Ringba account.
Jornaya Credentials - Account Level
In the sidebar menu Settings > Account Settings > Manage Account Settings, you will find the Jornya Settings:
- 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.
Tip: Once you set the above fields and save it, go to the desired campaign to enable the feature.
Jornaya Credentials - Campaign Level
- Go to the campaign you want to integrate with Jornaya and navigate to the Real Time Bidding tab.
- Choose Disabled, Enabled, or Required.
- If you choose Enabled, Ringba uses the JleadId and EntityCode to ping Jornaya to verify its authenticity.
- If you choose Required, Ringba does not return a bid unless a JleadId was provided and authenticated.
- Credentials for Jornaya can be overridden per campaign or at the account level ( LAC, LAK and Agency Code).
-
The next step is to share your RTB URL with your publisher and ask them to send you the required parameters and their values.
Example with a GET request: https://rtb.ringba.com/v1/production/12345.json?CID=14061571951&EntityCode=value&JleadId=value
Note: In the RTB documentation, these tags will be automatically populated when Jornaya is enabled or required