November 19, 2026

Omnichannel integrations

How to sync mail delivery events back into your CRM

Let Lob streamline your mail, while you grow your business.

Red lobster holding a purple postcard with a blue stamp and wavy postmark lines.

For more information about how this data is handled, please view our Privacy Policy

You sent the mail. Your direct mail platform says it was delivered. But when a rep pulls up the contact in Salesforce and there's no record of it, the campaign might as well not have happened.

That gap between "we can see delivery status" and "delivery data lives in the CRM" is where attribution falls apart and follow-up timing goes sideways. This guide covers how to get mail delivery events into your CRM using native integrations, webhooks, and middleware – plus how to map events to the right records and trigger workflows when mail lands.

What mail delivery events are and why they belong in your CRM

To sync mail delivery events back into a CRM, you can use native integrations, webhooks, or middleware tools like Zapier. The right approach depends on whether your direct mail platform offers pre-built connectors or requires a custom pipeline. What matters most is pushing USPS scan data into your CRM so the data ties to contact records and becomes available for workflows, rather than sitting in a separate dashboard no one checks.

Mail delivery events are scan-based status updates from USPS. They tell you where a piece of mail is in the postal stream, and they're more specific than a simple "sent" confirmation. You're getting real signals: processed at a sorting facility, scanned at a local post office, flagged as undeliverable.

Without delivery events in your CRM, timing and attribution get messy. A rep might call a prospect before the mailer arrives. A follow-up email might fire three days too early. And the gap between "we sent it" and "they received it" grows wider.

In transit

Mail has entered the postal stream but hasn't reached the destination facility. It confirms movement, though it doesn't tell you when the piece will land.

In local area

The piece is now at the destination post office. Delivery typically happens within one to two days. For sales teams, this is a good signal to start warming up outreach.

Processed for delivery

The carrier has the piece and is heading out. This is the closest you'll get to "in mailbox." If you're timing a follow-up call or email, this is the event to trigger on.

Re-routed

USPS has forwarded the mail due to an address change. Delivery timing shifts, and the event often signals a data quality issue worth flagging in your CRM.

Returned to sender

The mail couldn't be delivered. Use this event for list hygiene: suppress bad addresses and avoid wasting future postage.

Syncing mail delivery events is not the same as tracking them

Teams often assume that because they can see delivery status in their direct mail platform, the data is "in the system." It's not.

  • Tracking: Viewing delivery status in your direct mail platform's dashboard
  • Syncing: Writing delivery events as activities or records inside your CRM, tied to contacts

Disconnected delivery data is a major barrier to CRM effectiveness. If delivery data shows up on the contact timeline and can trigger automation, you're syncing. The difference shows up when a rep wants to know whether a prospect received a mailer before picking up the phone.

What you need before you connect your direct mail platform to your CRM

A few things can trip you up if they're not in place before you start:

  • A direct mail platform that surfaces delivery events: Not all vendors provide real-time USPS scan data. Confirm yours shares delivery events via API or webhooks.
  • A unique identifier in both systems: Typically a send ID, campaign ID, or external reference you pass at send time. This is how you'll match events to the right CRM record.
  • CRM admin access: You'll likely create custom fields, objects, or workflow triggers.
  • A destination for the data: Decide whether events write to a custom object, the activity timeline, or a custom field on the contact record.

Ways to sync mail delivery events to a CRM

There's no single right approach. It depends on your tech stack, team resources, and how much control you want.

MethodBest forTrade-offs
Native CRM integrationsTeams using Salesforce, HubSpot, or Marketo who want fast setupLimited to supported CRMs; less customization
Webhooks and APIsEngineering teams who want full control over data structureRequires development resources to build and maintain
iPaaS and middleware toolsMarketing ops teams without dedicated engineeringAdds another tool to manage; may have volume limits
Manual CSV importsOne-off analysis or backfillsNot real-time; doesn't scale

Native CRM integrations for Salesforce, HubSpot, and Marketo

If your CRM is supported, native integrations are the fastest path. Lob offers pre-built connectors that push delivery events directly into Salesforce, HubSpot, and Marketo without custom code.

Webhooks and APIs

