One script tag, one SDK call, or a warehouse connection. Events arrive within about five minutes.
The workflow
Most analytics rollouts die in the modelling phase. Cadence is designed so the boring part is finished before lunch and the useful part starts the same day.
One script tag, one SDK call, or a warehouse connection. Events arrive within about five minutes.
Cadence proposes a schema from what it sees. You approve names, mark the sensitive ones, and move on.
Funnels, retention, paths and segments — rebuilt in under a second, so you can keep asking.
Save the metrics that matter. Cadence watches them and pings the channel that owns each one.
Step 01 · install
Drop the tag in your layout, or install the package your framework already uses. Cadence starts collecting page views, clicks and session boundaries immediately — you don't have to instrument anything to see the first chart.
Step 02 · model
Cadence groups what it receives, spots the near-duplicates — signup_done, SignupComplete, signup-finished — and proposes one name for the set. You approve or rename, and every historical event is remapped, not just the new ones.
Step 03 · explore
Funnels rebuild while you're still moving the mouse. Add a breakdown, drop a step, switch the window from 30 to 90 days — none of it queues, so the shape of the answer stays in your head long enough to be useful.
Step 04 · automate
A dashboard nobody opens is a dashboard nobody trusts. Cadence learns the normal shape of each saved metric — including its weekly rhythm — and only speaks up when a cohort genuinely breaks its own pattern.
Averaged across the last 300 workspaces that onboarded without a solutions engineer.
Install and first chart. The snippet goes in, auto-capture starts, and someone shares a link to a page-view breakdown before the end of the day.
Naming. You accept most of the proposed schema, rename a handful of events, and mark two or three properties as sensitive.
The activation funnel exists. It has an owner, a definition everyone has read, and a number that stops being argued about.
Retention baselines. Weekly cohorts go back as far as your warehouse backfill reached, so you're comparing against real history, not the day you installed.
Alerts and the Monday digest. People stop opening dashboards out of anxiety, because the tool tells them when there's something to see.
No. The install is a script tag or a package, and the schema step is a review screen, not a modelling project. Teams with a warehouse usually connect it in the first week as well, but nothing depends on that.
If it lives in a warehouse, Cadence backfills up to 24 months on request so your retention curves start with real history. If it lives in another analytics tool, we import from Amplitude, Mixpanel and Heap exports directly.
Yes. Every chart exposes the query it ran, you can edit it, and you can query the underlying tables through the read-only Postgres-compatible endpoint on Business and above.
Anything you mark sensitive is hashed or dropped at the edge, before it is written to storage. Session replay masks all input values by default — you opt specific fields in, not out.
One button produces a full export of raw events in Parquet plus your metric definitions as JSON. We don't hold the export hostage behind a support ticket, and it works on every plan including Free.
Only on Free, which is capped at three. Every paid plan is unlimited — you're billed on events, so inviting the whole company costs nothing and is usually the point.
Get started
Free for 30 days on the full product. Five-minute install, no card, no onboarding call unless you want one.