What counts as activation, which events stand behind it.
Skene turns that into a check on every release.
Growth
Did activation fall after the release, or did the tracking?
Activation is down eleven percent since Tuesday. Your release shipped Tuesday. Your growth review is Thursday, and nobody can tell you yet which of those two facts explains the first one.
Free means one audit: sign in, connect a source, no card.
Activation funnelLast 28 days
| Step | Value |
|---|---|
| Signed up · Event verified | 4,820 |
| Invited a teammate · Event renamed on 12 Aug | 1,510 |
| Reached first value · Never tracked | not measured |
The drop gets an explanation
When activation moves, you know whether behavior changed or the recording did.
Caught at the release, not at the review
The break is flagged the day it ships, not three weeks later when the chart goes flat.
Numbers you can defend
Every funnel step is checked against an event that actually arrived.
What happened
The rename works. The funnel reads the old name.
A renamed call doesn't look like a data problem, so nobody goes looking.
Signed up, invited, reached first value.
A team renames signup_completed to account_created while splitting a signup handler. The new name fires correctly. The activation funnel still reads the old one.
- Skene's first job is to see the evidence: map what your product collects
- Then flag broken, incomplete or missing signals
Activation funnelLast 28 days
| Step | Value |
|---|---|
| Signed up · Event verified | 4,820 |
| Invited a teammate · Event renamed on 12 Aug | 1,510 |
| Reached first value · Never tracked | not measured |
The check runs on the release, not after the review.
Skene reviews the pull request that renames the call, compares it against what your workspace knows, and requests changes with inline comments.
- Where the fix is one line, it arrives as a suggestion you commit from the pull request
- The question never reaches Thursday's review
acme/webappchanges requested
Sskene-aibot
Skene Analytics Drift Review
This pull request renames a tracked call the activation journey depends on.
src/onboarding/handler.ts:42
Removedtrack("signup_completed")
Addedtrack("account_created")
Issues
Medium:
signup_completed renamed at src/onboarding/handler.ts:42src/onboarding/handler.ts1 comment
Catch it before it ships.
Describe the plan first. Skene marks it ready to launch only when the signals to judge it exist, not three weeks later.
- First-week first-order activation rate =
first_order_within_seven_days / customer_created - No target set, 30-day window
Skene / skene-dashboard10 signals missing
Activation: first project within seven days of signup
Check · no data for this window
| Result | Value |
|---|---|
| Current | — |
| Previous | — |
| Change | — |
Activation funnelLast 28 days
- Your release shipped Tuesday.
- Your growth review is Thursday.
Invited a teammate · Event renamed on 12 Aug
Who owns whatYou decide Engineering does The paths behind the number
A specific finding on a specific line.
When a change would break something you said mattered.
A funnel stage is a count. This is the route people took.
Pricing → Signup → Onboarding → Dashboard, real conversion at each step.