Glossary: Onchain Attribution

What is Onchain Attribution?

Onchain attribution connects captured acquisition context, such as a referrer, UTM, or ad click, with a later wallet action. Coverage depends on linking app sessions to addresses and defining the conversion, attribution model, and lookback window.

Onchain Attribution Explained

Imagine you run a campaign across three different channels and suddenly your protocol gets a wave of new wallets connecting.

Which channel sent them?

Off-chain analytics can tell you where website traffic came from. But once a user connects their wallet and starts transacting, traditional tools lose the trail.

Onchain attribution picks it up from there.

It connects the dots between where a user came from and what they actually did on the blockchain, giving teams a complete picture of what is driving real results.

What Onchain Attribution Means For

Examples

1. A protocol tags referral links with unique identifiers and maps each new wallet connection back to the specific campaign or community that generated it.

2. A growth team uses onchain attribution to discover that users acquired through a Discord partnership have a transaction completion rate three times higher than users from paid social ads.

3. An analyst builds an attribution model combining UTM data with on-chain wallet activity to measure the full journey from first click to first transaction for each acquisition channel.

4. A token project uses onchain attribution to identify which community ambassadors are driving the highest quality wallet activations and increases their rewards accordingly.

Persistence and attribution rules

UTM parameters, referral codes, referrers, and ad identifiers must remain associated with the journey long enough to reach the measured outcome. First-touch and last-touch models can produce different answers, and cross-domain journeys need consistent identity persistence. Document the attribution window and how direct visits affect credit.

Wallet-level versus campaign-level attribution

Wallet-level attribution explains which source is associated with one wallet and its outcomes. Campaign-level attribution aggregates many attributed wallets and outcomes to evaluate a campaign. Volume attribution and revenue attribution describe the value being credited; they should not be substituted for wallet counts or conversion rates.

Related reading

Explore onchain attribution, Attribution Window, Wallet-Level Attribution, Campaign-Level Attribution, and the complete onchain attribution guide.

Some transactions carry an application or builder identifier in their calldata, which can support transaction-level attribution when the identifier is present and mapped correctly. For example, ERC-8021 builder codes identify the app associated with a tagged transaction. They complement session and campaign signals such as referrers and UTMs; they do not identify every user journey or prove which marketing campaign caused a conversion. Report the coverage of tagged transactions and the rules used to connect wallet activity with acquisition touchpoints.

Related terms: Builder Codes (ERC-8021), Conversion Event, Attribution Model, First-touch Attribution, and Last-touch Attribution.

FAQs

Why can attribution be difficult for blockchain app conversions?

A visit, wallet connection, and onchain transaction are different events recorded in different systems. A transaction’s public address does not reveal which campaign led to it, so attribution depends on preserving campaign data and an explicit session-to-wallet or account link.

What is the difference between onchain attribution and UTM tracking?

UTM tracking captures where traffic came from off-chain. Onchain attribution extends that by linking the traffic source to actual on-chain actions like wallet connections and transactions.

Can onchain attribution work without cookies?

It can. A first-party session ID, an explicit wallet connection event, or another documented identifier can link app activity to an address. The address alone cannot identify the campaign or browser session; cookie use and consent requirements depend on implementation and applicable rules.

What data is needed for onchain attribution?

Keep campaign and referrer data, app or session events, the explicit wallet or account connection event, and the qualifying onchain outcome with its chain, contract, and transaction status. Define the identity unit, attribution model, and lookback window before comparing results.

How can teams validate onchain attribution?

Compare attributed records with underlying app events and indexed transactions. Check chain and contract coverage, event decoding, duplicate handling, failed transactions, delayed confirmations, and the share of outcomes that could not be linked to a campaign.