Events tasks

What are Events Tasks?

For details on the API method used to send these events, please refer to the API methods.

To create a Custom Events Count task:

Now move on to configuring the specific settings for your Event task and configure the following fields:

Completion points: The number of points awarded once the user reaches the required event count.
Points multiplier (%): Boost the final reward by a percentage. For example, setting 5% will give a user 105 points instead of 100.
Recurrence: Choose how often the task can be completed – once, daily, weekly, or multiple times.
Event Category: A tag that helps you organize and group event types.
Event Name: The exact event identifier being tracked (e.g., GameSession).
Platform: The platform or integration source that sends the event.
Events Count: The minimum number of events required to trigger the reward.
Button Text: Custom label for the task’s CTA button.

Is progressive reward?
When enabled, the final reward scales based on how much the user exceeds the expected event value or count. For example, if the expected value is 10 events and the user completes 30, they’ll receive 3x the reward. Progressive rewards are ideal when you want to motivate users to keep interacting and performing additional actions beyond the minimum requirement.
Is continuous?
When enabled, the task stays open even after it’s been completed once. This allows users to keep earning additional points whenever they meet the conditions again — for example, if they make another transaction or complete more sessions in the following days. Instead of capping the task after a single claim, the user can return to it and continue accumulating points over time.

This setting also changes how recurrence logic works. For example:

With daily recurrence and continuous off all events are tracked and counted.
With daily recurrence and continuous on, only activity from the past 24 hours is checked.

This helps campaigns promote ongoing engagement by encouraging users to return regularly and continue earning points.

Once you’re done:

Click Create task to save and add it to your quest right away. You’ll now see the task listed in your quest. From there, you can reorder it, delete it, or edit it anytime.
Or, click Advanced settings to continue configuring more options specific to the selected task type.
To find out more, read our Task settings article.

To create a Custom Events Value task:

Now move on to configuring the specific settings for your Event task and configure the following fields:

Completion points: The number of points awarded once the total event value reaches the threshold.
Points multiplier (%): Boost the final reward by a percentage. For example, setting 5% will give a user 105 points instead of 100.
Recurrence: Choose how often the task can be completed – once, daily, weekly, or multiple times.
Event Category: A tag that helps you organize and group event types.
Event Name: The exact event identifier being tracked (e.g., GameSession).
Platform: The platform or integration source that sends the event.
Query: A path that extracts the numeric value from incoming events. See the example of a generated query below.
Events Value: The minimum total value needed across all received events to trigger the reward.
Button Text: Custom label for the task’s CTA button.

Is progressive reward?
When enabled, the final reward scales based on how much the user exceeds the expected value. For example, if the expected value is 500 and the user reaches 1500, they’ll receive 3x the reward. This feature is useful when the event contains monetary or quantity values (e.g., amount of a deposit, number of items used, etc.). It motivates users to do more in one go and rewards them proportionally.
Is continuous?
When enabled, the task remains active even after it’s been completed once. Users can keep earning additional points every time they reach the threshold again — for example, if they keep placing new bets or making additional deposits across days.

This setting also changes how recurrence logic works:

With daily recurrence and continuous off, the platform counts the total value across all events.
With daily recurrence and continuous on, only the value generated in the last 24 hours is considered.

This setup encourages repeated user actions and long-term engagement, helping you drive sustained campaign activity.

Once you’re done:

Click Create task to save and add it to your quest right away. You’ll now see the task listed in your quest. From there, you can reorder it, delete it, or edit it anytime.
Or, click Advanced settings to continue configuring more options specific to the selected task type.
To find out more, read our Task settings article.

Prompt example: Provide a JMESPath query to extract the data.bet attribute from each item in a list.

Prompt answer:

To extract the data.bet attribute from each item in a list using JMESPath, use the [].data.bet query:

[
  { "data": { "bet": 100 } },
  { "data": { "bet": 200 } },
  { "data": { "bet": 300 } }
]

Result

[100, 200, 300]

Last updated 5 days ago

Was this helpful?