Did activation fall after the release, or did the tracking?
Activation is down eleven percent since Tuesday. You have a release that shipped Tuesday. You have a growth review on Thursday.
Everyone trusts the number, including the people who could check it.
If the tracking did break, every day nobody goes looking is a day of activation data you don't get back.
Nobody in the room doubts the chart. Your team reads eleven percent and starts working the problem. Engineering checks the release, finds the feature working and the tests green, and confirms it shipped clean. Both are right, and the number is still wrong, because a renamed call is not a broken release.
That is why this one survives. It does not look like a data problem to anyone who could catch it, so nobody goes looking, and the days keep passing. If the tracking did break, the activation data for those days is not recoverable later.
- Release
- Down eleven points
The rename works. The funnel reads the old name.
The chart says onboarding broke, so your team spends two weeks fixing a step that was never broken.
Say a team renames signup_completed to account_created while splitting a signup handler in two. The new name fires correctly. The activation funnel still reads the old one.
The funnel shows activation falling off a cliff on the release date and staying there, which reads exactly like a broken onboarding flow, and the team spends two weeks redesigning a step that was working the whole time.
The check runs on the release, not after the review.
The rename comes back as a comment on the exact line that broke it, with a suggestion you commit in one click.
Skene reviews the pull request that renames the call, compares it against what your workspace already knows about your tracking, and requests changes with inline comments on the exact lines. Where the fix pins to a single span it arrives as a suggestion you commit in one click.
The point is not the alert. It is that the question never reaches Thursday's review, because the break was caught at the release that caused it.
signup_completed renamed at src/checkout/handler.ts:42Catch it before it ships.
The same problem has a version you can catch earlier. Describe the change you are about to make and what you expect it to move, and Skene tells you whether the signals needed to judge it already exist. A plan is marked ready to launch only when they do, which is a better moment to find out than the review three weeks later.
A funnel stage is a count. This is the route people took to it.
The funnel above says the stage fell. Flows says which way people actually came, and where they went instead. When a rename breaks a stage, the paths keep working and only the count moves, which is the tell.
You decide
What counts as activation, which events stand behind it, and which reports depend on them. That is a growth decision and it stays with you.
Engineering does
A specific finding on a specific line when a change would break something you said mattered. No second analytics tool, no reporting to own.