The Jornaya node lets you ping Jornaya's TCPA Guardian service to pull information about whether a lead provided TCPA consent. This tool helps you avoid non-compliant calls and reduce the risk of TCPA litigation by having proof of consent.
You use the Jornaya node in your call flows. See Call Flows with Ringba for instructions on setting up nodes in your call flow and adding your call flow to a campaigns.
Important: This article describes configuring the Jornaya node for static calls that don't involve dynamic bids. If you are using real-time bidding, see the Jornaya Integration - RTB version article for step-by-step instructions.
After you add the Jornaya node to your call flow, click it to open the drawer with the configuration tools. The following controls appear:
- Node Name: Enter a meaningful name for the Jornaya node. This name helps you identify the node when you review the Call Details report later.
-
Credentials: Toggle on this switch to override the Jornaya account credentials you set up in your Account Settings. If you toggle on this switch, the following fields appear:
- Account Code (LAC): Enter your Jornaya account code.
- Audit Key (LAK): Enter the audit key you want Ringba to use for this Jornaya query.
- Agency Code: If you are an AOR or LMS, use this parameter to pass your own account code while performing queries on behalf of a client.
- Entity Code: Enter the tag name your publisher uses to pass the Jornaya Entity Code value. You must enter a tag macro in this field, for example [tag:User:EntityCode].
-
Lead ID: Enter the tag name your publisher uses to pass the Jornaya Lead ID value. You must enter a tag macro in this field, for example [tag:User:JleadId].
Important: Make sure that you create a URL parameter for each of the Entity Code and Lead ID tags. See URL Parameters for step-by-step instructions. - Time out (sec): Enter the number of milliseconds the request can take before it times out.
- Test Mode: Toggle on this switch to enable Test Mode for requests.