Analytics and reporting
Product analytics on raw,
real-time events
Funnels, retention, cohorts, journeys, drill and crash analytics on the same live data. Raw events by default, no pre-aggregation, no overnight jobs; sampling is an option you switch on, never something done to you. Events are queryable the moment they arrive.
Reports
Every report,
on the same live data
Every report type on one data layer. Anything you find here can become a cohort, an alert or an audience for engagement.
Sessions and users
Active, new and returning users, session length and frequency, by platform and version.
Events
Custom events with segmentation properties, sums and durations.
Views and sources
Screens and pages, entry and exit points, acquisition sources and campaigns.
Drill
Ad-hoc segmentation of any event by any property, with period comparison.
Funnels
Sequential and exact funnels with completion windows and segment breakdown.
Retention
Retention grids by any starting and returning behavior, slipping-away detection.
Cohorts
Behavioral cohorts that update in real time and feed engagement.
Flows and journeys
Real paths through the product from any starting point.
Formulas
Derived metrics from any events and properties, on live data.
Crashes and performance
Crash groups, symbolicated stack traces and affected users; app start, network and custom traces.
Dashboards, alerts and reports
Team dashboards, metric alerts and scheduled email reports.
AI Analytics
Adoption, cost, quality and performance of the AI features in your product. See AI Analytics
In depth
How it works,
in detail
The parts that matter when you evaluate this area seriously: what it does, how it behaves at the edges, and what your team controls.
Drill is the segmentation engine behind every report. Filter by event properties, profile attributes, cohorts and time, compare two periods side by side, and turn the result into a widget. Cee sits next to it to write the query for you.
- Any property, any operator, any time range
- Period comparison and breakdown by any dimension
- Results open in Funnels, Cohorts or Dashboards
Retention grids for sessions or any event, split by segment. When users go quiet, open the count, save them as a cohort and aim a message at it.
- Retention of sessions or any event
- Slipping Away at each inactivity threshold
- From a count to a cohort to a campaign
Crash groups, symbolicated stack traces and affected users sit in the same workspace as funnels and retention. You can see what a user did in the session before a crash, how many users of a version are affected, and whether a release changed crash-free sessions. Performance traces cover app start, network requests and custom spans.
- Crash groups with version, OS and device breakdown
- Session timeline before the crash
- Crash-free users and sessions as alertable metrics
- App start, network and custom performance traces
FAQ
Questions
teams ask us
Straight answers on how this part of Countly works in practice. For anything else, talk to us.
Do you sample or pre-aggregate?
Not by default. Countly stores raw events and computes reports on the complete data set. On very high volumes you can enable sampling yourself for specific reports; it is your decision, visible in the report, never applied silently by the vendor.
How fast is data available?
Events are queryable within seconds of arrival. There is no batch window and no overnight job.
Can we bring internal data into reports?
Yes. Profile properties and events written through the API appear in Drill like any SDK event, so revenue, plan or support data can segment any report.
How do teams share analyses?
Saved Drill queries, cohorts and dashboards are shared per app with role-based permissions. Scheduled email reports and alerts cover the rest.
