FOR PROTOCOLS

Know what your users actually do.

Your analytics count function calls. The reading layer sees journeys: who arrived, what they tried, what they did next, and which of your “users” are users at all.

who actually pays
self-paid751,514
someone else paid248,486

A quarter of all activity runs on someone else's gas. If you count addresses, you are counting budgets.

what “usage” can hide
91,283

transactions — 9% of the whole chain — were one app's daily check-in button, pressed by 88,169 addresses. Every dashboard counts that as engagement.

concept
the journey console — what this becomes
100%
arrived
64%
first success
31%
second action
12%
still here day 7

Between every pair of steps: the exact place users stop, what stopped them, and whether it was your contract, their wallet, or a broken integration — with the cohort you could win back.

Where exactly do new users stop — and why?

Which integrations send us malformed transactions?

What do our best users do after they leave?

Run a protocol? Which of these would move a decision this quarter?

bartosz@research.tech