Testing Your Task
Before integrating the library into your production app, you can verify task behaviour directly from the console using test mode. This lets you simulate user interactions and confirm that tracking, completion logic, and rewards work as expected.
Using test mode in the console
Open your task from the Tasks tab.
Look for the Test action on the task detail page.
Enter a test user identifier to simulate a user session.
Trigger the Go action — this represents a user starting the task.
Trigger the Claim action — this represents a user completing the task.
The console will reflect each event in real time.
Test mode events are recorded and visible in Statistics, so you can verify the full tracking flow without touching your live application.
What to check
After running a test sequence, confirm the following:
The task status transitions as expected (started → completed).
The reward is assigned to the test user on claim.
The events appear in the Statistics dashboard under the correct task and application.
Any automation rules (rate limits, quotas) behave as configured.
Activating the task
Once you are satisfied with the behaviour in test mode, make sure the task status is set to Active before going live. Inactive or not-started tasks will not be processed when the library is called from your application.
Last updated