Overview
When customers enter a store for a visit, they usually hope to capture the customer's behavior of browsing pages, browsing products, adding purchases, placing orders, etc. in the store in real time, and when these behaviors occur, push emails or text messages in real time to promote their order placement. Or the goal of a return visit. At this time, automated marketing is a good means.
SmartPush's automated marketing supports rich automation scenarios and simple and easy-to-use process configuration. Automation scenarios include but are not limited to: welcome to subscribe (pushed when customers subscribe on the website), abandoned shopping cart recall (pushed when adding items to the shopping cart), abandoned order recall (pushed when entering the checkout page and judging that the order has not been completed), customer win Reply (pushed after placing an order or when no order is placed for a period of time), etc.
This article will cover the following:
● Necessary understanding of automated process configuration
● The concept and setting method of process start (trigger, trigger filter conditions, exit conditions)
● Differences in triggers on different platforms
● The concept and setting method of process splitting
● The concept and setting method of delay
● The concept and setting method of executing actions
● Data display logic within the process
● Automated data reporting
● Automated templates
Necessary understanding of automated process configuration
1. Nodes included in the automated configuration: triggers, trigger filtering, exit conditions, process splitting, delays, and execution actions.
2. Each automated task to be started contains at least a trigger and an execution action.
3. Automated task status: draft, opened, paused (only started and paused tasks will generate automated data reports)
4. For tasks that have been opened, every time you enter the task details page from the task list, the latest process of publishing it online will be displayed.
Process start (trigger, trigger filter conditions exit conditions)
●Trigger: used to configure different trigger events, which determines what kind of event each automated process will start.
After the trigger data is generated, the sendable object of the trigger object will be queried in real time, usually its email address/mobile phone number. If the email address or mobile phone number is not queried, or the format of the queried email address and mobile phone number is incorrect (for example, the email address is: example @), the sending request is not met, and the trigger will not enter the subsequent process.
●Trigger filter conditions:
○Trigger filter conditions are not required to be configured. If not configured, no filtering will be performed. If configured, only triggers that meet the configuration conditions can enter the subsequent process.
○Each trigger has its own filtering conditions, which can be used to determine whether the process can actually be entered. Example: Take the order creation trigger as an example. The order amount is used as a trigger filter condition, and the order amount is set to be greater than 50. This means: only when the order amount is greater than or equal to 50, the process will be entered. Otherwise, the process will not be entered.
○Up to 3 conditions can be added to each process, and the conditions can have "and" or "or" relationships.
●Exit conditions
The exit condition determines what conditions the user entering the process can exit the process without continuing to send. The timing of judgment is to determine whether the user meets the set exit conditions before each sending action is performed. If the user meets the set exit conditions, it will not continue to push emails/text messages from all subsequent nodes and exit from the process.
Trigger differences on different platforms
! Note: There are differences in the triggers, trigger filters, and exit conditions supported by stores on different platforms. Please click here to view them respectively:
[coming soon] Trigger for all platforms - contact enters group
Applicable to stores whose Admin background link is: shoplienapp.com, go to view the trigger
Applicable to stores with Admin background link: shopify.com, go to view the trigger
Process splitting
By setting process splitting conditions, you can split the process into two branches: "YES" and "NO". If the conditions are met, it will enter "YES". Otherwise, it will enter "NO".
Split conditions:
●Trigger filtering: The same as the filtering conditions in the trigger. The data used is the data generated when triggered.
●Basic attributes of the contact: split based on the attributes of the contact. The usage data is split to query the latest status of the contact in real time when the node is executed. (⚠️Note: If the contact does not exist/the attribute does not exist, it is considered that the conditions are not met and the "NO" branch is entered)
●Recipient behavior: Split based on the recipient's open or click behavior from the previous message.
Basic attributes of a contact include the following fields
|
type |
Field |
Data acquisition source |
comparison operation |
target value |
|
Options |
gender |
Basic attributes of the contact, gender |
equal to, not equal to |
Male, female, unknown |
|
nation |
Countries for all addresses of the contact |
Drop-down country range: All countries covered by all contacts are used as drop-down options, displayed with country names, following language B |
||
|
Custom labels |
Contact tags (main site synchronized tags & SP imported tags), excluding imported batch tags |
Option range: All contacts override to label as drop down option |
||
|
Subscription status |
Get a contact’s real-time subscription status |
Subscribed email address, subscribed mobile phone number |
||
|
membership level |
Only stores whose Admin link is shoplineapp.com have this field |
All levels in the store as drop-down options |
||
|
Verification status |
Only stores whose Admin link is shoplineapp.com have this field |
Verified email, verified mobile phone number |
The "Recipient behavior" conditions include the following setup options：
| Type | Action | Result value |
| Open email | Supports selecting all email tasks upon the node. You need to specify an email task based on the email subject. | Proceed to the next step in the process based on whether the specifed email is opened by the recipient. |
| Click email | Supports selecting all email tasks upon the node. You need to specify an email task based on the email subject. |
URL supports specifying: 1. Any URL, indicating that upon clicking on any URL, customers will proceed to the next step in the process. |
| Click SMS | Supports selecting all SMS tasks upon the node. You need to specify an SMS task based on the email subject. |
⚠️Note: Using recipient behavior judgment requires a delay node in the upstream.
Delay
Delay is configured based on the waiting time between the previous node and the next node, and supports two types of time settings:
●Relative time: Based on the previous node, wait for the set relative time before entering the next node. The maximum number of days that can be entered is 60 days
●Specified time: After the previous node of the delay node is triggered, if the setting of the specified time is not met, it will continue to wait until the set time is reached.
Supports setting daily, weekly, and monthly granularity
Every day: Set the specific time every day
Weekly: Select the day of the week and then the specific time. You can select up to 3 dates. When multiple dates are selected, the trigger will only be triggered on a nearby date, not all triggers (for example: if the previous node of the delayed node is triggered on Tuesday. The set rule is: triggered at 10 o'clock every Wednesday/Thursday , then Wednesday is closer to Tuesday, triggering will occur on Wednesday, and will not trigger again on Thursday)
Monthly: Select the day of each month and then select the specific time. You can select up to 3 dates. When multiple dates are selected, the trigger logic is the same as every week
Execute actions
Supported execution action types: send email, send text message
●Sending emails through automated tasks does not occupy the contact quota of the package, but will consume email/text messages.
●The object sent depends on the trigger, and the objects sent are different for different triggers. You can go to the trigger rule introduction to view the objects to which each trigger is sent ( applicable to stores with Admin backend link: shoplienapp.com, go to view the triggers. Applicable to stores with Admin backend link: shopify.com, go to view triggers)
●Execution actions support copying. Click ":" to generate copied nodes below. You can drag the newly copied nodes to any expected location.
Data display logic within the process
●The data display within the automated process only counts the data of the past 30 days, and data will be generated for the "opened" and "paused" status (to view the accumulated data, you can go to the automated data report, see the description in point "7" for details)
●Once the process starts, the data generated by each node follows the node. If the node is dragged and adjusted, there may be a problem of top-down data funnel misalignment.
Automated data reporting
Location: Each automated task that is turned on will generate a data report. Data Reporting - Automation
The data report contains 3 modules: task information, overview data, and activities in the process
Mission information
Show a preview of the process and other basic information
Number of triggers: After meeting the trigger and filter conditions, the number of triggerable users who enter the process (triggerable means that the sending email address/mobile phone number of the user is found)
Overview data
Real-time display of data generated by each automated task
activities in the process
Display the data of the email/SMS nodes configured in the automation task
Each node supports clicking drill-down to view user details and export them.
Automated templates
Automation process setup is the most critical step in starting your automation journey. In order to simplify your setup process, SmartPush has preset multiple sets of automated processes for you to apply with one click. You only need to make simple modifications based on the actual situation of the store to publish the process.
Enter Automation - Automation Templates to browse all preset automation processes (!! Note: There are differences in the automation templates of different platforms. The actual templates are subject to the display in the system. The following screenshots are for illustration only)
Select the expected automation template and click [Create Automation] to enter the automation process editing page, edit it again, and finally publish it.
Comments