What changed

“What changed” compares the selected range with the range of the same length just before it. In the MCP tool, this_month and last_month are compared with the previous calendar month. A range that is still running is compared over the same elapsed time: today so far against yesterday up to the same hour. It is deterministic: no model runs on our side.

It appears on the dashboard’s Overview, at GET /v1/sites/{id}/stats/changes, and as the what_changed MCP tool (which can also compare with the same period last year).

What it looks at

• Totals: visitors, visits, page views, conversions, bounce rate, engaged time per visit.
• Drivers: the change in visits split by channel, source, country and device; page views by page; conversions by event. Each driver has its share of the overall change.
• Trust: the grade, measured loss, the share of bot and suspicious traffic.
• Revenue: net per currency, when Stripe is connected.
• Heatmaps: rage and dead click spikes per page, when heatmaps are on.

When a change counts

• Counts: at least 15% and at least 20 visits, or 2% of the larger period’s visits if that is more. Conversions need 5.
• A rise from a base under 30 (10 for conversions) gets no percentage: it is called new. Falls from such a small base are not reported. A fall that ends under 30 is called gone.
• Bounce rate: 5 points or more. Engaged time: 15% or more. Both need 30 visits on each side.
• Trust: any change of grade; loss or non-human share moving 5 points or more.

At most eight findings, ranked by impact. A D grade or fewer than 30 visits puts an uncertain warning first.

A finding

{
  "kind": "new",
  "metric": "visits",
  "dimension": "source",
  "key": "news.ycombinator.com",
  "before": 3,
  "after": 340,
  "change": 337,
  "change_pct": null,
  "share_of_change": 0.71,
  "sentence": "Visits from news.ycombinator.com jumped from 3 to 340."
}