Crescender Lab
Created Aug 24, 2023Tutorials|Customer Journey ✨ New ✨
#
💁🏻♀️ Advantages
Enhance interaction and conversion for various marketing scenarios, cultivate audience loyalty, and create unique journey experiences to enhance personal and customized experiences.
Save your valuable work time, let your brand communicate automatically with the audience effortlessly.
The upgraded customer journey not only adds more conditions for contact behavior triggers on the website, including browsing web pages and adding products to the shopping cart but also adds branch conditions and more diverse node condition settings, making brand automated communication and customized experiences closer to the use of marketing scenarios!
💡Reminder:
The Customer journey has increased the diversity of trigger conditions. In order to provide contacts with a better journey experience, we have adjusted the maximum number of ongoing journey to 350 sets.
A maximum of 30 nodes can be set for a single automatic journey, including the ending Exit node.
#
➤ Plan Availability
All MAAC Plans
If you want to use GA events (web tracking behavior) to trigger auto journeys, you must be a user of the e-commerce plan and have completed GA integration.
#
▶︎ Setting Steps
💡 Reminder: Tracked behaviors will only begin to be monitored once the journey starts.
💡 Reminder:
Using tags as trigger conditions - To prevent contacts from triggering journeys repeatedly, tag trigger conditions will currently trigger only once within an hour. For example, if a friend triggers an automated journey at 12:00, and the brand adds tags to the friend again using "Bulk Add Tags" at 12:59, the friend will not trigger the automated journey.
Using GA data events as trigger conditions - each contact will only be triggered once within 24 hours.
Trigger Condition - Tag Added
When a contact is tagged a specific tag. Brands can choose from MAAC or CAAC tags.
*Only can choose 1 tag once*

Yes/No Branch - You can add "yes/no" branch conditions and then use tags and web tracking behavior to set the journey path.
Time Delay - You can design whether to wait for a specified time in minutes, hours, days, or weeks.
Scheduling time - you can design the sending time in minutes, hours, days, and weeks
Send LINE message - You can use the editor to design the message content to be sent.

Please note: If the journey is already activated, adding or reducing nodes will not be allowed to prevent unknown or unclear journey conditions. We recommend using a copy to make additions or reductions in settings.
Branch conditions - tags
Can choose to determine based on having specific / not having specific tags or having any / not having any tags.
Can choose from MAAC tags or CAAC tags.

Can choose to determine based on having previously viewed specific / not previously viewed specific pages or having previously viewed any / not previously viewed any pages, and select behavior for how many times, how many seconds each time, and within a specified number of days in the past.

💡 Reminder: Due to the current delay of 24-48 hours in data transmission within GA4 itself, it is recommended that you use GA event data, including shopping, webpage browsing, and adding to the shopping cart, with a data range of at least 1 day or more.
[GA4 Data Delay Statistics] According to our data engineers' research and testing, the detailed investigation data range is referenced below, providing you with a reference for setting up automatic journey wait times:
Within 24 hours, 80% of the data will be delivered.
Within 30 hours, 90% of the data will be delivered.
Within 36 hours, 98% of the data will be delivered.