A quest should feel like a fair trade: a few moments of attention for a reward that matters. When that trade is unclear, completion drops and trust erodes.
Start with one job
Every quest needs a single primary action. Examples:
- Watch a branded video, then answer one question
- Return three days in a row to keep a streak
- Share a story asset from your brand kit
- Hit a high score inside a mini game
If you need multiple jobs, ship multiple quests.
Match reward to effort
Low effort quests (survey, story share) work with smaller token grants or gift codes. Higher effort quests (multi-day streaks, long videos) need clearer progress and a stronger prize.
AdQuest lotteries sit on top of that economy: users earn tickets with tokens, then enter draws you fund and fulfill through the platform.
Keep chrome familiar
Use your platform theme so the SDK feels native — primary CTAs, surface cards, and fonts from the dashboard theme studio. Avoid surprising users with a totally foreign UI when they open Rewards.
Close the loop in product
After completion:
- Show the reward immediately
- Let users rewatch or review when appropriate
- Deep-link back into the host experience with
onClose/onNavigate
Iterate with data
Ship, measure start and completion rates, then adjust length, copy, and reward size. Small changes to the first screen often outperform large redesigns.
Ready to try formats? Explore Video, Streak, and Story quest patterns on the AdQuest landing page, then create your first campaign in the dashboard.