Glossary: Revenue Analytics
Revenue analytics shows how a product or protocol earns money across fees, spreads, subscriptions, and other sources. In DeFi, it helps separate revenue kept by the protocol from trading volume and token incentives.
What is Revenue Analytics?
Revenue analytics organizes income events such as swap fees, lending spreads, or subscription payments across contracts and chains. Consistent event definitions and price timestamps help teams compare products, users, and periods without confusing revenue with volume or incentives.
Revenue Analytics Explained
Onchain revenue rarely shows up as a single clean number. It's scattered across swap fees, protocol take-rates, MEV rebates, subscription payments in stablecoins, and NFT royalties, often spread across multiple chains and contracts.
Revenue analytics pulls these signals together into a coherent picture: how much a protocol earned, where it came from, and how it's trending. Instead of manually parsing contract events or reconciling multiple explorers, teams get a single source of truth that ties revenue to specific products, fee tiers, or user cohorts. This turns raw transaction data into the kind of financial reporting a business actually runs on.
What Revenue Analytics Means For
Audience | Use Case |
|---|---|
Protocol teams | Track fee revenue by product line to see which features actually drive income |
Finance and ops | Produce reliable revenue reporting across chains without manual reconciliation |
Investors and DAOs | Evaluate protocol health and sustainability using real, verifiable onchain earnings |
Examples
A DEX tracks swap fee revenue by pool to identify which trading pairs are most profitable.
A lending protocol breaks down interest spread revenue by asset to decide where to adjust rates.
A DAO treasury team reports monthly protocol revenue to token holders using onchain fee data.
An NFT marketplace attributes royalty revenue to specific collections to inform partnership decisions.
Crypto and DeFi example
A lending protocol can report interest spread and liquidation fees separately by market and chain, then compare those amounts with deposits and active wallets. This prevents large loan balances or transaction volume from being misreported as revenue and makes changes in fee policy easier to evaluate.
Related reading
Explore Protocol Revenue, Revenue Attribution, Revenue per Wallet, TVL, and DeFi Analytics.
FAQs
What counts as onchain revenue?
Revenue is value a protocol recognizes under its accounting definition, such as fees retained by the protocol. Gross trading volume, user deposits, and fees passed to liquidity providers are not automatically protocol revenue. State which contracts, fee recipients, assets, and time period are included.
How is revenue analytics different from volume analytics?
Volume analytics measures the value of activity, such as swaps or loans. Revenue analytics measures the fees or other income the protocol retains under a stated method. High volume does not necessarily produce high revenue.
Why can onchain revenue attribution be difficult?
Revenue may be emitted or transferred across multiple contracts, pools, recipients, and chains. Teams must identify qualifying fee events, account for splits and token prices, and define how the revenue is linked to a campaign; a transaction’s volume is not a substitute.
Can revenue analytics compare revenue across multiple chains?
Yes, if the data covers the relevant contracts and applies consistent definitions, token pricing, fee-recipient rules, and time periods. Disclose gaps and avoid double counting assets or fees moving between chains.
The data platform onchain apps
Get actionable analytics and attribution for crypto and DeFi.
Stay up to date with weekly product updates and the latest industry insights.
Platform