Product analytics that tells you why metrics moved.
Ferno watches your product events, flags the numbers that changed, and shows you the cause with the evidence behind it.
npm install @fernohq/analytics-nextSignals
Why did fewer people finish signing up this week?
Tuesday’s update broke the Continue button on the Android sign-up form.
- The drop began within an hour of Tuesday’s update.Supports
- Sign-ups on iPhone and web stayed normal.Supports
- Ad traffic held steady, so fewer visitors isn’t the reason.Not the cause
deviceapp_versionsignup_source01 / The questions behind the change
The graph moved.
The questions start there.
- What changed?
- Who felt it?
- Is it real?
- What happens next?
02 / One investigation
From change
to cause.
A signal arrives. Ferno compares the baseline, tests the strongest explanations, and keeps the evidence attached.
Did it really change?
DoneWho and where?
DoneWhat else explains it?
Checking nowWhat should happen next?
Up next
Investigation in progress
Did the release cause the activation drop?
Broke the change down by
platformversionacquisition_source- Holds
- The change is concentrated in new browser projects.
- Doesn’t hold
- The same release is healthy in existing projects.
03 / The handoff
Bring an answer
to the room.
A recommended next move, with the evidence and the open questions attached.
04 / Connect the product
Start with the events you already send.
Ferno’s browser and Node SDKs take track, identify, page, screen, group, and alias calls. Keep the event names your team already understands.
import { AnalyticsBrowser } from
'@fernohq/analytics-next'
const analytics = AnalyticsBrowser.load({
writeKey: 'ferno_pk_••••••'
})
analytics.track('checkout_started')05 / Questions
Before you connect anything.
No. Ferno’s browser and Node SDKs are built on Segment’s open-source analytics library, so track, identify, page, screen, group, and alias work the way your team already writes them. Point them at your Ferno project key and keep your event names.
Ferno compares each project’s most recent 24 hours of events with the previous 24 hours. When something moves enough to matter, it opens an investigation instead of just raising an alert.
Every report states its confidence, shows the queries Ferno ran and what they returned, and lists what it couldn’t rule out. Your team can check the reasoning instead of taking it on trust.
No. Investigations are read-only. Ferno recommends a next move, and anything that touches a connected tool, like your Linear workspace, needs someone on your team to approve it first.
Every API key belongs to one workspace and project, and Ferno decides where events go from the key itself. Keys are stored as a one-way digest, and connected integration credentials are encrypted at rest.
Read the security overview