Webhooks push events in real time as they occur. APIs let you pull data on demand. For keeping your CRM current, webhooks are the stronger choice because you receive a POST request each time a delivery event fires.

iPaaS and middleware tools

Tools like Zapier, Workato, or Tray.io can bridge platforms when native integration isn't available. They're useful for marketing ops teams, though you're adding more tools to manage.

Manual CSV imports

Only practical for historical backfills or ad-hoc reporting. Not a real sync, just a snapshot.

How to subscribe to mail delivery webhooks

Step 1. Stand up a webhook endpoint

You'll need a URL that can receive POST requests. A cloud function, your own server, or an iPaaS endpoint all work.

Step 2. Register the endpoint with your direct mail platform

In Lob, you do this in the dashboard under Settings > Webhooks, or via the API. Point it to the URL you created.

Step 3. Select the delivery events you want to receive

Not every event is useful for CRM sync. Focus on processed for delivery, returned to sender, and re-routed. These are the highest-value events for sales and marketing workflows.

Step 4. Verify the subscription with a test mailpiece

Send a test piece and confirm events flow through to your endpoint before connecting to production CRM data. This catches configuration issues early.

What a mail delivery event payload contains

When a webhook fires, you receive a JSON payload with details about the event:

  • Event type: The delivery status (e.g., in_transit, processed_for_delivery, returned_to_sender)
  • Mailpiece ID: Unique identifier for the specific piece of mail
  • Send ID or external reference: The ID you passed at send time to link back to CRM records
  • Timestamp: When the scan occurred
  • Location data: City, state, or zip code of the scan event (when available)

Lob's webhook payloads include all of these fields and can be customized based on what you're tracking.

How to map mail delivery events to the right CRM record

Most teams get stuck in mapping. If mapping isn't set up correctly, events end up orphaned or attached to the wrong contact.

Here are some tips to get it right:

Use the send ID as your join key

When you trigger a send, pass a unique identifier like the CRM contact ID or opportunity ID. This ID comes back in the webhook payload, so you can match it to the right record.

Attach events to contacts, leads, and accounts

Decide your data model upfront. Most teams attach to the contact record. Some also roll up to accounts for account-based marketing (ABM) visibility.

Write events as activities or custom objects

Activities show on the timeline and are visible to reps. Custom objects give you more flexibility for reporting but may require additional configuration.

How to trigger sales and marketing workflows from delivery events

Once events are in your CRM, you can act on them. Here's where the value shows up.

Alert a rep when a mailpiece is delivered

Set a Slack notification or CRM task when a high-value prospect's mail shows "processed for delivery." Reps can time their call for when the piece lands.

Fire a follow-up email after a postcard lands

Trigger an email sequence two to three days after delivery confirmation. Having multiple touchpoint drives higher conversion than single-channel campaigns.

Suppress audiences when mail is returned to sender

Use returned-to-sender events to update contact records and exclude bad addresses from future sends. Lob makes this sync straightforward. Native integrations with Salesforce, HubSpot, and Marketo push delivery events directly, no custom code required. For teams that want more control, webhooks and APIs offer full flexibility.

With real-time delivery tracking and the ability to connect mail performance to downstream conversions, you get visibility into what's actually happening after mail leaves the printer.

Book a demo to see how Lob can help you close the loop between direct mail and your CRM.

Frequently asked questions about syncing mail delivery events to a CRM

FAQs

How often are mail delivery events updated in a CRM after syncing?

Events arrive in real time via webhooks, typically within minutes of the USPS scan. Your CRM reflects the update as soon as the webhook is processed.

Can you sync mail delivery events into HubSpot and Salesforce at the same time?

Yes. If your direct mail platform supports multiple webhook endpoints or native integrations, you can push the same events to both CRMs simultaneously.

Do you need an engineer to set up mail delivery event syncing?

It depends on your method. Native CRM integrations often require no code. Webhooks and APIs typically need engineering involvement to build and maintain the handler.

What is the difference between a scan event and a delivery confirmation?

A scan event is any USPS tracking update, such as "in transit" or "in local area." Delivery confirmation specifically refers to the "processed for delivery" scan, which indicates the carrier is delivering that day.

Answered by:

Image of Sam Melero

Sam Melero