Web3 Companies Suck at analytics and understanding user behavior. (Here’s how it should be done.)
The truth is, most Web3 companies suck at understanding fundamental insights and data about their users. Most chase metrics that look good on paper (and to investors) but reveal almost nothing about real people or lasting engagement.
The Musical Chairs Problem
At its core, Web3 today feels like a giant game of musical chairs. There’s a limited pool of active users, the same rotating capital, and the same Total Value Locked (TVL) being shuffled from one protocol to another. TVL, DAUs, MOUs etc has become a vanity metric impressive on leaderboards, but often meaningless for actual product health…or revenue lol.
The pattern plays out the same way every time:
A project launches → dangles juicy (or aggressively mid) incentives → attracts a flood of users chasing $ → rolls out a familiar product (DEX, perps, lending, aggregator, you name it) → users extract maximum value → project pumps more incentives → cycle continues until the money runs dry → silence.
Then the blame game starts. Technical founders point fingers at marketing for not “selling” the vision. The CMO gets pushed out because expectations and reality were never aligned. Business development can’t land partnerships (That make sense). Product roadmaps stall because engineering dismisses UX concerns (“mUh DoN’t tOuCH MuH cOdE”). Everyone’s frustrated, but the real question haunting every founder remains the same:
“Where are our actual users? Our loyal users? Our real partners?”
Why Current Analytics Don’t Cut It
We have no shortage of dashboards. Wallet trackers, transaction volumes, inflow & outflow charts— they’re everywhere. But they tell an incomplete story.
Tracking wallet addresses doesn’t reveal who’s behind them. Volume can be gamed through wash trading, bots, or speculative swings. These metrics create the illusion of activity without showing genuine demand or stickiness.
What’s missing is depth. We need to understand who is using our products, why they’re using them, when they engage, and how they behave over time. Without that, we’re building in the dark.
Behavior: The Pattern That Reveals Everything
Behavior is the signal hidden in all that noise.
Every interaction, swaps, deposits, bridging, staking, and even inactivity leaves a trace. When you piece those traces together, you start to see patterns. Patterns reveal intent. Intent lets you build better products, target the right users, and focus efforts where they actually matter.
This isn’t new. Traditional businesses have mastered it. Retail giants know your shopping habits, favorite categories, and purchase frequency. They use that to make offers feel personal, not random. Law enforcement builds profiles from past actions to predict future ones. Governments track behavior at scale, we’ve all seen where that leads.
Web3 has resisted this kind of insight, partly for good reasons (privacy fears), partly because the tools just aren’t there yet. But ignoring behavior entirely leaves projects guessing about what users really want.
The Privacy Tightrope: Having Your Cake and Eating It Too
The good news? We don’t have to choose between useful insights and strong privacy.
It’s possible to understand user behavior deeply while protecting individual rights. The key is designing systems that give teams the aggregated patterns they need without ever exposing or owning raw personal data.
Here’s how it can work (How we make it work):
- Collection via SDK Integration: Embed a lightweight SDK into your dApp or wallet. It observes on-chain and in-app actions anonymously as users naturally interact.
- Profile Building with Machine Learning: Use ML models to analyze those actions and build behavioral profiles identifying segments like long-term holders, frequent traders, or yield chasers without tying them to identities.
- Anonymization through Cryptography: Apply zero-knowledge proofs and advanced encryption to ensure insights are useful, but data remains private. Teams see trends and patterns. No one sees individual records. No central honeypot of personal info.
This approach gives you the best of both worlds: actionable intelligence for product decisions, without creating a surveillance-style database that could be hacked, sold, or abused.
So What Does Real Privacy Actually Look Like?
Real privacy isn’t about collecting nothing. That’s unrealistic, and it starves products of the feedback they need to improve.
Real privacy means collecting what’s necessary, protecting it fiercely, and ensuring it can’t be exploited even if a system is compromised.
It means building privacy into the foundation, not tacking it on later.
It means no more massive breaches leaking sensitive data because it was stored carelessly.
It means users get better experiences, relevant features, and smarter recommendations without feeling watched or losing control.
Businesses get the behavioral insights to survive and grow. Users keep ownership of their data. Everyone wins.
Web3 won’t mature until projects solve the user understanding problem. You can’t build sustainable products when you don’t know who’s using them or what they actually need.
But we don’t have to copy Web2’s invasive playbook to get there. The technology exists today, in the form of SDKs, machine learning, and zero-knowledge cryptography, to deliver deep behavioral insights with genuine privacy.
The choice is clear: keep playing musical chairs with the same transient users, or start building systems that attract and retain real ones.
For founders reading this: implement privacy-first behavior analytics before your runway runs out.
For users and builders: demand it from the projects you support.
The tools are ready. The question is whether we’ll use them to create something better or keep repeating the same mistakes.
Want to understand your users?
Want to start tracking and measuring the right things?
Sign up here.
Follow the team
Follow our founder
Follow our writer
