Convert & retain
See which GitHub commits moved traffic and revenue
Line up what you shipped with what happened next.
Updated · 1 min read
You ship a new pricing page on Tuesday and signups jump on Wednesday. Or a refactor goes out and conversions quietly slide for a week. Without your releases on the same chart as your traffic, these links are easy to miss.
Why this matters
Every change you ship is an experiment, whether you planned it or not. Knowing which commits moved traffic and revenue tells you what to double down on, and which change to roll back before it costs you more.
Why most analytics tools can't tell you
Analytics tools don't know what you deployed, and GitHub doesn't know what your visitors did. You end up scrolling commit history next to a chart, trying to match dates by hand.
How MetricRaven does it
MetricRaven connects one GitHub repository per website and draws its commits as markers on the traffic chart, next to visitors, revenue and conversions. It reads commit messages, authors, times and branches, never your source code. Conventional-commit prefixes such as feat: and fix: let you show only the commits that matter.
Releases on the traffic chart
Orbit Analytics · synthetic data · last 30 days
How to do it
- Open Settings → GitHub and enter the repository as owner/name (GitHub commits on your chart).
- For a private repository, add a fine-grained token with read-only Contents access to that one repository.
- Wait for the last 90 days of commits to import, then open Traffic.
- Hover a day to see its commits, or click a marker to list all of them with links to GitHub.
- Use the commits button in the chart toolbar to keep only types such as
featandfix, then compare the days before and after a release.
A commit next to a spike shows timing, not cause. Check the funnel and sources for that period before you credit a release. Commits stay private: share links and embeds never show them.