Wallet Intelligence - onchain meets in-product

An address is a start Activity is the story

Bring supported onchain activity and Wallet Score into the customer journey. Recognize meaningful actions, define who qualifies and give users a reason to take the next step.

  • Connected wallet context
  • Campaign conditions you define
Try a wallet eligibility ruleIllustrative preview
Fictional wallet profileWallet connectedSample Wallet Score
82
70
Score at least 70Required action
Example campaign available

Both example conditions match. The configured journey could now be offered.

Sample scores, not the Claimr scoring formula. Controls do not connect a wallet or issue rewards.

Onchain tracking

Make onchain activity part of the experience

Connect wallet signals to the same profile as product, social and referral activity. Choose supported networks and checks that fit the campaign.

Connected wallets

Associate a wallet with the user's Claimr profile so the campaign can use the relevant onchain context.

Activity and history

Use available wallet activity as context for participation, instead of working with an address alone.

Campaign-specific checks

Build around supported transaction, token balance or NFT balance conditions.

A shared user profile

Combine wallet context with product milestones or referral requirements when one signal is not enough.

Wallet Score

A useful signal, not a trust certificate

Wallet Score summarizes onchain context for segmentation and campaign rules. Use it alongside a relevant action, not as a shortcut to declaring an account safe or unsafe.

  1. 01

    Look beyond connection

    A wallet connection tells you an address is linked. Activity and score add context about how it has been used.

  2. 02

    Choose a campaign threshold

    Set a score condition that fits the campaign, then combine it with the behavior you actually want to recognize.

  3. 03

    Keep new users in mind

    Limited history is not proof of abuse. Give new participants a clear starting journey where appropriate.

How to use the context

Wallet Score

One input, alongside the required action

  • Wallet context
  • Campaign action
Explicit campaign eligibility
Conceptual flow - not a scoring formula

Wallet Score is not proof of identity, fraud prevention or financial reliability. Coverage and data availability depend on the supported integration.

Put the context to work

An onchain milestone with an in-product payoff

Build a clear route from the required action to the experience it unlocks. The reward should recognize the behavior your campaign is designed around.

  1. 01

    Connect the wallet

    Link the participant's wallet to their profile using the supported connection flow.

  2. 02

    Check the condition

    Match the supported onchain action and any additional campaign eligibility requirements.

  3. 03

    Recognize the milestone

    Update campaign progress and make the configured achievement or reward available.

Start with a useful moment

Give the signal somewhere to go

Choose a meaningful action, define what qualifies and make the next step clear to the person taking part.

Illustrative campaign ideas - conditions and outcomes are configured for your product

Web3 - activation

Celebrate the first meaningful action

When
A supported campaign transaction is confirmed
Next move
Unlock a first-action achievement
Gaming - ownership

Turn ownership into participation

When
A supported NFT balance condition is met
Next move
Open a holder challenge with a clear objective
Loyalty - qualification

Give regular participants a new level

When
Wallet Score condition + campaign milestone
Next move
Make an advanced reward journey available

Customer story · Proof of commitment

See how wallet history relates to participation

In one iGaming badge season, active participants with 100+ wallet transactions minted the entry badge more often than those with no recorded history. The comparison uses a mid-season snapshot and describes an association.

Read the case study

Anonymous iGaming operator · Ten-week badge season and later recorded activity

100+ transaction wallets minted
57%

Entry-badge mint rate among active participants whose matched wallet had 100+ transactions.

How it’s measured for 100+ transaction wallets minted
No-history wallets minted
7%

Entry-badge mint rate among active participants whose matched wallet had no recorded transactions.

How it’s measured for no-history wallets minted

A little more context

Good questions, clear answers

What the signals mean, how to use them and where the boundaries are.

How is onchain tracking different from Wallet Score?

Tracking provides activity and event context. Wallet Score summarizes aspects of that onchain activity. A campaign can use a supported event, a score condition or a combination of relevant signals.

Which networks and onchain checks can I use?

Coverage depends on the task and integration. Review the current Web3 task documentation and confirm your target network, asset and event with Claimr before defining the campaign. Browse supported Web3 tasks

Does a low Wallet Score mean a wallet is malicious?

No. A score is one input, and limited history can mean limited context. Do not treat a score or a newly connected wallet as proof of abuse, safety or a unique real-world identity.

Can I combine wallet signals with product or referral activity?

Yes. Wallet Intelligence is part of the user profile, so you can design campaign conditions around wallet context together with the supported product, social and referral signals relevant to that journey.

Does the preview connect my wallet or issue a reward?

No. It uses fictional wallet states, sample scores and an example threshold. Changing the controls stays within the preview and does not connect a wallet, calculate a live score or make a transaction.

Make the next move

Give onchain activity a place in the journey

Pick the action worth recognizing, then connect the profile, conditions and reward around it.

Explore the Widget