When a crash spike hits an app, it directly erodes retention. Attribr should ingest crash events from the planned Crashr SDK and show on the cohort chart exactly when crashes spiked and how much they bent the D1/D7/D30 curves downward. Correlation, not just co-occurrence.
Global retention numbers hide which channels bring quality users. Let founders see separate retention curves per source (organic App Store, paid social, referral link, etc.) so they know where to put their next £ of ad spend.
Which acquisition channel produces paying users? Add an optional IAP event (`Attribr.trackPurchase(productId:revenue:)`) so the dashboard can show LTV by channel, not just installs.
Attribr data currently sits in raw Supabase tables. Founders need a visual dashboard at attribr.mrvltechnologies.com (or similar) showing: daily installs, D1/D7/D30 curves, top channels, and recent crash events — without needing to open the Supabase console.
Know exactly when users leave — not just when they stop appearing in launch pings. Send a daily silent push to all known tokens; tokens that return "invalid" indicate an uninstall. Flag those installs as churned in the retention model.
A user uninstalls then reinstalls on the same or a new device. Attribr should recognise them via IDFV / hashed email and treat it as a reactivation event rather than a new organic install, giving an accurate picture of reactivation vs. true new users.
Don't see what you need?