Key Takeaways:
Win-back campaigns target dormant wallets that already transacted, not new users who have never engaged with your protocol.
Onchain signals reveal where churned users went, why they left, and what capital they moved, giving precision traditional marketing cannot match.
Segment churned wallets by churn cause before messaging. One broadcast to all dormant wallets wastes budget and credibility.
Reactivation rate alone does not measure success. Track second-transaction rate and 90-day retention to confirm durable re-engagement.
Do not launch a win-back campaign until the product issue that caused the original churn has been resolved and confirmed fixed.
What is a DeFi win-back campaign? |
A DeFi win-back campaign is a targeted re-engagement effort aimed at wallets that previously transacted with your protocol but have since gone dormant. It differs from a retention campaign in that it begins after churn has already occurred, using onchain signals to identify who left, why they left, and what offer is most likely to bring them back. |
A user finds your DeFi app, connects their wallet, executes a transaction, and disappears. You assume they are gone. They are not gone, they just have no reason to come back yet. Win-back campaigns exist to give them one.
This guide covers how to build a DeFi win-back campaign from scratch. It walks through six steps: defining a protocol-specific churn threshold, segmenting dormant wallets by onchain exit signal, diagnosing the churn cause, choosing the right re-engagement channel, writing messages that convert, and measuring whether the campaign created durable re-engagement.
Each section includes a worked example and a checklist you can apply directly to your protocol.
Why Win-Back Is a Different Motion from Retention
Retention campaigns target users while they are still active, reducing the likelihood they churn. Win-back campaigns start after churn has already happened. This is not a semantic distinction. It changes the data you need, the channels available to you, the message that converts, and how you measure success.
The economic logic for win-back is straightforward. A churned wallet already cleared the trust and friction barriers that make DeFi acquisition expensive. They connected a wallet. They signed a transaction. They accepted the risk of interacting with your smart contracts. The average cost to acquire a DeFi user who completes a first transaction runs to $85 per wallet, according to the Blockchain-Ads User Acquisition Trends Report 2026. Re-engaging a wallet that already crossed that threshold, and already knows your protocol, does not start from zero, and the acquisition cost does not apply again.
The mistake most DeFi growth teams make is treating win-back as a variant of retention, running a general re-engagement announcement to their entire community and calling it a campaign. That is not win-back. Win-back is a targeted, segmented motion using onchain evidence about who left, when, why, and where they went. The DeFi retention guide covers how to keep active users engaged. This article picks up where that one ends.
Your win-back readiness checklist
Before running any campaign, confirm:
☐ | You can identify wallets that transacted at least once but have not returned within your defined threshold |
☐ | You have an app-specific churn definition (not a generic 30-day lapse rule) |
☐ | You understand whether the product issue that caused churn has been addressed |
☐ | You have at least one channel to reach dormant wallets (Formo Wallet Intelligence export, email, paid crypto ad networks, onchain delivery, or direct community channels) |
☐ | You have defined what reactivated means: a specific onchain action, not a website visit |
Before You Start: What Onchain Data Gives You That Traditional Marketing Cannot
When a user churns from a traditional marketing context, you know when they last logged in and maybe why they cancelled. That is your entire dataset. When a DeFi user churns, the blockchain has a permanent, public record of every action they took, and every action they have taken since, on every other protocol.
That record lets you answer questions that are impossible with conventional re-engagement tools:
Did this wallet move capital to a direct competitor after leaving your protocol?
Was the user an experienced DeFi participant or a first-timer who got stuck?
Did they leave during a specific market event, such as a gas spike, a liquidation cascade, or a competing incentive launch?
Are they still active in DeFi, just not with you, or have they gone quiet entirely?
Illustrative example
A lending protocol notices a cohort of 400 wallets that deposited in November, were active for six weeks, then went quiet in January. A naive re-engagement campaign sends them all the same message. Onchain analysis tells a different story: roughly half migrated to a competitor that launched a higher-yield vault in January. A portion closed positions when gas spiked and never returned. Others are genuinely dormant across all DeFi. A small group repaid their loans and have no open position. They completed the job and left naturally. Four different situations, four different messages, one of which (the natural completers) is probably not worth targeting at all.
Formo's Wallet Intelligence surfaces this cross-protocol activity at the wallet level, showing where dormant users went, what they are doing there, and what their DeFi profile looks like, so you can segment before you message, not after.
Your onchain diagnosis checklist
Before building any segment, pull answers to:
☐ | When did the cohort last transact, and was timing correlated with any app or market event? |
☐ | Are these wallets active elsewhere in DeFi, or completely dormant? |
☐ | What was the last action they took on your app before going quiet? |
☐ | What was the median capital size of this cohort? High-value versus low-value changes the economics of every channel decision. |
☐ | Do any of these wallets now appear in competitor contract interactions? |
Step 1: Define Churn for Your Specific Protocol
How do you define churn for a DeFi app?
Churn for a DeFi app is when a wallet that completed your core action stops returning beyond your expected transaction cadence, adjusted for whether the user holds an open passive position.
The most common mistake in DeFi win-back is using a generic churn definition, "inactive for 30 days," copied from a conventional SaaS playbook. It is almost always wrong.
Churn in DeFi must reflect the natural transaction cadence of your core use case. A yield aggregator user who deposited six months ago and has not touched their position is likely not churned, they may be your most loyal user. A DEX user who has not swapped in 45 days is a meaningful dropout for an app where regular swaps are the core behaviour. A lending protocol borrower who repaid and withdrew is genuinely gone and worth targeting. Treating these three identically wastes budget and damages goodwill.
Protocol type | Core recurring action | Suggested churn threshold | High-risk false positive |
DEX | Swap | 30 to 45 days since last swap | LPs with open positions. They have not left. |
Lending protocol | Borrow and repay cycle | 60 days since last borrow or repay | Users with open positions still earning |
Yield aggregator | Deposit and withdraw | 90 or more days since last action | Passive depositors. Inactivity is expected. |
Perps and derivatives | Open and close position | 21 to 30 days since last trade | Users with open positions still running |
Illustrative example
A DEX with a concentrated liquidity model uses 45 days as its churn threshold for swappers. But it carves out any wallet that still has an active LP position. Those wallets have not churned, they are just not in the swap cadence window. The win-back campaign only goes to wallets with no open position and no swap in 45 days. This single cut dramatically improves the relevance of the outreach.
Your churn definition checklist
☐ | What is the core repeated action in your protocol? (swap, deposit, borrow, vote, bridge) |
☐ | What is the expected cadence for that action among active users? (daily, weekly, monthly) |
☐ | Are there passive states, such as open positions or staked assets, where inactivity is normal and expected? |
☐ | Have you carved passive-state wallets out of your churn definition? |
☐ | Does your threshold differ by user type? Power users and casual users may have different expected cadences. |
Step 2: Segment Before You Message
How do you segment churned wallets for a win-back campaign?
Segment churned wallets into four groups based on their onchain exit signal: high-value dormant wallets, users who hit a technical barrier, users who joined during a rewards programme, and users who left after a protocol incident.
Churned wallets are not a single audience. Sending one message to all dormant wallets is the fastest way to be ignored, and to waste the credibility you have with users who left for fixable reasons.
Four groups are worth treating differently in a win-back campaign:
Segment | Onchain signal | Priority | Why |
High-value dormant wallets | Large prior TVL or transaction volume, now quiet across all DeFi | Highest | Maximum return per reactivated wallet, lowest competition for their attention |
Users who hit a technical barrier | Left during a specific event: gas spike, UI change, failed transaction. Now partially active elsewhere. | High | They did not decide to leave; they were pushed out. Easiest to convert with a product-fix message. |
Users who joined during a rewards programme | Arrived during incentives, left when rewards ended, now farming elsewhere | Low to medium | Price-sensitive. Will return for the wrong reasons unless the product has genuinely improved. |
Users who left after a protocol incident | Left after a security incident, exploit, or protocol failure | Low initially, recoverable over time | Trust takes time. Premature outreach accelerates distrust. |
Natural completers | Repaid loans, withdrew positions, or completed a one-time action with no open state remaining | Lowest | No product failure to address. Only a new use case creates a reason to return. |
Illustrative example
A yield protocol runs a win-back campaign after noticing a large cohort went dormant six weeks after a rewards programme ended. Before messaging anyone, they pull wallet-level data and find: the majority of the dormant cohort is now active on a competitor with a similar incentive structure. A smaller share has gone completely quiet across all DeFi. A smaller group had above-average position sizes and their last action was withdrawing during a market volatility event, not correlated with the rewards programme at all.
The team runs three separate campaigns: a feature-update message for the high-value volatility group (highest priority), a general outreach for the fully-quiet cohort (lower conversion expected, but no competition), and nothing yet for the incentive joiners. They will wait until a genuine product improvement gives them something specific to say.
Your segmentation checklist
☐ | Have you separated wallets with prior high TVL or volume from low-value dormant wallets? |
☐ | Is there a correlation between churn timing and a specific event? (rewards end date, gas event, exploit, competitor launch) |
☐ | Are the dormant wallets still active elsewhere in DeFi, or completely dark? |
☐ | Do any of these wallets interact with direct competitors’ contracts? |
☐ | Have you excluded passive-state wallets (open positions, staked assets) from the win-back list? |
Step 3: Diagnose Why They Left
Why do DeFi users stop using a DeFi app?
DeFi users stop using a protocol for four reasons: yield migration to a higher-rate competitor, a technical barrier they could not get past, trust damage from a protocol incident, or natural completion of a one-time use case. Each requires a different win-back approach. The Blockchain-Ads User Acquisition Trends Report 2026 notes that DeFi users tend to be more financially savvy than users of other crypto verticals, and that credibility is their primary driver. A message that does not address the real reason a user left fails that credibility test immediately.
Four primary churn causes, each requiring a different campaign approach:
Yield migration
The user found a better rate and moved capital. The signal is a wallet that left during or shortly after a competing protocol's incentive launch and is now active there.
Win-back requires a genuine product reason to return: a rate improvement, a new vault type, a feature unavailable at the competitor. A "we miss you" message without substance will be ignored. A message that says "our Base vault now yields X% with no lock-up, compared to the 14-day lock at the category where you currently sit" is a different conversation.
Win-back message frame: Lead with the specific product improvement. Show the comparative advantage concretely. Give a time-limited reason to act. |
Technical barrier at a critical moment
The user hit a wall: a failed transaction during a gas spike, a confusing interface after a redesign, a broken mobile wallet flow, and never came back.
The signal is a wallet whose last action was an incomplete or failed transaction, or whose drop-off correlates with a UI change date. These are the easiest wins. They did not decide to leave. They got stuck.
Win-back message frame: Acknowledge the specific moment where friction occurred if you can identify it. Lead with what was fixed. Show the flow working. Make the first re-entry step smaller than the original point of failure. |
Trust damage from a protocol incident
The user left after a security incident, an exploit, a period of protocol instability, or a communication failure during a crisis. The signal is a correlated drop in wallet activity around the event date, particularly among wallets with larger positions.
Trust is the hardest churn cause to reverse. Campaigns that arrive before the app has demonstrably improved tend to accelerate permanent departure rather than reverse it.
Win-back message frame: Wait until you have concrete evidence of improvement: a completed re-audit, a sustained period without incident, a transparent post-mortem that has been publicly acknowledged. The message should open by naming what happened, not avoiding it. Never lead with an incentive for this segment, it reads as bribery. |
Natural use-case completion
The user finished the job your protocol was built for and has no reason to return. A wallet that bridged assets once, used your DEX to swap into a position, and then moved on.
These wallets are the hardest to win back because there is no product failure to fix. The only angle is a new use case, a feature or vault type that creates a reason to return that did not exist before.
Message frame: Lead with the new capability as a product announcement, not as a re-engagement request. The user has no unresolved issue to acknowledge.
Your diagnosis checklist
☐ | What was the last action each segment took before going quiet? |
☐ | Is there a correlation between churn timing and an app event, market event, or competitor launch? |
☐ | Did any churned wallets have a failed or incomplete transaction as their last interaction? |
☐ | Is there a trust event in your app history that coincides with a churn spike? |
☐ | For yield-migration wallets: do you have a genuine product improvement to message, or are you asking them to return to the same product? |
Step 4: Choose the Right Channel
How do you reach churned wallets?
DeFi win-back has a channel constraint that does not exist in conventional re-engagement: most of your churned wallets appear anonymous. A wallet address alone gives you no email and no social handle. The channels available to you depend entirely on how much identity data you can resolve from that address.
Channel | Best for | Key requirement |
Institutional users, high-value B2B users | Formo resolves wallet addresses to social profiles including X handles and email. Export a churned segment and contact users directly. | |
Ads on social platforms (X, LinkedIn) | Broad dormant cohorts | Works best when wallet data is layered with email or social identity from a Formo export. |
Direct community channels (Discord, Farcaster, Telegram) | Small, high-value segments | Not scalable. Higher conversion per contact when the personal touch matters. |
Formo's Wallet Intelligence resolves anonymous wallet addresses into social profiles, including X handles and email addresses. You can build a segment of churned wallets using Formo's user segmentation, export the segment with social contact details, and reach those users through the channels they already use, without requiring any prior email capture from your protocol.
Your channel selection checklist
☐ | Have you built a segment of churned wallets in Formo using lifecycle stage or last transaction date? |
☐ | Have you exported the segment with resolved social profiles (X, email) from Formo Wallet Intelligence? |
☐ | For high-value dormant wallets with no social profile: is onchain incentive delivery in your budget? |
☐ | Is your segment small enough that direct community outreach (Discord, Farcaster, Telegram) is feasible at quality? |
Step 5: Write Messages That Convert
What makes a DeFi win-back message effective?
An effective DeFi win-back message names what specifically changed since the user left and makes a single time-limited ask. Generic incentive offers without context do not convert.
The most common failure in DeFi win-back messages is leading with an incentive. "Come back and earn 10 USDC" reads as generic to an audience that evaluates protocols on rates, security records, and product depth. It also trains the wrong behaviour: users who return for the incentive but churn again immediately.
High-converting win-back messages share three characteristics:
They are specific about what changed.
Not "we've improved the app" but "gas costs on our Base deployment dropped from an average of $18 per transaction to $0.90 after our v2 migration. Your last transaction cost you $22." Specificity is evidence of competence. It also signals that you understand why the user left, which is the most trust-building thing a win-back message can do.
They make a concrete, time-limited ask.
"Come back whenever" is easy to defer forever. "Your position tier from November is still available if you reconnect before [date]" creates a decision point. The offer does not have to be a token incentive, it can be a feature window, a rate lock, or a whitelist spot.
Message structure that works
Effective win-back message structure: open with what happened to their prior activity, then name what has changed since they left, then give one concrete action to take and a reason to take it before a specific date. |
Worked example: user who hit a technical barrier
Example win-back message |
"In October, your transaction to open a lending position failed during a gas spike. You paid $31 in gas with no confirmation. That failure rate on the same flow is now under 1% after our v2 deployment. Gas on Base averages $0.60 for the same transaction. If you want to try again, this link reopens to your prior position parameters." |
That message is not trying to sell anything. It acknowledges a failure, proves it was fixed, and removes the specific barrier that caused the churn.
Your message checklist
☐ | Does it name what has changed since the user left: a specific product improvement, not a vague claim? |
☐ | Is the ask a single, clear onchain action? |
☐ | Is there a time-based reason to act now rather than later? |
☐ | For post-incident segments: does the message name the event directly, rather than ignoring it? |
☐ | Does the message avoid leading with a token incentive as the primary reason to return? |
Step 6: Measure Win-Back Correctly
Which metrics should you track for a DeFi win-back campaign?
Track four metrics for a DeFi win-back campaign: reactivation rate, second-transaction rate, retention cohort after reactivation, and cost per reactivated wallet versus new-user CAC. Track each in isolation from new-user data, or the results will be uninterpretable.
The most common measurement failure is mixing reactivated wallets into your new-user cohort, which inflates apparent acquisition numbers and obscures whether the campaign created durable re-engagement. The Blockchain-Ads User Acquisition Trends Report 2026 reports that only 32% of DeFi users who connect a wallet go on to complete a first transaction. Just as that first-to-second-action gap reveals whether a new user is genuinely engaged, the same logic applies to reactivated wallets: reaching a second transaction is the clearest signal that the original re-engagement problem has been solved, not just temporarily bypassed.
Four metrics to track, isolated to the win-back cohort:
Metric | What it tells you and what to watch for |
Reactivation rate | The percentage of targeted dormant wallets that execute at least one meaningful onchain transaction within a defined window after the campaign. A session or wallet connection does not count. A transaction counts. |
Second-transaction rate | Of wallets that reactivate, how many execute a second transaction within 30 days? A high reactivation rate paired with a low second-transaction rate means the campaign brought users back for one action but did not restore genuine engagement. |
Retention cohort after reactivation | Track reactivated wallets as a separate cohort over 60 and 90 days. If they churn again at the same rate as their original departure, the campaign masked the problem temporarily without fixing it. |
Cost per reactivated wallet vs. new-user CAC | Compare all-in campaign cost divided by reactivated wallets against your standard cost per newly acquired active wallet. The Blockchain-Ads 2026 report puts average DeFi CAC at $85 per wallet. If reactivation costs materially less, the economic case for win-back over acquisition is clear. |
If reactivated wallets are not tracked as a separate cohort from new users, you will never know whether your win-back campaign worked, or whether it appeared to work because something else was driving organic return at the same time. |
Your measurement checklist
☐ | Are reactivated wallets tracked as a separate cohort from new users? |
☐ | Have you defined reactivation as a specific onchain transaction, not a page view or wallet connection? |
☐ | Are you measuring second-transaction rate, not just reactivation rate? |
☐ | Is the 60 and 90-day retention cohort after reactivation set up before the campaign launches? |
☐ | Do you have a CAC benchmark to compare cost per reactivated wallet against? |
☐ | Are you attributing reactivation to the campaign specifically, not to organic return that happened concurrently? |
The Bottom Line
The dormant wallet base most DeFi apps accumulate is not a graveyard. It is a segmented audience of users who already cleared every trust and friction barrier that makes DeFi acquisition expensive, and who, for specific and often addressable reasons, have not returned. Win-back campaigns that treat this base as a single undifferentiated list will fail. Win-back campaigns that use onchain signals to identify who left, why they left, and what has changed since, will consistently outperform equivalent acquisition spend on high-value segments.
The onchain retention guide covers how to prevent churn before it happens. The DeFi growth experiments framework covers how to run structured tests on win-back messages before scaling them. The user lifecycle analysis shows how win-back fits into the full post-launch user journey.
Re-Engage Dormant Wallets with Formo Formo gives DeFi growth teams the onchain data to run win-back campaigns that work at the segment level, not the broadcast level. What you get with Formo: • Identify dormant wallets by your app-specific churn definition, not a generic lapse window • Segment churned wallets by prior value tier, churn timing, and cross-protocol activity • Surface where your dormant users went after leaving, and which competitor contracts they are now using • Export churned wallet segments with resolved social profiles (X, email) for direct outreach on any channel • Track reactivation rate, second-transaction rate, and retention cohort after reactivation as isolated groups |
More in This Series
Exploring DeFi growth strategy? Read the other articles in this series:
DeFi User Win-Back Campaigns (current article) |
Frequently Asked Questions
What is a DeFi win-back campaign?
A DeFi win-back campaign re-engages wallets that previously transacted with your protocol but have since gone dormant. Unlike retention, which keeps active users engaged, win-back starts after churn has already occurred. It uses onchain signals to identify which wallets to target, why they left, and what message is most likely to bring them back.
What is the difference between DeFi win-back and traditional re-engagement?
DeFi win-back differs from traditional re-engagement because it uses onchain data rather than lapse days or email open rates. Traditional tools know when a user last logged in. DeFi win-back can read where a dormant wallet went after leaving, what protocols it is now active on, how much capital it moved, and what its last failed interaction was, making segmentation far more precise.
How do I reach churned wallets if I do not have their email addresses?
Formo's Wallet Intelligence resolves anonymous wallet addresses into social profiles, including X handles and email addresses. Build a segment of churned wallets in Formo, export it with contact details, and reach those users on the channels they already use.
When should I not run a win-back campaign?
Do not run a win-back campaign until the product issue that caused the original churn has been fixed and verified. Returning users to the same broken experience accelerates permanent departure. For users who left after a security incident, wait until you have a completed audit, a public post-mortem, and a sustained period without incident before reaching out.
How do you measure the success of a DeFi win-back campaign?
Measure DeFi win-back success by second-transaction rate and 90-day retention, not reactivation rate alone. A reactivated wallet that completes a second transaction within 30 days and retains at a higher rate than its original cohort over 60 and 90 days signals a genuinely solved re-engagement. One-time reactivation without those follow-on signals means the underlying problem was masked, not fixed.
