Skip to documentation

Analytics

Kixo analytics turns your SDK event stream into dashboards, segments, funnels, cohorts, and plain-English answers. You can use the visual pages directly or ask Kixo Chat to build and explain them.

Core metrics

  • DAU / WAU / MAU -- how many audience members were active daily, weekly, or monthly.
  • Sessions -- visits or app openings grouped by idle timeout.
  • Activation -- whether new users reach the value moment you define.
  • Retention -- whether users return after signup, install, purchase, or another cohort start.
  • Revenue and goals -- product-specific outcomes such as purchase, subscription start, upgrade, or custom goals.
  • Quality signals -- errors, crashes, performance, and broken interaction patterns where supported by the SDK.

Dashboards

Dashboards collect the charts your team returns to often. Ask Kixo to build a dashboard from an outcome, then review the charts and filters it proposes.

Useful prompts:

  • Build a weekly executive dashboard for activation and retention.
  • Show the onboarding funnel by platform for the last 30 days.
  • Compare trial users who activated vs. users who did not.

Segments

Segments filter your audience by behavior, user properties, or platform. They can power dashboards, funnels, cohorts, and campaigns.

  • Users who signed up in the last 7 days but did not activate
  • Paid users on iOS with no session in 14 days
  • VIP users who opened a campaign but did not purchase

Funnels and cohorts

Funnels show conversion through ordered steps. Cohorts compare groups of users over time. Both work best when your SDK uses stable event names and properties across Web, iOS, and Android.

Journeys, maps, and flows

Beyond aggregate charts, Kixo reconstructs how people actually move through your product from the SDK stream:

  • Journeys and flows -- the paths users take between screens and pages, so you can see where they branch, loop, or drop off.
  • App map -- a graph of your screens and pages and the transitions between them, built from screen and page-view events across platforms.

Heatmaps

Heatmaps show where attention lands. Web heatmaps render click and scroll density over a snapshot of the page; the mobile heatmap tab shows where users tap on each screen, drawn from replayed sessions. Web click/scroll heatmaps are captured by default (mouse-move is disabled by default) -- see the Web SDK heatmap settings.

Session replay

Replay lets you watch a reconstruction of a single session next to its event timeline -- an rrweb DOM reconstruction on Web and visual frame capture on iOS and Android. Sensitive inputs and explicitly masked regions are redacted before upload. Replay is enabled from the project settings and subject to the project plan; the Replay and Sessions views link across to each other so you can jump from a session's event trail to its recording and back. See each SDK page (Web, iOS, Android) for how to enable it.