In-app quests are verified product-usage events, such as signup, onboarding completion, feature use, and retention milestones. They are verified through project webhooks or SDK integration and carry 15% of a base campaign pool.
The integration requirement is what distinguishes this lane. A project has to report the event from inside its own product, which means in-app quests only exist where the project has done that work. This is also why they measure genuine usage rather than intent.
Retention milestones are the most demanding of the set, since they require a participant to come back rather than complete something once. For projects that is the point: it separates a signup that stuck from a conversion that did not.
For participants this lane rewards genuine product use rather than reach, which makes it accessible to anyone willing to try the product regardless of audience size.
