No single tool follows a crypto campaign from ad impression to on-chain action, which is why most teams run three at once. The tools split into four groups that answer different questions, and the most common budget mistake is buying two from the same group and none from the others. A query platform tells you what happened on chain. A wallet intelligence tool tells you who the wallet is. An attribution platform tells you which campaign caused the visit. Product analytics tells you what the user did inside your app.
This guide is written from the buying side rather than the vendor side. We run campaigns and pay for these tools, so the useful part is which question each one actually answers and where the measurement breaks.
What are the four groups of Web3 marketing analytics tools?
| Group | Tools | Question it answers | Where it breaks |
|---|---|---|---|
| Blockchain query platforms | Dune, Flipside Crypto | What happened on chain, aggregated any way you can write SQL | Needs someone who writes SQL; tells you nothing about the ad that caused it |
| Wallet intelligence | Nansen, Arkham | Who this wallet is, what else it holds, how it behaves | Describes wallets, not campaigns; expensive per seat |
| Attribution | Spindl, Addressable, Cookie3, Formo | Which campaign or channel produced the wallet connection | Wallet identity does not travel like a cookie; coverage is partial by design |
| Product analytics | Mixpanel, Amplitude wired to wallet-connect | What the user did inside the product after arriving | Blind to everything before the connect event |
Market data services such as DeFiLlama and Messari sit outside these four. They describe protocols and markets rather than your users, and they belong in competitive research rather than in campaign measurement.
Which tool should you start with?
Start with the question that is currently unanswered, not with the most capable tool. If you can already see on-chain activity but cannot say which channel produced it, the gap is attribution. If you can see which channel produced a signup but not what the wallet did afterwards, the gap is a query platform. Buying Dune when the real problem is attribution produces beautiful dashboards that still cannot justify a media budget.
Dune and Flipside
These are query platforms, and their strength is that nothing is hidden: if the data is on chain, it can be counted. The practical cost is staffing. A dashboard is only as good as the SQL behind it, and a marketing team without an analyst tends to end up with a copied dashboard nobody can modify or verify.
Nansen and Arkham
Wallet intelligence is for qualification rather than measurement. It answers whether the wallets arriving are the kind you wanted: their history, holdings and behaviour. It is a strong pre-campaign and post-campaign tool and a poor day-to-day one, because it describes wallets rather than the campaigns that produced them.
Spindl, Addressable, Cookie3 and Formo
Attribution is the group built specifically for the problem crypto marketing has and Web2 marketing does not: the boundary between a click and a wallet. These tools bridge it with tagging, fingerprinting and signed wallet messages, and each covers the path slightly differently. Expect partial coverage rather than complete attribution, and treat any vendor promising full-path certainty with suspicion, because the identity simply does not travel the way a cookie does.
Product analytics with wallet-connect events
The most under-used option, and often the cheapest. Standard product analytics wired to the wallet-connect event answers what happened after arrival, which is where retention lives. It cannot see the ad that caused the visit, so it works as the second half of a pair rather than on its own.
What breaks in Web3 attribution?
The boundary itself. In Web2 a cookie or device identifier follows a user from impression to purchase. In crypto the user arrives as a browser session and converts as a wallet, and those two identities are not linked by anything the platform gives you. Every attribution tool in this category is a different attempt to reconnect them after the fact, which is why coverage is always partial and why two tools measuring the same campaign will disagree.
- Decide the conversion event before buying anything. Wallet connection, first transaction and first deposit are three different events with three different costs.
- Expect disagreement between tools and pick one as the reported number. Reconciling two attribution platforms every month is a job nobody has time for.
- Instrument the campaign, not just the product. A coded link or campaign-specific landing page set up before launch beats any attempt to reconstruct the path afterwards.
- Measure at day 30. Arrival is cheap in crypto and retention is not, so the figure that matters is the share still active a month later.
How do we use these tools in practice?
For influencer work the vetting happens before any spend: accounts entering our roster are screened through Wallchain, Sorsa and TwitterScore, because the fastest way to ruin an attribution model is to pay for an audience that is not real. Across our vetted network of 87 crypto accounts, the average account holds 110,106 followers but delivers 11,669 views per post at a 1.70% engagement rate, and no analytics stack recovers a budget spent on the difference between those two numbers.
For task and community campaigns the reported figure is verified participants rather than completions, and the result is read at day 30 rather than at the peak. Three 2026 campaigns run that way moved member counts from 35,000 to 47,000, from 130,000 to 141,000 and from 40,000 to 45,000.
Frequently Asked Questions
Which Web3 analytics tool is best?
There is no single best tool, because the four groups answer different questions and none covers the full path from ad impression to on-chain action. Most teams run a query platform, an attribution platform and product analytics together.
What is the difference between Dune and Spindl?
Dune is a query platform: it counts what happened on chain, in whatever shape you can write in SQL. Spindl is an attribution platform: it tries to connect an off-chain marketing touchpoint to an on-chain event. Dune tells you what happened, Spindl tries to tell you why.
Can Web3 attribution ever be complete?
No, and a vendor claiming otherwise is overselling. A browser session and a wallet are separate identities that the platform does not link for you, so every tool in this category reconnects them partially and by inference.
Do I need Nansen for marketing?
Only for qualification. Wallet intelligence answers whether the wallets you attracted are the kind you wanted, which is useful before and after a campaign but not as a running measurement tool.