What is wallet targeting in web3 advertising?

Wallet targeting is web3 advertising that selects its audience from what wallets have actually done onchain, not from what a user is assumed to want. Instead of building a segment from cookies or inferred interests, the network groups wallets by their public transaction history (the tokens they hold, the protocols they use, the trades they make) and shows ads to the people behind those wallets.

How it works

The mechanism has three parts:

1. Public onchain history. Every transaction on a public chain is visible to anyone: swaps, deposits, mints, bridges, token balances. This is the same data you can read on a block explorer. A wallet that provides liquidity on Uniswap, lends on Aave, trades on 1inch, or holds wBTC leaves a permanent, checkable record of doing so.
2. Wallet-to-audience segmentation. The network reads that history and sorts wallets into behavioral audiences. Specify builds these across 6,000+ protocols and 15+ chains, so an audience can be as specific as Hyperliquid traders, Sky savers, or Aave lenders rather than a vague interest label.
3. Matching wallets to ad surfaces. Ads then serve where those users are already recognized by their wallet: native placements inside wallets, block explorers, and apps like Coin98, Blockscout, Turtle, Collab.Land, and Outposts. The person is identified by the wallet they connect, not by a profile bought from a data broker.

Wallet targeting vs cookie and interest targeting

The difference is observed behavior versus claimed behavior. Interest targeting guesses what someone might like from browsing signals and lookalike models. Wallet targeting starts from an action that already happened and is recorded on a public ledger. A wallet either supplied liquidity to a pool or it did not.

It is also more durable. There are no cookies to expire, and the targeting survives browser privacy changes, tracking-prevention updates, and cleared caches, because the identity anchors to the wallet rather than to a browser. Specify ID resolves wallets and devices to one human so the same person is never targeted or paid for twice, and verified onchain conversions close the loop with the same public data.

What about privacy?

The honest answer: onchain data is public by design. Transparent chains publish every transaction, and wallet targeting uses that public record, the same data anyone can see on a block explorer. Nothing here is bought from data brokers.

What matters is the line between public onchain data and private offchain profiles. In Specify’s implementation, the identifier is consent-gated in the SDK: identities anchor to first-hand wallet connections plus public onchain history. There is no page content collected, no browsing history, and no fingerprint surface. Advertising a crypto project this way reaches real users by what they did, without assembling a shadow profile of what they read.

Quick answers

Can users opt out? Yes. The identifier is consent-gated in the SDK, so wallet-verified recognition only happens with the user’s consent, and users who decline are not identified.

Does it work for people without a wallet? Onchain audiences require a wallet to exist. Audience Extension then recognizes wallet-verified users, with consent, on pages where no wallet connects, so a campaign can reach the same known humans beyond the moment of connection.

How precise are the segments? As precise as the behavior they are built from. Because audiences map to specific protocol activity across 6,000+ protocols and 15+ chains, you can target Uniswap LPs or Sky savers directly rather than a broad “crypto interested” bucket. The cleanest way to check the fit is the $1,000 test, which runs real wallet targeting against your own audience and reports the results.