How to Create a Challenge

To create a new challenge, follow these steps:

1. Navigate to the Challenges Section

On your admin panel, locate the side menu on the left. Click on the “Challenges” menu option.

2. View Existing Challenges

If you have previously created challenges, they will be listed on this screen. You can view and manage them here.
If no challenges have been created yet, the screen will appear empty.

3. Create a New Challenge

To start creating a new challenge, click on the “Create New Challenge” button located in the top-right corner of the screen.

4. Mini Challenge Creation Screen

After clicking the “Create New Challenge” button, a mini screen will appear.
This screen includes the following fields and options:

Hidden Challenge: A toggle switch that allows you to create the challenge as hidden, meaning it won’t be visible to users until you choose to make it active. Learn more about Hidden Challenges
Prerequisite Challenge: A dropdown to select any challenges that must be completed before this one becomes available.
Name: A text field to enter the name of your challenge.
Description: An area to provide a detailed description of the challenge.
Repeatable: A toggle switch that allows the challenge to be repeated by the user.

  If you want to allow a challenge to be completed multiple times by users, you should activate this field. The "Repeatable" option turns the challenge into a task that can be completed repeatedly.

Challenge Configuration

When you fill in the required fields on the mini screen, a screen will appear where you need to specify the details of the challenge. Looking at the fields on this screen in sequence:

1. Repeatable

Important Note: Once a challenge is created, this value cannot be changed.

2. Start Date & End Date

Usage: These fields determine the start and end date and time of the challenge. Users can only participate in and complete the challenge within these dates.
- Start Date: Specifies the date when the challenge will be active.
- End Date: Indicates the date when the challenge will end. After this date, users will not be able to see or complete the challenge.

3. Completion Limit

Usage: Determines the total number of times a challenge can be completed. If set to 10, the challenge can be completed a total of 10 times before it is no longer available to participants.
Important Note:
- If the challenge is repeatable, it means that one user can participate in the same challenge multiple times. For example, if a repeatable challenge has a completion limit of 10, a single user could complete the challenge 10 times to reach the limit.
- If the challenge is a one-time challenge (i.e., each user can participate only once), a completion limit of 10 means that exactly 10 different users can complete the challenge before the limit is reached.
Example:
- For a repeatable challenge with a limit of 10, a single user could complete it 10 times.
- For a non-repeatable challenge with a limit of 10, 10 different users would need to complete it once each to reach the limit.

4. Daily Limit per User

Usage: Determines how many times a user can complete the challenge per day. For example, if set to 5, a user can complete the challenge up to a maximum of 5 times per day.

5. Total Point Limit

Usage: This field determines the maximum number of points that can be earned from a challenge. If this limit is exceeded, users will not be able to earn more points, even if they continue to participate in the challenge.

6. Description

Usage: A text field that explains the purpose of the challenge and how it can be completed. Necessary details should be provided here to help users better understand the challenge.
Example: "You need to make a purchase of 500 TL or more to earn points."

Prerequisite Challenge

Description:
The Prerequisite Challenge feature allows you to set a requirement for completing another challenge before a user can participate in the current one.
If a Prerequisite Challenge is defined, users must complete the specified challenge before they are eligible to begin this one.

This feature is particularly useful for creating a progressive gamification experience, where challenges are unlocked only after certain conditions (previous challenges) are met.

Learn more about Prerequisite Challenges

How to Configure:

In the challenge creation screen, locate the Prerequisite Challenge dropdown menu.
Select the desired prerequisite challenge from the list of available challenges.
Ensure the selected challenge is active and configured correctly to ensure a smooth user experience.

Player Tags

The Player Tags field allows you to manually input one or more tags that have been previously defined within your system. These tags help categorize users and create tailored challenges for different user segments, such as VIPs, new users, or loyal customers. By using tags, you can configure challenge conditions and rewards based on specific user groups.

Steps to Use Player Tags

Click on the Player Tags field.
Start typing the desired tag(s) (e.g., VIP, New User, Frequent Buyer). These tags must already be predefined in the system.
If you enter a wrong tag, click the X button next to it to remove the tag.
You can input multiple tags, separated by spaces or commas, to target multiple user groups.
After entering the tags, configure the corresponding points or rewards in the Tag Points section if different rewards are to be given to users with specific tags.

Learn more about Player Tags

Leaderboard

Description

The Leaderboard field allows you to select a leaderboard that you have previously created in the Leaderboards menu. If you have not created any leaderboards, this field will appear empty.

Usage

Field Type: Dropdown
Selection: You can select one or more leaderboards for a single challenge.
Functionality: Adding a leaderboard to a challenge means that all users who complete that challenge will be ranked based on the points earned in the selected leaderboard.
Multiple Selections: You can select multiple leaderboards for one challenge, and a single leaderboard can be used by multiple challenges.
Optional Field: A challenge can be created without selecting any leaderboard, as this field is not mandatory.

