A founder asks how many wallets a press cycle actually brought in, and most PR reporting stops at impressions and backlinks, numbers that describe attention without describing action. Crypto has an answer web2 marketing never had: a public, permanent record of every wallet that ever touched the contract. The catch is that the record only becomes useful if someone builds the attribution layer before the campaign runs, because trying to reconstruct it afterward from a general block explorer is close to guesswork.
Why This Is Actually Easier Than Web2 Attribution, in One Specific Way
A cookie can be cleared, an ad blocker can strip a tracking pixel, and a UTM parameter dies the moment someone screenshots a link instead of clicking it. A wallet address does none of that. Once a transaction lands onchain it’s permanent, public, and queryable by anyone with the tools to look, which means the attribution problem in crypto isn’t a data-availability problem. It’s a data-organization problem.
The Building Blocks: Dedicated Addresses, Not Dedicated Links
The web2 instinct is to generate a unique tracking link per channel. The onchain equivalent is a unique deposit or claim address per campaign, whether that’s a distinct minting contract deployed for a specific KOL’s audience, a discount or allowlist code that routes to a separate claim path, or a presale tranche opened for a named partner. Launchpads already structure raises into tranches for exactly this reason, and that same tranche logic doubles as an attribution tool once someone thinks to tag it that way from the start rather than bolting it on after the fact.
Reading Wallet Funding Sources Backward Tells You Where Demand Actually Came From
Every wallet that interacts with a contract has a funding history, and most block explorers surface a “funded by” trail showing which address sent it its first balance. Cross-referencing the timestamp of a KOL post, an AMA, or a press pickup against a spike in freshly funded wallets interacting with the contract in the following hours gives a rough but real correlation. It’s not proof any single wallet came from any single post, but a pattern across dozens or hundreds of wallets funded from the same exchange in a tight window right after a specific piece of coverage went live is a signal a spreadsheet full of pageviews can’t produce.
Public Dashboards Do Most of the Heavy Lifting Now
Dune Analytics lets anyone write SQL against indexed onchain data and publish a live dashboard tracking a specific contract’s wallet growth over time. Nansen’s wallet labeling adds a layer on top, flagging when known smart-money or exchange-linked addresses show up in the activity. Etherscan and its equivalents on other chains remain the ground truth for verifying any individual transaction a dashboard surfaces. None of these tools were built for marketing attribution specifically, but stitched together they do the job a dedicated MarTech stack does in web2, at a fraction of the cost and with data nobody can dispute.
The Honest Limitation: First Touch Is Still Mostly Invisible
A wallet that bridges funds through an intermediary, moves through a mixer, or simply waits three weeks between reading a headline and acting on it breaks the timing correlation that makes this whole method work. Onchain attribution is much stronger at last-touch and campaign-window analysis, did activity spike in the hours after this specific push, than at reconstructing a user’s full journey from first exposure to final transaction. Anyone presenting this data should say so plainly rather than implying more certainty than the method actually supports.
This Pairs With, Not Replaces, Search-Side Attribution
None of this touches how a project gets found before a wallet exists at all. Ranking for the searches a prospective holder runs before ever visiting a dApp and showing up when someone asks an AI assistant about the category are earlier-funnel problems that wallet data can’t measure directly. The two approaches answer different questions: search and AI visibility explain how someone found the project, onchain data explains what they did once they arrived.
What to Actually Set Up Before the Next Campaign, Not After
Agree on a tagging convention for campaign-specific addresses before launch, not during a postmortem. Build the Dune dashboard alongside the campaign plan so it’s capturing data from block one instead of being reverse-engineered from a contract that’s already three weeks old. And report the correlation with its actual confidence level attached, a spike is a spike, not a guarantee, and treating it as one erodes the credibility of every attribution claim that follows it.