Skip to content
How it works

From the codebase to the conversation.

Eventra reads your code to learn what features exist, then compares that list with what happens in production.

01 / The method

Scan. Compare. Decide.

Run eventra sync and the CLI finds your tracking calls, through wrappers and re-exports. Eventra send registers them, and the dashboard shows what production did with each one.

Terminal / Example

$

Scanning...

Found 47 events, 3 function wrappers

Then, after eventra send: dashboard / Features

  • checkout_startedActive12,480 events
  • invite_teammateDeclining-62% vs previous period
  • legacy_exportDeadlast used 41 days ago
  • bulk_taggingNever seenin code, 0 events ever

$

Illustrative example. Feature names and numbers are made up.
  1. 01

    Scan

    The CLI reads your code and registers each tracking call it finds as a feature in your catalog.

  2. 02

    Compare

    The dashboard sets that catalog against the events production actually sent.

  3. 03

    Decide

    Features that went quiet are listed as candidates. You choose what stays.

02 / What you get

Everything it does.

The catalog comes from your code, not from a list someone has to maintain.

The CLI scans your codebase with the TypeScript compiler API and follows wrappers, re-exports and barrel files. Every track() call with a name the scan can read is found, even ones you forgot about. React JSX works out of the box; Vue, Svelte, Astro and Angular templates through official plugins.

Read the docs

A feature that had events but none past your dead-feature threshold (14 days by default, configurable per project) shows up on its own, grouped by how long it has been silent. You do not have to list what should count as dead.

Read the docs

Still used, but at half or less of the period before, once it had at least 10 uses then. Each period is as long as your dead-feature threshold. Eventra flags it and shows usage and users before and after, so you can ask what changed while the team still remembers.

Read the docs

A feature the CLI found in your code that has never sent a single event is its own signal: unreachable code, a broken flow, or tracking that is not wired up. Registering it never counts as a use or a user.

Read the docs

eventra check exits 1 when your code and catalog are out of sync, and with --strict when the scan itself was not clean. New features get caught before they ship invisible. Run eventra send from your main branch and removed features are marked as removed instead of lingering as ghost data.

Read the docs

Events and exact unique users over time, custom date ranges, adoption, property breakdowns, per-user activity and the raw event stream. Overview cards and top lists link to the feature, user or event behind them.

Read the docs
03 / The lifecycle

Five states.

Every feature is in exactly one of them, and moves as the events come in or stop.

  1. New

    First event within the new-feature threshold. Too early to call, give it time.

  2. Active

    At least one event within the dead-feature threshold. Leave it alone.

  3. Declining

    Still used, but at half or less of the period before (after at least 10 uses then). Worth a look now.

  4. Dead

    Had usage before, nothing since the threshold passed. A candidate for removal.

  5. Never seen

    In your code, never reached the platform. Misconfigured or unreachable.

Days since the last eventlegacy_export
ActiveDead, past the 14-day threshold41 days

Default thresholds: 7 days for new, 14 for dead. Both are configurable per project, and a single feature can have its own dead threshold or be muted.

Try it

Find your first
dead feature.

Run eventra init, sync and send, then open the dashboard. Your catalog is there in minutes.

Free tier, 100k events a month, no credit card.