Learn more about Creating Leaderboards

Point Config

The Point Config section allows you to define how points are awarded for completing a challenge. This section consists of two tabs that give you flexibility in assigning either static or dynamic points to users. Additionally, you can configure when these points will expire, if needed, using the Point Expiration Settings. Here’s a detailed breakdown of each option:

Static Points1

The Static Points option allows you to assign a fixed amount of points to users when they complete the challenge.

How it Works: If you choose this option, users will receive the same, pre-defined number of points every time they successfully complete the challenge.
When to Use: This option is ideal when you want all users to earn the same reward for completing the challenge, regardless of any other conditions.
Example Use Case:

If the challenge is to leave a product review, you might set the static points at 100 points. Every user who leaves a review will receive exactly 100 points for completing the task.

Dynamic Points

The Dynamic Points option allows for more flexible point distribution based on a multiplier or coefficient, rather than a fixed number.

How it Works: In this setup, points are calculated dynamically based on an external factor, such as the number of items purchased, the total order value, or the user’s engagement level. The system multiplies the user’s performance by a pre-defined coefficient to determine the final point amount.
When to Use: Use dynamic points when you want to incentivize greater user actions, like spending more money or completing more tasks, by offering higher rewards for larger actions.

Example Use Case:

You might configure the dynamic points to award 10 points for every dollar spent. If a user spends $50, they will earn 500 points (10 points x $50). This approach encourages users to engage more to earn higher rewards.

Point Expiration Settings

The Point Expiration Settings section allows you to define when the points earned from completing a challenge will expire. This is useful for maintaining engagement by encouraging users to redeem their points within a certain time frame.

How it Works: In this section, you can set a specific expiration date and time for the points earned through the challenge. Once the expiration date passes, any unused points will be removed from the user’s account.
When to Use: Use point expiration settings if you want to create a sense of urgency for users to redeem their points and increase engagement with your loyalty program. Expiring points also help manage your overall point liability.

Example Use Case:

If the challenge involves completing a purchase during a promotional period, you might set the point expiration to 30 days from the date the points are awarded. Users would need to use their points within that period, or they will lose them.

How to Configure Point Config:

Static Points:

Select the Static Points tab (which is open by default).
Enter the fixed number of points that users will receive upon completing the challenge.
(Optional) Move to the Point Expiration Settings to set an expiration for these points.
2. Dynamic Points:
Click on the Dynamic Points tab.
Enter the multiplier or coefficient that will determine the number of points users earn based on their performance (e.g., 10 points per dollar spent).
(Optional) Go to the Point Expiration Settings to specify an expiration period for these dynamically calculated points.
3. Point Expiration Settings:
Within either the Static or Dynamic Points tabs, scroll down to the Point Expiration Settings section.
Use the date and time picker to define when the points will expire. The points will no longer be valid for redemption after this date.
(Optional) Leave this field blank if you don’t want the points to expire.

Important Notes:

Either Static or Dynamic Points: You must choose between static or dynamic points. Both options cannot be selected simultaneously for the same challenge.
Expiration Settings: The point expiration feature is optional, but when set, it encourages users to redeem their points within the allocated timeframe. It’s important to clearly communicate the expiration to your users.

Tag Points Configuration

The Tag Points tab provides the flexibility to assign different point values to users based on their assigned tags. This allows you to create more personalized challenges, rewarding certain segments of users (like VIPs) with higher points or specific incentives. You can define points for multiple tags using the Add Tag Point button.

Just like the Static Points and Dynamic Points in the previous tab, this section also includes options for setting point expiration and calculating dynamic points based on the user’s actions. Here’s a breakdown of how the Tag Points tab functions:

1. Player Tag

The Player Tag field allows you to assign points to users based on specific tags that have been defined within your system. The tag must be created and correctly defined on both the customer and admin side to ensure accurate tracking.

How it Works: To use this feature, you must enter a tag (for example, "VIP") in the Player Tag field. This ensures that users with this tag will receive the custom point configuration you set in this tab. If you have multiple tags, you can use the Add Tag Point button to create additional tag-based configurations.
When to Use: This is ideal for tiered reward programs, where certain groups of users (e.g., VIP, Gold, etc.) receive higher rewards for completing the same challenge. It's a great way to incentivize higher engagement from valuable customer segments.

Example Use Case:

You could configure the challenge so that regular users receive 100 points for completing it, but users tagged as VIP receive 200 points. In this case, the tag is VIP, and it’s linked to a higher point reward to reflect the elevated status of those users.

2. Points Field

In the Points field, you define the number of points that users with the specified tag will earn. This can be either a static or dynamic point assignment, depending on your reward strategy.

