Triggers
Triggers start it all. These are entry points or conditions that set the context of the journey, helping you narrow down the target audience.

Event-triggered

Event-triggered journeys are based on a specific event (e.g., sign_up, purchase, etc.) and it triggers a series of messages that are spread out over time (days, weeks, etc.).
Example event-triggered journeys:
  • Welcome series for a new user
  • Onboarding customers
  • Abandoned browse/search/cart follow-up emails
  • Post Purchase up-sell/cross-sell
  • Add To Wishlist/Registry follow-ups

Trigger Settings

Create multi-step, multi-channel journeys with complex conditional filters for events.

Frequency

Frequency defines how often a user should be allowed to enter each Journey.
If the frequency is set, users can re-enter at fixed intervals (e.g., every week) or when they re-match the trigger conditions and qualify for re-entry.
By default, event-triggered journeys will send each time the event is received. We do, however, ask if you want to set a limit here:
Choosing yes means that you can limit how many times people can move through journeys. If you do so, you will have two options:
Once: people will only receive the journey the first time they perform the event. For example, if you’d like to congratulate someone the first time they complete a lesson in your eLearning app, you can use this setting. This way, you’ll ensure they don’t receive the email again once they’re a seasoned student and flying through lessons regularly.
Once within a time period: people will only receive the journey once within a time period of your choosing. For example, you want to send an email to someone when they receive notifications in your app. You only want them to receive the email once a day, regardless of how many application notifications they receive. Setting Frequency to “at most once within 24 hours” will ensure that, no matter how many new notifications people get, they will only get an email once.

Examples

Welcome series

A welcome series allows you to introduce your brand to your subscribers. It creates trust and helps you establish a relationship with your customer.
Here's an example of a multi-channel, multi-series welcome email that uses our advanced filtering and branching capabilities.
Step 1: Identify the event that would trigger the journey
Step 2: Create multi-channel journeys
Using Intempt's event filter capabilities, we can reach users based on their behavior. You can also send a follow-up to users if they have not made a purchase 7 days after they first signed_up.

Abandoned Cart

A cart abandonment occurs when a user/visitor adds item(s) to their cart, but does not follow through on the purchase. The overall intent here is to bring them back to your site to finish the purchase.

Messaging

If you would like to control the number of abandoned carts per day, you can honor the messaging limits and/or set this up as a segment-triggered journey.
Step 1: Select the Add_to_cart event to trigger the journey.
Step 2: Create the first trigger in the abandon cart flow. In this scenario, we are targeting users who added an item to the cart but haven't made a purchase in the past two hours.
Step 3: Create additional triggers in the abandon cart flow. For this example, we are splitting the audience into two groups based on their interaction and purchase activity.

Segment-triggered

Segment-triggered journeys are based on users entering a segment with multiple conditions (events, attributes, etc.). An action is sent to the existing users in segment once a journey is launched, and thereafter all new users entering the segment are sent a message.
Important: For segment-triggered journeys, the user always has to be a part of the sending segment to qualify.

Examples

  • Customer reactivation
  • Time to repurchase or replenishment emails
  • Catalog driven changes
  • Birthday reminder
  • Loyalty rewards and promotions

Trigger settings

Frequency defines how often a user should be allowed to enter each Journey.
If the frequency is set, users can re-enter at fixed intervals (e.g., every week) or when they re-match the trigger conditions and qualify for re-entry.
By default, people will enter segment journeys once. We do, however, ask if you want to allow them to enter multiple times:
Choosing yes means that people can move through the journey multiple times. There are two different ways the journey can recur:

Every segment re-enter:

Users must stop matching the trigger and filter conditions in order to match again. For example, if you’d like a customer to get a nudge if they’ve been inactive for two weeks, the trigger condition would be a segment that catches people who have not logged into your app for two weeks. When people enter that segment, they’re sent a message by your journey. If this journey is set to re-enter, they will have to exit and then re-enter that segment (become active, then become inactive again) in order to trigger the journey again.

Examples

Reactivation

Retaining a customer is more cost-effective than acquiring a new customer as that customer will already have a relationship and a trust level with your brand, company or product.
In the example below, we are targeting users who purchased previously, but have not visited the site recently.
Step 1: Create a Winback segment
Step 2: Create an email template so you can send specific content based on gender or other user attributes. For example, Top Selling Items in Male/Female, Latest Items in User's Preferred Categories with promo code, etc.
Step 3: You can also choose to follow up with these customers after a few days if they haven't responded to your journey.

Catalog Driven Changes

Intempt has the ability to auto-generate and trigger smart notifications (email or push) such as price drop, back in stock alerts, etc. Our platform uses a combination of user's metadata, browsing behavior and catalog/content changes to trigger these notifications. Here are some examples and please contact our Success team to explore these and other custom use cases.

1 - Price Drop

When – The price of item changes within X days (we recommend at least 7 days) Who to target – All users who have viewed but have not purchased (can also base it off other events)
Data Needed - Product catalog with price information

2 - Back In Stock

When – The product they viewed in the last 7 days in is back in stock Who to target – All users who have viewed an out of stock item
Data Needed - Product catalog with availability (in stock or out of stock) or dates (start and end)