Email Output Columns
Use this article if your batch processing includes Email validation. Applies to file-based batch processing only — not real-time API responses.
Dynamic email field names
Email column names include {FIELD_NAME_EMAIL}, replaced by your actual input column name.
Example: if your email column is email, then DQE_{FIELD_NAME_EMAIL}_ERROR_CODE becomes DQE_email_ERROR_CODE.
Email columns
| Column name | Description |
|---|---|
| DQE_{FIELD_NAME_EMAIL}_ERROR_CODE | Return code after Email processing |
| DQE_{FIELD_NAME_EMAIL}_ERROR_LABEL | Return code label after Email processing |
How to use email results
Use the error code for automated filtering, mapping, or business rules. Use the error label for business users, support teams, and manual review.
Best practices
- Use ERROR_CODE to segment valid, invalid, or uncertain email addresses
- Use ERROR_LABEL to make results easier to understand for non-technical users
- Keep the original input email field to compare with DQVerify result
- Review email results before applying automatic updates to production data