Conditionals (if/else) block

• Conditional blocks are like if/else blocks, which can be used to check for conditions within a flow.
• Typical use cases:
  • In the below on the right we are checking whether customer name exists or not for the user.
  • Check for a particular product id / collection id in the flow - Set up specific cross/up/resell on your hero product
  • Split the flow basis certain order/customer tags

Filter block

• Filter block can be used to filter users in a flow basis user properties (ex: their phone number, total orders placed, source etc)
• Typical filters that can be applied are:
  • First order date (old or new customer)
  • Last order date (to check if there is any active order)
  • RFM segments (customer cohorts)
  • Average and total order value
  • New vs. Returning customers (through total order count)
  • Customer city/state
  • Customer tag as defined on BIK or shopify
  • Exact customer id (email/phone)
  • Customer marketing consent on sms/whatsapp/email.

AB Testing

With AB test block, users in the journey can be randomly split between a set of 2 or more paths. The relative weightage / probability of these paths can also be defined.

With the choice of ‘randomise path for every visit’ - there is no hard bound of user id and the path. For retargeting journeys like Abandon cart, we typically recommend no checking this box. If one of the path has discount, then one user always goes in discount or no discount path.

Cancel trigger

• Cancel trigger can be used to stop the execution of any Journey for that user, if a particular event happens.
• So essentially we can set another event as a trigger to cancel the execution of a Journey.
• Brands can setup Cancel triggers, while setting the main configuration for a trigger.
• For example, in the above scenario, currently there is no trigger set to cancel this Journey.
• The main trigger for this Journey is ‘Abandoned cart’.
• We have set ordered event as a cancel trigger for this Journey.
• So now, if an ordered event gets triggered for a particular user, then execution of this Journey for that user, will stop.
• You can also set multiple events as cancel triggers. If any one of them gets triggered during the Journey execution, then the Journey for that user will be canceled.

Trigger frequency

• This feature can be used to set a limit on the number of times a Journey can be triggered for a particular user within a specified duration of time.
• Lets take the example of Abandoned browse journey:
  • Say a user is visiting products (PDP pages) on a web-store.
  • Each PDP page visit will trigger a Product viewed event.
  • This event can be used to set an abandoned browse journey.
  • We can check for an order placed event after 20-30 mins, and if the user has not placed any order we can send him a reminder message with some discount code.
  • But since each product page visit will trigger an event, this might trigger multiple abandoned browse journeys.
  • So we can set a frequency of 1 per hour to limit the execution of multiple journeys of same type for the user. This will protect us from spamming the user.