...
Validation lists give the users the ability to add custom pick lists to the platform in order to use these lists as validation against their lead data.
In the majority of cases, users would be uploading a variety of different data sets:
- Domain Suppression
- Email Suppression
- Account-Based Marketing lists
- Data pick lists eg a list of product ranges
- Accepted Country lists
What use case(s) does this apply to?
| Status | ||||
|---|---|---|---|---|
|
| Action | Description |
|---|
Acceptance Criteria | |||
|---|---|---|---|
| 1 | User can list all filed names to be used for validation | This allows user to set all the input fields they want to validate against for e.g. email, name, date | A user can select a field for the validation list to run against |
| 2 | User can configure an 'Operator' | This is used to determine how values are viewed eg.
|
|
|
| Depending on the operator the data will be checked against accordingly | ||
| 3 | 'validationRule' - User can set if a Validation Rule should 'pass' or 'fail' | This is used to determine if a rule is set in the Validation of data should pass or fail. eg. User wants to fail leads based on min value and the min value of a specific lead does not meet the value set. This would result in the lead returning a 'fail' status | If the rule is set to pass and the value matches a value against the validation list the job will pass. If the rule is set to fail and the value matches a value against the validation list the job will fail. |
| 4 | 'passEmpty' -User can set if a value being passed can be Empty | This allows users to configure if they want to allow certain values to be passed without having any data / value being empty. | eg. A user could set 'Job title' on a Validation list to 'passEmpty' = 'True' which would allow for values to be collected if entered by leads however if no value was entered the lead would still be passed through for processing by the platform. If 'passEmpty' = 'FALSE' the field value would not allow for empty values to be passed to the platform. |
| 5 | 'multiValue' - User can collect multiple values on a field value | This allows users to collect multiple responses from a single input. |
| If the user set a 'multiValue' = TRUE for a multi select value (a dropdown list) and wanted to Validate that multiple values were present/selected this would | ||
| 6 | 'multiValueDelimiter' - Use can configure how multiple values should be separated. | This allows users to select how they want values to be |
| separated | a user has the option to specify the delimiter eg ',' , ';' , ':' , '.' , '/' , '-' | |
| 7 | 'caseSensitive' User can set if values are validated based on case sensitivity | This allows users to set if a value is validated based on character case |
| sensitivity | If 'caseSensitivity' is set to 'TRUE' any leads that are submitted |
| that do not meet the case will be rejected | ||
| 8 | Private list - Use can set if the values for a Validation list are hidden from Publisher / Advertiser | This allows users to |
| mask the values |
| within a validation list |
| If a Publisher plans to validate against 'email' values all the email values will |
| masked in the platform. |
Why would clients find this useful?
- Makes sure data is formatted exactly to the needs of the client or user
- Helps with standardisation of data collected, which in turn helps with reporting and interrogating of data.
- When leads are being run against Key accounts or Suppression list
An example of how it would be implemented?
Global Validation List example:
Adding a Validation List to an Advertiser:
| View file | ||||
|---|---|---|---|---|
|
Adding Validation list to a Campaign
...
The main use case would be around data consistency and standardisation. From a users perspective by having the ability to upload a list of accepted values prevents any incorrect data from flowing to other systems they are using.
For example, a user uploads a list of Domains, which the data has to be suppressed against. Thus preventing any leads with this particular domain to flow through to their other data systems such as their ESP or CRM systems.
However, this is just one scenario where it can be applied. as mentioned above this can be used in a variety of different ways eg
- Domain Suppression
- Email Suppression
- Account-Based Marketing lists
- Data pick lists eg a list of product ranges
- Accepted Country lists
- List of accepted Assets
Key talking points:
- When clients are looking to Validate against specified list values
- When a client wants to keep validation fields private
- When clients want to collect multiple values for a field and to reject when not all values are met
- When clients want to be able to set a pass or fail status for leads that don't include specified values
- When clients are looking to validate leads that contain certain character values
An example of how it would be implemented?
Global Validation List example:
| View file | ||||
|---|---|---|---|---|
|
Adding a Validation List to an Advertiser:
| View file | ||||
|---|---|---|---|---|
|
Adding Validation list to a Campaign
| View file | ||||
|---|---|---|---|---|
|