Service Objects Email Validation Follow

Overview

Service Objects DOTS Email Validation 3 (EV3) can be used with Convertr to validate email addresses during lead processing.

For a straightforward pass/fail email validation, this can be configured using the Universal Connector Processr job. The Service Objects response can be evaluated using:

ValidateEmailInfo.Score

The same Service Objects response can also be consumed through Universal Enrichment where returned data needs to be made available for further processing, validation or delivery.

Service Objects returns a score between 0 and 4, with lower scores representing a higher likelihood that the email address is valid.

Requirements

Before configuring the integration, you will need:

• A Service Objects Email Validation account and licence key.
• Access to configure Processr jobs on the campaign.
• An email address field available on the lead.
• A Service Objects trial or production endpoint.

Service Objects offers trial keys for testing. Service Objects Email Validation

Configure the Service Objects request

Add a Universal Connector validation job to the campaign and configure the request to call the Service Objects EV3 API.

For the ValidateEmailFull operation, the trial URL should follow this format:

https://trial.serviceobjects.com/ev3/api.svc/ValidateEmailInfo/Full/##email##/{LICENSE-KEY}?format=json

Replace {LICENSE-KEY} with the appropriate Service Objects licence key.

The ##email## placeholder is dynamically replaced with the email address from the lead when the request is made.

Service Objects documents this URL structure for its ValidateEmailFull operation.

Service Objects response

A successful response contains a ValidateEmailInfo object. For example, an invalid email may return a response similar to:

{
  "ValidateEmailInfo": {
    "Score": 4,
    "IsDeliverable": "false",
    "EmailAddressIn": "example@example.com"
  }
}

For this configuration, the field we are interested in is:

ValidateEmailInfo.Score

Email validation scores

Service Objects defines the scores as follows:

Service Objects generally recommends treating 0, 1 and 2 as acceptable, although the exact acceptance criteria can be adjusted depending on the customer's requirements. A stricter implementation could accept only scores 0 and 1.

Configure the validation conditions

In the Universal Connector Validation Conditions, set the Response Field to:

ValidateEmailInfo.Score

For the standard configuration shown below, set Overall Operation to ANY and add the following conditions:

This allows a lead to meet the validation criteria when Service Objects returns Good, Probably Good, or Unknown.

Scores 3 and 4 fall outside these accepted conditions and can therefore be treated as invalid by the job.

[Insert screenshot: Universal Connector Validation Conditions]

Alternative validation rules

The acceptance criteria can be changed depending on the customer's requirements:

• Standard: accept 0, 1 and 2.
• Strict: accept only 0 and 1.
• Lenient: accept 0 through 3, rejecting only 4.

The appropriate configuration should be agreed with the customer before enabling the job on a live campaign.

Testing the configuration

Before using the integration on live traffic, test the job with both known valid and invalid email addresses.

Check the returned response and confirm that:

1. The lead email is correctly inserted into the Service Objects request.
2. A successful API response is returned.
3. ValidateEmailInfo.Score is available to the validation conditions.
4. Expected scores pass or fail according to the configured rules.
5. Invalid API credentials or other Service Objects errors are handled appropriately.

A response with Score: 4, for example, represents an email classified by Service Objects as Bad.

Additional considerations

The ValidateEmailFull operation performs real-time SMTP checks, so individual requests can take several seconds depending on the recipient's mail server. This should be considered when testing campaign processing performance.

Service Objects also returns fields such as IsDeliverable, warning codes and corrected email information. These can be used for more advanced rules if required, but ValidateEmailInfo.Score provides the simplest single-field validation approach.

Service Objects currently identifies ValidateEmailAddress as its recommended EV3 operation for new integrations. This article documents ValidateEmailFull because that is the endpoint used and tested with the Convertr configuration above.

Service Objects documentation

DOTS Email Validation 3 documentation

ValidateEmailFull operation