Know if what you shipped actually landed.
Skene checks that a launch can be measured before it ships, then compares the result with your target. Missing tracking and a missed goal are different findings.
Sign in, connect one source, and the one-time analysis returns what you already collect.
A repository or a database is enough for the first analysis.
See what's tracked today.
Run the one-time analysis. Skene maps what exists, what is tracked but not placed, and what is missing.
- Regex over thirteen analytics platforms, no model in it
- Reads the repository read-only, nothing is written back
Schema inspection does not sample row values. Measurement reads the inputs available through connected sources.
Define the outcome before you ship.
Name what the change should move. The plan records the metric, reporting window and the signals needed to answer that question.
Verify checks each required event and field before launch. Finding a source is separate from measuring the result.
What the plan keeps together
The hypothesis and success metric describe the outcome. Required events and fields name the evidence. The success formula defines the calculation and optional target.
Read the plan referenceProtect that as your team keeps shipping.
Skene checks every change you ship against that plan and names the event, file and line where tracking went missing.
- Install the GitHub App, turn on pull request reviews
- Every pull request gets a review with comments on changed lines
After launch, read the result against the plan.
Run Check for the reporting window. It reads the success metric from connected data and keeps the result with the plan.
A computed result and a met target are different facts. No data stays distinct from zero, so an unavailable measurement does not become a conclusion about the change you shipped.