...
- 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 Users can list all filed field names to be used for validation | This allows user users 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 Users 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. |
What use case(s) does this apply to?
| Status | ||||
|---|---|---|---|---|
|
Why would clients find this useful?
...
- Domain Suppression
- Email Suppression
- Account-Based Marketing lists
- Data pick lists eg a list of product ranges
- Accepted Country lists
- List of accepted Assets (name of the material the user downloaded or viewed)
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
...