Overview
This article mainly introduces the types of triggers applicable to SHOPLINE, when they will be triggered, and what kind of application scenarios they satisfy.
Essential to know
The following feature intro is only applicable to stores with an Admin link as "shoplineapp.com".
Before delving into the following content, it's advisable to get to know the concepts such as triggers, exit conditions, trigger frequency, etc., in an automated process. Please refer to Marketing Automation Overview for more details.
This article will cover the following
● Trigger on customer subscription
● Trigger on member registration
● Trigger on adding product to cart
● Trigger on entering checkout page
● Trigger on viewing product details page
● Trigger on viewing product category page
Trigger on order creation
Triggered shortly after order creation, i.e. when the order status shows "Processing."
What are the filtering conditions for this trigger?
1. Order amount
2. Product name (based on the product name comparison in the order)
3. Order source: There are three options, as shown below.
a. Online store (including admin, shop, sc, mc. sc_manual_order, and post)
b. Retail store (including SmartOMO and POS)
c. Others (openapi and import)
For a detailed understanding of all order sources on SHOPLINE, you can refer to this article.
Exit conditions
Number of orders within a certain period (view the range of orders generated by a specific user within a specific time).
1. Time: a. As of the beginning of the process (trigger time) b. The last N days (N ranging from 1-30 days, following the store's time zone).
2. Operation: Equal to, Not equal to, Greater than or equal to, Less than or equal to.
Recipient
The email/ phone number of the customers from the orders obtained.
Trigger on order completion
Triggers shortly after order completion, i.e. when the order status shows "Completed."
What are the filtering conditions for this trigger?
1. Order amount.
2. Product name (based on the product name comparison in the order).
3. Order source: There are three options, as shown below.
Exit conditions
1. Number of orders within a certain period (same as above).
2. Completed order reviews (checks if the triggered order has a completed order review).
Recipient
The email/ phone number of the customers from the orders obtained.
Trigger on customer subscription
Tigger will take place in the following scenarios:
1. Triggers when the subscription box is selected in the member center.
2. Triggers when the "I agree to receive" option is selected during the order placement process.
3. When importing a list into the store, if column I is filled with "Y" indicating acceptance of promotional campaigns, and simultaneously the email is filled in column B or the phone number is filled in columns C and D, it is considered a successful subscription and will trigger the process (please refer to the import list document for details).
What are the filtering conditions for this trigger?
Subscription types: There are two options - Email and SMS.
Trigger for receiving email or SMS subscriptions periodically.
Exit conditions
1. Number of orders within a certain period (same as above).
2. Completed order reviews (checks if the triggered order has a completed order review).
Recipient
The email/ phone number provided by the customer during the subscription.
Trigger on member registration
Tigger will take place in the following scenarios:
1. Triggers when a customer signs up as a member in the store.
2. Triggers when the "Create an account" option is selected during the order placement process.
3. When importing a list into the store, if column H is filled with "Y," it signifies that the user is a member, and thus will trigger the process ( please refer to the import list document for details).
Exit conditions
1. Number of orders within a certain period (same as above).
2. Completed subscription (checks if the user has made a subscription, either via email or SMS).
3. Claiming Member Profile Completion Reward (checks if the user has claimed any Member Profile Completion Rewards).
Recipient
The email/ phone number provided by the user during member registration.
Trigger on adding product to cart
Triggers when a logged-in user adds a product to the cart (the shopping cart here specifically refers to the cart in the store and does not include features like live shopping).
What are the filtering conditions for this trigger?
Shopping cart total amount
The control target of trigger frequency
For each new product added by a logged-in user, a process is triggered. To avoid frequent email notifications that may disturb customers, it is advisable to configure the trigger frequency.
View the introduction of trigger frequency >>
Exit conditions
1. Order generated from the shopping cart (i.e. exits the process when there is an order created from the current cart).
2. Entering the checkout page from the shopping cart (i.e. exits the process when the products in the current cart are submitted to the checkout page).
Recipient
The email/ phone number used to inquire about the subscription of logged-in users
Trigger on entering checkout page
For a logged-in user, the trigger occurs upon entering the checkout page. There is an expected maximum delay of 10 minutes, meaning the process will not be triggered shortly after the customer enters the checkout page but can have a delay of up to 10 minutes (applicable only to entering the checkout page in one-page stores and regular stores, excluding live shopping).
What are the filtering conditions for this trigger?
Checkout page total amount
The control target of trigger frequency
For a logged-in user, a process is triggered each time a new product is added. To avoid frequent email notifications that may disturb customers, it is advisable to configure the trigger frequency.
View the introduction of trigger frequency >>
Exit conditions
1. Order creation (i.e. when an order is created upon entering the checkout page).
Recipient
The email/ phone number used to inquire about the subscription of logged-in users.
Trigger on viewing product details page
For a logged-in user, the trigger occurs upon entering any product details page and accumulating more than 5 views. There is an expected maximum delay of 1 hour, meaning the process will not be triggered shortly after the customer views the product details page but can have a delay of up to 1 hour (applicable only to viewing regular stores but excluding live shopping).
What are the filtering conditions for this trigger?
Product name
The control target of trigger frequency
For a logged-in user, a process is triggered each time a new product is added. To avoid frequent email notifications that may disturb customers, it is advisable to configure the trigger frequency.
View the introfuction of trigger frequency >>
Exit conditions
1. The number of orders within a certain period.
Recipient
The email/ phone number used to inquire about the subscription of logged-in users.
Trigger on viewing product category page
For a logged-in user, the trigger occurs upon viewing any product category page and accumulating more than 5 views. There is an expected max delay of 1 hour, meaning the process will not be triggered shortly after the customer views the product category page but can have a delay of up to 1 hour (applicable only to viewing regular stores but excluding live shopping).
What are the filtering conditions for this trigger?
Product category name
The control target of trigger frequency
For a logged-in user, a process is triggered each time a new product is added. To avoid frequent email notifications that may disturb customers, it is advisable to configure the trigger frequency.
View the concept of trigger frequency >>
Exit conditions
1. The number of orders within a certain period.
Recipient
The email/ phone number used to inquire about the subscription of logged-in users.
Other suggestions
The 'AND' and 'OR' logic of filtering conditions
1. Product name
a. When setting the product name, selecting "equal to" / "including" indicates that if any product in the order meets the conditions, the criteria are satisfied. Choosing "not equal to" / "not including" indicates that all products in the order must meet the conditions for the criteria to be satisfied.
When using the order creation and order completion triggers to send content, you can leverage the following two teniques to meet application scenarios.
1. Use the order information block to capture the order details. See how to use the order information block >> (Example scenarios: When you wish to send order notifications to customers, you can add this block to the email content. The automated process will automatically include order information in the block when sending).
2. Use the order URL to redirect to the Order Details page. See how to use the [[orderUrl]] variable >> (Example scenarios: When you want to direct customers to the Order Details page, you can include this variable in clickable blocks/ buttons in emails or SMS messages. The automated process will automatically include the link to the Order Details page corresponding to that order when sending).
To learn more about automated process configurations, check out more info on the automated process.
Comments