Customer story · Fintech / Crypto wallets

294,000 checked partner actions from an in-wallet quest marketplace

A crypto wallet app embedded Claimr to run a partner quest marketplace inside its app. Over 18 months, 29 partner brands reached its users through one quest feed, with audience targeting for selected offers and about 294,000 checked partner actions. The marketplace is still running.

Anonymous crypto wallet app · Partner quest marketplace, April 2025-October 2026 · Still running

Explore the resultsAll customer stories

The program at a glance

From a wallet audience to partner reach

  1. Open quests in the wallet

    Sign in automatically with the wallet account

  2. Discover partner offers

    Selected offers filtered by wallet-supplied tags

  3. Complete and earn

    Finish partner tasks for rewards

Reported campaign outcomes

What the marketplace delivered

Checked actions use platform, code or server checks. Checked totals are approximate because X sampling periods are reconstructed from code history. Link clicks and intent tasks are counted separately and do not confirm sign-ups. Partner sign-ups, payouts and revenue are recorded outside Claimr.

Checked partner actions
~294,000

Partner membership checks, X follows and reposts, code submissions and server checks. Link clicks, intent tasks and sampled X periods are excluded.

Partner brands with completed tasks
29

Exchanges, games, AI projects, Web3 protocols, earning apps and media, all in one in-wallet quest feed.

Live and still running
18 months

April 2025 to October 2026. A median of about 26,000 accounts were active in each full month.

Accounts that completed a task
~395,000

Wallet accounts with at least one completed task; about 352,000 completed a partner task. Accounts are not verified people.

Accounts that engaged with 5+ partners
~30,000

Accounts completing tasks for at least five partner brands. About 101,000 engaged with two or more.

Geo- or audience-targeted partner quests
6

Quests configured to display using country or audience tags supplied by the wallet. Claimr did not independently verify user eligibility.

Anonymous crypto wallet app · Partner quest marketplace, April 2025-October 2026 · Still running

The challenge

Turn a wallet audience into a partner channel

The wallet had a large user base, and partners wanted to reach it. Running that as a business needed a steady flow of partner placements: launch a partner quest quickly, target it to the intended audience, prove what users did, and keep going month after month without engineering work for each partner.

Claimr’s role

Run the marketplace inside the wallet app

Claimr ran as an embedded quest experience in the wallet app, with sign-in through Claimr’s API. The wallet’s partnerships team created, staged and targeted partner quests in Claimr, and Claimr’s checks confirmed joins, follows, codes and in-game progress.

The Claimr setup

One quest feed, many partners

The marketplace combined embedded sign-in, a growing partner quest library, audience tags and automatic checks.

Embedded sign-in

The wallet requested Claimr tokens for its users through the API, so quests opened in the app without a separate login.

Partner quest library

About 40 partner quests over 18 months, from a single follow to multi-step journeys: install an app, join its channels, submit a wallet address.

Audience tags

Targeted quests were hidden by default. Claimr displayed offers using audience tags supplied by the wallet, which controlled how users were assigned to each audience.

Checked actions

Claimr confirmed Telegram and Discord membership, X follows and reposts, and codes from partner games.

Server-side milestones

A game quest called the wallet’s own API to confirm an in-game milestone before the task counted.

Staged launches

The partnerships team previewed new partner quests behind an internal tag before releasing them to users.

Embedded widgetAPI sign-inPartner questsAudience tagsGeo-targeted offersTelegram and Discord checksX follow and repost checksPartner game codesServer-side API checksStaged quest previews

Marketplace activity

Eighteen months of partner quests, every month active

The marketplace opened in April 2025 and is still running. New partner quests kept arriving, and between 11,600 and 68,000 accounts were active in each full month. Over the whole period, 395,125 accounts completed at least one task.

Accounts with task activity, by monthFull UTC calendar months · May 2025-September 2026
May 25
67,985
Jun 25
26,461
Jul 25
40,084
Aug 25
30,970
Sep 25
39,920
Oct 25
25,336
Nov 25
36,216
Dec 25
18,901
Jan 26
28,674
Feb 26
18,550
Mar 26
11,618
Apr 26
15,224
May 26
14,897
Jun 26
19,192
Jul 26
27,156
Aug 26
29,967
Sep 26
20,690

Accounts with any recorded task activity in the month, including tasks they did not finish. Monthly totals are not a retention rate.

Partner mix

29 partners across six categories

One quest feed carried very different partners: trading platforms, Telegram and Web3 games, AI projects, protocols, media and pay-per-sign-up earning apps. Each could run anything from a single follow to a multi-step journey.

Partner categories by accounts reached
CategoryPartnersAccounts completing a taskChecked actionsLink clicks
Exchanges and markets2173,91144,058202,880
Games6153,69381,335140,881
Web3 protocols and tools1183,785109,29431,997
AI projects557,40554,28916,857
Media and newsletters328,6685,13818,714
Earning apps29,342010,081

Claimr assigned the categories. An account can appear in several categories. The five largest partners account for 51% of checked partner actions.

Verification

What Claimr confirmed for partners

A partner placement is only as good as the actions it delivers, so the marketplace needed to show which ones really happened. Claimr checked memberships, follows, codes and server milestones directly, and recorded about 294,000 checked partner actions. Clicks and intent prompts are reported separately.

