Every release, marked on the timeline your numbers already live on.
Most analytics tools know a metric moved. They do not know you shipped. GitHub gives Reveliqo the deployment record — commit, environment, release identifier and timestamp — so a change in conversion or latency can be read against the releases that sit either side of it.
In short: Reveliqo reads commits, deployments and releases from your repositories and marks them on the same timeline as traffic, conversions and revenue, so a change to the site has a visible position in the data.
What it is
GitHub hosts source repositories and the events around them: commits, pull requests, releases and deployment records written by GitHub Actions or whatever pipeline reports back to it. Reveliqo reads that record; it does not run your pipeline.
What this lets you ask
- “What changed after yesterday's deployment?”
- “Which release does the Safari conversion drop line up with?”
- “Does revenue per visit differ either side of last week's checkout rewrite, or only latency?”
What Reveliqo receives
- Commit SHA, message and author for the deployed revision
- Deployment and release identifiers, with the target environment
- Deployment timestamp in UTC, used as the annotation point on every chart
- Changed route and content metadata where the workflow reports it
How it is connected
- Authorise the GitHub App on the organisation, or on the specific repositories you want annotated
- Map each repository to the Reveliqo site or sites it deploys
- Select which environments count — production annotations are on by default, preview and staging are opt-in
- Post changed routes from your workflow if you want the comparison narrowed to the pages a release actually touched
How you verify it
- The deployment appears on the Live timeline within a minute of the workflow finishing
- Opening a release shows the before-and-after comparison window, and how many visits fall on each side of it
- The connection page lists the last deployments received, with their environment and commit
Limits worth knowing
- A deployment marker is a time coordinate, not a cause. Reveliqo reports that the change begins shortly after a release and says so in those words; causation has not been proven by a timestamp.
- When several deployments land inside one comparison window, their effects cannot be separated. Reveliqo widens the window and states that the correlation is shared rather than picking one release to blame.
- Changed-route metadata depends on your workflow reporting it. Without it, the comparison runs at site and segment level rather than per route.
Other integrations
Connect the rest of the stack
Connect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo