The Basic Email Domain Validation third-party service allows you to check the lead’s email address and its domain validity to filter out incorrect or unwanted leads.
To enable this service, go to the Fraud and Anomaly > iClear > Lead Processing Rules section and select a Product from the drop-down list.
Once you select the Product, you’ll be automatically redirected to the Lead Processing Rules (iClear) tab. You may also navigate here by selecting the System Management > Products section on the left-hand menu and clicking on the “Settings” button for the corresponding product (Lead Processing Rules (iClear) tab).
To configure this service, click the “Add Service” button in the Global Rules block. Fill in the following fields:
- Select Third Party Service: Select the “Basic Email Domain Validation” option.
- Execution Type:
- Select the "Synchronous" option to wait for the service outcome before processing a lead. This execution type is recommended for real-time lead filtration based on the service status.
- Select the "Asynchronous" option to make a simultaneous request and process a lead without waiting for the service outcome. This execution type is recommended for analytical purposes, not real-time lead filtration based on the service status.
- Select the “On-Demand” option to enable leads filtration when the “% of lead to lookup” is set as 0 (null).
- % of leads lookup: Set the percentage of leads to be checked through this service. Note: This field is available only for Synchronous and Asynchronous Execution types.
- Select a field to retrieve email: Select a field to retrieve the lead’s email address (e.g., email).
- Reject if email is not valid: Select the “Yes” option to filter out the lead with an invalid email address.
- Enable Domain check: Select the “Yes” option to check the domain’s validity.
- Reject if domain does not exist: Select the “Yes” option to reject the lead with an email address that contains a non-existent domain. This field is available if the domain check is enabled in the field above.
- Reject if domain does not have MX records: Select the “Yes” option to reject the lead with an email address from a domain without an email exchanger record. In other words, if a domain does not have an MX record, it cannot receive emails. This field is available if the domain check is enabled in the field above.
- Reject lead if the number of dots in the email is greater than or equal to: Enter the maximum number of dots allowed in the lead's email address.
Example: If you enter '1' in this field, the email address 'example@example.com' will be accepted, while 'example.example@example.com' will be rejected. - Reject lead if the email contains a plus sign: Select the “Yes” option to filter leads with a ‘+’ sign in their email addresses.
The “Additional Run Settings” configuration block allows you to configure more options to determine at which stage you would prefer to run the service.
- Service run time: Select whether you would prefer to run the service before or after the leads are filtered out (After filtration / Before filtration).
Note: Please be aware that selecting this option may impact your invoice. Once this option is selected and no campaigns remain for the service to run, there will be no charges incurred. - Run service on (PingPost products only): Select one of the options to determine at which stage you would prefer to run the service for the Ping Post products (Ping / Post / Ping and Post).
- Run service on silent ping: Select “Yes” if you would like to run the service during the silent ping stage. Select “No” to exclude this option.
- No response service action: (The system runs a lookup service, in case the service did not get any response you can select the preferable action)
- Select the “Continue Processing” option if you want to continue processing leads when the service does not respond.
- Select the “Reject the Lead” option if you want to reject the lead when the service does not respond.
Click the “Add” button to confirm.
Read more about the Global and Advanced Rules configurations in this Knowledge Base article.