← All changelog updates

Deploy impact scoring, error spike alerts, and usage forecasting

See whether a deploy moved your traffic and revenue, spot error spikes on your chart, and forecast your monthly usage before you hit quota.

Deploy impact scoring

If a site has a connected GitHub repo, every recent commit now gets a badge showing whether the 24 hours after it shipped looked better, worse, or about the same as the 24 hours before — comparing visitors, bounce rate, conversions, and revenue. Commits with too little traffic to draw a real conclusion from are marked as such instead of guessing, and a commit whose window hasn't fully elapsed yet shows as "Pending."

Error spikes on your chart

The "Visitors over time" chart now flags moments where errors on our end spiked well above normal for your site, using the same note/commit marker style already on the chart — a distinct red marker so a real problem doesn't look like an ordinary annotation. Only genuine spikes are marked, not routine background noise.

Usage forecasting

Settings' Usage & plan card now breaks down this month's event volume by site and shows a simple forecast — whether you're on pace to exceed your quota, and roughly when. It also shows what share of your raw traffic is bot/crawler activity, which is already excluded from your billed usage but still worth knowing about.

What shipped

  • NewSee whether a GitHub push actually moved your traffic, bounce rate, or revenue — right on your site's dashboard.
  • NewError spikes are now flagged directly on the "Visitors over time" chart, so you can spot when something broke without digging through logs.
  • NewSettings now shows a per-site usage breakdown and a forecast of whether you're on pace to exceed your monthly event quota.
  • FixedThe "Visitors over time" chart's dashed projection line for the current, still-in-progress hour was rendering incorrectly.
  • FixedSorting the Visitors and Revenue breakdown tables by revenue could return rows in the wrong order.