Try a useful workflow
- User action
- Create and use a first report, integration or automation
- Claimr experience
- A feature challenge built around the completed result
Product Adoption
Introduce a useful feature through a guided challenge. Show users what to do, recognize the completed workflow, and give them a reason to use it again.
Discover a feature challenge
Complete a useful workflow
Use the feature again
Example journey - adapt the actions and rules to your product
How it works
Start with the problem a feature solves for the customer. Build the challenge around that outcome, not around opening another screen.
Choose a cohort that can benefit from the feature and has not reached the relevant milestone yet.
Use quest steps to take someone from discovery to a concrete result, with a visible achievement at the finish.
Recognize the first use, then measure or encourage repeat use when the feature naturally calls for it.
See it in practice
Select a step to see what the participant does and how Claimr responds. These are example campaign rules you can adapt to your product.
The participant
Claimr responds
Show the journey to the intended cohort using the supported display and eligibility setup.
Example only - exploring these steps does not complete campaign activity or issue campaign rewards.
Your industry
Start with an action that matters to your audience. Define the requirements and recognition before you launch.
Illustrative programs - available actions and requirements depend on your integration.
Build it with Claimr
Connect the capabilities your program needs, from campaign rules to the experience participants see.
Create a focused route to a feature's useful outcome.
Explore Quests and challengesUse the profile and relevant segments to shape discovery.
Explore User IntelligenceConnect the supported events and interface controls the journey needs.
Explore API & SDKCustomer story · Testnet to builders
An EVM testnet used Claimr to guide participants through five deployment milestones. About 60,000 accounts completed the track, combining a custom contract check with accepted address submissions.
Read the case studyAnonymous EVM testnet · 2024 program · Full exported cohort
Accounts with accepted completions for all five deployment tasks, across the configured builder track.
How it’s measured for completed the five-contract track60,295 of 104,485 task-active accounts completed the five deployment milestones.
How it’s measured for of active participants finished all fiveDefine success
Define feature adoption before the campaign starts. Keep first-use, repeated use and broader product outcomes distinct.
Participants can differ from non-participants before a campaign starts. A simple comparison does not establish that the campaign caused adoption.
Questions, answered
Yes. Product adoption is not limited to onboarding. Design a relevant campaign for an existing cohort that has not used the feature or completed its useful workflow.
Only if the required milestone is not already available through your integration. Choose an event that confirms real feature use and connect it through the supported path.
Activation focuses on the first meaningful product value. Adoption focuses on discovering and using additional capabilities, often after someone is already active.
A campaign can provide progress and participation data. To estimate causal impact, define a suitable experiment or comparison with your analytics team instead of assuming every difference is caused by Claimr.
Choose one feature and the workflow that demonstrates its value. We can help turn it into a guided challenge.