Behaviors in Zaius

Behaviors are a series of customer actions that model the way customers interact with your brand. More granularly in Zaius, they are a set of specific Expressions in a specific order. An example of a behavior is cart abandonment, which can be broken down into three steps:

Step 1: Customer added an item to their cart in the last day
Step 2: Customer did not remove that item from their cart
Step 3: Customer did not purchase that item

Behaviors are constructed exactly like this in Zaius—as a series of steps. Behaviors are used to create Segments or to populate Dynamic Grids in campaigns. 

Behaviors can easily be created, edited, and viewed in Zaius. From the Customers menu, click the Behaviors tab. Here you will see a list of the behaviors you have created. You have the option to edit, delete, or clone a behavior. 

Creating a Behavior

To create the cart abandonment Behavior above, we would click New Behavior and then create the three steps as follows:  

For step 1 (customer added an item to their cart in the last day), the step syntax would be: Everyone who matched Product Add to Cart at least 1 time in the previous 1 day 

  • Everyone: We begin the segment without limiting it in any way.
  • who matched: We want customers who did do this step that we are currently defining.
  • Product Add to Cart: We want customers for whom we received an event that tells us they added a product to their cart.
  • at least 1 time: We are only requiring that customers did this action a single time.
  • in the previous 1 day: We are limiting the timeframe of this action to the previous 1 day (i.e., between now and 24 hours before now).

Next, for step 2 (customer did not remove that item from their cart), the step syntax would be: and then did not match Product Remove from Cart linked to Step 1 with same Product Id for all time

  • and then did not match: We want customers who did not do this step that we are currently defining.
  • Product Remove from Cart: We want customers for whom we did not receive an event that tells us they removed a product from their cart.
  • linked to Step 1 with same Product Id: We want to further restrict the Product Remove from Cart event to only include products that have the same Product Id as the product that was added to the cart in Step 1.
  • for all time: We are limiting the timeframe of this action to any time after the first step.

Finally, for step 3 (customer did not purchase that item), the step syntax would be: and then did not match Order Item Purchase linked to Step 1 with same Product Id for all time

  • and then did not match: We want customers who did not do this step that we are currently defining.
  • Order Item Purchase: We want customers for whom we did not receive an event that tells us they completed a purchase.
  • linked to Step 1 with same Product Id: We want to further restrict the Order Item Purchase event to only include products that have the same Product Id as the product that was added to the cart in Step 1.
  • for all time: We are limiting the timeframe of this action to any time after the first step.
Did this answer your question?