Product analytics,
kept in your warehouse.
Pageviews and the events you track land as rows you can query with SQL, next to your billing and app data.
npm install @embrasure/analyticsPress E to send an event of your own into the scene, and the left and right arrow keys to move between chapters.
- Three lines: You add three lines. import { createAnalytics } from "@embrasure/analytics"; const analytics = createAnalytics({ projectKey: "pk_example" }); analytics.track("signup_started");
- Launch: You launch on Thursday.
- Launch day: 785 pageviews on launch day.
- First signup: The first signup: Thursday, 02:34 UTC.
- Activation: 557 reports created in the first week.
- Invites: 116 invites sent.
- Retention: Signups by week, and how many come back.
- Churn: By Sunday, pageviews fall to 13 an hour.
- One table: 5,696 events, one row each.
Product analytics that keeps every event in your warehouse.
npm install @embrasure/analyticsMany teams only need a record of who used what, and when. Embrasure keeps that record as tables in your own warehouse.
Each event is a row in product_analytics.events, with people and sessions in tables beside it. Query them with SQL, dbt, a BI tool or Ember, next to your billing and app data.
One row per event
Path, referrer, UTM tags, device, browser and country are typed columns. Your own properties stay as JSON beside them.
People and sessions included
Signed-out and signed-in IDs resolve to one person. Each session has its duration, bounce, entry path and channel.
Retries don't duplicate rows
Events are keyed by their ID, so a request the browser resends after a dropped connection is stored once.
No autocapture
Pageviews record the path, not query strings, page text or form values. Other events are recorded where you call track(), and there's no session replay.
Browser, Node and Python
The browser SDK records pageviews as the route changes. Server SDKs send from your backend with a server key.
Collection is open to pilot workspaces. Book a demo to turn it on for yours.