What is a behavior in a SessionM campaign?

A behavior refers to the actions that you want members to perform. Behaviors can be simple (buy a coffee) or more complex (buy a coffee and a scone, muffin or bagel during the morning hours at a new store in Boise).

Behaviors are powered by the SessionM rules engine, which evaluates member engagement and purchase-related events. For each campaign, you can model sophisticated combinations of member behaviors that the SessionM rules engine evaluates in real-time and then awards outcomes to members when they complete designated behaviors.

Behaviors are used in both promotional and messaging campaigns:

  • In messaging campaigns, behaviors are actions performed by a member that trigger the delivery of the campaign's message.

  • In a promotional campaign, behaviors are actions performed by a member that trigger the presentation of an offer or an award to a member.

Components of a behavior

Let's take a closer look at the components of a behavior. A behavior has a name and one or more rules (or groups of rules).

Rule

A rule consists of one or more events and any restrictions applied to those events. A single behavior can have one or more rules.

Event

An event is an action that a member performs. An example of an event in the SessionM platform is a completing a purchase.

Events can be recorded from a variety of sources (for example, point-of-sale, website or mobile app) and sent through methods such as the SessionM Events API, mobile app SDKs, integrated client CRM/point-of-sale systems or flat files. Once ingested, events are processed in real time by the SessionM Rules Engine.

Available events are defined during integration and can include purchases and engagements implemented in your mobile and desktop apps. You can also define a behavior from a custom-named event, which is an brand-specific event that has been integrated into your app.

Event types

A SessionM campaign supports the following event types:

  • Purchase

  • Engagement

  • Campaign

Restriction

A restriction qualifies the action indicated by the event. For example, a restriction can specify the timeframe in which the event must be completed once started, or the max number of times the behavior can be completed within the timeframe and still earn an award.

Restrictions exist at two levels in a SessionM campaign:

  • A behavior-wide restriction applies to all the rules and events in a behavior. Think of it as a global restriction.

  • An event-wide restriction applies to an event. It can be specific to a particular event (for example, the SKU number for a qualifying purchase), or generic in that it can be applied to any event (for example, the timeframe in which the event must be completed).

SessionM supports the following restrictions on events: