It’s easy to use Postalytics Status Codes in HubSpot to accomplish a wide variety of integration tasks. They’re designed to help marketers, salespeople, CRM’s and Marketing Automation platforms like HubSpot initiate workflows and processes that could never before be done.
Postalytics Status Codes In HubSpot Contacts
Postalytics automatically creates a Custom Property in HubSpot Contacts when either of two things happen:
- You create a Smart Send Campaign using a Contact List that was imported using the HubSpot Integration
- You create a Triggered Drip Campaign and sync the activity back to Hubspot
Each Postalytics Campaign (Smart Send or Triggered Drip) is assigned a unique Mail Drop Number that is created as a Custom Property in HubSpot Contacts, as in “Postalytics Mail Drop 110“. This will be the field that will track the delivery and response status for the length of the campaign. You can modify the name, or Label of the status code in HubSpot Property Settings.
Common Postalytics Status Code Use Cases
Postalytics and HubSpot 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 HubSpot Workflows. Some typical things that marketers focus on include:
- Sending an email to a mail recipient based on the timing of the mail delivery
- Triggering the next step in a workflow
- Sending a text message to a sales rep when a mail recipient completes their online goal URL
It is easy to access the Postalytics Status Codes from within HubSpot Workflows. They appear as a Contact Property, and always begin with “Postalytics”.
What Are The Postalytics Status Codes That Appear In HubSpot?
In Transit – The mailpiece is being processed at the entry/origin facility.
In Local Area – The mailpiece is being processed at the destination facility.
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).