Overview
This article will explore a new type of trigger based on the contact's date attributes. Examples include the contact's birthday, the email subscription date, etc. This is used for triggering events related to birthdays, subscription anniversaries, and the anniversary of becoming a customer. These triggers are for maintaining and enhancing relationships with our customers.
Key takeaway:
- This trigger is applicable to stores with admin URLs which include myshopline.com, shoplineapp.com, and shopify.com.
- For stores with a "myshopline.com" admin URL, this trigger is applicable only to the new editor; the old one currently does not support this trigger.
This article will cover the following:
Trigger logic
Trigger type: Date attribute. The available date fields include: Birthday, Email Subscription Time, SMS Subscription Time, Customer Creation Time.
- For each selectable date field, you can set triggers N hour(s) before, after, or at N o'clock on the day of that date field; the specific time will align with the displayed time zone (the trigger condition is that the corresponding date field of the contact must have a value, for instance, the contact must have a birthday field to be triggered based on the specific birthday).
- Supports trigger repetition, with options for non-repetition, monthly repetition, and annual repetition (commonly used in birthday greeting scenarios).
Monthly repetition
Contacts enter the workflow on the same day every month. If a contact's date happens to fall on a non-existent date in a given month, it will skip that month and not send a repeated message. For example, there are 28 days in February, and when the trigger takes place on the 30th of each month, it will skip the trigger for February.
Annual repetition
Contacts enter the workflow on the same date every year.
Once the trigger conditions are set, the system will automatically collect the corresponding dates of the contacts. Only before, on, or after that date will the contact enter the workflow. This enables automated and personalized triggers for each contact based on their individual date nodes.
Filter conditions
The selectable filtering conditions for this trigger include all the condition types supported by the SmartPush segmentation feature.
Exit conditions
The exit condition supported by this trigger is "the number of orders within a specific period."
Time types: From the start of the workflow until now, The last N days, Cumulative.
Application scenarios
Suppose we want to send a greeting email to a customer one day before their birthday, we can use this trigger with the following setup:
Frequently asked questions
Question 1: If the initially set trigger rule is N days before the birthday, and later the rule is updated to be on the birthday itself, how will the automation rule be triggered for the contacts?
When the date has already reached N days before the corresponding birthday of the contacts, the automation will be triggered N days before the birthdays for those contacts as per the old rule. On the other hand, contacts for whom the date has not yet arrived will be processed as per the new rule.
Example: Suppose today is 5 January 2024, and the automation is set to trigger 3 days before the birthday. For contacts with birthdays on 8 January, they will have entered the workflow and will continue to be triggered according to this rule (3 days before the birthday). Later in the afternoon of 5 January, the rule is changed to triggerring on the birthday. For contacts with birthdays on 6 January and onwards, the automation will be triggered according to the new rule on the birthday. At this point, contacts with a birthday on 8 January will receive emails both 3 days before the birthday and on the birthday because they meet both sets of rules.
To learn more about setting up automated marketing processes, check out Introduction to Automated Marketing >>
Comments