Static Tag Points: Assign a fixed point value to the users with the defined tag. This is similar to the Static Points feature in the primary points configuration tab, but targeted at a specific user segment.
Dynamic Tag Points: Assign points dynamically based on a multiplier or coefficient. This allows points to scale depending on user actions, like the value of purchases or the number of tasks completed.

Example Use Case:

If your VIP users are required to spend money to complete the challenge, you might configure the tag-based dynamic points to award 15 points for every dollar spent. A VIP user who spends $100 will then earn 1,500 points for completing the challenge.

3. Point Expiration Settings (Tag-Specific)

Similar to the Point Expiration Settings in the main Point Config tab, you can set when the points for a tagged user will expire. This setting ensures that even personalized, tag-based points can have a specific expiration date.

How it Works: You can define an expiration date and time for points awarded to users with the assigned tag. After this expiration date, any unredeemed points will be removed from the user’s account.
When to Use: This feature is helpful if you want to encourage users with specific tags to use their points within a particular time frame, creating urgency and engagement.

Example Use Case:

If the challenge offers additional points for VIP users, you may set a 30-day expiration period for those points. This ensures that VIP users are incentivized to use their points sooner, driving engagement and rewards redemption.

How to Configure Tag Points:

Player Tag:
- Enter the specific Player Tag in the field (e.g., "VIP").
- To add more tags with custom point values, click Add Tag Point and repeat the process for each tag.
Points Field:
- For each tag, assign either a Static Point Value (e.g., "200 points for VIP") or a Dynamic Point Multiplier (e.g., "15 points per dollar spent").
Point Expiration Settings:
- Scroll down to the Point Expiration Settings field to define the expiration date and time for the points awarded to users with the specified tag.
- (Optional) Leave the expiration field blank if points for tagged users should not expire.

Important Notes:

You can assign multiple tag-specific points by clicking the Add Tag Point button.
Tag Points must be configured for users with the specified tag, otherwise, the general point configuration will apply.
Point Expiration is optional but recommended for driving timely user engagement with tag-specific rewards.

By using Tag Points, you can create more customized and targeted rewards, ensuring that specific user segments are incentivized with higher or different point values, while also maintaining control over point expiration.

Rules Section

The Rules section is the core of a challenge, defining the conditions that users must meet to complete the challenge. This section allows you to specify the event that needs to occur, how many times the event must happen, within what time frame, and any additional conditions based on metadata. This flexible and highly configurable system enables you to create a wide range of challenges with detailed requirements.

How the Rules Section Works

Event Selection:
The first step in setting up the rule is selecting an Event. The event defines the primary action that the user needs to perform in order to progress in or complete the challenge.
- Example Events:
  - order_placed: The user places an order.
  - product_reviewed: The user submits a product review.
  - cart_abandoned: The user abandons their shopping cart.
Number of Calls:
Once the event is selected, you can specify how many times the event needs to be completed for the user to achieve the challenge.
- Number of Call Field: This field allows you to enter the number of times the event must occur. For example, if the challenge requires the user to place 5 orders, you would set this field to "5."
Time Range (Optional):
If the challenge requires the event to occur within a specific time frame, you can enable the Time Range checkbox and set the desired time limit. This option is useful when you want to introduce urgency or set a time-based goal for the challenge.
- In Last [Time Unit]: Once enabled, you can choose to limit the event completion to a certain number of hours, days, or months.
  - Example: If the challenge is to place 3 orders in the last 30 days, you would configure the time range as In Last 30 Days.
Conditions:
The Conditions section allows you to add specific requirements based on event metadata. These conditions further refine the event by adding parameters that must be met. You can create multiple conditions for each event, making it highly customizable.
- Metadata Key: First, choose the metadata key from the event. This metadata defines specific details about the event that can be used to create a condition.
  - Example Metadata for order_placed event:
    - paymentType: Defines how the order was paid for.
    - deliveryType: Specifies the delivery method (e.g., standard, express).
- Operator: After selecting the metadata key, choose an operator that defines the logic of the condition. Common operators include:
  - Equals: The metadata must exactly match the specified value.
  - Not Equals: The metadata must not match the specified value.
  - Contains: The metadata must include the specified value.
- Value: Finally, choose the value for the condition. This is the value that the metadata key must match in order for the condition to be fulfilled.
  - Example: If you're creating a challenge that rewards users for placing an order using a credit card, you would select the paymentType metadata key, choose the Equals operator, and set the value to CreditCard.
- Multiple Conditions: You can add multiple conditions for each event, making the challenge more granular. For example, you could set up a condition that requires both paymentType = CreditCard and deliveryType = Express.
Adding Multiple Rules:
You can also add multiple rules to a single challenge. This allows you to create complex challenges that require users to complete several distinct tasks to succeed. For example, a challenge could require users to:The system is designed to be flexible, enabling you to build layered and sophisticated challenges that cater to a variety of user behaviors.
- Place 3 orders in the last 30 days (Rule 1)
- Submit a product review (Rule 2)