Partner task completions by completion method
MethodCompletionsWhat it shows
Checked by Claimr~294,000Telegram and Discord membership, X follows and reposts, codes, server requests
X tasks in sampled periods~121,000Checks used a 50% sampling setting; all completions from these periods are excluded from the checked total
Link clicks421,410Includes sign-up offers; conversions tracked by partners
Intent tasks60,623Like and repost prompts; not confirmed on X
Other17,662Forms, videos and email sign-ups
3,102

Accounts with a server-confirmed game milestone

Claimr asked the wallet’s API to confirm in-game progress before counting the task. The quest also recorded 30,293 game-link clicks; these are separate counts, not a click-to-milestone conversion rate.

~190,000

Checked actions for the wallet’s own channels

The same feed recorded checked actions for the wallet’s Telegram, X and Discord channels alongside its partners. These are task completions, not a measure of new community members.

Checks confirm the action when the task was completed, not whether a follow or membership lasted. X sampling periods are reconstructed from code-change dates; deployment dates and the exact share checked are unconfirmed, so checked totals are approximate.

Targeting

Match partner offers to wallet-defined audiences

Partner offers can be designed for different countries or audiences. 6 partner quests used audience tags supplied by the wallet to control which offers appeared in the embedded feed. The partnerships team also used internal tags to stage quest previews.

Selected countries

5 quests used tags for selected countries or regions. The wallet supplied the audience tags; Claimr used them to display the offers.

Partner audiences

A partner quest used a wallet-defined audience tag, bringing partner-specific targeting into the same feed.

Launch previews

Internal tags let the partnerships team stage quests for preview before a wider release.

The wallet controlled tag assignment. Claimr did not independently verify location or eligibility, and participant records do not retain audience tags. Completions on sign-up offers are link clicks, not confirmed sign-ups.

Engagement depth

More partners discovered in one place

The shared quest feed gave accounts a way to discover multiple partners: 101,240 accounts completed tasks for two or more partner brands. Most partner-active accounts completed tasks for one brand during the measured period.

Partner brands per account351,770 accounts with a completed partner task
1 partner
71.2%
2-4 partners
20.2%
5-9 partners
6.9%
10+ partners
1.7%
101,240

Accounts engaged with multiple partners

Completed at least one task for each of two or more distinct partner brands.

30,161

Accounts engaged with five or more partners

A core of accounts explored several brands through the same in-wallet quest feed.

Engagement includes link clicks and intent tasks. Across all task-active accounts, 83% recorded activity on one UTC day and 59% completed only clicks or intent tasks. 9,574 accounts had activity in four or more calendar months. Partner breadth does not measure retention or confirmed sign-ups.

What this makes possible

Make every partner placement measurable

The marketplace shows that a wallet audience can carry a steady flow of partners. The next step is closing the loop on the outcomes partners care about.

Bring conversions back in

Pass pay-per-sign-up conversions back to Claimr through its API, so the wallet and its partners see confirmed sign-ups next to clicks.

Match checks to the outcome

Use platform checks for memberships and server checks for product milestones. Report sampled and intent-only completions separately so partners can read the results clearly.

Use server checks for product steps

The game milestone shows the pattern: confirm in-app progress through an API wherever a partner can provide one.

Methodology

How to read the results

View sources and measurement details

Figures come from the campaign configuration and full participant export, exported October 13, 2026, and from Claimr’s task-check code. Rounded totals describe recorded participation; each metric keeps its own definition.

Scope and accounts
The export holds 2,364,312 participant records. Each was created when the embedded quest experience loaded for a wallet account. Whether a load means the user viewed the quests depends on how the app embeds it, so that total is not used as an audience figure. 395,125 accounts completed a task. Accounts are wallet logins, not verified people.
Checked actions
Telegram membership is read back by a bot, Discord membership through the user’s Discord login, and X follows and reposts through an X data provider. Codes are matched against configured values, and one game milestone is confirmed by the wallet’s API. Checks confirm the action at completion, not that it lasted.
Spot-checked X periods
Some X checks used a 50% sampling setting. All completions from periods identified in code history, about 121,000 partner tasks, are excluded from the checked total. The exact share actually checked is not recorded. Deployment dates are unconfirmed, so checked totals are approximate.
Clicks and intent tasks
About 421,000 partner link clicks, including sign-up offers, and 61,000 intent tasks are reported separately. They do not confirm a sign-up, install or purchase. Pay-per-sign-up conversions were tracked by partners.
Partners and categories
Claimr grouped partner brands into categories. About 158,000 completions belong to tasks whose quests were later removed; they are excluded from partner totals. The five largest partners account for 51% of checked partner actions.
Audience targeting
Offers were configured to display using tags supplied by the wallet. Claimr did not independently verify location or eligibility, and participant records do not retain audience tags.
Activity and depth
Monthly activity counts accounts with any recorded task activity in a UTC calendar month; the first and latest months are partial. 83% of task-active accounts were active on a single day, and 59% completed only link-click or intent tasks.

Turn your audience into a partner channel

Talk to Claimr about embedding quests in your app, targeting partner offers and confirming what users do.

Try live quests