Introduction
When leads are invalidated in the platform, they can be flagged for a variety of reasons. This document walks through the common reasons, what they mean and what you can do to resolve them.
Please note: This is a live and evolving document that will be updated as new jobs are created.
Invalid Lead Reasons
| Error Message | Definition | What To Do |
|
The lead value does not [Operator (equal/startswith/endswith/contains)] any values on the validation list [Name of validation List] on the field [Name of field] |
A value on the lead does not match a value on the validation List |
Check the field value against the list provided by the client. Please note if the operator is equal, then this must be exactly the same, including any spaces, characters or capitalisations. |
|
The field [Name of field] with the operator [Operator (equal/startswith/endswith/contains)] was not found in the list of values. The value supplied was [XXXXXX] |
A value within the specified field is not on the required list. The uploaded value was .... |
Check the field value against the list provided by the client. Please note if the operator is equal, then this must be exactly the same, including any spaces, characters or capitalisations. |
|
The Length Check, field [Name of field], returned a length of XX, The minimum length is 0 and the maximum length is 100 |
The value on the lead is outside of the accepted field length |
Check the length of the value in the field |
|
Required lead data is empty or missing. Please check the following fields [Name of field] |
The lead does not contain data within the specified field |
A required value is missing. Ensure you have included all the values the client has requested |
|
The lead contains multiple unexpected characters in the [Name of field] |
Within the specified field there are unaccepted characters e.g: [}\ |
Check the flagged field for any unexpected characters, for example: []{}\|@£$%^&*() |
|
The value of the field [Name of field] did not match the date format DD-MM-YY |
The date value submitted is not in the correct format of DD-MM-YY |
Check the date you have submitted matches the format the client has requested |
|
Vowel Check returned invalid words: [Example invalid word] |
The value supplied does not have enough vowels |
Check the field value is correct |
|
Test Data Check for [Name of field]: [example field value] returned a status of 'Test Data Found'. |
The field identified in the error message contains a value which includes the word 'Test' in it |
Check the field does not contain the word 'Test'. Sometimes some names or emails may form the word 'test' when merged together. If this is the case, let your client know |
|
Live Email Check returned a status of 'unknown' which is configured to fail this check. |
The third party email provider has deemed the email to be 'unknown' and therefore invalid |
The third party email provider has flagged the email address as unknown. Check the email value has been submitted as expected |
|
Live Email Check returned a status of 'NDC Not Found' which is configured to fail this check. |
The Third Party Email Provider can not identify a valid Country Code |
NDC refers to the country code on a Telephone number. Ensure your telephone number has a country code |
|
Telephone Format Check returned a status of 'Too Many Sequential or Repeated Numbers' |
The Telephone field has too many sequential numbers or repeated numbers within it |
Check your telephone value is correct |
|
The lead telephone number is empty |
The Telephone field is empty where there should be a value |
Check the Telephone field and ensure there is a value in it |
|
Verification of global telephone numbers: Invalid API Response |
The Global Telephone Test is unable to verify the phone number |
Check that the job has been mapped properly. If not, it may be that the telephone field has not been populated by the correctly |
|
Duplicate Field check for [Name of field] returned a status of 'Duplicate Found' (Lead ID, Lead ID, Lead ID) |
The field named contains a duplicate value within the listed IDs |
Check the listed ID to see the duplication, then action as needed |
|
Duplicate Email for Same Publisher returned a status of 'Duplicate Found' |
The lead has been found to be a duplicate |
Replace the lead if required |
|
The lead data contains foul language, see element: [Name of field] |
Profanity has been found in the field indicated. |
Check the value in the field indicated and validate/invalidate accordingly. Note that some valid words may contain a profane word. |
|
Suppressed Telephone: Invaild API Response |
The Suppressed Telephone Check is unable to verify the phone number |
Check that the job has been mapped properly. If not, it may be that the Telephone field has not been populated by the publisher |
|
This email was found in a previous campaign. Within the past [XX] days |
The email in the lead has been found in another campaign within the past set number of days |
Check the lead value and action as needed |
|
The lead details have been found X times within similar campaigns in the past X months. |
The lead has been found in a number of campaigns within the set number of months |
The lead can either be validated or invalidated, depending on whether it can be accepted. |
|
Multiple Field Duplication: [Name of field] not found in lead data |
An expected field is not found in the lead data |
Check the field in the error and ensure there is a value |