Product Adoption

Help users discover more of your product

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.

Feature discovery
  1. 01

    Discover a feature challenge

  2. 02

    Complete a useful workflow

  3. 03

    Use the feature again

The goalProgress from first use to repeat use

Example journey - adapt the actions and rules to your product

How it works

Put the feature inside a useful mission

Start with the problem a feature solves for the customer. Build the challenge around that outcome, not around opening another screen.

  1. 01

    Find the audience it fits

    Choose a cohort that can benefit from the feature and has not reached the relevant milestone yet.

  2. 02

    Guide a complete workflow

    Use quest steps to take someone from discovery to a concrete result, with a visible achievement at the finish.

  3. 03

    Separate trying from adopting

    Recognize the first use, then measure or encourage repeat use when the feature naturally calls for it.

See it in practice

From feature discovery to repeat use

Select a step to see what the participant does and how Claimr responds. These are example campaign rules you can adapt to your product.

Feature discoveryStep 1 of 3

The participant

An eligible user sees a workflow challenge

Claimr responds

Introduce a feature in context

What makes it count

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

What this could look like in your product

Start with an action that matters to your audience. Define the requirements and recognition before you launch.

SaaS

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
Gaming

Discover a new game mode

User action
Complete the tutorial and first session in a new mode
Claimr experience
A discovery quest with an achievement and a follow-on challenge
Web3

Explore a new capability

User action
Complete a supported feature or onchain milestone
Claimr experience
A guided campaign with clear conditions and visible progress

Illustrative programs - available actions and requirements depend on your integration.

Build it with Claimr

The tools behind the experience

Connect the capabilities your program needs, from campaign rules to the experience participants see.

API & SDK

Connect the supported events and interface controls the journey needs.

Explore API & SDK

Customer story · Testnet to builders

Help participants put the product to work

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 study

Anonymous EVM testnet · 2024 program · Full exported cohort

Completed the five-contract track
~60,000

Accounts with accepted completions for all five deployment tasks, across the configured builder track.

How it’s measured for completed the five-contract track
Of active participants finished all five
58%

60,295 of 104,485 task-active accounts completed the five deployment milestones.

How it’s measured for of active participants finished all five

Define success

Did they try it - and did they use it again?

Define feature adoption before the campaign starts. Keep first-use, repeated use and broader product outcomes distinct.

01First-use rate
Eligible users who complete the feature's chosen first-use event in the measurement window.
02Repeat-use rate
First-time users who return to the feature within a relevant follow-up period.
03Time to useful outcome
Time from eligibility or exposure to the completed feature workflow.

Participants can differ from non-participants before a campaign starts. A simple comparison does not establish that the campaign caused adoption.

Questions, answered

Before you get started

Can these journeys target existing users?

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.

Do we need to track a new event?

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.

How is this different from activation?

Activation focuses on the first meaningful product value. Adoption focuses on discovering and using additional capabilities, often after someone is already active.

Can the campaign prove it improved adoption?

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.

Help a valuable feature get used

Choose one feature and the workflow that demonstrates its value. We can help turn it into a guided challenge.