Creating Challenges
To create a challenge, navigate to Loyalty Modules → Challenges in the sidebar and click the Create Challenge button in the top-right corner. The creation wizard guides you through five steps:
Challenge info
Milestones
Rules & Effects
Limitation & Budget
Summary
Step 1: Challenge info
The first step collects the challenge's basic information. It is divided into six collapsible sections.
1.1. Title and description

Name (en)
Yes
The challenge name displayed to members. Supports multiple languages via + Add translation.
Description (en)
No
An optional description of the challenge.
Display order
No
A numeric value that controls the sorting position of the challenge in lists.
1.2. Start & end date
Define the period when the challenge is active in the system.

Start at
Yes
The date and time when the challenge becomes active.
End at
No
The date and time when the challenge ends. If no end date is set, the challenge stays active all the time.
1.3. Availability
Define when members can make progress toward completing the challenge — for example, limiting it to certain days of the week or a specific date range.

The Timeframe dropdown offers the following options:
Always available
No time restrictions; members can progress at any time.
Is after
Members can progress after a selected date.
Is before
Members can progress until a selected date.
Is day of week
Progress counts only on selected days of the week.
Is nth day of the month
Progress counts only on a specific day of the month (e.g., the 1st or 15th).
Is month of year
Progress counts only during selected months.
Is between
Progress counts only between two specific dates.
Is not between
Progress counts at any time except between two specific dates.
Is time between
Progress counts only during a specific time-of-day window.
1.4. Visibility
Choose which member groups will be able to see this challenge.

Visible for everyone
All members can see the challenge.
Visible for a specific segment
Only members in the selected segment can see it.
Visible for a specific tier
Only members in the selected tier can see it.
Hidden
The challenge is not visible to any member.
Visibility only affects who can see the challenge. It does not prevent other members from progressing. To restrict who can progress, use trigger conditions in the Milestones step.
1.5. Custom attributes
Custom attributes are data fields used to store additional details about the challenge. Click New custom attribute to add key-value pairs.

1.6. Status
A member can progress only when the challenge is active. Use the toggle to activate or deactivate the challenge.

Once you have filled in the basic information, click Next: Milestones to proceed.
Step 2: Milestones
Milestones are the individual tasks a member must complete within the challenge. A challenge can have up to six milestones, each with its own conditions, triggers, and types representing a unique goal. Each milestone is tracked independently, and members can complete milestones in any order.
Click + Add milestone to add additional milestones. Use the three-dot menu (⋮) on a milestone tab to rename or remove it.
Each milestone is configured through six sections:
2.1. Title and description

Milestone name
No
A descriptive name for the milestone.
Milestone description
No
An optional description.
2.2. Type and trigger
This section determines who can progress the milestone and what event triggers it.

Type defines who can progress a milestone. There are two options:
Direct milestone
The member themselves progresses the challenge by performing the trigger action.
Referral milestone
A referee (a user referred by a member) progresses the member's challenge.
Trigger defines which event will activate the milestone. There are two trigger types:
Purchase transaction
The milestone is triggered automatically based on purchase transactions matched with a member.
Custom event
The milestone is triggered by a custom event performed by a member. When selected, an Event type dropdown appears to choose the specific custom event schema.
2.3. Trigger conditions (Optional)
Set detailed conditions for the chosen trigger to determine when the milestone progresses. If no conditions are set, all transactions or selected custom events will count toward challenge progress.
For transactions, conditions are based on attributes such as where the purchase was made, transaction value, item categories, and more.
For custom events, conditions depend on your custom event's specific parameters.
Conditions related to members are available for both triggers.
You can also use Expressions to create more tailored setups.
Click Add condition to define one or more conditions.

2.4. Progress tracking

