Configure Streaks

Suggest Edits

Accessing streaks

🚧

Attention

By default, Streaks is not enabled for the orgs. To enable, contact your CSR.

Streaks can be accessed using the link https://{host}/tesseract/ui/streaks. For example, if your organisation is in the EU cluster, you can access streaks using the link:

Streaks in EU Cluster

Streaks home page

After accessing the Streaks homepage through the provided URL, the Streak home page appears.

This is the Streaks landing page, where all existing streaks are visible. Brands can search for a specific streak using the following criteria:

  1. Name of the streak
  2. Duration of the streak
  3. Status of the streak
  4. Frequency at which the streak operates

Creating streak

To create a new streak, on the home page, click New streak and enter the below details:

  1. Basic details
  2. Customer enrolment details
  3. Activity details

Basic details

In the Basic details section, define the following:

  • Name - Name of the streak

  • Description - A short description of the streak.

  • Duration: Duration for which the Streaks need to be active. For example, a brand wants to run a weekly streak, requiring its users to make three weekly transactions. If a user accomplishes this for five, ten, and fifteen consecutive weeks, they will receive 10, 20, and 30 points respectively. If the brand intends to start this streak on January 10th, 2023, the start date is defined as January 10th, 2023, and the end date is 15 weeks from January 10th, 2023.

  • Till code: Select the till code. This till code is used to attribute all the points that are going out from the streaks module.

Customer enrollment

In the Customer enrolment section, define the audience to whom you want to enroll in the Streaks program.

  • All customers: All customers in the organization who have registered for loyalty will become part of the streak.
  • Audience list: This helps enrol the users into the streaks based on filters, existing user groups, or via CSV upload. This is similar to the audience capability in Engage+.

Note: This step is the same as the "customer enrollment" step in Milestones. For detailed information on this step, please visit the following page: here .

Activity

This is the core section of the streak where the brand has to configure the below components of the streak:

  1. Activity on which the streak will run, and the associated KPI.
  2. Target value for each cycle
  3. Frequency of the streak
  4. Scope filter & rule filters
  5. Levels of the streak also known as streak definitions

Defining the type of activity on which Streaks need to be created.

From the Activity drop-down, select the type of activity based on which you want to create the streak.

  • Transactional activities
  • Behavioral activities
  • All other customer-level activities:
    • Number of returns made by the customer
    • Number of point transfers made by the user
    • Number of point redemptions made by the user
    • Number of successful referrals made by the user
    • and all other activities**
  1. Transactional activities: Helps in tracking transactional properties
    1. Gross sales (both bill level & line item level)
      1. The total gross sales made by the user in the cycle. The gross amount is the amount on the bill before the user avails any kind of discount.
    2. Net sales (both bill level & line item level)
      1. The total net sales made by the user in the cycle. The net amount is the final amount that the user has paid. This means the discounts will be excluded from the tracking.
    3. Quantity (line item level)
      1. The number of quantities purchased by the user in the cycle. When used with a specific line item rule, the brand can track the number of specific line items bought by the user in the cycle.
    4. Transactions count (bill level)
      1. The total number of transactions made by the user in the cycle.
    5. Days of activity (bill level)
      1. The total number of unique days on which the user has made at least 1 transaction.
    6. Transactional extended fields
      1. The following KPIs are supported:
        1. COUNT: The number of times a transactional extended field came with a specific value. This specific value needs to be configured in the rule box.
          1. E.g.: The number of transactions that came with extended field value as "Gold".
        2. SUM: The sum of the selected transactional extended field in the cycle.
    7. Lineitem extended fields
      1. The following KPIs are supported:
        1. COUNT: The number of times a line-item extended field came with a specific value. This specific value needs to be configured in the rule box.
          1. E.g: The number of line items that came with the extended field value as "edible food".
        2. SUM: The sum of the selected line-item extended field in the cycle.
    8. Reward currencies (aka points):
      1. Regular points: Number of regular points earned by the user in the cycle
      2. Promotional points: Number of promotional points earned by the user in the cycle
      3. Both: Number of total regular & promotional points earned by the user in the cycle

The following image shows the screen when "transaction" is selected:

  1. Behavioral activities:Helps in tracking behavioral events
    1. All the Behavioural events configured for the org will be available here.
    2. The following KPIs are supported in behavioral events tracking:
      1. COUNT: The number of times the event has been triggered in a cycle.
      2. VISIT: The number of unique days on which the event has been triggered in a cycle.
      3. SUM: Summing the attribute value of the behavioral event in a cycle.
        1. E.g.: Assume there is a behavioral event called "walking" with an attribute called "steps walked". Now, this attribute value can be summed in a period & based on that rewards can be assigned.

