See who keeps using your app.Know what each release did.
Omni tracks retention day by day, split by app version, device and country. It reads every release you ship to see what it did to new and existing users, and explains what changed. When people drift away, it writes a win-back email to your list and sends it with your OK.
Retention loopRound 1Omni reads and writes; you approve what goes out.
Scribo · retentionActive again, by day since install
Numbers in the loop and the chart are Scribo's real data, October 17–21, 2026. The email is an example.
Know who stays,
and why.
Omni reads every day of your app's life and every version you ship. You decide what to change.
Tracks who comes back, day by day
Every install starts a group. Omni counts who's active again on day 1, 2, 3 and on, or week by week, only once that day has fully passed, and splits it by app version, device, platform or country.
Day-7 retention · by version
Reads what you shipped
Omni follows your commits, pull requests and App Store releases, notices new or silent events, and writes down what changed in plain words, so a dip or a jump has a cause next to it.
What changed in 2.4
- Daily review moved to the home screen
- New event “review_streak_kept”
- “widget_opened” went silent
Tells you what each release did
New users who started on the new version are compared with the ones on the version before. Existing users are compared with themselves, the week before updating against the week after. Omni calls it: up, down, no clear change, or not enough data.
2.4 · existing users, week after updating
Up · active days +0.6 a week, 95% interval +0.2 to +1.0
2.4 · new users, day-7 retention
No clear change · 26% vs 21%, interval −3 to +13 pts
Keeps renewals and cancellations in view
From RevenueCat or Stripe, Omni records every renewal, cancellation, expiry and billing issue, so you see subscribers leaving next to the release they left after.
Subscriptions this week
41
Renewed
9
Cancelled
6
Expired
2
Billing issue
Brings people back by email, with your OK
Omni writes a win-back email and, once you approve it, sends it to a segment you keep in Resend, with an unsubscribe link and no repeat sends. Then it reports opens, clicks and App Store downloads from that email.
Win-back · results
38%
Opened
9%
Clicked
14
Downloads
Cards above are examples. The Scribo numbers below are real.
Scribo's reminders didn't bring people back.
Scribo asks new users during onboarding whether it can send reading reminders. Among new installs, the ones who said yes came back after day one 29% of the time. The ones who said no came back 35% of the time. The ones who quit onboarding before the question came back 14%.
What predicted coming back wasn't the reminder. It was getting through onboarding at all, which is the same leak the activation read found.
An early signal, not a verdict
Five days of data and a day-one window: too short to call. Omni's day-7 read on these groups lands once each has a full week.
From Omni's change log
Version 2.4.1 is out (first seen 2026-10-21): 2% of yesterday's people are on it.
Scribo on iOS · PostHog events, October 17–21, 2026 · day-by-day curve: 62 installs from October 17–18
Active again, by day since install
Came back after day one
22 of 75 new installs
12 of 34 new installs
4 of 29 new installs
Connect what your app already uses.
Product events show who comes back. Your code and store show what changed. Your email list reaches the ones who left.
To see who comes back
PostHog, or Omni's own SDK for iOS and web.
To know what shipped
Commits, pull requests and App Store releases.
To reach people again
Win-back email to a list you keep in Resend.
Questions about retention with Omni.
It starts a group at each person's install and counts who's active again on day 1, 2, 3 and so on, or week by week, only once that day has fully passed for them. You can split it by app version, platform, device type or country.