Release-aware analytics

See which release moved your numbers

Ometra pins every deploy and Webflow publish to your traffic chart, alerts you when something shifts, and tells you what shipped around the same time — so “what happened on Tuesday?” takes seconds, not an afternoon.

Get started freeRead the setup guide

Analytics that know what you shipped

Most analytics tools can tell you that sign-ups fell 18% on Tuesday. None of them know that you shipped a new checkout flow on Tuesday morning. So someone scrolls through Slack, cross-checks the deploy log, and pieces together a timeline by hand — usually days later.

Ometra puts both on the same chart. Your releases appear as markers alongside visitors, sources, and conversions, and when Ometra's anomaly detection spots an unusual change it attaches the release that went out around the same time. You start your investigation in the right place.

How release tracking works in Ometra

A marker for every release

Your CI sends one small request after each deploy, and a pin appears on that day of your traffic chart with the label, commit, environment, and a link back to the build.

Works with any pipeline

GitHub Actions, GitLab CI, Vercel and Netlify deploy hooks, Coolify, or a script — if it can run curl, it can send a marker. Nothing changes on your website.

Alerts with context

When a conversion rate drops or a traffic source vanishes, Ometra's alert names the release that shipped around the same time, so you know where to look first.

Plain-English summaries

AI insights explain what changed and what coincided with it — written carefully as correlation, never as proof that a deploy caused the change.

Then look at the page

Open the click and scroll heatmap for the affected page to see whether visitors still reach and click what you changed.

Annotate everything else

Not every change is code. Add notes for campaigns, pricing changes, or outages so the whole team sees them on the same chart.

One step in your pipeline

Add this after a successful deploy. Ometra gives you the exact command, with your endpoint and secret filled in.

curl -X POST "https://ometra.io/api/sites/<site-id>/deploys" \
  -H "Authorization: Bearer $OMETRA_DEPLOY_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"environment":"production","sha":"'"$GIT_SHA"'","label":"Checkout v2"}'

GitHub Actions example and every field explained in the deploy tracking docs. On Webflow? See Webflow analytics.

Correlation first, then confirmation

A release that lines up with a change is a lead, not a verdict. Weekends, campaigns, seasonality, and tracking breakages all move numbers too. Ometra is deliberately careful here: it shows you what coincided, and leaves the conclusion to you.

We wrote up the full method — comparing like-for-like windows, checking the pages you changed, and when to reach for a proper A/B test — in how to see which deploy changed your conversion rate.

FAQ

Release tracking FAQ

What is release tracking in web analytics?

Release tracking (or deploy tracking) records each time you ship a change and shows it as a marker on your analytics charts. It lets you line up a change in traffic or conversions with the release that went out at the same time, instead of guessing what happened that day.

How do I send deploys to Ometra?

Generate a deploy secret under Settings → Deploys and add the ready-made curl command as a step after your deploy — in GitHub Actions, GitLab CI, a Vercel or Netlify deploy hook, or any CI. Every field is optional, so even an empty request records a deploy at the current time.

Do I need to change my website's code?

No. Deploy markers come from your build pipeline, not from your site. For Webflow, connecting a site API token is enough — Ometra registers a publish webhook for you.

Will Ometra tell me a deploy caused a drop?

No, and you should be wary of any tool that does. Ometra tells you a change happened and which release shipped around the same time. Confirming cause takes a closer look — comparing like-for-like periods, checking the affected pages, or running a controlled test.

Which plan includes release tracking?

Deploy and Webflow publish markers are on the Agency plan. Manual chart annotations start on the Individual plan, and anomaly alerts and insights are on all paid plans.

Does it work with Webflow?

Yes. Connect your Webflow site once and every publish is pinned automatically, labeled "Published via Webflow".

Ship, then see what it did.

Add one small script and get a dashboard you'll actually enjoy checking — without cookies, banners, or a data-privacy headache.

Get started freeSee plans

Deploy and Webflow publish markers are on the Agency plan; annotations start on Individual.