Scrimmage offers an innovative and user-friendly approach to creating and managing quests in gamified systems. Your dashboard can have thousands of quests, and the user will see only 2, which you will configure him to see using requirements.

Using our quest system, you can create quests like

1. Complete reading this article in the next 30 seconds and get ten coins.
2. Buy one new item from our shop every month for six months and get the unique perk.
3. Spend more than $100 in our bar 5 times a row and get a trophy.
4. Click here to complete 2FA and get your sign-up bonus.
5. Woohoo, you have a win streak of 5. Win five next games and get a legendary perk

Event Completion conditions

Once the user accepts the quest, it starts listening to every event happening with the user and changing progress. The most straightforward quest can be created by just beginning to count the amount of events the user receives. More complex quests can be made by adding additional event filters.

To gain a deeper understanding of how event conditions function, explore the Introduction to Events section

Event Filters

Every event has a data type attached to it. Data type automatically tracks (indexes) what possible properties and values an event can have. Admin can also modify potential properties and values from the admin panel to start making quests without integrating data.

Event filter uses data type information to render a UI that helps the admin find correct properties visually. That allows the admin to know available event properties and enables cross-functional collaboration.

In-row events

The hardest part of product gamification is to make quests that are challenging enough so that users don't feel bored. Scrimmage allows admins to increase the complexity of quests with in-row event configurations, forcing you to receive events that will pass the event filter N times in a row.

It is essential to understand loose conditions in this case. If the user receives the same event you attached to the quest but this event will fail condition - the quest's progress will get reset.

📘

Skill based challenges

You can use an in-row filter to create skill-based quests like "Win bet three times in a row."

Multiple events

Sometimes, you want to make a quest that requires multiple events to be completed. For example, you want the user to buy a product and then leave a review. You can use multiple events to create such quests. The user will have to complete both events to finish the quest. Events can be completed in any order. In-row events can be used in multiple events as well. In this case, in-row conditions work independently for each event.

By default, all quests contains only one event, but you can add more events to the quest by clicking on the "+" button at the bottom of the event list.

Completion period

Admins can define the time frame for completion, adding a sense of urgency and enhancing user motivation. Quest with a deadline, on average, performs better than quests without it.

Occurrence

Sometimes, we want to make users form a habit, and nothing can be more straightforward than giving them a quest to visit the app seven days in a row. You can choose different completion periods like 'Visit app at least once per week for four weeks.' Occurrence can help you to do that.

Reward and price

Quests are a crucial part of the loyalty economy as they can represent authentic user engagement. By default, in our system, we have two user properties: Gold Trophy and Feature Trophy. Those are two types of trophies you can reward users for completing quests. It is also a common practice to reward tokens.

Acceptance price

Sometimes, you want to make your users more serious about quests. In this case, you can add an acceptance price to your quest. While doing this, be sure you configured your economy so the user will have money to buy the quest. Also, ensure that the quest reward is better than the price.

🚧

All quests have to be accepted.

By default, the user must accept all quests, even with a price of 0. If you want to make quests taken automatically, please request the feature via [email protected]

Quest reward

Quests are integrated into a global rewards framework, enabling a flexible and customizable selection of rewards. This system allows for personalization at both the individual user and segment levels. Detailed information on the variety of rewards is available in the rewards section of our documentation. Transaction histories will reflect the quest and the bonus earned, enhancing transparency and user engagement.

For completing quest you can reward your users with everything that global rewards framework supports including:

1. Tokens
2. Perks
3. Status Points
4. etc.

Quest availability

Users get quest after meeting the requirements

With this configuration, the user will get the quest after meeting the requirements. If the user doesn't meet the requirements, the quest won't show up.

You have direct access to all available system and custom user properties from the quest. This means you can create conditions for levels, experience, perks, or any other custom parameter you make.

Users can get quests after the previous quest is completed

With this configuration, the user will get the next quest after completing the previous one.

If the user cancels or loses the previous quest, the next quest won't be given.

Quest as a reward

You can also make quests as a reward anywhere in the system. This can be used to create a quest chain or a quest that is a reward for a specific action.

Scheduling dates

You can allow your quest to be available only during specific dates. It can allow you to create seasonal quests or whole battle-pass seasons.

Completion Frequency

From the inside of the quest, you can control how much time a single user can complete this quest. You can make it a one-time quest or allow users to complete it a maximum of once per month.

Non-cancelable quests

In some cases, like onboarding, you don't want your users to be able to cancel a quest. In this case, you can make the pursuit non-cancelable, and the user will be stuck with this quest forever.

UI configurations

If you plan to use our widgets, you may be interested in the UI customizations of the quests.

Quests Widget

We have designed a separate small widget that allows you to use our quest page separately from everything else using a small configurable iFrame widget.

Provide Description

You can customize the description of every quest. Our widget usually counts on descriptions of various sizes so that you can insert whole stories into quests or short tasks.

👍

AI helps to generate descriptions.

To further automate admin work, we built an AI integration, which generates quest descriptions based on configurations.

Provide Units

Every quest will count something, whether referrals you made or money you spent. Our system can't automatically detect what we are measuring, so you can set anything appropriate to show the user.

Quest Grouping

You can group quests into categories. This can help you to make the user experience more organized and help users to find quests they are interested in.

Find Group field in the quest configuration and add a group name there. If the group doesn't exist, it will be created automatically.

Quest Redirects

Sometimes, you want the user to be able to click on quest and get redirected to the specific page or website where he can complete the desired action. Due to iFrame limitations and security reasons, we can't directly redirect users. However, we can make signals that can be listened to from your application that will do redirects and other native events like vibrations.

Quests Statistics

You can track the performance of your quests in the admin panel.

Status

Accepted, completed, failed, canceled. You can see how many users are in each state. Quests that can be completed multiple times will have all-time statistics.

Completion time

You can see how much time it takes for users to complete the quest. Completion time available in buckets. Also, you can see the average completion time.

Completion percentage

You can see how many users at the specified completion percentage. Users who completed the quest will be in the 100% bucket. Users who just accepted the quest will be in the 0% bucket.