Import Metrics

When importing data into Messaging, the system can be configured to send alert notifications based on the selected exceptions or error conditions. However, not every metric is relevant, or makes sense, for every import method. For example, the "Duplicates on the File" metric isn't relevant for API Posts or Web Forms, because those methods load data one record at a time, rather than via a file.

The following table lists all of the supported exceptions and error conditions, and indicates which ones are utilized by which import method. This table also indicates which exceptions are identified during the parsing step, and which are identified during the database update step.

		Import Method				Import Step
Condition	Description	API Post	Web Form	Manual Import	FTP Import Template	Parsing	Update
File Parsing Statistics
Warnings for the file	The system identified missing, empty or unmapped columns, but the row will be imported.
Missing Unique ID Columns	The unique identifier is missing on the row, and the row will not be imported.
Empty Rows	No data in the row, nothing to import.
Email Address Validation
Cleaned Emails	Email addresses were cleaned (if possible).
Invalid Emails	Email column will not be imported.
Banned Emails (Global)	Known invalid email addresses are banned from sending.
Banned Emails (Custom)	Custom additions to the Banned Email list.
Hard Bounces	Emails that previously had Hard Bounces and will not send in the future.
Soft Bounces	Emails that previously had Soft Bounces and will not send in the future.
Known Bad Addresses	Emails that are known to be bad addresses; shown here to indicate list health.
Phone Number Validation
Cleaned Phones	Phone Numbers were cleaned (if possible).
Invalid Phones	Phone Number column will not be imported.
Banned Phones	Mobile Carriers prevent messages being sent to this phone number.
Bounced Phones	Phone numbers that previously bounced.
Unique Identifier Cleaning
Primary Key Not Found in Database	The Primary Key was imported but was not found in the database; the record will not be updated/created.
Unique ID Incomplete	The Unique ID was missing information; the record will not be updated/created.
Primary Key / Alternate Key Conflict	The Primary Key was imported to change the Unique ID of the record, but new Unique ID already exists on existing record; the record will not be updated/created.
Duplicates on the File	The same Unique ID appeared on two or more records on the file; the first record will be updated/created, the remaining duplicate records will not be updated/created.
Unique Identifier Matching
Primary Key Duplicates	After all methods to detect unique records, primary key duplicates removed.