Introduction to the Notification Flow Triggers and Filters
Overview
In this article, we explore the definitions of various notification flows and conditional split and trigger split filters within the AfterShip Tracking's notification flow. These notification flows encompass various stages of customer engagement, from email interactions to cart behavior and shopping activities. Understanding these flows and events is vital for timely communication and actions. Additionally, we delve into conditional split filters, which enable businesses to segment customers based on specific conditions, such as cart value, order history, and demographic attributes.
What you'll learn
In this tutorial, we'll discuss:
- Notification flows and their definitions
- Conditional split filters and definitions
- Trigger split filters and definitions
Notification flows and their definitions
The table below provides a comprehensive overview of various notification flows and flow logic elements involved in managing shipments and orders effectively.
Feature name | Sub feature name | Definition | Who can access it? |
|---|---|---|---|
Shipment status flow trigger | Info received | A trigger event related to receiving information about the shipment status. | All users |
| In transit | A trigger event indicating that the shipment is currently in transit. | All users |
| Out for delivery | A trigger event denoting that the shipment is out for delivery to the recipient. | All users |
| Available for pick up | A trigger event indicating that the shipment is ready and available for the recipient to pick up. | All users |
| Delivered | A trigger event confirming the successful delivery of the shipment. | All users |
| Exception | A trigger event indicating an exceptional circumstance or issue with the shipment. | All users |
| Failed attempt | A trigger event indicating a failed attempt to deliver the shipment. | All users |
Split order summary | All split order shipments delivered | A trigger that all shipments associated with a split order have been delivered. | Commerce API, eCommerce platform, order CSV |
Pre-shipment status flow trigger | Order fulfilled/partially fulfilled/unfufilled | A trigger event based on the fulfillment status of an order. | Commerce API, eCommerce platform, order CSV |
| Order placed | A trigger event indicating that the order is received but not yet processed. | Commerce API, eCommerce platform, order CSV |
| Order cancelled | A trigger event indicating that the order is cancelled. | Commerce API, eCommerce platform, order CSV |
| Processing | A trigger event indicating that the order is being processed. | Commerce API |
| Custom status | A trigger event that that order is updated to the custom status. | Commerce API |
In-store pickup status flow trigger | Order placed | A trigger event indicating that the in-store pickup order is received. | Shopify, Commerce API |
| Order processing | A trigger event indicating that the in-store pickup order is being prepared for pickup. | Commerce API |
| Order ready for pickup | A trigger event indicating that the in-store pickup order is ready to be picked up from the pickup location. | Shopify, Commerce API |
| Order picked up | A trigger event indicating that the in-store pickup order is picked up from the pickup location. | Shopify, Commerce API |
| Order cancelled | A trigger event that the in-store pickup order is cancelled. | Shopify, Commerce API |
| Custom status | A trigger event that the in-store pickup order is updated to the custom status. | Commerce API |
Estimated delivery date flow trigger | Estimated delivery date revised | A trigger event indicating a revision or update to the estimated delivery date of an order. | All users |
| Estimated delivery date missed | A trigger event signifying that the estimated delivery date for an order has passed. | All users |
Trigger frequency | Shipments can never re-trigger this flow after [For shipment status trigger] | When a shipment has already been processed within a specific shipment status update flow, it will be excluded from any further triggering or reprocessing. For example, if a shipment has triggered a transit notification once in the flow, it won't be retriggered to avoid redundancy. | All users |
| Order fulfillment can never re-trigger this flow after [Not applicable to order placed and cancelled triggers] | Similarly, this feature enables skipping or bypassing the fulfillment process for orders that have already been fulfilled within the flow. It ensures that orders that have already undergone fulfillment don't go through the fulfillment process again, preventing redundant actions and unnecessary handling of already fulfilled orders. | All users |
Flow running logic | Conditonal split | A logical branch within a flow where actions are taken based on specific conditions depending on customer's historical behaviors or customer attributes | All users |
| Flow filter | Flow filter and conditional split are similar in that they both utilize customer historical behaviors or attributes. The key distinction is that flow filter acts as a global filter applied to the entire flow, checking conditions before each step. Customers must meet these filter conditions to progress through the flow. | All users |
| Trigger split | A logical branch within a flow that splits based on specific trigger events or conditions depending on the values or parameters associated with the triggering event. | All users |
| Trigger filter | Trigger filter and trigger split share similarities as they both utilize the parameters of a trigger's event. However, the key distinction lies in their roles: while trigger split determines how the flow branches based on the event's parameters, trigger filter specifically determines which event triggers the flow to start or proceed. | All users |
| Random split | A random selection or branching within a flow that distributes recipients randomly among 2 paths. | All users |
Flow running timing | Time delay | A specified delay or waiting period within a flow before executing the next action or step. | All users |
| Trigger status unchanged | A condition within a flow that checks if the trigger status remains unchanged before proceeding to the next step. | All users |
Flow actions | Send email to customer | The action of sending an email to the customer as part of an automated flow. | All users |
| Send SMS to customer | The action of sending an SMS text message to the customer as part of an automated flow. | All users |
| Send email to org member | The action of sending an email to an organization member as part of an automated flow. | All users |
| Send SMS to org member | The action of sending an SMS text message to an organization member as part of an automated flow. | All users |
Conditional split filters and definitions
The table below provides an insightful overview of various customer behavior and attributes tracked within the AfterShip platform. From campaign interactions to shopping behavior and customer attributes, this comprehensive list offers valuable insights into customer engagement, preferences, and demographics.
Category | Filter | Definition | Who can access it? |
|---|---|---|---|
Campaign behavior | Interacted with emails - Number of emails received | Total count of emails received by customers from AfterShip, including tracking notifications via our tracking app and marketing emails sent via our Automizely Marketing app. | All users |
| Interacted with emails - Number of emails opened | Number of emails that customers have opened among those sent from AfterShip, including tracking notifications and marketing emails sent via our Automizely Marketing app. | All users |
| Interacted with emails - Number of emails clicked | Number of emails that customers have clicked on among those sent from AfterShip, including tracking notifications via our tracking app and marketing emails sent via our Automizely Marketing app. | All users |
| Interacted with emails - Did not receive any emails | Customers who have not received any emails sent from AfterShip, including tracking notifications via our tracking app and marketing emails sent via our Automizely Marketing app. | All users |
| Interacted with emails - Did not click any emails | Customers who have not clicked on any emails sent from AfterShip, including tracking notifications via our tracking app and marketing emails sent via our Automizely Marketing app. | All users |
| Have not entered the flow | Customers who have not yet been triggered or initiated any specific tracking, order, or EDD (Estimated Delivery Date) flow within the system. | All users |
Cart Behavior | Current cart value | Current value (total price) of items in a customer's shopping cart on the website. | Shopify users |
| Current number of cart items | Current count of items in a customer's shopping cart on the website. | Shopify users |
| Products in cart | Specific products currently present in a customer's shopping cart. | Shopify users |
| Products viewed | Products that a customer has viewed in their browsing session [only logged-in users will be tracked.] | Shopify users |
Shopping Behavior | Total spent (in last 30d) | Total amount spent by a customer within the last 30 days. | Shopify users |
| Avg. order value | Average value of all orders placed by a customer. | Shopify users |
| Number of recent orders | Number of orders placed by a customer within a recent timeframe. | Shopify users |
| Total orders with coupon | Total number of orders made by a customer using a coupon. | Shopify users |
| Total orders without coupon | Total number of orders made by a customer without using a coupon. | Shopify users |
| First order date | Date when a customer placed their first order. | Shopify users |
| Last order date | Most recent date when a customer placed an order. | Shopify users |
| Purchased products | Specific products that a customer has purchased. Please note that for the | Shopify users |
Customer Attributes | Country/region | Customer's country/region. | Shopify users |
| Email address | Customer's email address. | All users |
| Shopify tag | Tags assigned to customers in the Shopify platform. | Shopify users |
| Email marketing subscription | Identification of customers who have opted in or out of email marketing communications. | Shopify users |
| Email marketing suppression | Identifications of customers that are excluded from receiving marketing emails. These customers are identified based on their suppression status like hard bounced, soft bounced, marked email as spam, and not suppressed. | Shopify users |
|
| Soft bounced: It indicates that the email could not be delivered due to a temporary issue. |
|
|
| Hard bounced: It indicates that the email cannot be delivered to the recipient due to reasons such as invalid email address, domain name issues, or blocked emails. |
|
|
| Marked as spam: It indicates that the recipient has marked the sender email as spam (or junk) or it has gone straight to recipient's spam inbox. |
|
|
| Not suppressed: It indicates that an email address is not on a suppression list, meaning it is eligible to receive emails. |
|
| SMS marketing subscription | Identification of customers who have subscribed or unsubscribed from SMS marketing communications. | Shopify users |
| SMS marketing suppression | Identifications of customers that are excluded from receiving marketing SMS marketing communications. These customers are identified based on their suppression status like bounced and not suppressed. | Shopify users |
| Customer created date | Date when a customer's account was created. | Shopify users |
Trigger split filters and definitions
The table below provides an insightful overview of various shipment, carrier, and order information tracked within the AfterShip platform.
Trigger category | Filter | Definition | Who can access it? |
|---|---|---|---|
Split order, Pre-shipment status & In-store pickup status | Products in order | Specific products included in a customer's order. | Commerce API, eCommerce platform |
| Order value | The total value of the order placed by customer. | Commerce API, eCommerce platform, order CSV |
| Order status | The current state of the order throughout its journey (e.g., open, closed, and cancelled). | Commerce API, eCommerce platform, order CSV |
| Destination country/region | The geographical location where the order is intended to be shipped. | Commerce API, eCommerce platform, order CSV |
| Source | The eCommerce platform or channel through which the order was imported to AfterShip. | Commerce API, eCommerce platform, order CSV |
| Order number | A unique identifier assigned to each order. | Commerce API, eCommerce platform, order CSV |
| Order ID | A unique identifier assigned to a specific order placed by a customer | Commerce API, eCommerce platform, order CSV |
| Product type | The category or type of products purchased by customer. | Commerce API, eCommerce platform |
| Shopify order tags | Tags or labels assigned to orders in Shopify to categorize or identify them based on certain criteria. | Shopify users |
Shipment status & Estimated delivery date | Sub status | The current sub-status of the shipment. | All users |
| Origin country/region | The sender's country/region that the shipment is shipping from. | All users |
| Destination country/region | The recipient's country/region that the shipment is shipping to. | All users |
| Source | The channel through which the shipment was imported to AfterShip. | All users |
| Transit time | Total transit time of the shipment in days For delivered shipments: Transit time (in days) = Delivered date - Pick-up date For undelivered shipments: Transit time (in days) = Current date - Pick-up date | All users |
| Custom fields | The customized data field you add in shipments to display additional information that is not covered by standard fields. | All users |
| Estimated delivery date | The projected date on which a shipment is expected to arrive at its destination. | All users |
| Shipment tag | A label or identifier that can be assigned to a shipment to categorize or mark it for specific handling or processing. | All users |
| Products in shipment | Specific products included in the shipment. | Commerce API, eCommerce platform, order CSV |
| Slug | AfterShip's unique code of courier. Please refer to https://track.aftership.com/couriers/download. | All users |
| Carrier service type | The type of shipping service provided by the carrier. | All users |
| Order number | A unique identifier for the order that the shipment is associated with. | Commerce API, eCommerce platform, order CSV |
| Order ID | A unique identifier assigned to a specific order placed by a customer | Commerce API, eCommerce platform, order CSV |
| Shopify order tags | Tags or labels assigned to orders in Shopify to categorize or identify them based on certain criteria that the shipment is associated with. | Shopify users |
Shipment status | Order contains multiple shipments | The order is shipped by multiple shipments, which the shipment belongs to. | Commerce API, eCommerce platform, order CSV |
| Package was damaged | The package is marked as damaged | All users |
| Package was lost | The package is marked as lost | All users |
| Package was returned to sender | The package is marked as returned to sender | All users |
Estimated delivery date | Latest shipment status | The current status of the shipment | All users |
Updated on: 20/02/2025