Pre-Audit API
- 21 Oct 2024
- 9 Minutes to read
- Print
- DarkLight
Pre-Audit API
- Updated on 21 Oct 2024
- 9 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Introduction
Pre-Audit allows publishers to query an advertiser’s default audit profile and obtain yellow or red flags for both Jornaya Intelligence and TCPA Guardian data points. These flags give publishers an indication of whether a lead would be reviewed or rejected by the advertiser, based on the client’s profile settings for Jornaya Intelligence and TCPA Guardian, before sending the lead to the advertiser.
Looking for More?
For instructions on how to set up Jornaya Pre-Audit, be sure to check out the Pre-Audit Getting Started Guide.
Example Request Structure (GET method)
https://api.leadid.com/SinglePreAudit?lac={ACCOUNTCODE}&id={LEADIDTOKEN}&lec={ENTITYCODE}&data={DATA}
Parameter Definitions
| Name | Value | Required | Description |
| URL | https://api.leadid.com/SinglePreAudit | Yes | The URL to be used for the query. |
| Method | GET or POST | Yes | The HTTPS method to be used. |
| lac | xxxxxxxx-xxxx-xxxx-xxxx | Yes | Your Jornaya Account Code. |
| id | 36 Character LeadiD token | Yes | The LeadiD token. |
| lec | xxxxxxxx-xxxx-xxxx-xxxx | Yes | The Entity Code of the party to whom you plan to sell the lead. |
| lpc | Alphanumeric string | No | A value that identifies the Provider from whom you received this lead. |
| data | Pipe | Separated Data with field data labels delimited by semicolons. e.g., email;joe@smith.com|f_name;joe | No | The data for which you want to determine Data Integrity. Note: a list of Data Integrity Field Data Labels can be found at the end of this document. |
| format | json, xml | No | The format in which you would like the data returned. The default value is JSON. |
Security for Usage
The usage of HTTPS/TLS is highly recommended when implementing the Jornaya TCPA Guardian (3rd Party) API. This ensures data transmitted between your networks and Jornaya’s systems are securely encrypted and protected. Jornaya supports the usage and configuration of TLS 1.2, and the following TLS cipher suites:
| ECDHE-ECDSA-AES128-GCM-SHA256 | ECDHE-RSA-AES256-SHA384 |
| ECDHE-RSA-AES128-GCM-SHA256 | ECDHE-RSA-AES256-SHA |
| ECDHE-ECDSA-AES128-SHA256 | ECDHE-ECDSA-AES256-SHA |
| ECDHE-RSA-AES128-SHA256 | AES128-GCM-SHA256 |
| ECDHE-ECDSA-AES128-SHA | AES128-SHA256 |
| ECDHE-RSA-AES128-SHA | AES128-SHA |
| ECDHE-ECDSA-AES256-GCM-SHA384 | AES256-GCM-SHA384 |
| ECDHE-RSA-AES256-GCM-SHA384 | AES256-SHA256 |
| ECDHE-ECDSA-AES256-SHA384 |
Revisions
At any future time, Jornaya may revise the list of supported TLS protocols and cipher suites as required by industry security best practices. You will be notified in advance of such changes to ensure continued successful operations of your integrations with Jornaya’s services.
Example Response Structure
| JSON | XML |
|---|---|
| { | <preaudit> |
| "preaudit": { | <header> |
| "header": { | <flags> |
| "flags": { | <f1>Good Lead</f1> |
| "f1": "Good Lead", | <f2>Review Lead</f2> |
| "f2: "Review Lead", | <f3>Reject</f3> |
| "f3: "Reject" | </flags> |
| } | </header> |
| }, | <body> |
| "body": { | <reasons> |
| "reasons": { | <2.1>3</2.1> |
| "r2.1": 3 | </reasons> |
| } | <result>3</result> |
| "result": 3 | </body> |
| } | </preaudit> |
| } | |
| } |
Data Responses
The following sections list the responses (and associated values) received when employing Jornaya Intelligence during a lead audit.
Pre-Audit > Header > Flags | ||
|---|---|---|
| Data Point | Value | Description |
| f1 | Green | The text labels for green-flagged results. This parameter will only be displayed if the entity is valid and if you have permission to pre-audit this entity's leads. |
| f2 | Yellow | The text labels for yellow-flagged results. This parameter will only be displayed if the entity is valid and if you have permission to pre-audit this entity's leads. |
| f3 | Red | The text labels for red-flagged results. This parameter will only be displayed if the entity is valid and if you have permission to pre-audit this entity's leads. |
Pre-Audit > Body > Result | ||
|---|---|---|
| Data Point | Value | Description |
| Green | 1 | The returned result of the Pre-Audit is green. |
| Yellow | 2 | The returned result of the Pre-Audit is yellow. |
| Red | 3 | The returned result of the Pre-Audit is red. |
NOTEThe overall result does not include the brand names and topical relevance flag results.
NOTE
The overall result does not include the brand names and topical relevance flag results.
Authentic | ||
|---|---|---|
| Data Point | Value | Description |
| LeadiD Authenticity | r1 | Yellow or Red flag: One or more of the conditions have been met below and no additional data will be returned for this LeadiD token: One or more of the conditions have been met below and no additional data will be returned for this LeadiD token:
|
Lead Age | ||
|---|---|---|
| Data Point | Value | Description |
| Lead Age | r2 | Yellow or Red flag: lead was created too long ago. |
Lead Duration | ||
|---|---|---|
| Data Point | Value | Description |
| Lead Duration | r2.1 | Yellow or Red flag: lead duration was too short or too long. |
Data Integrity | ||
|---|---|---|
| Data Point | Value | Description |
| Data Integrity | r3 | Yellow or Red flag: data required for the integrity check was incorrect or missing. |
| Data Integrity Blocked | r3.1 | Yellow or Red flag: buyer has flagged this lead because the generator blocked data integrity. |
Lead Origin | ||
|---|---|---|
| Data Point | Value | Description |
| URL Flag | r4.12 | Yellow or Red flag: buyer has flagged this lead that originated from this URL. |
| URL Flag Blocked | r4.17 | Yellow or Red flag: buyer has flagged this lead because the generator blocked the URL flags. |
| Entity Flag | r4.13 | Yellow or Red flag: buyer has flagged this lead that was generated by this company. |
| Entity Flag Blocked | r4.18 | Yellow or Red flag: buyer has flagged this lead because the generator blocked the entity flags. |
Consumer Origin | ||
|---|---|---|
| Data Point | Value | Description |
| Consumer Origin | r4 | Yellow or Red flag: device is unknown. |
| Device Velocity 5 Minutes | r4.1 | Yellow or Red flag: too many leads generated from this device in the past 5 minutes. |
| Device Velocity Past Hour | r4.2 | Yellow or Red flag: too many leads generated from this device in the past hour. |
| Device Velocity Past 12 Hours | r4.3 | Yellow or Red flag: too many leads generated from this device in the past 12 hours. |
| Device Velocity Past Day | r4.4 | Yellow or Red flag: too many leads generated from this device in the past day. |
| Device Velocity Past Week | r4.5 | Yellow or Red flag: too many leads generated from this device in the past week. |
| Device Velocity Blocked | r4.15 | Yellow or Red flag: buyer has flagged this lead because the generator blocked the device instances. |
| IP Velocity 5 Minutes | r4.6 | Yellow or Red flag: too many leads generated from this IP address in the past 5 minutes. |
| IP Velocity Past Hour | r4.7 | Yellow or Red flag: too many leads generated from this IP address in the past hour. |
| IP Velocity Past 12 Hours | r4.8 | Yellow or Red flag: too many leads generated from this IP address in the past 12 hours. |
| IP Velocity Past Day | r4.9 | Yellow or Red flag: too many leads generated from this IP address in the past day. |
| IP Velocity Past Week | r4.10 | Yellow or Red flag: too many leads generated from this IP address in the past week. |
| IP Velocity Blocked | r4.16 | Yellow or Red flag: buyer has flagged this lead because the generator blocked the IP instances. |
| Call Center Originated | r4.11 | Yellow or Red flag: buyer has flagged this lead because the generator indicated it was created at a call center. |
Lead Velocity | ||
|---|---|---|
| Data Point | Value | Description |
| Lead Velocity Past 5 Minutes | r5.1 | Yellow or Red flag: queries too many times in the past 5 minutes. |
| Lead Velocity Past Hour | r5.2 | Yellow or Red flag: queries too many times in the past hour. |
| Lead Velocity Past 12 Hours | r5.3 | Yellow or Red flag: queries too many times in the past 12 hours. |
| Lead Velocity Past Day | r5.4 | Yellow or Red flag: queries too many times in the past day. |
| Lead Velocity Past Week | r5.5 | Yellow or Red flag: queries too many times in the past week. |
| Lead Velocity Blocked | r5.6 | Yellow or Red flag: buyer has flagged this lead because the generator blocked lead velocity. |
Consumer Velocity | ||
|---|---|---|
| Data Point | Value | Description |
| Consumer Velocity Past 5 Minutes | r6.1 | Yellow or Red flag: consumer's email address witnessed too many times in the past 5 minutes. |
| Consumer Velocity Past Hour | r6.2 | Yellow or Red flag: consumer's email address witnessed too many times in the past hour. |
| Consumer Velocity Past 12 Hours | r6.3 | Yellow or Red flag: consumer's email address witnessed too many times in the past 12 hours. |
| Consumer Velocity Past Day | r6.4 | Yellow or Red flag: consumer's email address witnessed too many times in the past day. |
| Consumer Velocity Past Week | r6.5 | Yellow or Red flag: consumer's email address witnessed too many times in the past week. |
| Consumer Velocity Blocked | r6.6 | Yellow or Red flag: buyer has flagged this lead because the generator blocked consumer velocity. |
Lead Lineage | ||
|---|---|---|
| Data Point | Value | Description |
| Total Entities | r7.1 | Yellow or Red flag: lead has been seen by too many entities. |
| Total Entities Blocked | r7.2 | Yellow or Red flag: buyer has flagged this lead the generator blocked total entities. |
| Total Hops | r7.3 | Yellow or Red flag: lead took too many hops between the generator and you. |
| Total Hops Blocked | r7.4 | Yellow or Red flag: buyer hs flagged this lead because the generator blocked total hops. |
Lead Duplication | ||
|---|---|---|
| Data Point | Value | Description |
| LeadiD Dupe Check | r8.1 | Yellow or Red flag: buyer has already queried this LeadiD. |
| Consumer Dupe Check | r8.2 | Yellow or Red flag: buyer has already queried a LeadiD with this consumer's email address. |
| LeadiD Dupe Check Blocked | r8.3 | Yellow or Red flag: buyer has flagged this lead because the generator blocked lead duplication checking. |
| Consumer Dupe Check Blocked | r8.4 | Yellow or Red flag: buyer has flagged this lead because the generator blocked consumer duplication checking. |
TCPA Guardian
Note:
The responses in this section will only appear if the buyer has Jornaya's TCPA Guardian (3rd Party) installed and turned on for their default Audit Profile
TCPA Guardian | ||
|---|---|---|
| Data Point | Value | Description |
| Specified TCPA Disclosure | r9.1 | Yellow or Red flag: TCPA disclosure language approved by the buyer was not present on the lead form. |
| Consumer's Consent | r9.2 | Yellow or Red flag: the consent option was not approved by the buyer. |
| TCPA Consent Type | r9.3 | Yellow or Red flag: the consent type was not approved by the buyer. |
| Prominence | r9.4 | Yellow or Red flag: the TCPA disclosure language was in a font size not approved by the buyer. |
| Contrast | r9.5 | Yellow or Red flag: the contrast between the TCPA disclosure language and the form background color was not approved by the buyer. |
| Visibility | r9.6 | Yellow or Red flag: the visibility (calculated using Prominence & Contrast) was not approved by the buyer. |
| Visual Playback Capture Verification | r9.7 | Yellow or Red flag: the Visual Playback capture response was not approved by the buyer. |
| Visual Playback Storage Verification | r9.8 | Yellow or Red flag: the Visual Playback storage response was not approved by the buyer. |
| Overall TCPA Guardian Response | r9.9 | Yellow or Red flag: the Overall TCPA Guardian response was not approved by the buyer. NOTE: The overall response does not include the brand name and topical relevance flag results. |
Field Data Labels
| Label | Description |
| f_name | First Name |
| l_name | Last Name |
| phone1 | Phone1 |
| address1 | Address1 |
| city | City |
| state | State |
| zip | Zip |
Was this article helpful?
