1. Home
  2. Support
  3. Postalytics User Guides & Documentation
  4. Direct Mail Campaigns
  5. Delivery And Response Status Codes

Delivery And Response Status Codes

Postalytics Delivery and Response Status Codes - Zapier

The Postalytics Delivery and Response Status Codes capture information from the USPS Intelligent Mail Barcode system (for delivery) and the pURLs that you can include in your direct mail pieces (for response). Their designed to give near real time (delivery) and real time (response) data to marketers, salespeople, CRM’s and Marketing Automation tools for use in a variety of ways.

What Are The Postalytics Delivery And Response Status Codes?

In Transit – The mailpiece is being processed at the entry/origin facility.

In Local Area – The mailpiece is being processed at the destination facility.

Processed for Delivery – The mailpiece has been greenlit for delivery at the recipient’s nearest postal facility. The mailpiece should reach the mailbox within 1 to 2 business days of this scan event. Our experience is that the majority of deliveries occur within 1 day of this scan.

**Note** Use this status code to trigger other actions based on mail delivery. For example, you can use the Processed For Delivery event, with a 2 day “Wait” in an automation sequence, to send automated messages out to coincide with mail delivery.

Re-routed – The mailpiece is re-routed due to recipient change of address, address errors, or USPS relabeling of barcode/ID tag area.

Returned to Sender – The mailpiece is being returned to sender due to barcode, ID tag area, or address errors.

pURL Opened – the recipient has visited their pURL. Each visit will trigger a new event.

pURL Completed – the recipient has visited their Goal URL. Each visit will trigger a new event.

None – a general error that occured

Error – the mailpiece is not created due to an error, such as invalid data (a non existent state code, for example).

When and Where do the Postalytics Delivery and Response Status Codes appear?

Postalytics automatically creates status codes for each recipient of mail when a campaign is created. These are available to be viewed or exported in the Campaign Dashboard of each Smart Send or Triggered Drip Campaign. When you use a Integration (such as HubSpot, Zapier or Salesforce) , Postalytics will create a custom field in the Integration source (such as HubSpot or Salesforce or a Zapier Trigger) for the campaign that then keeps track of all status updates.

Each Postalytics Campaign (Smart Send or Triggered Drip) is assigned a unique Mail Drop Number, like “Postalytics Mail Drop 110“. When you use an integration, this is the name of the custom field that gets created. This will be the field that will track the delivery and response status for the length of the campaign.

Common Postalytics Status Code Use Cases

Postalytics delivery and response status codes and your CRM or Marketing Automation Tools can be easily used together to automate many tasks that have traditionally been too hard, time consuming or expensive to attempt with traditional direct mail technology. Typically, these automation tasks involve Workflow features of your CRM or Automation tool. Some typical things that marketers focus on include:

  1. Sending an email to a mail recipient based on the timing of the mail delivery
  2. Triggering the next step in a workflow
  3. Sending a text message to a sales rep when a mail recipient completes their online goal URL

Here’s an example of a Status code being used in a HubSpot Workflow. The status codes work the same for all Integrations.

 

Tags , ,

Was this article helpful to you? Yes No

How can we help?