Example Use Cases:

Simple Challenge with One Rule:
- Challenge: Place 5 orders in the last 30 days using a credit card.
- Event: order_placed
- Number of Calls: 5
- Time Range: In Last 30 Days
- Condition: paymentType = CreditCard
Complex Challenge with Multiple Rules:
- Challenge: Place 3 orders using a credit card and submit 1 product review.
- Rule 1:
  - Event: order_placed
  - Number of Calls: 3
  - Condition: paymentType = CreditCard
- Rule 2:
  - Event: product_reviewed
  - Number of Calls: 1

Key Points to Remember:

You can define events, conditions, and time ranges to create highly specific challenge requirements.
Conditions are based on event metadata, allowing you to refine the challenge based on specific user actions or details.
Multiple rules can be added to the same challenge, enabling complex scenarios that require users to complete various tasks to earn rewards.

Flexible Setup:

The Rules section offers exceptional flexibility. You can mix and match different events, conditions, and time limits to create unique challenges that align with your goals. Whether it's rewarding frequent buyers or encouraging reviews, the system adapts to your requirements.

Note: The events encompass all actions performed by the customer on your site or app. As long as these events are fed to our system, rules can be created based on them. It's sufficient for these events to be sent to us. All actions will immediately appear in the Events section once received.

Icon and Badge Fields

The Icon and Badge fields allow you to upload visual elements that enhance the visibility and appeal of your challenges on your site or app. These fields offer a way to differentiate your challenges and motivate users by adding attractive icons and badges.

Icon Field:

The Icon field is used to upload the image that will represent the challenge on your platform. This icon will be visible to users in their challenge list or profile, acting as a visual representation of the challenge. The icon is important for creating an engaging and intuitive user experience, helping users easily identify and distinguish between different challenges.

To upload an icon:

Click the "Select or drag and drop a file" text inside the Icon field.
You can either drag and drop an image file or select one from your local drive.

Badge Field:

The Badge field is used to upload an image that will be awarded to users upon completing the challenge. Instead of points, users can receive a badge, which acts as a recognition of their achievement. Badges serve as a motivational tool by encouraging users to complete more challenges, especially for those users who are driven by non-monetary rewards or status symbols.

To upload a badge:

Click the "Select or drag and drop a file" text inside the Badge field.
You can either drag and drop an image file or select one from your local drive.

Important Notes:

Point Field Optional: In challenges, the Point field is not mandatory. You can leave the point configuration empty if you wish to offer a badge as the sole reward for completing the challenge.
User Motivation: Badges can serve as a strong motivator for your users, providing them with a sense of achievement and recognition. For users who are more driven by status and accomplishments rather than points, badges offer a way to boost their engagement and loyalty without needing to assign points to every challenge.

Notification Field

The Notification field is crucial for providing instant feedback to users once they complete a challenge. This helps enhance user engagement by immediately recognizing their achievements and keeping them motivated. When a user completes a challenge, they will receive a notification containing the details of their accomplishment.

The Notification field consists of the following subfields:

1. Title:

The Title field is used to define the heading of the notification message. This title is prominently displayed to the user and should clearly indicate the accomplishment, such as "Challenge Completed!" or "Congratulations!"

2. Message:

The Message field is where you can provide more detailed information about the challenge completion. This could include a custom message congratulating the user and providing context on what they earned, such as points or a badge.

You can personalize the message by using the {{point}} variable. The {{point}} variable dynamically inserts the actual number of points earned by the user into the notification message. This is particularly important in scenarios where points are awarded differently based on dynamic points, user tags, or tier levels. For example, if a user earned 200 points based on their VIP tag, and another earned 100 points based on general criteria, each user's message would reflect their specific earned points.Example:
- Message: "You’ve earned {{point}} points for completing the challenge!"
- If User A earned 200 points, the message would display: "You’ve earned 200 points for completing the challenge!"
- If User B earned 100 points, the message would display: "You’ve earned 100 points for completing the challenge!"

3. Notification Image:

The Notification Image field allows you to upload a visual element to accompany the notification message. Adding an image can make the notification more engaging and help visually reinforce the user’s success.

For example, if the user completes a badge challenge, you can include an image of the badge they’ve earned or use celebratory icons to highlight their achievement.

Importance of the Notification Field

Instant Feedback: The notification provides instant feedback, reinforcing user accomplishments and encouraging continued interaction with the platform.
Personalization: With dynamic variables like {{point}}, users receive personalized messages that reflect their specific rewards, enhancing the overall experience.
Visual Enhancement: Including a Notification Image adds an extra layer of recognition by making the notification more visually appealing and rewarding.

By filling out the Title, Message, and Notification Image fields, you ensure that the user receives clear, personalized, and visually engaging feedback as soon as they complete a challenge.