Our New Campaign Event Zapier Trigger takes advantage of one of the groundbreaking features of ChurchStamp; the ability to track exactly where your mail is in both the USPS first class mailing tracing program, as well as how the recipients of your mail respond online.
ChurchStamp uses status codes or “Events” to:
track the journey through the Postal Service scan events
indicate that a mail recipient has entered their pURL to respond to your offer
trace mail recipients who have reached their “Goal URL” indicating campaign success
What to do with the New Campaign Event Zapier Trigger
ChurchStamp is a direct mail automation tool. Automation can mean many things, but in this context, there are a few use cases that stand out.
The New Campaign Event Zapier Trigger can be used to automate things such as:
Sending an email to a mail recipient based on the timing of the mail delivery
Triggering the next step in an automation process in Planning Center
Sending a text message to a new guest when a mail recipient visits your website
What are the ChurchStamp Campaign Event 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 the barcode/ID tag area.
Returned to Sender – The mailpiece is being returned to the 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.
How to set up the New Campaign Event Zapier Trigger
We’ll walk through the setup of a Zap that uses the New Campaign Event Zapier Trigger to send an email using the Email by Zapier Outbound Email action each time a mailpiece has a change in status.
You’ll need a ChurchStamp account and a campaign set up, along with a Zapier account and a 3rd party app account (in this case, Email by Zapier).
Make a Zap & Select The Trigger
Login (or create) your Zapier account, click “Make a Zap” and select ChurchStamp as the trigger app:
-medium.png)
Select the ChurchStamp Trigger Campaign
Click continue and then choose your ChurchStamp account (login/authenticate if you haven’t done so yet).
Click continue and then choose the ChurchStamp campaign that will be the triggering campaign:
-medium.png)
Choose and configure the Action app
For the purposes of this example, we’ll choose a simple email application for Trigger to initiate.
Search for the “Email by Zapier” app and choose the “Outbound Email” Action:
-medium.png)
This will parse the event from the ChurchStamp workflow campaign and email it to the chosen email addresses.
More advanced uses would be to push this into a CRM as a new status of a custom field. Zapier will do a test at the end and you should get an email similar to the following:
To fully test, go to a ChurchStamp Campaign, select “Edit” from the menu, and then click the “Preview Created Mail” button at the top of the campaign dashboard.
View one of the postcards or letters and choose the pURL generated and type it into a browser to visit it.
This will create a “Campaign Event” that will generate the email.
When your email arrives, you know your New Campaign Event Zapier Trigger is properly configured and is generating the proper Action within the Zap:
