Data Loader – Email Validity Processing

Overview

Email validity data from supported vendors can be processed directly through Data Loader. You no longer need to send validity files to Omeda for processing. Map the vendor, vendor code, and validation date from your file alongside the email address, and the validity data is written as part of the Data Loader job.

Email validity fields can be included in any Data Loader file, either on their own or alongside other contact data. Mappings can be saved to a template, so recurring validity loads can run without remapping each time.

Note: Email validity processing is also available in Inputs, using the same fields and rules described below.

Supported Vendors

Vendor names must match one of the values below character for character, including spaces. Matching is not case sensitive, so freshaddress and FRESHADDRESS are both accepted, but Fresh Address is not.

• FreshAddress

• InfoGroup

• Synthio

• SAE Validity

• Zero Bounce

• Tower Data

• Data Axel

• ALFRED

• Webbula

A single file can contain validity data from multiple vendors. Each row is processed based on the vendor in that row.

Mapping Email Validity Fields

Email validity fields are mapped in the General Mapping step under the Email Validity category. There is no separate Email Validity step. Map these three fields:

An email address must also be mapped.

Mapping Requirements

• If any Email Validity field is mapped, all three must be mapped. Mapping only one or two will show an error and block saving.

• If any Email Validity field is mapped, Email Address must also be mapped, or saving is blocked.

• If no Email Validity fields are mapped, the file processes normally and no validity data is written.

How Rows Are Processed

Each row is validated before any data from that row is written.

• All three validity values present: the validity data is written for the row's email address.

• All three validity values blank: the row processes normally with no validity data written. This lets a file mix rows with and without validity data.

• One or two validity values present: the entire row is held, including any non-validity data on that row.

• Blank email address on a row with validity data: the row is held.

• Unsupported vendor name: the row is held.

• Vendor code not valid for that vendor: the row is held.

• Missing or unreadable Validation Date: the row is held.

Held rows don't stop the rest of the file. Valid rows continue processing, and the file finishes with a status of Completed w/Errors. Held rows and the reason for each can be reviewed from View Row Errors in the file's action menu. To load the held rows, correct them in your source file and upload them again. See Data Loader – Loading Data for more on file statuses and row errors.

How Updates Are Applied

• Validity data is stored at the email address level, with one active code per vendor.

• When a new code is loaded for an email address and vendor that already has one, the new code becomes active and the previous code is made inactive.

• If a file contains more than one row for the same email address and vendor, the row with the most recent Validation Date becomes active. If the dates are the same, the last row in the file is used.

Invalid Email and Spam Trap Updates

Loading email validity codes through Data Loader does not update email addresses to Invalid or flag them as spam traps, even when the loaded code indicates the address is undeliverable or a spam trap.

To mark those email addresses as Invalid or as spam traps, submit a separate ticket through the Support Portal after your file has processed.

Valid Codes by Vendor

Vendor codes must be entered exactly as listed below.

FreshAddress

InfoGroup

Synthio

SAE Validity

Zero Bounce

Tower Data

Data Axel

ALFRED

Webbula

Questions?

Reach out to your Client Success Manager or submit a ticket through the Support Portal.

Table of Contents