Ototi
Operations
Analytics, onboarding experiments, and push delivery in one private workspace.
Access is restricted to the owner allowlist.
Ototi
Operations
Product health
Analytics
01 / Version cohorts
From install to real value
Each cohort is the app version first registered by an installation. Trial and learning are parallel outcomes after the paywall, not one forced linear path. Legacy versions are labelled approximate when their first-build snapshot had to be reconstructed.
Android funnel
Review prompt requests
The app can record a request to the operating system. Apple and Google do not disclose whether the prompt was actually shown or which action the person took.
Push opt-in
Accepted is shown against all observed installations. It is not a prompt acceptance rate because denied/dismissed permission outcomes are not collected.
iOS daily retention
Android daily retention
iOS weekly retention
Android weekly retention
Engagement by install cohort
Verified minutes come from meaningful-session evidence, divided by onboarded installations. They are not a claim about all background playback minutes.
Onboarding variants by build
A single active variant remains visible as one row; future A/B revisions split automatically by platform, app version and variant.
Paywall variants by build
RevenueCat initial purchases are the authoritative production outcome. Trial starts are device-observed; checkout failures count affected installations, not noisy repeated error events.
02 / Pulse
What is happening now
Daily activity
App builds
03 / Activation
From first open to first value
Activation funnel
Onboarding journey
Revision 0 means no experiment. Its history is limited to the available raw window (up to 27 days); assigned cohorts use durable daily counts. Not completed is a count difference, not proof that someone permanently left.
Welcome and onboarding handoff
Counts sum daily unique installations. Already-linked accounts and unavailable plan previews are explicit bypasses, not drop-offs.
Onboarding answers
Screen reach
04 / Discovery & learning
What people choose and finish
Discovery surfaces
Learning modes & quality
Ototi performance
Search & offline reliability
05 / Retention
Whether value becomes a habit
Retention & recall
06 / Revenue & identity
Paywall, subscription and account health
Commerce funnel
RevenueCat lifecycle
Account & authentication
07 / Quality
Trust, reliability and privacy
Quality reports
Content access decisions
Complete typed event coverage
Includes unobserved events at zero. Raw history is bounded; use retention health before interpreting longer windows.
Daily events
Deletion queue & retained audit
Completed-request history is a bounded 30-day operational audit, not an all-time total.
Open content reports
Recent incidents
08 / Operations
Editorial and platform operations
Content jobs
Audit actions
Safe rollout
Onboarding experiments
Paywall design, offerings and independent paywall experiments: RevenueCat Paywalls. Native support requires the updated production build.
Publish starts a new revision for new installations. Pause stops new assignments; journeys already started keep their variant. Review builds are excluded from measurement. Only variants bundled in the selected app version can be published.
Revisions
New onboarding revision
Consent-aware messaging
Push
“Accepted by Expo” and “accepted by provider” are transport acknowledgements, not proof of device delivery.