Select how progress is tracked toward completing the milestone. There are two methods:
Number of event occurrences
Tracks how many times the trigger event happens. Examples: "place 5 transactions above $50", "add 10 product reviews", "place 5 transactions in June".
Value of event attributes
Tracks the value of a specific attribute. Examples: "spend $10 in February", "spend $100 on 'ACME' products", "walk 1,000 steps".
2.5. Goals
Set the target to complete this milestone. The goal configuration depends on the Occurrence type you select:
Overall — The member must reach the goal target at any time, with no streak requirement.
Goal
The target number of events or attribute value.
Streak — The member must reach the goal consistently over consecutive time periods.
Streak type
Daily streak, Weekly streak, Monthly streak, or Yearly streak.
Goal (per period)
The target number per streak period (e.g., events per week).
Streak period (Value)
How many consecutive periods the member must maintain the goal (e.g., "3 weeks in a row").
When the streak type is selected, the system displays a summary sentence: "The member must log X events every [period], for Y [period] in a row."
Count only unique custom event attributes — An optional toggle available for both occurrence types. When enabled, progress increases only for unique values. For example, when considering the attribute "brand": a member purchasing products from three different brands advances progress three times, while purchasing three products from the same brand advances progress only once.
2.6. Event limit
Restrict how many times an event can count toward progress within a specified timeframe.

The Timeframe dropdown offers:
Unlimited
No restriction; every qualifying event counts.
Per hour
Only a set number of events count per hour.
Per day
Only a set number of events count per day.
Per week
Only a set number of events count per week.
Per month
Only a set number of events count per month.
Per year
Only a set number of events count per year.
In total
A fixed total number of events that can ever count.
Step 3: Rules & Effects
Rules define the conditions participants must meet to trigger an outcome in the challenge. Effects define what happens once those conditions are met — such as granting rewards, updating units, or modifying member data.

Click + Add rule to create additional rules. Each rule has a name, description, and three components:
Trigger type
The trigger type determines when the rule fires. There are two options:
Challenge completion
The rule fires only after the entire challenge is completed — meaning all required milestones are finished.
Milestone progression
The rule fires each time a member reaches a specific milestone, even if the challenge is not yet completed.
Challenge completion example: If a challenge requires 5 purchases, the reward is granted only after all 5 purchases are made.
Milestone progression example: If a challenge requires 5 purchases, you can grant a reward after 2 purchases while progress continues.
Conditions
Optional conditions that further refine when the rule applies. Click + Add condition to add criteria such as member attributes, spending thresholds, or other data.
Effects
Click + Add effect to define what happens when the rule triggers. Effects can include adding or removing units from a wallet, granting a reward, or assigning/removing custom member attributes.
If at least one effect is triggered — for example, one out of five possible effects — the challenge is counted as completed.
Step 4: Limitation & Budget
This step controls how often members can complete the challenge and the total reward budget.
4.1. Challenge limit
Defines how many times a member can complete this challenge within a selected timeframe.

Challenge completion per member
How often a single member can complete the challenge.
Timeframe
The period for the completion limit (see below).
The Challenge completion per member dropdown and the Timeframe dropdown both offer the same options: Unlimited, Per hour, Per day, Per week, Per month, Per year, and In total.
For example, setting a limit of 2 per month means a member can complete the challenge no more than twice each month.
How completion is counted depends on the trigger type used in the challenge rule:
If the rule uses milestone progression, each reached milestone triggers the configured effects and increases the challenge completion count.
If the rule uses challenge completion, the completion count increases only after all required milestones in the challenge are completed.
4.2. Challenge budget
Controls the total availability of rewards issued by the challenge.

Units issued by the challenge
The maximum total units that can be distributed across all members. Options: Unlimited, or a cap with a timeframe (Per hour / Per day / Per week / Per month / Per year / In total).
Units issued per member
The maximum units a single member can receive. Same timeframe options as above.
Step 5: Summary
The final step presents a read-only review of the entire challenge configuration, organized into collapsible sections:
Basic info summary — Challenge name, description, start and end date, availability, visibility, and status.
Milestones summary — For each milestone: title, description, type, trigger, progress tracking method, goal, and event limit.
Rules summary — Each rule with its trigger type, conditions, and effects.
Limitations summary — Challenge limit and budget settings.
Each section has an edit (pencil) icon that takes you back to the relevant step to make changes.
Editing certain challenge settings after activation will reset member progress.
After creating a challenge, you can duplicate it to quickly create a similar one with minor adjustments.
Once you are satisfied with the configuration, confirm to save the challenge. If the status is set to Active, it becomes available to members immediately based on the configuration you've set.
Last updated
Was this helpful?

