TCPA Guardian - FAQ

A ‘No Label’ response means that TCPA Guardian did not witness a TCPA disclosure at the lead event. 

There are two reasons for this:

1. A TCPA disclosure statement was NOT present on the web page
2. A disclosure was present but was not labeled properly using the TCPA Disclosure labels.

In some instances, it may not be obvious why certain disclosure language is mismatching. For example, a publisher may have shared all the TCPA languages they believe are being displayed, and the customer may have added these languages to their audit profile; however, the customer is still receiving TCPA mismatches on leads from this particular publisher. 

Customers should ensure that their vendors are sharing all languages on their own pages and languages on the pages of their sub-affiliates. 

Sellers should ensure that they are sharing all languages present on their pages and all languages on the pages of their sub-affiliates with the advertiser/brand who is purchasing their leads.

A ‘Not Visible’ response occurs when the TCPA disclosure language on the form was present within the coding of the webpage, however, it was not visible to the user. 

Such examples include:

• The code within the TCPA labels or the label itself contains "display: none"
• The disclosure text appears in a 0x0 container.

This is an update that the creator of the webpage would need to adjust.

If a lead is rejected due to the TCPA Guardian response ‘disclosure’ or ‘disclosure_rule,’ it means that the TCPA disclosure statement that was captured at the lead event is being flagged by the auditing party for their TCPA Disclosure rule as set in their Audit profile. 

Auditors can designate disclosure rules based on three responses: 

• Match - The captured language matched one of the customer's approved languages in their audit profile.
• Mismatch - The language captured at the lead event did not match the language listed in the customer's audit profile.
• No label (tag) - A disclosure language did not have the TCPA labels around it for it to be captured properly.

To discover why a particular lead failed because of Disclosure, you should contact your buyer and ask "Which of the TCPA Guardian Disclosure responses the lead was flagged for"?

If a lead is rejected due to the TCPA Guardian responses ‘consent’ or ‘consent_rule,’ it means that the consent which was captured with the matching TCPA disclosure is being flagged by the auditing party for their TCPA Consent rule as set in their Audit profile. 

Auditors can designate disclosure rules based on five responses (definitions below): 

• Consent Actively Provided - the user proactively selected a consent option
• Consent Passively Provided - a consent option was pre-selected for the user
• Consent Passively Declined - the user did not provide consent and the consent option was not prepopulated
• Consent Actively Declined - the user proactively deselected a consent option
• No Interaction Required on the form - the user was not required to indicate whether they consent to TCPA or not
  • Consent is given through form submission (e.g. clicking a Submit button).

To discover why a particular lead failed because of Consent, you should contact your buyer and ask "Which of the TCPA Guardian Consent responses the lead was flagged for"?

If a lead is rejected due to one of these TCPA Guardian responses, it means that the attributes of the matching TCPA disclosure are being flagged by the auditing party for their rule(s) as set in their Audit profile. Definitions of each data point are as follows: 

Contrast: Measures the difference between the font color of the disclosure text and the color of the background on which the text was presented. 

Prominence: Based on the font size of the disclosure that was presented to the user. 

Visibility: Composite score of the Prominence and Contrast scores.

Spacing: If the removal of space turns two adjacent words into one word, a mismatch will result. However, if two adjacent words remain separate, it does not matter how many spaces are between them.

Punctuation: Jornaya removes all punctuation when performing a check for TCPA match.

The script registers the disclosure as seen by the user. If the user has their browser translated into a different language (e.g. Spanish), the script will capture the disclosure in Spanish. 

In this case, the Spanish disclosure will be compared against the lead buyer's approved list of TCPA disclosures. If the Spanish disclosure is not on the lead buyer's approved list, it will result in a TCPA Mismatch.

The easiest way to tell if Jornaya is capturing your TCPA disclosure is to view the lead event in the Jornaya Member Portal. 

1. Login to the Jornaya Member Portal
2. Navigate to the ‘My LeadiDs’ section under the ‘Campaigns’ tab. 
3. Paste the LeadiD token from the lead event into the search box and click ‘search.’

If any disclosures were captured, they will appear at the top of the page, under the ‘TCPA Disclosure’ section. 

If no disclosures were captured, the text ‘No TCPA disclosure label was found’ will be present under the heading.

No, the letter case does not matter in a TCPA Guardian disclosure comparison.

If you are attempting to implement the Jornaya TCPA label tags and find yourself unable to update the ID to "leadid_tcpa_disclosure", the Name field can be used in its place. Our script will recognize either to capture the tag and its contents.

Standard Implementation (Recommended): 

id="leadid_tcpa_disclosure"

Optional: 

name="leadid_tcpa_disclosure"

Checkbox:

<label>
 <input type="checkbox" name="leadid_tcpa_disclosure"/>[ENTER DESIRED OR SPECIFIED DISCLOSURE TEXT HERE]
</label>

No Interaction:

<label>
 <input type="hidden" name="leadid_tcpa_disclosure"/>[ENTER DESIRED OR SPECIFIED DISCLOSURE TEXT HERE]
</label>

Radio Buttons:

<label> 
 <input type="radio" name="leadid_tcpa_disclosure"/>[ENTER DESIRED OR SPECIFIED DISCLOSURE TEXT HERE]
</label>

Yes/No Menu:

<label>[ENTER DESIRED OR SPECIFIED DISCLOSURE TEXT HERE]
  <select name="leadid_tcpa_disclosure">
    <option value="Any_Value_You_Want">Yes</option>
    <option value="Any_Value_You_Want">No</option>
  </select>
</label>

At this time, we do not share the source URL in our API response. It is possible we change this position if market conditions change. These could be changes to regulatory policy, privacy laws, or industry norms. We know that many lead sellers do share URL and we will continue to evaluate our position.