Unreal Ops Platform
Unreal Ops Analytics
Traffic and events on the project Monitor already watches.
Crash data tells you what broke. Analytics tells you what was happening before that, and what happens on the days when nothing breaks at all: which pages people reach, where they came from, and what they did once they arrived.
Analytics counts the traffic on this site and on monitor.unrealops.ai today, and you can create a write key without asking anybody. Funnels, retention and cohorts are the analysis it does not do yet. There is no billing, so nothing here can be bought and nothing here has a customer.
Aggregated on the way in
There is no row per event. Counts are rolled up as they arrive, which is why a year is as quick to read as a day, and why a drop in traffic and a spike in errors on the same release are one investigation rather than two tools you line up by hand.
Sessions are worked out on the server from what actually arrived, rather than trusted from a number the client sends, so a client that gets it wrong does not move your figures.
The trade is worth knowing before you choose it. Analytics answers the questions its breakdowns were built for, and it cannot go back and answer a new one about last month, because the individual events are not kept to re-ask.
What Analytics does
Everything in this grid runs today, on this site and on Monitor's.
Page views and custom events
A typed event call from the same SDK surface the rest of the platform uses, so you are not wiring a second vendor into your app to answer one question. The browser script is one file, small enough to read before you decide to trust it.
Visitors and sessions
Derived on the server from the events that arrived, so the number does not depend on the client being honest or on a timer surviving a background tab.
Breakdowns that already exist
Event, path, referrer, platform, country, device, operating system, release and environment. Any of them against any date range.
Release and environment aware
The same release and environment Monitor reports crashes against, so traffic and stability are read on the same axis rather than two that nearly line up.
Privacy by default
Events you define rather than blanket auto capture, no third party advertising identifiers, and deletion by user id when somebody asks.
The same project as Monitor
One project can receive from an app and from the website that sells it, reported together rather than side by side.
Who it is for
- Teams already using Monitor who want traffic and product data under the same account.
- Developers who want events without a heavyweight analytics install.
- Operators who need five reliable numbers, not a hundred unreliable ones.
One account, one project, one SDK surface
Analytics is not a separate product with a separate login. It reads the same project as Monitor: same app, same releases, same environments, same teammates.
That is the entire reason to build it here rather than bolt on somebody else's. Two tools that already agree on what a release is beat two tools you reconcile by hand every time something looks wrong.
The rest of the platform
Analytics shares its account and its project structure with everything else Unreal Ops builds. The full build order is on the platform overview.
Requirements, not signups
Tell us which question it should answer next.
Funnels, retention and cohorts are the obvious gaps, and which of them matters first depends on what you actually measure. That is cheap to absorb now and expensive once the schema is settled.
Say what you measure today and what you gave up trying to measure, and it will shape what gets built.
Every product here is built by Unreal Ops. Nothing on this site can be bought yet, and nothing has a customer. When that changes, these pages change with it.
Monitor, in its own words: what it stores and what it drops, how long it keeps it, and who answers.