---
title: "Airdrop Retention Metrics: What to Track and How to Report It"
description: "The airdrop retention metrics worth tracking after a token drop, the cohort windows to use, and how to report the numbers honestly to investors and press."
author: "Shilika Jain"
date: "2026-10-28T01:06:50.255+00:00"
tags: ["airdrops", "retention", "tge pr", "pr metrics", "web3 marketing"]
canonical: "https://www.shilikajain.com/blog/post-airdrop-retention-metrics-reporting"
---

# Airdrop Retention Metrics: What to Track and How to Report It

By [Shilika Jain](https://www.shilikajain.com/authors/shilika-jain) - 10/28/2026

The airdrop retention metrics worth tracking after a token drop, the cohort windows to use, and how to report the numbers honestly to investors and press.

---

# Airdrop Retention Metrics: What to Track and How to Report It

The airdrop retention metrics that matter are cohort-based: of the wallets that claimed, how many used the product's core action again at 30, 90 and 180 days, split by whether they were users before the campaign or arrived because of it. Claim rate and holder counts are context, not retention. Report the cohort numbers with their definitions and time windows, and put the clean signal, activity from wallets that never received the drop, alongside them.

Most teams measure the drop itself very carefully and the months after it barely at all. That's backwards. The drop is a distribution event. Retention is the only part that tells you whether it worked.

## Why are most post-airdrop numbers misleading?

The numbers that are easiest to pull after a drop are also the least useful. Total claims, total holders and the number of wallets that interacted with the token in week one mostly measure how attractive the reward was. They say very little about whether anyone wants the product.

There are three distortions to keep in mind before you build any report:

- **A wallet isn't a person.** Farmers run many wallets, and real users sometimes use more than one. Every wallet-based metric overstates people.
- **Holding isn't using.** Someone can hold your token for a year and never touch the product. Holder retention tells you about the token, not the product.
- **Price moves everything.** If the token rallies, activity rises. If it dumps, activity falls. A retention figure taken in a strong week can look much better than the product deserves.

> user acquisition is hard but retention is harder!
>
> [Shilika Jain on X, 9 Nov 2023](https://x.com/Shilika_jain/status/1722591507897803125)

It's also harder to measure honestly, which is part of why so few teams report it.

## Which airdrop retention metrics should you track?

These are the metrics I ask clients to track after a drop, roughly in order of how much they tell you. None of them are perfect, so the table also says how farming distorts each one and where the number belongs.

| Metric | What it measures | How farming distorts it | Where it belongs |
| --- | --- | --- | --- |
| Core-action cohort retention (day 30/90/180) | Share of claiming wallets that performed the product's main action in each window | Least distorted, if "core action" is defined tightly | Investor updates, community updates, press with definition |
| Pre-campaign vs campaign-arrival split | Retention of wallets that used the product before incentives were announced vs those that arrived during | Makes farming visible rather than hiding it | Internal first, then investors |
| Post-drop new users (non-recipients) | Wallets doing the core action that never received the drop | Not distorted by the drop at all | Press and community updates |
| Fees or revenue from the recipient cohort | Whether recipients pay to use the product | Hard to farm | Investors, press if meaningful |
| Fast exit rate | Share of claimed tokens moved to exchanges or sold within the first 7 days | Inflated by farmers, which is useful information | Internal and investors |
| Holder retention at day 90 | Share of recipients still holding some of the drop | Inflated by passive holders and locked wallets | Context only |
| Claim rate | Share of eligible wallets that claimed | Inflated by farmers, who always claim | Context only |

The first two rows do most of the work. If you only have the bandwidth for two numbers, pick those.

## The claim-cohort ladder: four windows, three checks each

I frame post-drop measurement as a ladder of four windows. At each rung, you run the same three checks on the claiming cohort and the pre-campaign subset. The answers get written down before anyone drafts an update, so the narrative follows the data rather than the other way round.

**Rung 1: claim week.**
Count how many eligible wallets claimed, what share of claimed tokens moved to exchanges within 7 days, and which segments exited fastest.
This rung tells you about the audience you distributed to, not retention. Its job is to set a baseline.

**Rung 2: day 30.**
Measure the share of claiming wallets that did the core action at least once in days 8 to 30, compare pre-campaign users with campaign arrivals, and count any non-recipient wallets that started using the product.
This is the first honest look. Expect the campaign-arrival group to drop off sharply here.

**Rung 3: day 90.**
Measure the share of claiming wallets that did the core action in days 31 to 90, check whether that's one-off or repeat use, and work out what share of fees came from recipients.
I treat day 90 as the number to quote externally, because short-term reward hunting has usually played out by then.

**Rung 4: day 180.**
Check whether the day-90 cohort is still active, whether non-recipient users are now a larger share of activity than recipients, and whether a behaviour you never rewarded has emerged.
This rung is where you find out whether the drop seeded a user base or just a distribution list.

Getting these numbers isn't always easy for a small team. You need someone who can query on-chain data, not just read a dashboard.

> if the growth & BD teams knew how to write SQL, there would be better chances of analysing on-chain data to build effective marketing plans & valuable partnerships!
>
> [Shilika Jain on X, 25 Jan 2023](https://x.com/Shilika_jain/status/1618163344317505536)

If nobody in-house can do it, a short engagement with an on-chain analyst before the drop pays for itself. Agree the definitions and queries in advance, so day 30 isn't the first time anyone thinks about it.

## How should you define "active" after an airdrop?

This is where honest reporting is won or lost. A loose definition of active will make any cohort look healthy.

Some rules I use:

- **Active means the core action, not any transaction.** For a lending protocol, that's supplying or borrowing. For a wallet, it's sending or swapping. Claiming, transferring the airdropped token, or interacting with a governance contract doesn't count.
- **Set a minimum.** One dust-sized transaction shouldn't make a wallet active. Pick a threshold that fits your product and keep it.
- **Exclude incentive-driven activity where you can.** If a second rewards program started after the drop, separate wallets earning those rewards from wallets that aren't.
- **Keep the definition fixed.** Changing it between reports to make a number look better is the fastest way to lose an investor's trust.

Write the definition into every report, in one sentence. "Active: wallet supplied or borrowed at least $50 on the protocol in the window, excluding wallets participating in the Season 2 rewards program." That sentence is what makes the number believable.

## How do you report retention honestly in updates and press?

Different audiences need different levels of detail, but the same underlying numbers. Never run two sets of figures.

**Investor updates** get the full ladder, the pre-campaign split, the fast exit rate and what you're doing about it. Investors have usually seen worse numbers than yours, and they care more about whether you understand your cohort than about the cohort itself.

> classic problem of web3 startups: don't understand CAC, LTV, turnover or other basic metrics!
>
> [Shilika Jain on X, 8 Dec 2022](https://x.com/Shilika_jain/status/1600724726149574656)

An investor reading a post-drop update is checking for exactly that. Showing them you know what your drop cost per retained user, even as a rough estimate, separates you from teams that only report totals. The structure I use for investor and board reporting is in my [Web3 PR metrics dashboard](/blog/web3-pr-metrics-board-reporting-dashboard) piece.

**Community updates** get the day-30 and day-90 cohort numbers, the definition, and a plain statement of what changed in the product because of what you learned. Communities respond well to being shown the real number, including when it's low, as long as there's a plan attached.

**Press** gets one or two numbers at most: usually day-90 cohort retention and non-recipient growth. The fill-in-the-blanks sentence I start from for a press-ready line:

*"90 days after the airdrop, [X] of the [Y] wallets that claimed are still [core action] each month, and [Z] wallets that never received the drop have started using the protocol."*

Every part of it is doing a job: a retained count, a defined action, a time window, and a clean signal from non-recipients. That's a line a reporter can print without needing to fact-check a dashboard. I've written more on why farmed totals backfire in [inflated user numbers in crypto press](/blog/farmed-metrics-crypto-press-honesty).

## What's a "good" airdrop retention rate?

I won't give you a benchmark percentage, because I don't have a sourced one and I'd be wary of anyone who quotes one without a definition attached. Retention varies hugely by category: a wallet will see different patterns from a perp DEX, and a gaming project different again.

What I'd look for instead:

1. **Direction over level.** Is the day-90 cohort holding steady into day 180, or still falling?
2. **The pre-campaign group outperforming the campaign arrivals.** If they don't, something unusual is happening and it's worth understanding.
3. **Non-recipient activity growing.** This is the clearest sign the product has a life beyond the drop.
4. **Fees from a small cohort.** A few thousand retained wallets that pay fees can matter more than a large cohort that only farms the next program.

If your numbers look bad on all four, the problem probably isn't the airdrop. It's the product or the onboarding, and no amount of reporting will fix it. What to do about the people themselves, including who's worth re-engaging and who to stop chasing, is the subject of [converting airdrop recipients into real users](/blog/convert-airdrop-recipients-to-real-users).

## When shouldn't you publish retention numbers?

There are situations where publishing cohort retention does more harm than good:

- **Before day 30.** Early numbers swing too much and you'll end up correcting yourself.
- **During a token price crash.** Activity will be depressed for reasons unrelated to the product, and the number becomes a weapon for critics. Report it to investors, hold it for the community until things settle.
- **When the definition is still being argued internally.** Publish once, with a definition you'll keep.

The cost of holding back is that silence can look like you're hiding something. If you choose not to publish, say when you will. "We'll share 90-day cohort data in our [month] update" is better than nothing, and it commits you to the measurement. For the broader communications calendar after a token goes live, see my [post-TGE PR plan for the first 90 days](/playbook/post-tge-pr-first-90-days-2026), and for help building the reporting into a launch, my [token launch PR](/services/token-launch-pr) work covers it.

## FAQ

### Should we track retention by wallet or by person?

By wallet, because that's what you can measure, but say so in every report. If you have sybil clustering data, you can also report clustered entities alongside wallets, which gives a more honest picture of how many people you're actually retaining.

### Does staking the airdropped token count as retention?

Only if staking is your product's core action. For most projects, staking the reward token shows holder commitment, which is worth knowing, but it isn't the same as using the product. Report it separately.

### How soon after an airdrop should we start measuring?

Before it. Agree the definitions, the cohorts and the queries during campaign design, and snapshot the pre-campaign user list before the program is announced. Without that list, you can't separate real users from arrivals later.

### What if our retention numbers are really low?

Report them to investors anyway, with a diagnosis and a plan. For the community, pair the number with what you're changing. A low number explained well damages trust far less than a high number that someone later proves was inflated.

*Planning the reporting before your drop rather than scrambling after it? [Book 30 minutes with me](https://calendly.com/shilikajain/30min/) and we'll set up the cohorts and the story together.*

---

**Book a 30-min post-airdrop reporting review with Shilika** - https://calendly.com/shilikajain/30min/

Canonical: https://www.shilikajain.com/blog/post-airdrop-retention-metrics-reporting