Email.
Same audience as the mail. Same campaign timeline.
A direct mail program coordinated with email gets two touches on the same recipient in the same window — and the response math compounds materially over either channel alone. Most programs try to coordinate by stitching a standalone email tool to the mail platform; lists diverge, segments break, attribution stitches with UTM parameters that get stripped at the inbox layer. The integrated engine eliminates the stitching: shared list, shared variable data, four send modes including the flagship USPS-scan-triggered mode that lands the email the moment USPS scans the mail piece.
Five steps. Four send modes. One unified campaign.
- 01
One list drives mail and email together
The campaign list that addresses the mail piece is the same list that fires the email. No parallel list to maintain, no segment sync to break, no UTM-parameter stitching layer to carry attribution between channels.
- 02
Compose in the email editor with shared variables
The editor binds variable subject lines, hero images, headlines, and CTAs to the same fields driving the variable mail piece. The recipient sees a coordinated message in two channels with one source of truth.
- 03
Pick the send mode that matches the campaign
Standalone immediate, scheduled (specific time or relative to drop date), recurring (event-triggered programs), or USPS-scan-triggered (per-recipient release on the actual DDU scan of their specific mail piece).
- 04
Deliverability infrastructure handles the heavy lift
Sender reputation, SPF/DKIM/DMARC alignment, bounce processing, unsubscribe management, feedback-loop integration with major mailbox providers — all managed by the platform. Teams focus on the campaign, not the deliverability tuning.
- 05
Engagement reports back to the campaign — not a silo
Opens, clicks, bounces, unsubscribes, conversions all post to the same campaign dashboard as the mail piece scan data and landing page metrics. Per-recipient, per-channel, unified attribution.
Why integrated email beats stitched email.
A standalone email tool can produce a great email. What it cannot do is fire on a per-recipient USPS scan event — the latency budget between the scan and the email release is measured in minutes, and a stitched stack with cross-tool API calls and list-sync cycles cannot meet it. The flagship coordination mode for direct mail and email — co-landing the two touches on the same day — only works when both engines run on the same platform connected to the same scan stream.
The compounding lift is on attribution. Every email send carries the recipient ID encoded in the tracked URLs. Every click, form submission, conversion, and revenue event ties back to the recipient record and the originating campaign. The dashboard reports unified per-recipient performance — not a per-channel summary that requires manual reconciliation against revenue. The CFO question gets a single answer.
And deliverability is the silent third lever. Most teams underestimate how much of email performance is just "the email reached the inbox." The platform manages SPF, DKIM, DMARC, sender reputation, bounce processing, unsubscribe compliance, and feedback-loop integration automatically — work that historically required a dedicated email-ops engineer to maintain. Inbox placement stays high without ongoing tuning.
Where integrated email earns its keep.
-
Pre-drop announcement send
A standalone email lands a few days before the mail piece arrives, priming the recipient. Same audience, primed and ready when the physical piece hits the mailbox.
-
Scan-triggered co-landing email
The flagship mode: email fires per recipient on the actual DDU scan of the specific mail piece — inbox and mailbox co-land the same day. Open rates spike in the 2-4 hour window after the scan.
-
Post-drop follow-up to non-responders
A scheduled send 7 days after the drop reaches recipients who did not respond. The email reinforces the offer with the original mail piece imagery, plus a one-click conversion path.
-
Recurring lifecycle programs
Service reminders, anniversary emails, milestone communications — all event-triggered from the recipient list, all running on the same engine that handles the mail.
Questions teams ask before deploying.
Short answers. For implementation specifics on deliverability, custom domains, dedicated IPs, or scan-trigger configuration, book a demo.
-
Why does direct mail need an integrated email engine?
A direct mail program coordinated with email gets two touches on the same recipient in the same window — and the response math compounds materially over either channel alone. Most programs try to coordinate by stitching a standalone email tool to the mail platform: the list lives in two places, segments diverge, attribution requires UTM parameter passing that breaks at the inbox layer. The integrated engine eliminates the stitching by sharing the list, the variables, the campaign timeline, and the reporting layer with the mail piece directly.
-
What send modes are available?
Standalone immediate (a one-off email blast), scheduled (specific date and time, or relative to the campaign drop date — for example "fire 3 days after drop"), recurring (event-driven programs that fire on triggers like service anniversary, account-tier change, mileage threshold), and USPS-scan-triggered (the flagship mode where email releases per recipient on the actual DDU scan of their specific mail piece, so inbox and mailbox co-land the same day).
-
How does deliverability work — what does the platform handle automatically?
DirectMail.io manages the full deliverability stack: SPF, DKIM, and DMARC alignment for sending domains; sender reputation monitoring; bounce processing and list hygiene; unsubscribe handling compliant with CAN-SPAM; feedback loops with major mailbox providers (Gmail, Microsoft, Yahoo); IP warming for new sending domains. Teams configure the sending domain once; the platform handles the ongoing work that determines whether email lands in the inbox or the spam folder.
-
Can we use a custom sending domain or a dedicated IP?
Yes to both. Custom sending domains configure with standard DNS records (the platform provides the records to add); dedicated IPs are available for high-volume use cases that benefit from sender-reputation isolation. The platform manages IP warming on dedicated IPs to establish reputation with mailbox providers before high-volume sending starts.
-
How does the USPS scan trigger fire email per recipient?
When a campaign is configured with the scan-trigger send mode, the email is composed and queued before the drop. As USPS scans each piece during sortation, scan events stream into the platform via Informed Visibility (IV-MTR). The DDU scan — the final scan before carrier pickup — fires the email release for that specific recipient. Inbox and mailbox arrive within hours of each other for the vast majority of recipients. The full mechanics live on the USPS Scan Trigger feature page.
-
How do conversions tie back to the email and the mail piece?
Every email send carries the recipient ID encoded in tracked URLs and the campaign source. When the recipient clicks through to the personalized landing page, submits a form, places an order, or calls a tracked number, the conversion attributes back to the recipient record. The dashboard reports the conversion against both channels — the mail piece and the email — with per-recipient resolution. The CFO question of "did this campaign work" gets a unified answer rather than a per-channel one.
-
Can email run as part of an event-triggered or recurring program?
Yes. Recurring sends fire on events from the recipient list — service anniversary, account-tier change, behavioral threshold, mileage milestone, lifecycle stage. The trigger logic configures inside the platform with no engineering work. Programs that historically required marketing automation infrastructure (Marketo, Eloqua, HubSpot Marketing Hub) plus a separate mail platform run end-to-end inside DirectMail.io.
Run a coordinated email + mail campaign on a sample list.
Bring 100 records. We’ll set up the variable email, configure the USPS-scan-triggered send, and walk through the deliverability and engagement reporting — in 30 minutes.