Usage events

What your customers actually do inside your product, under Events on each app.

How data gets here

Your product sends usage events to CoreX: from the browser with the SDK snippet, or from your backend through the ingestion API with the X-CoreX-Token header. Get a key on the app’s Connect page, under API keys. The Send events button on the Events overview shows a copy-ready snippet for your stack and checks that the first event arrived.

What you see

One Events area per app, with these tabs:

  • Overview — active customers, events tracked, new and churned customers and the activation rate for the dates you pick, each compared with the period before; daily activity; which features customers use, as a share of your installs; and notices when tracking breaks (an event that stopped arriving, a sudden drop, an activation event that never matches).
  • Explorer — every event as it arrives, your own events first and the auto-tracked page views one tab away. Filter by event, customer, contact, payload text and dates; open a row for its full payload; export the view.
  • Lifecycle — sign-ups, plan changes and departures (see App events).
  • Definitions — give each event a readable name, a description and a category, hide the ones that are plumbing, and choose your activation event. Your Usage metrics and the usage pricing replay live at the bottom.
  • Performance — Core Web Vitals and JavaScript errors from the browser snippet.

Explorer, Definitions and Performance need the Usage analytics app. Overview and Lifecycle are there for every workspace.

Why it matters

Usage is the truest leading indicator of retention and expansion — far earlier than billing.