What is Web-to-Onchain Funnel?

A web-to-onchain funnel tracks how users move from an offchain visit through wallet interaction to a successful onchain action. A common sequence is first visit → wallet connect → signature → first confirmed transaction → repeat transaction. It reveals where reach, intent, authorization, execution, or retention breaks down.

How a web-to-onchain funnel works

Define an ordered event sequence, the eligible population, the identity rule, and the maximum time allowed between steps. Track wallet connection, signature, transaction submission, confirmation, failure, and repeat activity as distinct states. Measure both overall completion and step-to-step conversion so the main source of friction is visible.

Web-to-onchain funnel example

Of 10,000 first-time visitors, 2,500 connect a wallet, 1,600 sign, 1,200 submit a transaction, 1,050 receive confirmation, and 420 return for another transaction. The largest early drop suggests a connection or value-proposition issue; the submission-to-confirmation gap points to execution failures.

Common mistakes

Do not treat a wallet connect or signature as a successful transaction. Separate submitted, confirmed, failed, dropped, and reverted states. Avoid mixing visitors and wallets without a documented identity rule, and do not let repeated attempts from one user inflate the number entering each step.

Using Web-to-Onchain Funnel in practice

Use this funnel to diagnose onboarding and activation, compare acquisition sources, and measure whether product changes reduce time and drop-off between web and onchain steps. Break results down by device, wallet type, chain, campaign, or cohort when sample sizes remain meaningful.

Related reading

Explore product analytics, Funnel Analytics, Time to First Transaction, Wallet Activation, and the DeFi growth funnel guide.

FAQs

What are the main web-to-onchain funnel steps?

A common sequence is first visit, wallet connect, signature, first confirmed transaction, and repeat transaction.

Should failed transactions count as completed?

No. Failed, dropped, or reverted attempts should be tracked as diagnostic states, while completion normally requires a confirmed successful outcome.

Can the funnel include product-specific steps?

Yes. Add steps such as onboarding, quote selection, approval, or feature use when they represent real prerequisites in the user journey.