Configure Events and Conditions

Events in a journey are a user event, also known as entry trigger, wherein the customer enters the journey based on any transactional or non-transactional activity (behavioral events). You can further add conditions based on the selected event to define which customers qualify to enter the journey. With the help of user events, brands can include multiple paths within a journey depending on customer activity.

There are two types of user events -

  • Transactional events - This refers to customer activity related to a purchase, transaction, registration, or coupon redeemed which can be used to trigger or personalize customer journeys. When adding a transactional event, the brand must select specific events that define when customers will enter the journey.
  • Behavioral events - This refers to user activities that can be tracked and used to trigger or personalize journeys. These events include both standard events and custom events.
    1. Standard events are predefined and based on common attributes such as price, quantity, productType, cardId, and productName.
    2. Custom events can be created to track specific user actions that are not covered by standard events. For steps to create custom events, refer to the Add and Map Custom Event documentation.

You can also use behavioral events to define conditions, filter your audience, and create different journey paths based on user behavior.

📘

Notes

  • Newly created Behavioral Events (BE) will appear in the Journeys dropdown one day after creation.
  • When configuring a Behavioral Event, make sure to select the “Loyalty” checkbox.

Adding transactional events

To add a transactional event perform the following:

  1. Create a new journey.
  2. On the journey canvas, select Entry Trigger.
  3. Choose User Event as the type of entry trigger.
  4. From the Who have performed the event drop-down, select the event type Transactional.
  5. From the list of available transactional events, select the one that best matches the action you want to trigger the journey. The table below lists the available events along with their descriptions.
Event conditionDescription
Current transactionChecks when a user enters into a journey when a transaction is completed.
Customer registrationChecks when a user enters into a journey based on the customer registration event. Configure the associated rules and actions as needed.
Coupon redeemChecks when a user enters into a journey when a coupon is redeemed . Use this event to configure actions based on coupon redemption.
Target enrollmentChecks when a user enters into a journey when they are enrolled in a target .
Target value achievedChecks a user enters into a journey when the predefined target value is achieved .
Partner program linkedChecks when a user enters into a journey when they are linked to a partner program .
Promotion issuedChecks when a user enters into a journey when a promotion is issued to them .
Customer updateChecks when a user enters into a journey based on the customer update event.
Reward issuedChecks when a user enters into a journey whenever a reward is issued .
Points issuedChecks when a user enters into a journey when points are issued .
Coupon issuedChecks when a user enters into a journey when a coupon is issued .
Tier upgradedChecks when a user enters into a journey their tier is upgraded .
Tier downgradedChecks a when user enters into a journey when their tier is downgraded .

Adding behavioral events

To add behavioral events perform the following:

  1. Create a new journey.
  2. On the journey canvas, select Entry Trigger.
  3. Choose User Event as the type of entry trigger.
  4. From the Who have performed the event drop-down, select the event type Behavioral.
  5. From the list of available behavioral events, you can either select from the existing custom events (if they meet your requirements) or create your own custom events.

Adding conditions in user event

Conditions in a User Eventallow you to define which customers can enter a journey based on specific criteria. For example, if you want to send an engagement offer only to customers who haven’t made a purchase in the past month, you can set a condition to include only those customers. This ensures that your journey targets the right audience.

You can set conditions based on either Transactional Events or Behavioral Events. When you select a Transactional Event, a list of available events appears from which you can choose the specific customer action to track. Similarly, when you select a Behavioral Event, you can choose from relevant customer interaction events to define your entry conditions.

Adding conditions for transactional events

To add conditions for Transactional Events, perform the following:

  1. Create a new journey.
  2. On the journey canvas, selectEntry Trigger.
  3. Choose User Eventas the type of entry trigger.
  4. From the Who have performed the event drop-down, select the event type Transaction event.
  5. Select +Add entry paths to define further criteria for the customer to enter the journey.
  6. Select +Conditions to add further conditions. For transactional event types, you can define conditions using various attributes based on the selected transactional type. These attributes help segment and direct customers through different paths based on specific characteristics or purchase details, such as loyalty status or engagement patterns.

Event Profiles and Attribute

The table below lists the available attributes for all transactional and behavioral event types along with their descriptions.

Transactional event

  • Customer profile ( This applies to all the transaction event type )
AttributesDescription
Customer's segmentsCheck if the customer belongs to a specific segment or cluster (such as a behavioral or demographic group).
Lifetime pointsCheck if the customer’s total accumulated loyalty points (lifetime points) meet a specified threshold.
Lifetime transaction amountCheck if the customer’s total spend (lifetime purchase value) reaches a defined amount.
Customer extended fields filterCheck if a customer’s profile contains a specific value in an extended field.
Linked supplementary programCheck if the customer is linked to a specific supplementary or partner program.
External IDCheck if the customer’s profile matches a specific external ID or pattern.
Customer custom fields filterCheck if a customer’s profile contains (or does not contain) a specific value in a custom field.
Current points balanceCheck if the customer’s current balance of redeemable points meets a specified condition.

  • Transaction profile (This applies to Current transaction event type)

Attributes

Description

Transaction date

Check if a transaction occurs on a specific date or within a date range.

Transaction value

Check if the total value of a transaction meets a specified condition.

Extended fields in the transaction

Check if a transaction contains a specific value in an extended field.

Total discount

Check if the total discount applied to a transaction meets a specified condition.

Transaction number

Check if the transaction number (or ID) matches a specific value or pattern.

Line-item count

Check if the number of line items in a transaction meets a specified condition.

Basket amount

