Events tasks
Last updated
Was this helpful?
Last updated
Was this helpful?
The Events task type allows you to reward users in claimr based on specific actions or occurrences that happen within your own application or product. This is ideal for integrating off-platform user activity with your claimr reward system.
Reward users for in-app actions, like completing levels in a game or making a purchase.
Sync external user achievements with their claimr profile.
Track specific user behaviors that are relevant to your campaign goals.
Encourage participation in activities outside of the claimr platform
Select Events.
Select Custom Events Count to specify the task.
Once you've selected both, move on to configuring the specific settings for your Event task and configure the following fields:
Event Category: This defines a broad classification for the event that is sent from your application. For example, it could be "Dices" if the action is related to a game, or "Transaction" for a financial action. This helps in filtering and organizing events within your claimr analytics.
Name: This is the specific name of the action or event you want to count. For instance, if the category is "Dices," the name could be "game session" to signify a completed gaming session. This precisely identifies the user action.
Platform: This field helps claimr identify how the user involved in the event was logged in or recognized on your platform. For example, if the user logs in via Web3, you would specify "Web3," linking the event to their wallet. This ensures that the incoming event data from your application is correctly associated with the specific user in claimr.
Events count: Specify the target number of times this event must occur for the user to complete the task and receive the reward.
Button text: This is the text that will appear on the button for this task in the claimr widget for users to interact with.
Select Events.
Select Custom Events Value to specify the task.
Select Custom Events Value to specify the task. Once you've selected both, move on to configuring the specific settings for your Event task and configure the following fields:
Event Category: This defines a broad classification for the event that is sent from your application. For example, it could be "Dices" if the action is related to a game, or "Transaction" for a financial action. This helps in filtering and organizing events within your claimr analytics.
Event Name: This is the specific name of the action or event you want to count. For instance, if the category is "Dices," the name could be "game session" to signify a completed gaming session. This precisely identifies the user action.
Platform: This field helps claimr identify how the user involved in the event was logged in or recognized on your platform. For example, if the user logs in via Web3, you would specify "Web3," linking the event to their wallet. This ensures that the incoming event data from your application is correctly associated with the specific user in claimr.
Query: This field holds the detailed data requested by the API call, such as a list of completed actions or quests. Its specific content will vary depending on the type of activity retrieved.
Events value: The aggregated numerical result related to the query, such as a total count or a final score.
Button text: This is the text that will appear on the button for this task in the claimr widget for users to interact with.
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:
[] — iterates over each element in the list.
.data.bet — accesses the data.bet attribute of each element.
Result
Remember, these events are sent from your client application to claimr via an API method. For details on the API method used to send these events, please refer to the API methods.
