Web3 growth metrics: measuring retention after incentives

A campaign can attract new addresses and reward claims without creating a lasting reason to use the product. Track participants from their first meaningful action to repeat use, and record which channels and incentives brought them to the product.

Block Consult3 min read
In this article
Figure · Growth

Define the action that delivers product value

Choose an activation event that represents the product doing its job. For a developer service, that could be a successful production request. For a marketplace, it could be a completed purchase. Signing in, connecting an account and claiming a reward may be necessary steps, but they should be reported separately from the outcome the product exists to deliver.

Specify the event precisely: which action counts, whether it must succeed, how test environments are excluded and how duplicates are handled. Agree the definition before the campaign begins. Keep it consistent across channels so a change in instrumentation does not look like a change in adoption.

Be clear about what you are counting

An address count is not automatically a count of people. Ethereum's account guide explains that a wallet can manage several accounts and an account can be accessed through several wallets. For analysis, label the unit you can observe: accounts, addresses, organisations or authenticated users. Do not silently switch between them.

Maintain explicit rules for internal test activity, known service accounts and suspected duplicate participation. Keep the unfiltered totals available alongside the filtered view. Automated activity can be legitimate demand for an infrastructure product, so classify it according to the use case rather than treating every bot as irrelevant.

Build cohorts with a complete observation window

Group participants by when they activated, their acquisition channel and their exposure to incentives. A cohort follows a group sharing an entry condition over time; Google's cohort documentation distinguishes that entry condition from the action that counts as a return. Apply the same distinction to your product events.

Keep inactive accounts in the denominator. Otherwise the report improves simply because departed participants disappear from it. State whether a metric uses a specific day, a fixed interval or any later return: those definitions answer different questions and cannot be compared as if they were the same measure.

Separate product use from the reward mechanism

  • Acquisition: how many eligible accounts arrived from each channel?
  • Activation: how many completed the defined product action?
  • Reward participation: how many claimed or received an incentive?
  • Retention: how many repeated the product action in the agreed window?
  • Cost: what did the campaign cost per activated account and per retained account?

For the cost calculation, state which campaign spend, distributed rewards and operating expenses are included, and how token amounts are valued. Keep gross product fees separate from incentives and other costs. A rise in activity during a reward period does not, by itself, show sustainable demand. Check the economics of that activity.

Compare mature cohorts before, during and after an incentive programme, accounting for changes in product, channel mix and market conditions. These comparisons can reveal useful patterns, but they do not isolate the incentive's causal effect. Where feasible and appropriate, a planned experiment can provide stronger evidence than a before-and-after chart.

Use the report to choose the next experiment

If acquisition is strong but activation is weak, inspect onboarding and the first successful action. If activation is healthy but repeat use fades, investigate whether the underlying task recurs and whether the product solves it well enough. Speak with willing participants about the friction they encountered; aggregate activity alone rarely explains their reasons.

Keep a short experiment record with the audience, hypothesis, one primary outcome, observation window and spending limit. Decide when to stop or revise the campaign before scaling it. Use the findings in go-to-market planning, community development and Web3 outreach.

Frequently asked questions

Is a reward claim an activation event?
It can be a campaign participation event. Treat it as product activation only if it is the meaningful outcome your product is designed to deliver, and document that choice before measuring the campaign.
What is a good retention rate for a Web3 product?
There is no single threshold that suits every product or usage frequency. Define the action and observation window, compare like-for-like cohorts and relate the result to the product's operating economics and expected use.
Does better retention after a campaign prove the campaign worked?
It is evidence worth investigating, but other changes may explain part of the result. Record product changes, audience differences and market conditions, and use a suitable experiment when the decision needs a causal estimate.
Contact

Let's build something durable.

Tell us about your project. We reply within two business days.

EssentialAs needed
We use storage to keep portal sign-in secure, verify invitations and remember that you’ve seen this notice. Security controls also help protect the site.
Your preferences and toolsWhen you use them
Your browser can save your chosen theme, chat conversation in this tab, simulator model and workspace preferences. You can clear this data in your browser settings.
Analytics and advertisingNot used
We don’t use Google Analytics, advertising pixels or cross-site tracking. We use Search Console to see how the site appears in Google Search; it adds no tracking script to this site.

Acknowledging this notice does not give consent to tracking. We will ask for your consent before adding optional tracking.

Cookie policyPrivacy policy