Email output columns

When the Email process is enabled, DQE adds email output columns to the processed file.

These columns help you understand the validation result returned for each email address and read the associated error code and label.

Who should read this article

Use this article if your file-based batch processing includes Email validation and you need to understand the DQE email columns added to your output file.

This article applies to file-based batch processing via SFTP. It does not apply to real-time API responses.

Dynamic email field names

Email output column names include the placeholder {FIELD_NAME_EMAIL}.

This placeholder is replaced by the name of the input email field processed by DQE.

For example, if your input email column is named email, the output column DQE_{FIELD_NAME_EMAIL}_ERROR_CODE may appear as DQE_email_ERROR_CODE.

Email columns

How to use email results

Use the email error code and label together to understand the returned validation result.

• The error code is useful for automated filtering, mapping, or business rules.
• The error label is useful for business users, support teams, and manual review.

Best practices

• Use DQE_{FIELD_NAME_EMAIL}_ERROR_CODE to segment valid, invalid, or uncertain email addresses according to your project rules.
• Use DQE_{FIELD_NAME_EMAIL}_ERROR_LABEL to make the result easier to understand for non-technical users.
• Keep the original input email field so that you can compare it with the DQE result.
• Review email results before applying automatic updates to production data.

Related articles

• Understand DQE output columns
• E-Activity output columns
• Understand file-based batch processing