They didn't churn. They got frustrated.
A cohort curve tells you when people stopped coming back. The crash, the rage click, the screen that took nine seconds to draw — those tell you why. Cxorbi keeps both, on the same session, long enough for you to find them.
Retention
How many users come back, by first-seen week.
Average retention curve
Cohorts by first-seen week
Churn is a symptom. Friction is the disease.
By the time a retention curve visibly bends, the thing that bent it happened weeks earlier, in a session nobody watched, to a user who never filed a ticket. The only way to answer it later is to have kept the evidence at the time.
By sessions
not by log volume
Errors and crashes are ranked by how many sessions they touch, so the costliest one surfaces — not the noisiest.
p75
Core Web Vitals
The percentile that reflects a bad day for a real user, on web and on mobile.
1
session id
A cohort, an error and a survey answer resolve to the same user without a join you have to write.
3
platforms
Web, iOS and Android, from one SDK and one identity.
Solve your most critical retention challenges
Stop losing people to friction
Rage clicks, dead clicks and errors, surfaced on the sessions they actually spoiled.
Fix the bug that actually costs you
The loudest error is rarely the costliest. Rank by sessions affected and the order changes.
Say something before they go
Ask the people showing churn signals what went wrong, then answer them in the product.
Retention
How many users come back, by first-seen week.
Average retention curve
Cohorts by first-seen week
Retention & Cohorts
See who comes back, and when they stop
Group users by when they arrived or what they first did, then watch each cohort's curve — so a drop is attached to a group of people rather than to a month.
- Retention curves by cohort, week over week and month over month
- Compare cohorts by platform, acquisition week or first action taken
- Drop from a cohort into the individual sessions inside it
Error Analysis
Prioritize technical errors, UX friction, and product-flow issues by session impact.
Showing 3 of 128 issues
Errors & Crashes
Rank bugs by the people they cost you
A stack trace count tells you which error logs the most. Session impact tells you which one is quietly costing you a cohort.
- Web errors and mobile crashes ranked by sessions affected
- The screen, release and device it happened on
- Open the replay of a session that hit it and watch the moment it broke
Web Performance
Core Web Vitals (RUM) at the 75th percentile, by device and page group.
p95 4.12s · n=1284
p95 2.61s · n=2140
p95 402ms · n=1180
p95 240ms · n=2012
p95 0.184 · n=1284
p95 0.092 · n=2140
Worst page groups
Right-click a page group to open it in Journeys or Heatmaps.
Performance
Slow is a churn reason too
Nobody writes a review about latency. They just stop opening the app. Core Web Vitals at p75 on web, cold start and screen render on mobile.
- Core Web Vitals at p75 — the percentile a real bad day lives at
- Mobile cold start and screen render times, per release
- Tie a slow screen to the sessions that gave up on it
In-app Nudges
Winter release announcement
Draft setup: Banner · Event trigger
Version 4
2d ago
Planned maintenance
Draft setup: Banner · App open
Version 2
6d ago
Welcome message
Draft setup: Modal · Route rule
—
—
Delivery summary
Read-only lifecycle totals from the selected project.
IMPRESSIONS
12,480
ACTIONS
2,317
COMPLETIONS
1,904
DISMISSALS
806
UNIQUE SUBJECTS
9,142
RENDER FAILURES
12
Backend window: 2026-07-06 to 2026-08-05
In-App Messages
Answer them inside the product
Finding the friction is half of it. Publish a banner, a modal or an inline message to the exact audience that hit it, without shipping a release to do it.
- Banners, modals and inline messages, published to a targeted audience
- Target by behaviour, page, screen or cohort
- Change the copy without waiting on an app store review
Keeping people takes more than one team
Engineering
Fix the error that costs the most sessions instead of the one that logs the loudest, with the recording attached.
For engineersProduct
See which cohorts stay, which ones fade, and what the fading ones ran into on the way out.
For product managersDesign
Find the interactions people fight with — the ones that never make it into a bug report.
For designers