USPS Scan Trigger

A USPS Scan Trigger is a workflow that fires a marketing action the moment USPS scans a piece of mail at a defined point in transit. The mail piece carries an Intelligent Mail Barcode with a unique serial number per piece. USPS sortation infrastructure scans the barcode at every facility the piece passes through and exposes those scans through the Informed Visibility feed within hours, sometimes minutes. A scan trigger listens for a specific scan event — usually the destination-facility scan that means the piece is hours away from the recipient’s mailbox — and uses it as the trigger to fire a follow-up: an email, an SMS, a Meta custom audience refresh, a CRM record update. The mailing becomes a synchronized event across channels rather than a one-off send and hope.

Where this came from

The mechanical infrastructure has been in place since USPS launched Informed Visibility in 2018, which exposed the IMb scan stream to mailers as an API feed. What the API made possible — turning a scan event into a real-time marketing action — took the industry a few years to build operationally. DirectMail.io built our scan-trigger workflow as a signature feature of the platform; today it is the most direct demonstration of why mail and email belong on the same platform rather than in separate vendor stacks. The pattern is increasingly standard across modern direct mail platforms, but the implementations differ substantially in how fast they react and how reliable the trigger fires are.

How it actually works

Every piece on a drop is encoded with an IMb that includes a globally unique serial number tied back to the recipient record on the source list. The drop tenders to USPS through whatever postage strategy is appropriate — Local Entry, Dropship, or co-mingle. As USPS sortation processes the pieces, scans flow back through Informed Visibility into the platform, each scan tagged with the piece’s serial number, the timestamp, and the facility code that performed the scan. The platform reconciles each scan to the originating piece and the recipient, then evaluates whether that scan matches a configured trigger condition.

The most common trigger condition is the destination delivery unit (DDU) scan — the scan that happens at the local post office that will deliver the piece, typically 4 to 24 hours before the carrier walks it to the box. When that scan fires, the platform’s automation engine kicks off the configured follow-up: send the recipient an email referencing the mail piece, push them into a Meta retargeting audience, fire a webhook into the brand’s CRM, or any combination. The recipient experiences the mail piece, the email, and the digital ad as a single synchronized moment. Response rates on synchronized sends substantially outperform either channel alone.

What goes in, what comes out

Input: a recipient list with email or other digital identifiers attached, a mail piece with a properly encoded IMb tied back to the list, and a configured trigger workflow defining the scan event and the follow-up actions. Output: a real-time stream of triggered events firing as scans land, with full attribution from the scan back to the recipient back to the originating campaign. The platform records which pieces fired which triggers, when, and what each triggered action returned.

Common pitfalls

The first pitfall is firing on the wrong scan. The IMb scan stream includes scans from every facility a piece passes through — origin, transit, destination — and the trigger that fires when the piece is still in network transit lands the email three or four days before the mail piece does, which destroys the synchronization the workflow exists to create. The right scan is almost always the destination delivery unit scan, sometimes the destination sectional center scan for time-critical sends. The second pitfall is missing email or digital identifiers on the source list. The trigger workflow needs to know who to send the follow-up to; a list with the recipient’s mailing address but no email or phone number can’t fire anything beyond a CRM update. Email appends on the source list at ingest is how serious shops solve this. The third pitfall is over-triggering: firing email, SMS, and three different audience updates off the same scan creates a coordinated barrage the recipient experiences as spam.

How DirectMail.io runs it

DirectMail.io ingests the Informed Visibility scan stream in near-real-time, reconciles each scan to the originating piece and recipient, and evaluates configured triggers as scans land. Email follow-ups go through the platform’s email engine; SMS through the SMS engine; audience updates through the Meta and Google custom-audience integrations. Everything is one platform — one login, one campaign record, one attribution model — which is why the trigger fires reliably instead of breaking at vendor boundaries. The USPS Scan Trigger feature page covers the operational mechanics; the step-by-step walkthrough covers a complete email workflow.

When to use this

• On any drop where the recipient has both a mailing address and an email or phone number. The synchronized send substantially outperforms the mail piece alone.
• For high-consideration offers. Refinancing, vehicle equity, healthcare enrollment, fundraising appeals — offers where the recipient needs multiple touches to convert benefit most from the synchronization.
• For event-driven sends. New-mover, post-purchase, post-event — any campaign where landing the mail and the email together amplifies the moment the campaign is built around.