Output Files
The Contact Validation task can write all data to a single output file. Or, it can write data to two files: a high-confidence output file and a low-confidence output file. You can configure a task to write validated or corrected data to a high-confidence output file and write invalid data to low-confidence output file for data stewardship.
The following table describes the data that the Contact Validation task can write to the high-confidence and low-confidence output files. When you configure the task, you define the data written to each file. If you configure the task for a single output file, all processed data is written to the single output file.
Type of Data | High Confidence Output File Can Include... | Low-Confidence Output File Can Include... |
|---|
Postal Address Data | Valid postal addresses: - - Source data valid. All relevant data checked, and input matches perfectly.
- - Source data seems valid, but some or all elements were standardized, or input includes outdated names or exonyms.
Corrected postal addresses: - - All elements checked and corrected.
- - Many elements checked and corrected, but some elements could not be checked or corrected.
Geocode information, if requested and available. | Invalid postal addresses: - - Source data seems valid, but some or all elements could not be validated due to incomplete reference data.
- - Source data seems valid, but the data format can result in problems with delivery. For example, using a five-digit zip code instead of a nine-digit zip code.
Postal addresses that are not correctable: - - Some elements were not checked. Reference data not available for all elements.
- - Some elements were not checked. Source data format is incorrect or outdated.
- - Some elements could not be corrected, but the address might be deliverable.
|
Email Addresses | Valid, working email addresses. | Email addresses that are invalid or do not exist. |
Phone Numbers | Phone numbers that are not listed with the National Do Not Call Registry. | Phone numbers that are listed with the National Do Not Call Registry. Phone numbers that you do not have a subscription to validate. |
You might use a Data Synchronization task to load data from the high-confidence output file to a non-file target, or to process data from the low-confidence output file.
Output File Details and Field Names
Contact validation output files can include the following information:
- •Validation fields. Source fields selected for validation.
- •Contact fields. Contact fields selected for the address.
- •Pass-through fields. Additional fields from the source written to the output file without validation or correction.
- •Validation output fields. Output fields that contain the address, email address, or phone number information that was processed. Validation output field names are generated by the Contact Validation task. Output field names use the following convention: <output information>_OUT.
Output files can include the following output fields:
- - The validation output fields for email addresses: tns_EMail0_OUT, tns_LocalPart_OUT, and tns_DomainPart_OUT.
- - The validation output field for phone numbers: tns_PhoneNumber0_OUT.
- - Validation output fields for addresses use the following naming convention: <address information>_OUT. For example, validation output fields for geocode information are: GeoLatitude_OUT and GeoLongitude_OUT.
- - Supplementary output fields for addresses from the United States and Great Britain.
Supplemental output fields for the United States use the following naming convention: SuppUS<information>.
Supplemental output fields for Great Britain use the following naming convention: SuppGB<information>.
- •Formatted Address Line (FAL) fields. Address data formatted for use based on the address conventions of the country. For example, in the United States, a FAL1 field might include a building number, street name, and apartment number.
- •Residue fields. Address data that is not used for validation, but might be useful for delivery.
- •Validation code fields. Code fields added by the Contact Validation task. Codes indicate the status or results of the validation process.
- •Validation message fields. Message fields added by the Contact Validation task. Messages provide additional information about the status or results of the validation process.
- •Certified process mode output fields. When use the certified process mode, the output file can contain additional output fields based on country:
- - United States. CASS status and address fields use the following naming convention: Cass<information>.
- - Australian. AMAS code and address fields use the following naming convention: Amas<information>.
- - Canadian. SERP code fields use the following naming convention: Serp<information>.
- - France. SNA code fields use the following naming convention: Sna<information>.
Scripts in Output Files
Output files can contain data that has been converted from the source script to a different script.
Based on the Preferred Script advanced option on the Schedule page, the Contact Validation task can convert validated data to Latin or the standard script for a country.
As a result, output files can contain processed data in the converted script, pass-through data in the original script, and data that was not validated in the original script.
Date Formats in Output Files
For flat file sources, dates are written to output files in the format used by the source file.
For all other source types, dates are written to output file in the following format:
MM/DD/YYYY HH:mm:ss