Intent
Taps, impressions, and client “success” callbacks. Useful for UX. Dangerous as revenue. Intent events must carry a surface and a timestamp, not a money amount.
Method
Realtime event monitoring that finance can still read
This page is the short version of how Apieventstack watches freemium revenue events as they fire — without turning the live stream into a vanity wall. If you want the exercises, go to the course catalogue.
Start with the clock, not the model
Freemium teams often open a notebook on LTV or payback before they agree when a user “started.” Install, first open, trial start, and first paid receipt are four different clocks. Mixing them makes holiday campaigns look like a new baseline and makes organic cohorts look weak.
We ask every studio to write the clock in a sentence a controller would accept. Until that sentence exists, we do not discuss curves.
Three layers we refuse to collapse
Receipt
Store settlement lines: gross, tax, commission, refunds, chargebacks. This is cash-adjacent. It is slower than the client stream and occasionally revises last month.
Contract
The published definition: grain, owner, filters, refresh, and what the number is forbidden to mean. Without it, every new hire rebuilds the dashboard from folklore.
What we ignore on purpose
Creative testing, bidding, mediation waterfalls, and “AI insights” overlays. Those problems are real; they are not this studio’s work. Collapsing them into revenue analytics is how vanity metrics return through a side door.
One page
The artefact we care about most is a single event contract, not a 40-tile dashboard.
How this shows up in class
Flagship students spend week one renaming events. Week two joining a receipt file. Week three choosing a cohort clock. Only then do they sketch LTV. Short labs isolate one of those layers if you cannot take six weeks.