Check if the total value (amount) of a transaction's basket meets a specified threshold.
In scenarios where the basket amount can match the threshold exactly, it is recommended to use the greater than (>) operator. Using greater than or equal to (≥) will also qualify transactions where the basket amount equals the threshold, allowing customers to enter the journey even when that may not be intended

Bill points

Check if the number of points awarded for a transaction meets a specified condition.

Transaction Id

Check if a transaction matches a specific transaction ID.

Custom fields in the transaction

Check if a transaction contains a specific value in a custom field.

Gross amount

Check if the gross amount (total before discounts) of a transaction or its line items meets a specified condition.

Bill date

Check if the transaction occurred on a specific bill date or within a date range.

Outlier stauts

Checks whether the transaction is normal or flagged with a specific status such as FRAUD, or RETRO.


  • Store profile (This applies to Current transaction, customer update , coupon issued and coupon redeem event type)
AttributesDescription
ZoneCheck if a transaction occurs in a specific geographical zone or region.
ConceptCheck if a transaction occurs in a specific concept (a logical grouping of stores, like a brand).
Concept nameCheck if a transaction occurs in a store belonging to a specific concept name.
StoreCheck if a transaction occurs at a specific store.

  • Customer Registration Event Profile (This applies to Customer registration event type)
AttributesDescription
Customer Registration Event SourceChannel through which the registration happened.
Created AtTimestamp when the registration event was created.
Entered AtTimestamp when the customer was added to the system.

  • Cart promotion / Gift voucher redemption (This applies to Cart promotion / Gift voucher event type which is triggered when a user performs the entry action)
AttributesDescription
Cart promotion / Gift voucher redeemed from mentioned promotionsCheck if the user has redeemed a cart promotion or gift voucher from the specified promotions.
Created AtThe date when the redemption event was captured.

  • Target Profile (This applies to Target enrollment, Target value achieved and Promotion issued event type)
AttributesDescription
Target Rule IDUnique identifier of the target rule.
Target Rule NameName of the target rule.
Target Group Start DateStart date of the associated target group.
Target Group End DateEnd date of the associated target group.
Target Group IDUnique identifier of the target group.
Target Group NameName of the target group.

  • Partner Program Profile (This applies to Partner program linked event type)
AttributeDescription
Linked Supplementary ProgramName of the linked supplementary partner program.

  • Promotion Profile (This applies to Promotion issued event type)
AttributesDescription
Promotion NameName of the issued promotion.
Promotion Start DateStart date of the promotion.
Promotion End DateEnd date of the promotion.
Promotion Issued DateDate when the promotion was issued.
Promotion Issued Expiry DateExpiry date of the issued promotion.

  • Customer Updated Profile (This applies to Customer update event type)
AttributeDescription
Customer Previous Custom Fields FilterPrevious custom field values.
Customer Previous LabelPreviously assigned customer label.
Customer Current LabelCurrent assigned customer label.
Customer Current Custom Fields FilterCurrent custom field values.
Customer Previous Extended Fields FilterPrevious extended field values.
Customer Current Extended Fields FilterCurrent extended field values.
Customer Previous StatusCustomer’s previous status.
Customer Current StatusCustomer’s current status.
Customer Updated Event SourceSource of the update event.
Created AtTimestamp when the update was captured.

  • Reward Issued Profile (This applies to Reward issued event type)
AttributeDescription
Reward GroupCategory or group of the reward.
Reward Redemption TypeRedemption method (e.g., online/offline).
Reward LabelLabel assigned to the reward.
Reward TypeType of reward issued.

  • Points issued Profile (This applies to Points issued event type)
AttributeDescription
Triggering Activity NameActivity that triggered the point issuance.
Total Points IssuedTotal points granted to the customer.
Created AtTimestamp when points were issued.

  • Coupon Series Profile (This applies to Coupon issued and coupon redeem event type)
AttributesDescription
Coupon Series TypeType/category of the coupon series.
Added At DateDate when the series was added.
Coupon from Mentioned SeriesSpecific coupon issued to the customer.
Coupon Series DescriptionDescription of the coupon series.
Created At DateTimestamp when the coupon was issued.

  • Coupon Redeem Profile ( This applies to Coupon reedem event type which is triggered when a user performs the entry action. )
AttributeDescription
Coupon CodeThe unique code of the coupon triggered the redemption event.
Coupon Redemption DateThe date when the coupon was redeemed.
Coupon Series IdIdentifier of the coupon series to which the redeemed coupon belongs.
Coupon IdUnique identifier of the redeemed coupon.

  • Tier Upgraded Profile (This applies to Tier upgraded event type)
AttributeDescription
Created AtTimestamp when the tier upgrade was processed.
Loyalty Program IDIdentifier of the loyalty program.
Previous Tier NumberCustomer’s previous tier.
Tier Upgraded Expiry DateExpiry date of the upgraded tier.
Tier Upgraded NumberNew tier assigned to the customer.

  • Tier downgraded Profile (This applies to Tier downgraded event type)
AttributeDescription
Created AtTimestamp when the tier downgrade happened.
Loyalty Program IDIdentifier of the loyalty program.
Tier Downgraded NumberNew downgraded tier assigned.
Previous Tier NumberCustomer’s previous higher tier.
Tier Downgraded Expiry DateExpiry date of the downgraded tier.

Behavioral event

For behavioral event type you can define conditions using three key attributes. The available attribute categories are Customer Profile, Store Profile and Behavioral Event Profile. The Customer Profile and Store Profile attributes are the same as those used for transactional events. However, for the Behavioral Event Profile, you need to configure the attributes based on your specific requirements.