Email editor.
Same list as the mail. Same variable data.
A campaign email that doesn’t know about the mail piece can only do half the job. The DirectMail.io email editor shares the same recipient list, the same variable data layer, and the same campaign reporting as the mail piece and the landing page — so the email subject line that personalizes per recipient is driven by the same field that drove the variable headline on the postcard. Visual or HTML editing, inbox previews across major providers, full deliverability infrastructure, and three send modes including the flagship USPS-scan-triggered send that lands the email the moment USPS scans the recipient’s mail piece.
Five steps. One editor metaphor. Three send modes.
- 01
Open the same editor metaphor as print and landing
The email editor uses the same drag-and-drop building approach as the print and landing page editors. A team that knows one knows all three. The variable data layer is shared; the recipient list driving the mail piece drives the email automatically.
- 02
Build in visual or HTML mode
Drag-and-drop blocks for designers and marketers; raw HTML mode for developers who want pixel-perfect control. The two modes are interoperable — the visual output produces clean, deliverable HTML, and HTML edits round-trip back to the visual editor.
- 03
Bind variable fields to the recipient list
Subject line, preheader, headline, body copy, CTA, hero image — every element is variable-data-aware. The same field that personalizes the mail piece personalizes the email; one source of truth, no parallel field mapping.
- 04
Inbox-test before sending
The editor surfaces inbox previews across major providers (Gmail, Outlook desktop, Apple Mail, Outlook web, mobile clients). Spam-score check runs on the composed email. Issues surface before send, not after.
- 05
Send standalone, scheduled, or USPS-scan-triggered
The send modes match the campaign: a standalone email blast, a scheduled send tied to the drop date, or a USPS-scan-triggered fire that releases per recipient on the actual DDU scan of their specific mail piece. Same editor, three send modes.
Why the email editor lives where the mail list lives.
Stitching a standalone email tool to a direct mail program is the kind of project that looks straightforward on a whiteboard and bleeds engineering time for years. List sync runs every few hours and lags reality. Segment definitions diverge between the two tools. Attribution requires UTM parameters that get stripped at the inbox layer or hidden form fields that recipient browsers block. The maintenance cost compounds; the coordination value erodes.
The same email editor inside the same platform that owns the mail piece, the postal stack, and the recipient list collapses every one of those failure modes. The list is the list. The variable data layer is shared. The campaign reporting unifies. And the send modes — standalone, scheduled, scan-triggered — all reference the same campaign timeline, so the email fires when the campaign needs it to fire, not when an integration manages to sync.
The flagship payoff is the USPS-scan-triggered send. The email releases per recipient on the actual DDU scan of their individual mail piece — inbox and mailbox arrive within hours. That coordination is impossible with a stitched stack because the latency budget between the USPS scan event and the email release is measured in minutes. In-platform, it is the default mode for any campaign that wants the co-landing lift.
Where the email editor earns its keep.
-
Pre-drop announcement email
A standalone email lands a few days before the mail piece arrives, priming the recipient. The same recipient gets the mail piece, then the matching scan-triggered email on delivery day — a three-touch sequence on the same audience.
-
Scan-triggered co-landing send
The flagship use: email fires per recipient on the actual DDU scan of their specific mail piece. Inbox and mailbox arrive within hours of each other. The full mechanics live on the USPS Scan Trigger page.
-
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 program automation
Service reminders, anniversary emails, and milestone communications run as recurring sends tied to events on the recipient list — service date, signup anniversary, account-tier change.
Questions teams ask before deploying.
Short answers. For implementation specifics on deliverability, custom domains, or scan-trigger configuration, book a demo.
-
How is this email editor different from a standalone email tool?
A standalone email tool (Mailchimp, Klaviyo, Iterable) builds the email but does not know about the mail piece, the postal scan stream, or the recipient list driving the print run. To coordinate email with mail, the team has to maintain a parallel list, sync segments, and stitch attribution by hand. The DirectMail.io email editor shares the same list, the same variable data, and the same campaign reporting as the mail piece — coordination is automatic, not a project.
-
Does the editor support visual editing and raw HTML?
Yes — both, with full round-trip interoperability. Marketers and designers work in the visual drag-and-drop interface; developers can switch to HTML mode for pixel-perfect control or to integrate custom blocks. Edits in either mode reflect in the other. Teams with mixed skill profiles can collaborate on the same email without forcing everyone into the same toolset.
-
What variable data can be personalized in the email?
Subject line, preheader, sender name, headline, body copy, CTA text and destination URL, hero image (variable image swap from URLs in the list), embedded offer blocks, and any custom block field. The variable data is bound to the same recipient list driving the mail piece, so the field that drove the variable headline on the postcard drives the variable subject line on the matching email automatically.
-
How does deliverability work — what does the platform handle?
DirectMail.io manages deliverability infrastructure: SPF, DKIM, DMARC alignment for sending domains, sender reputation monitoring, bounce handling, and unsubscribe management compliant with CAN-SPAM. Sending is routed through deliverability-monitored IPs with feedback loops to major mailbox providers. Teams can also configure a dedicated IP or warm a custom sending domain for high-volume use cases.
-
Can the editor produce the ride-along creative for USPS Informed Delivery?
Yes. Informed Delivery ride-along is treated as a campaign asset alongside the mail piece and the campaign email. The editor produces the ride-along image at the USPS spec, ties it to the campaign, and submits it to the USPS Mailer Campaign Portal automatically. The Informed Delivery FAQ page covers the campaign mechanics; the editor is where the creative composes.
-
What send-time options are available?
Standalone immediate send, scheduled send (specific date and time, or relative to the campaign drop date), recurring send (for ongoing programs), and USPS-scan-triggered send — the flagship coordination mode where the email fires per recipient on the actual DDU scan of their specific mail piece. The full mechanics of the scan trigger live on its own feature page; the editor is where the email content is composed.
-
How does email reporting tie back to the campaign?
Opens, clicks, bounces, unsubscribes, and conversions all post to the same campaign dashboard as the mail piece and the landing page metrics. Per-recipient attribution ties email engagement back to the originating record, the originating drop, and any downstream landing-page conversion or revenue. The "did this campaign work" question gets a unified answer — not a per-channel one that requires manual reconciliation.
Send a coordinated email + mail campaign on a sample list.
Bring 100 records. We’ll build the variable email, schedule the USPS-scan-triggered send, and walk through the inbox preview and deliverability checks — in 30 minutes.