What you will get: a precise definition of user activation in DeFi, a map of where users drop off between wallet connect and first transaction, the friction points that cause most of that loss, UX patterns that reliably close the gap, the key metrics to track activation rates, and a set of experiments you can run today.
Why Wallet Connect Is Not Activation
Most DeFi analytics dashboards show the number of unique wallets as a top-line metric. Teams celebrate when the number goes up. But a wallet does not equal a user. It is an expression of interest, nothing more. A person who connects a wallet and leaves without transacting has not used your app or protocol. They have only visited it.
The gap between wallet connects and first transactions is where most DeFi protocols haemorrhage potential users. In some protocols, fewer than 20% of wallets that connect ever complete a first transaction. The rest drop off somewhere between the connect modal and the moment the action becomes real. Understanding what happens in that gap, and designing to close it, is what onchain activation work is about.
Activation sits at the narrow middle of the DeFi growth funnel. Acquisition brings users to the door. Retention keeps them coming back. But neither compounds if activation fails first. A protocol with strong acquisition and weak activation is paying to fill a leaky bucket.
What User Activation Means in DeFi
Activation in DeFi means a user completes their first meaningful onchain transaction. Not a wallet connection. Not a message signature. Not a dashboard view. Activation starts when value moves or a contract is used in a way that reflects genuine product engagement.
What counts as meaningful varies by protocol type. For a DEX, it is a swap. For a lending protocol, it is a deposit or a borrow. For a yield aggregator, it is a vault deposit. The definition should be the smallest action that demonstrates the user has understood the protocol well enough to commit capital to it.
This definition matters because it changes what you measure and what you optimise. If you count wallet connects as activation, your funnel looks healthy while your real conversion rate collapses silently underneath. The DeFi KPIs guide covers how to structure your metrics so activation is measured correctly, separate from acquisition signals.
Definition: An activated user is one who has completed a first meaningful transaction. Everything before that is a visitor. Treat them differently in your analytics and your product design.
Where DeFi Users Drop Off Between Connect and Transaction
The journey from wallet connect to first transaction typically passes through four stages. Each stage has its own drop-off pattern and its own causes. Mapping this precisely for your protocol is the starting point for any activation improvement work.
Stage | What Happens | Typical Drop-Off Cause | Signal to Measure |
1. Connect | User arrives and connects wallet. Intent exists but commitment is low. | No immediate next step. UI presents options without guidance. User loses orientation. | % of connected wallets that view a specific action page within 5 minutes of connect. |
2. Explore | User views pools, rates, or product surfaces. Evaluating whether the protocol is worth trusting. | Insufficient trust signals. Rates unclear. Risk not explained. No obvious entry point. | % of exploring wallets that initiate a transaction flow (click swap, deposit, or borrow). |
3. Initiate | User begins a transaction. Enters amounts, sees approvals, and encounters gas estimate. | Gas cost is higher than expected. Approval flow is confusing. Warning language creates fear. | % of users who initiate a transaction and then abandon before confirming. |
4. Confirm | User reaches wallet confirmation step. The action is one click from being real. | Wallet UI presents unfamiliar contract interaction. User does not recognise what they are signing. | % of users who confirm in wallet versus abandon at the wallet prompt. |
Most activation loss is concentrated in stages 3 and 4, the initiation and confirmation steps. By the time a user has explored the protocol and entered an amount, they have demonstrated significant intent. Losing them at gas or at the wallet prompt is avoidable with the right UX interventions. The user lifecycle analysis guide explains how to segment users by lifecycle stage to pinpoint exactly where your protocol's drop-off is concentrated.
Common Friction Points in DeFi Onboarding
Each drop-off stage has specific friction causes. These are the four that account for the majority of activation loss across protocol types.
Gas Fees
Gas costs create two distinct types of friction. The first is the cost itself: a user who expected to pay two dollars and sees a fourteen dollar gas estimate may decide the transaction is not worth it, especially for a protocol they have not used before. The second is unpredictability: users do not know what gas will cost until they are mid-transaction. The surprise compounds the friction.
Low-fee chains reduce the first problem but not the second. Even on chains where gas is negligible, the presence of a fee prompt creates a moment of hesitation. Users who are new to DeFi interpret any wallet prompt as a potential risk. Gas estimates that are higher than the transaction value for small amounts can kill activation entirely for the users who most need a low-stakes first transaction.
User Experience
The crypto wallet confirmation screen is one of the most hostile UX environments in consumer software. A raw contract call presented as hexadecimal data, an opaque contract address, and a generic warning that this transaction cannot be undone are standard elements. For users new to DeFi, this screen is a dealbreaker.
Modern embedded wallets have made major improvements. Wallet standards such as EIP-712, transaction simulation in wallets like Rabby and Coinbase Wallet, and human-readable contract labels all help improve UX. But not all wallets support these standards, and not all protocols implement them. Every user who drops off at the wallet confirmation step is paying a UX tax for the gap between what wallets display and what users need to see. The more you can abstract away, the smoother your users’ journey will be.
Trust
Trust operates differently in DeFi than in Web2. In Web2, a user who makes a mistake can contact support and usually get it reversed. In DeFi, transactions are irreversible and exploits are real. Users are right to be cautious. A protocol that has not communicated its audit history, its TVL track record, or its team credibility is asking users to trust an anonymous contract with real money.
Trust signals that move activation rates include clearly visible audit reports from named firms, a track record of protocol uptime without exploits, transparent team information, and social proof in the form of TVL or user counts. For a new protocol, even a simple 'Audited by X, Y and Z' with links to reports materially improves first-transaction conversion. The onchain retention guide covers how trust continues to affect retention long after activation, and why it compounds over time.
Risk Clarity
Risk clarity is distinct from trust. Trust is about the protocol's track record. Risk clarity is about what this specific transaction will do. Many DeFi UIs present action buttons without explaining what will happen in plain language: which tokens will leave the wallet, at what rate, with what slippage, subject to what risks.
Users who do not understand what they are about to do will not do it. Fear of the unknown is a stronger force than potential yield. Protocols that surface clear, human-readable transaction previews showing exactly what comes in and what goes out reduce the ambiguity that causes abandonment at the confirmation step.
User Activation Design Patterns That Work
Knowing where users drop off and why is only useful if it leads to product changes. These three UX patterns reliably improve activation rates across protocol types.
Progressive Disclosure
Progressive disclosure means showing users only what they need to act, in the order they need it, rather than presenting the full complexity of the protocol on arrival. A user who has just connected a wallet does not need to see every pool, every advanced setting, and every risk parameter simultaneously. They need to see one clear next step.
In practice, progressive disclosure looks like a default view that surfaces a single recommended action for new wallets, with advanced options available but not prominent. New wallets can be identified onchain: a wallet that has never interacted with the protocol, or that has minimal onchain history, can be shown a simplified UI that gradually reveals complexity as they take actions. This reduces the overwhelm response that causes many first-session drop-offs.
Pattern: New wallet connects → show one recommended action with a brief explanation → reveal full protocol complexity after first transaction is complete.
Guided First Transaction
A guided first transaction is a structured flow that walks the user through their first action step by step, with contextual explanation at each point. It is different from a product tour, which is often a passive modal sequence that users dismiss. A guided transaction is embedded in the actual action flow: as the user fills in an amount, they see an explanation of slippage. As they reach the gas step, they see an explanation of what gas is and what this specific cost covers. As they reach wallet confirmation, they see a plain-language summary of what will happen.
The goal is to eliminate every moment where the user has to pause and wonder what they are doing. Pausing is where abandonment happens. Guided flows keep momentum without removing user control.
Sensible Defaults
Sensible defaults or pre-filled actions reduce the cognitive load of the first transaction by removing unnecessary decisions. A new user who arrives on a DEX does not need to choose which token pair to trade, which amount to enter, and what slippage to set. They need a sensible, safe default which they can adjust if they want. Pre-filled defaults should be based on what actually converts: the most common first transaction in your protocol, the lowest-risk entry point, and the amount that produces the highest activation rate without creating disappointment.
Pre-filled actions work particularly well when combined with campaign landing pages. A user arriving from a campaign link about ETH-USDC liquidity provision should land on a page pre-configured for that specific action, not on a generic homepage. Matching the landing experience to the acquisition context materially improves conversion. The onchain attribution guide explains how to connect acquisition source to onchain outcomes so you can measure which landing configurations actually convert.
Activation Metrics to Track
Activation metrics need to be specific enough to reveal where the funnel breaks. Generic conversion rates are not sufficient. Here is the measurement framework, aligned with the DeFi KPIs that matter for growth teams.
Metric | What It Measures | Healthy Benchmark | Warning Sign |
Connect-to-Transaction Rate | % of connected wallets that complete a first transaction within 7 days | A protocol with clear UX and low friction converts a meaningfully higher share of connects to transactions than one that has not optimised this step. | A low connect-to-transaction rate that does not improve after UX changes suggests a structural activation problem, not just a traffic quality issue. |
Time to First Transaction | Median time between wallet connect and first confirmed transaction | A short time-to-first-transaction indicates the onboarding flow is working. Protocols with guided flows and low gas friction see users transact quickly after connecting. | A long median time-to-first-transaction suggests users are leaving after connecting and either returning much later or not at all. |
Initiation-to-Confirmation Rate | % of users who begin a transaction flow and reach wallet confirmation | A high initiation-to-confirm rate indicates the in-product flow is working. A low rate means friction exists before the wallet step. | A low rate indicates users are abandoning at the gas estimate or approval step before reaching the wallet. |
Confirmation-to-Completion Rate | % of users who reach wallet prompt and then confirm the transaction | Users who reach wallet confirmation have high intent. This rate should be the strongest in the funnel. | A low confirmation rate suggests the wallet prompt itself is creating hesitation. Check for unsupported wallets or missing human-readable transaction labels. |
Activation Rate by Acquisition Source | First-transaction rate broken down by where the wallet came from | Organic and referral sources typically outperform paid on activation quality | If paid acquisition activation rate is less than half of organic, the campaign is bringing low-intent traffic |
How to Diagnose Activation Bottlenecks
Measuring activation metrics is the first step. Diagnosing why the metrics look the way they do requires a structured approach. The goal is to identify which stage of the connect-to-transaction funnel is losing the most users and then find the specific cause within that stage.
Step 1: Map Your Funnel Precisely
Define the exact events that correspond to each funnel stage: wallet connect, first page view of an action surface, transaction initiation, wallet prompt display, and transaction confirmation. If your analytics tool does not capture all of these, you have a measurement gap before you have a diagnosis. Formo's analytics connects frontend events to onchain outcomes at the wallet level, giving you this funnel without requiring custom data infrastructure.
Step 2: Find the Biggest Drop
Calculate the percentage drop at each stage: connect to explore, explore to initiate, initiate to confirm, confirm to complete. The largest single percentage drop tells you where to focus. In most protocols, the answer is either initiate-to-confirm (gas and approval friction) or confirm-to-complete (wallet prompt friction). This tells you whether the problem is in your product UX or in the wallet experience.
Step 3: Segment by Wallet Type
Break activation rates down by wallet provider. MetaMask users may have different confirmation rates than Coinbase Wallet or Rabby users, because each wallet renders contract interactions differently. If one wallet type has materially lower confirmation rates, the problem may be in how that wallet displays your contract, not in your UI. Wallet profiles in Formo make this segmentation straightforward, giving you wallet-level data on which providers are converting and which are leaking.
Step 4: Segment by Acquisition Source
Users who arrive from different sources often have different activation rates because they have different intent levels. Organic search users have high intent. Social campaign users have lower intent and higher curiosity. If your overall activation rate looks poor, segmenting by source may reveal that the problem is traffic quality, not product UX. Use onchain attribution to connect each wallet's first transaction back to its acquisition source.
Step 5: Watch Where Time Is Lost
For wallets that do eventually activate, look at the time distribution between each stage. If there is a long median time between explore and initiate, users are hesitating at the product evaluation stage, which suggests trust or value proposition issues. If there is a long time between initiate and confirm, users are pausing at gas or approvals. Each delay pattern points to a different fix.
Simple Activation Experiments to Run
Activation improvements compound. A 10-percentage-point improvement in connect-to-transaction rate means 10% more users entering the retention funnel. These experiments are ordered by implementation speed and expected impact. For a structured approach to running experiments systematically, see the DeFi growth experiments guide.
Experiment | What to Test | Metric to Watch | Implementation Effort |
Gas Estimate Early Display | Show gas cost estimate on the action selection screen, before the user enters amounts. Compare initiation rate versus showing gas only at the confirmation step. | Initiation-to-confirmation rate. Drop in surprises at gas step. | Low. Frontend change only. |
Pre-Filled First Action | For new wallet connects, default the action surface to a specific recommended transaction with amounts pre-filled. Compare activation rate versus blank default state. | Connect-to-transaction rate for new wallets. Time to first transaction. | Low to medium. Requires wallet age detection and UI defaults. |
Plain-Language Transaction Preview | Add a human-readable summary above the confirm button showing exactly what will happen: which tokens leave, which arrive, at what rate, with what slippage. Test against current UI. | Confirmation-to-completion rate. Abandonment at confirm step. | Low. Copy and layout change only. |
Audit Badge Placement | Move audit and security information from the footer or about page to a visible position on the main action surface. Test impact on initiation rate for new wallets. | Initiation rate for first-session wallets. Time-on-page before initiation. | Low. Layout change only. |
Wallet-Specific Guidance | Detect wallet provider on connect and show tailored guidance for that wallet's confirmation UI. Test against generic guidance. Start with the lowest-converting wallet type identified in your segmentation. | Confirmation-to-completion rate by wallet provider. | Medium. Requires wallet detection logic and multiple copy variants. |
Campaign Landing Page Match | For users arriving from specific acquisition campaigns, create landing states pre-configured for the action advertised in the campaign. Compare activation rate versus generic homepage landing. | Activation rate by acquisition source. Connect-to-transaction rate for campaign traffic. | Medium. Requires campaign-aware routing and per-campaign UI states. |
The Bottom Line
Wallet connect is not activation. It is the beginning of the most fragile part of your growth funnel. The users you lose between connect and first transaction are users who showed up with intent and left because the product did not meet them with sufficient clarity, trust, or guidance.
Activation work is not glamorous. It does not produce big acquisition numbers or headline TVL figures. What it produces is a higher percentage of the users you are already paying to acquire actually becoming real protocol participants. Improving activation rate is often more valuable than increasing traffic volume. A higher share of existing traffic completing a first transaction compounds directly into the retention funnel without additional acquisition spend.
Once users activate, retention determines whether they compound into long-term protocol participants or churn after a single transaction. Activation is what gets them to the point where retention can do its work.
Diagnose and Fix Your Activation Funnel with Formo
You can’t improve what you can’t measure. Most DeFi protocols have a significant blind spot between wallet connect and first transaction because their fragmented analytics tools are siloed. A product analytics tool measures in-app events and their blockchain analytics tool shows confirmed transactions, with no clear links in between. Formo closes that gap by giving you full visibility of the DeFi user journey from first click to transactions onchain in one place. .
For DeFi teams working on activation, Formo provides:
Full funnel visibility from wallet connect to first transaction, with per-stage drop-off rates — powered by Formo's analytics
Acquisition source attribution so you can see which channels produce wallets that actually activate — via onchain attribution
Wallet-level segmentation by provider, onchain history, and lifecycle stage through wallet profiles, so you can pinpoint which wallet types are losing at confirmation
Cohort analysis to compare activation rates across acquisition periods, campaigns, and onboarding experiments — connected to retention analytics so you can see whether activated users actually stay
Ask AI to surface your activation bottlenecks directly, without SQL or a dedicated data analyst
DeFi teams including Kyberswap and WalletConnect use Formo to drive growth onchain.
Explore the Onchain Growth Series
This article is part of Formo's onchain series, a collection of practical guides for DeFi founders and growth teams covering the full post-launch lifecycle. Each guide goes deep on a single growth challenge with frameworks you can apply directly to your protocol.
FAQs About Onchain Activation
Why do people connect a wallet but never make a transaction?
People connect wallets out of curiosity, but many leave when they see fees, risk, or confusing next steps. Gas costs, scary warnings, and unclear value cause most drop-offs after connect. If the first action is not obvious, users stall. Wallet connect alone does not mean activation.
What actually counts as 'activation' in DeFi?
Activation in DeFi means a user completes their first meaningful onchain transaction. A connected wallet without a transaction is not an activated user. Signing a message or viewing a dashboard does not count. Activation starts when value moves or a contract is used.
Are gas fees the main reason users drop off?
Gas fees are a major reason users drop off, but they are not the only reason. Users also leave due to confusing wallet flows, fear of losing funds, and unclear outcomes. Even low gas chains see drop-offs if UX is bad. Lowering gas alone does not fix activation.
What part of onboarding causes the most users to quit?
The biggest drop-off usually happens right before the first transaction. This is where users face gas, approvals, and irreversible actions. If the UI does not clearly explain what will happen, users freeze. Most activation loss happens in the last step, not the first click.
Can you 'force' activation with rewards or bonuses?
No, rewards alone cannot force real activation if users do not understand the action or risk. Incentives may push a first transaction, but many users churn after. If the product is confusing, bonuses only create shallow activation. Real activation requires clear UX and risk clarity, not just rewards.
