Features / Email Appends

Email appends.
Turn a postal list into an omni-channel one.

Most direct mail lists arrive postal-only. The team can mail to every record, but the email side of every coordinated campaign — pre-drop priming, scan-triggered co-landing, post-drop reactivation — is gated by which records happen to have an email already attached. Email append closes the gap. The platform matches postal records against consented email graphs, verifies every match through standard hygiene, and enriches the list in place. Records that were mail-only before become candidates for the full omni-channel coordination the rest of the platform delivers.

How it works

Five steps. Verified appends. Omni-channel-ready output.

  1. 01

    Submit the postal list for matching

    Upload, SFTP, or API-push the recipient list to the platform. Each record carries name and mailing address; many records lack a usable email. The list flows into the email append workflow.

  2. 02

    Match against consented email graphs

    The platform runs the records against B2C and B2B consented email graphs. Each match returns a verified email address tied to the postal identity, plus a deliverability score and a confidence rating per match.

  3. 03

    Suppression and verification on every match

    Matched emails run through hygiene before they hit a campaign — syntax check, MX record validation, mailbox-existence verification where supported, and suppression against unsubscribe and complaint lists. Bad matches surface as flagged records, not as silent failures in production.

  4. 04

    Appended records flow into the campaign list

    The original list is enriched in place — a new email column populates per record where a match landed, with the match metadata (source, confidence, append date) stored alongside. The list is now omni-channel-ready without the team building the second list manually.

  5. 05

    Campaign sends across both channels with shared attribution

    The mail piece addresses the postal record; the email engine sends to the appended email; both touches tie back to the same recipient ID. Conversion attribution unifies even on records where the appended email is the only digital identifier the team has.

Why it matters

Why a postal-only list is leaving response on the table.

A direct mail program coordinated with email gets multiple touches on the same recipient in the same window — and the response math compounds materially over either channel alone. But the email coordination only works on records where the team actually has an email address. On a typical acquisition list, the share of records arriving with email is well below 100 percent. Every record without an email is a recipient who only gets the physical touch — half the campaign that the platform was designed to run.

Email append solves this at the list-enrichment layer rather than the data-collection layer. The platform matches postal records to consented email graphs, verifies the matches through hygiene, and enriches the list before the campaign launches. The mail-only records become candidates for the same coordinated email send — scan-triggered co-landing included — that the email-attached records get. The campaign mechanics don't change; the addressable email audience grows.

The compounding lift is on attribution. Conversions on appended-email records tie back to the original recipient ID and the originating campaign. The team can measure exactly how much incremental response came from the records that joined the omni-channel campaign through append rather than through original data collection. The investment in append pays back per campaign on a measurable, per-record basis.

Per-match
Email append billing is per verified match returned, not per record submitted. Teams only pay for records that produce a usable appended email address. The platform reports the match-billable count before any charges commit, so the math is transparent before the spend.
Source: DirectMail.io email append billing model
Use cases

Where email append earns its keep.

  • Acquisition lists from third-party data partners

    Cold prospect lists arrive postal-only. Email append turns them into omni-channel-ready audiences before the first drop, so the campaign launches with email reinforcement from day one.

  • CRM enrichment for retention programs

    Customer records captured at sale frequently lack email — phone, address, but no inbox. Append fills the gap, opening retention email, scan-triggered email, and post-drop reactivation programs to records that were mail-only before.

  • Trade-show and event lead lists

    Lead lists from events with handwritten or scanned data frequently lack clean email. Append validates what came in and fills what didn't, producing a list ready for follow-up sequence within days of the event.

  • Multi-location franchise corporate rollouts

    Corporate-owned customer data joins per-location lists. Append normalizes the email coverage across locations so omni-channel campaigns reach a consistent percentage of recipients regardless of where they entered the system.

Email Appends FAQ

Questions teams ask before deploying.

Short answers. For implementation specifics on B2B vs B2C graphs, recurring append cadence, or compliance configuration, book a demo.

  • What is an email append and why does it matter?

    An email append is the process of matching postal-only recipient records against consented email databases to add a verified email address per record. The result is a list that supports both direct mail and email — coordinated touches on recipients who otherwise would only be reachable through the mailbox. For programs running scan-trigger email co-landing, email-appended recipients become eligible for the same scan-triggered automation as recipients who arrived with email already attached.

  • How accurate are appended emails — what match rate should we expect?

    Match rates vary by audience profile and the breadth of the underlying consent graphs. B2C consumer audiences typically match at higher rates than B2B firmographic lists. Every matched email runs through verification before joining the campaign — syntax, MX, mailbox existence — and confidence-scored matches surface in the platform so the team can choose to include or exclude lower-confidence matches per campaign.

  • Are the appended emails consent-compliant under CAN-SPAM and CCPA?

    The append graphs DirectMail.io draws from are built from consented data sources — recipients who opted in to receive marketing email from the source. The platform respects unsubscribe and suppression status on every send, regardless of how the email arrived in the list. For CCPA right-to-delete workflows, appended records are fully suppressed when a consumer requests deletion. Compliance posture matches the rest of the platform.

  • How is email append different from email hygiene?

    Append fills in missing emails on records that don't have one. Hygiene validates and cleans emails that already exist on the list. Both run as discrete features — append for enrichment, hygiene for validation. They compose: a list with both append and hygiene applied has the maximum percentage of usable email addresses possible. The two run in sequence on every list configured for both.

  • Does email append work for B2B lists with corporate addresses?

    B2B append works against firmographic email graphs that match recipient records to corporate emails based on name and company. Match rates skew lower than B2C consumer append because B2B email turnover is high (people change jobs and email addresses follow), but the match rate on durable corporate roles (executives, directors, named decision-makers) is meaningful. The platform reports the match rate per audience so the team can see the math on their specific list.

  • Can we run email append on demand or is it scheduled?

    Both. Append runs as a one-time enrichment on a list at upload, or as a recurring service on lists that flow in continuously through SFTP or API. For programs that ingest lists on an ongoing basis (printer client deliveries, CRM exports), recurring append keeps the omni-channel reach growing as the list grows.

  • What does email append cost and how is it billed?

    Email append billing is per-match (not per-record submitted) for most use cases — the team only pays for records that actually return a verified appended email. Plan tiers and volume detail live on the pricing page. The platform reports the match-billable count per append run before any charges are committed, so the team always sees the math before the spend.

Run an email append on a sample list.

Bring 1,000 postal records. We’ll show the match rate, the per-match confidence scoring, the verification report, and the omni-channel-ready output — in 30 minutes.