User GuideGamification GuideDeveloper GuideAPI Reference
User Guide
Xtremepush.com
Start typing to search…

Configure Quests

📘

For each quest, you must specify the following mandatory fields:

  • Completion Conditions: The event(s) the user must trigger to complete the quest.
  • Occurrence: If the event must be triggered once, over consecutive days, or over consecutive weeks.
  • Rewards: The reward your users get for completing the quest.
  • Name: The internal name of the quest.

To create a quest, go to Ways to Earn > Quests > Create. The sections below describe how to configure a quest.

Configure Complete Conditions

In the Completion Conditions section, specify the actions your user must perform to complete the quest. This involves configuring the user action (Desired Action) and the frequency of that action (Occurrence) .

  1. Specify Desired Action:

Under Desired Action, specify one or more user actions (events) and the number of times a user must complete that action to complete the quest. For example, a user logs in to your website three times.

You can further refine these triggers using the following options:

  • Add Requirement: Use event properties to refine the user action. See the image below for an example quest that requires users to save 500€.

  • Progress Reset: Use this toggle to require that events are completed in a specific sequence or condition. For example, if a user must place five 20€ bets in a row and one bet does not meet the specified bet amount, their progress resets to zero.

  • Make the challenge visible: Use this toggle to specify if a user can see this quest on your loyalty widget.

  1. Specify Occurrence: Specify how the event conditions must be met:
  • Once: The user must completes the Desired Actiononly once.
  • Over Consecutive Days: The user must complete the Desired Action every day for a set period between 1 and 15 days. For example, a user logs in to your website twice a day for five consecutive days to complete the quest.
  • Over Consecutive Weeks: The user must complete the Desired Action every week for a set period between 1 and 15 weeks. For example, a user places at least one bet of 20€ every week for four consecutive weeks to complete the quest.
📘

The occurrence option is different from the overall quest timeframe, which you configure under the Restrictions section of a quest.

Specify Quest Restrictions

Under Restrictions, you can specify the following for each quest:

  • Completion Period: Set the timeframe within which a user must finish the quest. You can select durations up to one month or choose to have no restriction.
  • Additional Restrictions:
    • Add Requirement: Restrict the quest to specific user segments.
    • Unlocks after completing: Use this option if you want this quest to only be available after a user has completed an existing quest. This option is useful if you want to create quest chains.
    • Quest Distribution: Define the dates when the quest is active. If your quest doesn’t have any defined dates, use the checkboxes Immediately and Until Canceled. This ensures your quest remains active until you deactivate it in the Quests tab.
    • can user do this quest only once: Use this option to specify if a user can complete the quest more than once. If you allow multiple completions, you can set limits such as once per day, once per week, or once per month.

Specify Quest Reward

Under Rewards, specify one or more rewards that the user receives when they trigger the quest. See Loyalty Reward Types for more information on the different reward types and how to configure them.

Use the Pay to Accept option to configure a token entry fee for the quest. If enabled, you must specify the price in tokens that a user must pay to start the quest. Only tokens can be used as quest entry fees.

Manage Quest Visibility

In this Overview section, you define the internal name and appearance of the quest in your widget.

  • Title: The title of the quest as it appears to users in the loyalty widget.
  • Show to User: Check this box to make the quest visible. When enabled, you must provide a Description and upload an Icon.
  • Can the user cancel this quest: Specify if users are allowed to opt out of a quest once they have started it. If a user opts out, a quest_canceled event is recorded for that user.
  • Group: You can organise quests into specific groups, such as Onboarding Quests. These groups appear internally in the Quest List section of the widget in the Customize tab.
  • Payload for event on click: Provide a URL to direct users to a specific location on your website or app. For example, if your quest requires users to make a referral, you can add a link that takes them directly to your referral page.

Updated about 5 hours ago

What’s Next