FOR GROWTH TEAMS

Know what your incentives actually bought.

Campaign spend buys transactions — but which ones? Separate real usage from mechanical check-ins, see which cohorts stay after the reward ends, and test eligibility criteria before announcing them.

concept

100,000 CLAIMERS · WHAT THE SPEND ACTUALLY BOUGHT

22% real usage

stayed & transacted organically

61% scripted check-ins

one button, machine cadence

17% claim-and-gone

one transaction, never again

RETENTION · real vs scripted

84% / 31%

61% / 9%

D30

44% / 3%

ELIGIBILITY SIMULATOR · next drop

✓ ≥ 3 protocols used✓ ≥ $50 moved✓ human cadence✓ active before campaign

8,412 addresses would qualify — 9.6% of last drop's claimers, 71% of its real usage

test the rule against real behavior before you announce it

How much of my "usage" is one scripted button?

Which claimers stayed a week later?

What would this airdrop rule actually select?

already real underneath

In our window, one app’s daily check-in button produced 91,283 transactions from 88,169 addresses — 9% of the entire chain, counted as “usage” by every dashboard.

Would you use this? What would you ask it first?

Tell us → bartosz@research.tech

← all use cases