The following image shows the screen when the "behavioral event" is selected:

  1. All other customer level activities: Helps in tracking all other customer level activities/events (aka different customer level events present in the workflow in the loyalty)
    1. Number of points redemptions made
    2. Number of returns made
    3. Number of points transfer made
    4. Number of referrals made
    5. The following KPIs are supported for all the above events:
      1. COUNT: The number of times the specific event selected is triggered in a cycle
      2. VISIT: The number of unique days on which the specific event has been triggered in a cycle.
        Note: Tracking for all the other events also will be available soon

The following example shows the screen when one of the EMF events (points redemption is selected):

An eagle-eye view of the above looks like this:

note: In the above table, EMF-level events are nothing but all other customer-level events/activities described in the previous paragraphs.

Frequency of each cycle

After selecting the tracking configurations based on the use case, the frequency for each cycle in which the user must achieve the defined value by the streak needs to be selected.

You can select a frequency from the available options or define a duration (custom duration).

  1. Custom duration

This option can be used when the user has to perform the specified activity within a custom duration, which is not available in the above options. For example, every 5 days, every 13 days, every 2 months, etc. Refer to the below images to learn more about custom duration.


Upload duration

You can click Upload duration and add the duration details in the sample template format provided.


  1. Selecting predefined duration

The below options are available:

  1. Daily
  2. Weekly
  3. Monthly
  4. Yearly

Depending on the chosen frequency, this option will present two choices for Weekly/Monthly/Yearly types. In the "Any day" scenario, users can perform their activity on any day of the cycle, while in the "Specific days" scenario, users are required to perform the activity on designated days.

  1. Weekly:
    1. Any day of the week
    2. Specific days of the week
  2. Monthly:
    1. Any day of the month
    2. Specific days of the month
  3. Yearly
    1. Any day of the year
    2. Specific days of the month
  • Target value needed to be achieved in selected each frequency:
    1. When the "Any day of the week/month/year" is selected for the duration, then the target value that needs to be achieved has to be entered manually.
    2. When the "Specific day of the week/month/year" is selected for the duration, then the target value for the frequency will be calculated automatically.
      1. For example, say frequency is selected "weekly" and "specific days of the week" are selected as Monday, Wednesday & Friday, then the target value will be interpreted as 3 automatically.

Filters: scope based & rule based

The filters available are scope-based & rule-based filters.

Scope based filtering:

  • Stores: Limit the streak to specific retail locations.
  • Zones: Apply the streak to defined geographical areas.
  • Concepts: Limits the streak to specific OUs

To define the streaks for complete stores, zones, and concepts, select All store, zone, and concept.

To define the Milestones for a specific store, zone, and concept, select Specific store, zone, and concept and select the stores/zones/concept.

Rule-based filtering:

For further refinement, you can define the rules in the rule box. For example, rules can be written to target specific line items, categories, minimum transaction amounts, etc.

  • Categories: Target specific product categories within the Milestone.
  • Line items: Apply the Milestone to specific products or SKUs.
  • Transaction amount: Set minimum or maximum purchase amounts for Milestone progress.

Streak levels also known as definitions

In the text box, you can enter the duration for which the streak should be maintained.

You can use the toggle switch to disable or enable a non-continuous streak.

Consider a scenario for your coffee brand's loyalty program:

  • Requirement: Customers must enjoy a cup of your brand's coffee every day.
  • Streak level/definition: Maintain a streak of 5 months within the streak duration.
  • Streak Duration: one year

How it works:

  • Achievement: Customers achieve the streak by drinking the brand's coffee every single day for a continuous period of 5 months.
  • Break Reset: If a customer misses a day, the streak counter resets to zero, and they must start building the streak again from scratch.

Notes:

  1. A user can add 10 different streak definitions in a single streak
  2. Streak levels need to be entered in ascending order.
  3. A user can achieve the streak level "X+1", only when the user has already achieved the "X" level.
  4. The maximum streak value should always be "<=" number of cycles. For example, say the duration is given as 2 months & frequency is given as weekly, then the maximum number of possible cycles is 8.

Non-continuous streaks

Non-continuous streaks, allow users to maintain a streak without performing the associated activity continuously. In this type of streak, breaks or gaps between performing the activity are permitted, as long as the user completes the activity a specified number of times within a defined timeframe. This feature is particularly useful when users may not be able to consistently engage in an activity every day or on a regular schedule but still want to achieve a goal over a period of time.

In the example above, if you set it as a non-continuous streak, customers achieve the streak if they drink the brand's coffee for any of the 5 months in the streak duration.

Click Show preview to view a preview of the streak definition.

Once all these configurations are successfully configured, click Preview & Save to save the streaks.

📘

As of today, event notifications are not available for streaks. Please be mindful about this, we will bring this soon.

Updated 3 days ago