Skip to content
Codeskop

Product analytics

See what users actually do in your apps, where they drop off, and which crashes, errors and slow APIs are behind it, in the same place you already monitor them.

Available on Growth and Scale

Product analytics is included on the Growth (1,000,000 analytics events a month) and Scale (10,000,000) plans. See Plans & features.

What you get

  • Events & screens: every custom event with its properties, and every screen or page view, with trends and breakdowns by property, platform, app version, OS and country.
  • Funnels: conversion and drop-off between steps, the median time to convert, and the crashes, errors and failed API calls that hit the users who dropped off at each step.
  • Retention: of the users who started in a week (or day), how many came back.
  • Paths: where users go after a screen, and where they came from; time on screen and exit rate.
  • User profiles: a user's traits, sessions and a single timeline of their screens, events, crashes and errors.
  • Segments: groups of users by traits and behavior, with CSV export of their ids and a webhook for new members.

Everything is in the dashboard under Analytics, for each project and environment.

How it works

  1. Screens are recorded automatically by the latest SDKs: Android Activities, Flutter routes (with CodeskopNavigatorObserver) and web pages, including React and Next.js navigation.
  2. You add the events that matter with one line: track("order_completed", { value: 49.99 }). See Track events & screens.
  3. You identify users with your own id, and optionally traits such as plan or city. Codeskop connects their events, sessions and issues.

Users are known by your id only

Codeskop never needs names, emails or phone numbers. Users are tagged by the user_id you pass to identify. Use it to look people up in your own systems. To keep it that way, any property or trait value that looks like an email address or phone number is replaced with [REDACTED] before it's stored, and page names never include query strings.

Pricing

Analytics events have their own monthly quota, separate from crash and error events; one never eats into the other.

OptionTypeDescription
Counts as an analytics eventn/aEach custom event (track), screen or page view, and identify call that sends traits.
Growth1,000,000 / monthThen $5 per 100,000 events, billed monthly.
Scale10,000,000 / monthThen $3 per 100,000 events, billed monthly.
Free & Startern/aNot included: the SDKs don't send analytics events.
Test environmentn/aFree and never counted, like all test traffic.

As a safety net, analytics capture pauses at 3× the quota. Usage is shown in Settings → Billing.

Turning it off

Switch Product analytics off for a project in Settings → SDK settings, or turn off automatic screens in the SDK (captureScreens on Android, capturePageViews on the web).

Next steps