Embedded sign-in
The wallet requested Claimr tokens for its users through the API, so quests opened in the app without a separate login.
Customer story · Fintech / Crypto wallets
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.
The program at a glance
Sign in automatically with the wallet account
Selected offers filtered by wallet-supplied tags
Finish partner tasks for rewards
Reported campaign outcomes
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.
Partner membership checks, X follows and reposts, code submissions and server checks. Link clicks, intent tasks and sampled X periods are excluded.
Exchanges, games, AI projects, Web3 protocols, earning apps and media, all in one in-wallet quest feed.
April 2025 to October 2026. A median of about 26,000 accounts were active in each full month.
Wallet accounts with at least one completed task; about 352,000 completed a partner task. Accounts are not verified people.
Accounts completing tasks for at least five partner brands. About 101,000 engaged with two or more.
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
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
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
The marketplace combined embedded sign-in, a growing partner quest library, audience tags and automatic checks.
The wallet requested Claimr tokens for its users through the API, so quests opened in the app without a separate login.
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.
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.
Claimr confirmed Telegram and Discord membership, X follows and reposts, and codes from partner games.
A game quest called the wallet’s own API to confirm an in-game milestone before the task counted.
The partnerships team previewed new partner quests behind an internal tag before releasing them to users.
Marketplace activity
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 any recorded task activity in the month, including tasks they did not finish. Monthly totals are not a retention rate.
Partner mix
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.
| Category | Partners | Accounts completing a task | Checked actions | Link clicks |
|---|---|---|---|---|
| Exchanges and markets | 2 | 173,911 | 44,058 | 202,880 |
| Games | 6 | 153,693 | 81,335 | 140,881 |
| Web3 protocols and tools | 11 | 83,785 | 109,294 | 31,997 |
| AI projects | 5 | 57,405 | 54,289 | 16,857 |
| Media and newsletters | 3 | 28,668 | 5,138 | 18,714 |
| Earning apps | 2 | 9,342 | 0 | 10,081 |
Claimr assigned the categories. An account can appear in several categories. The five largest partners account for 51% of checked partner actions.
Verification
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.
| Method | Completions | What it shows |
|---|---|---|
| Checked by Claimr | ~294,000 | Telegram and Discord membership, X follows and reposts, codes, server requests |
| X tasks in sampled periods | ~121,000 | Checks used a 50% sampling setting; all completions from these periods are excluded from the checked total |
| Link clicks | 421,410 | Includes sign-up offers; conversions tracked by partners |
| Intent tasks | 60,623 | Like and repost prompts; not confirmed on X |
| Other | 17,662 | Forms, videos and email sign-ups |
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.
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
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.
5 quests used tags for selected countries or regions. The wallet supplied the audience tags; Claimr used them to display the offers.
A partner quest used a wallet-defined audience tag, bringing partner-specific targeting into the same feed.
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
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.
Completed at least one task for each of two or more distinct partner brands.
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
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.
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.
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.
The game milestone shows the pattern: confirm in-app progress through an API wherever a partner can provide one.
Methodology
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.
Talk to Claimr about embedding quests in your app, targeting partner offers and confirming what users do.