Filters allow you to get specific about which subscribers Postscript includes in an automation series. Not only do filters help ensure the right messages are going to the right people, they can also help you better control overall spend and reduce unsubscribe rates.
Why You Should User Trigger and User Filters
- Refine the intended recipients of your automations to ensure subscribers are having the right experience with your brand.
- Choose from filtering by order or cart contents, user history, or combine both to make a highly unique and specific automation.
Define Trigger Filters
Trigger filters flag subscribers based on data related to the defined automation trigger. You have several different trigger filters available to you, and you can combine multiple trigger filters to help you narrow the intended recipients of your automation. Which filters appear once you enable Trigger Filters will depend on the automation trigger you selected.
Let's walk through some examples:
Say we want to create a unique abandoned cart experience for those subscribers building a high-value shopping cart. To do this, we'll need to define what "high-value" is so Postscript knows which subscribers and checkout experiences to pull into this abandoned cart automation.
- We set our Automation Trigger as Checkout Started. Available filters will be data associated with checkout (e.g., the items in the cart, discounts, the subtotal, the grand total, etc.)
- We add a filter and choose Subtotal Price. That means we're looking at the checkout total before the cost of shipping and taxes.
- We set our refinement filter as Greater Than so Postscript knows to include any checkout with a subtotal amount greater than the one we'll define.
- Why not Greater Than Or Equal To? We could absolutely choose this option if we also wanted to include the subtotal value of exactly $100.00.
- We set our value as $100.00.
What will this look like? Postscript will flag any "Checkout Started" event with a shopping cart subtotal greater than $100.00 as high-value and pull that subscriber into this abandoned cart automation.
Say we want to create a cross-sell automation to suggest a product based on previously purchased items. To do this, we'll need to define which items Postscript should look for in previous orders so those subscribers can be put into this cross-sell automation.
- We set our Automation Trigger as Order Delivered. Available filters will be data associated with the order (e.g., item SKUs, variant IDs, item price, item quantity, etc.)
- We want our specified item to match ANY item included in a previously delivered order.
- Why not ALL? Choosing all would mean that our specified item would need to match every line item in a previously delivered order.
- We want our item title (or product title) to Contain the word "Coat."
- Why not Equals? We have several coats that we sell and we want this automation to consider all of them. The Equals option is better suited for instances where we want to specify a specific item to include, such as "Olive Green Women's Coat."
- We want to join our two filters, Line Item: Coat and Line Item: Scarf, with an OR statement.
- Why not AND? Using AND would limit the number of previous orders that would be included in this automation. Postscript would look for previous orders that include a coat AND a scarf. We want Postscript to look for orders that contain a coat OR a scarf.
What will this look like? Postscript will flag any delivered orders that contained a coat or a scarf and pull that subscriber into this cross-sell automation for winter pom hats.
Define User Filters
Similar to trigger filters, user filters flag subscribers based on data related to the defined automation trigger. The difference here is the automation triggers are user-specific, not order-specific. Rather than Checkout Started or Order Created, user filters appear for Keyword Triggered and Subscriber Created (Popup, Keyword, or API).
You have several different user filters available to you, and you can combine multiple user filters to help you narrow the intended recipients of your automation. Which filters appear once you enable User Filters will depend on the automation trigger you selected.
Let's walk through some examples:
Say we host an end-of-summer giveaway. To enter, individuals simply need to opt-in by texting the keyword ENDOFSUMMER2021 to our short code. Once they do, we want them to be part of a unique welcome series that includes an entry confirmation message and an introduction to our brand.
- We set our Automation Trigger as Keyword Triggered.
- We choose the user filter Keyword Triggered.
- Why not Keyword Most Recently Triggered? Some brands run several promotions or have different keywords in play for campaigns, keyword-triggered conversation flows, etc. Keyword Most Recently Triggered would only look at the last keyword a subscriber texted, but we want to make sure that if a subscriber ever texted in our giveaway keyword, they're included.
- We set our refinement filter as Equals so Postscript knows to only include subscribers who texted in our giveaway keyword.
- We choose our desired keyword, ENDOFSUMMER2021.
Say we want to create a VIP club for customers who have spent over $500 at our store. Once they reach that level, we want them to be part of an automation series that features different products and offers periodic discounts. Or, we could use this automation as a VIP opt-in opportunity—Reply IMAVIP to join our VIP club—and create a Keyword Triggered automation that includes all the good stuff.
- We set our Automation Trigger as Order Delivered. This tells Postscript to consider the total of delivered orders (as opposed to the totals of checkouts started, etc.)
- We choose the user filter Total Spent. This allows us to filter by the overall amount a customer has spent in our store.
- We set our refinement filter as Greater Than or Equal To so Postscript knows to only include subscribers who have hit our specified value or more.
-
How could we use the other options? Say we want to get other customers to that $500+ level. We could send out automations to customers who have spent Less Than $500+ with incentives to help increase the total overall spend. We could even use two filter options to target customers who have spent $100-$499:
- (1) Total Spent greater than or equal to $100
- AND join statement
- (2) Total Spent less than $500.
-
How could we use the other options? Say we want to get other customers to that $500+ level. We could send out automations to customers who have spent Less Than $500+ with incentives to help increase the total overall spend. We could even use two filter options to target customers who have spent $100-$499:
- We define our desired value, $500.
Get Support
Have questions? Please feel free to reach out to our wonderful Support team at support@postscript.io or via live chat. You can also submit a support request here!
Need ongoing channel strategy guidance? Please fill out this form and we'll connect you to one of our certified partners.