Achievements allow you to define goals for your users. In contrast to quests, achievements are NOT global, and you don't have to distribute them. This means all users can access all achievements if they meet its requirements.

With achievements, you can do things like:

  1. "Complete the onboarding process and get a free week of using the app."
  2. "Achieve a winning streak of 5 to get this achievement and unlock the next tier of this achievement."
  3. Profile completeness achievement

Completion Conditions

Achievements can be created based on user properties. The user's achievement status will be recalculated whenever appropriate user properties are changed. You can mention the same property several times to create a range. For example, users need to deposit between 50 and 100 to get the achievement.

If any of the properties or achievement conditions are changed, the user will still have the achievement only if he has already claimed it. The user will see the updated progress if the achievement hasn't been claimed yet.


You can configure which users will be eligible to see the achievement, the dependencies between achievements, and whether the achievement will be locked until the user completes another achievement.

This way, you can create an "achievement tree" that users unlock as they progress through the system.


Achievements 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.


You can configure how your user will see the achievement from the presentation step. You can configure the title, description, and icon.


Hidden Achievements

By switching visibility to "Hidden, visible after completion", you can create an "Easter egg" or "hidden achievement". User will be able to see this achievement only after completing it