Skip to content
← All resources

Changelog

What has shipped

Entries are added when a capability is usable, not when work on it starts.

2026

September — Live and deployment intelligence
The real-time view with business context rather than a counter, deployment annotations ingested from GitHub, automatic before-and-after comparison around a release, and revenue impact analysis across technical segments.
August — Revenue & Sales
Finance and accounting integrations, sales attribution under selectable models, customer value by cohort and source, subscription and order analytics, refund handling that reduces revenue intelligence rather than leaving gross value standing, and margin analysis using the finance system's own measures.
July — Conversions
Goal configuration around a chosen business outcome, multi-step funnels with explained drop-off changes, form analytics, the server-side business event API with idempotency, transparent attribution models and customer journeys under the configured identity mode.
June — Intelligence
The daily, weekly and executive briefings, anomaly detection with context-aware baselines, automated root-cause decomposition, opportunities, period comparison, Explain This and the evidence model behind every answer.
May — Ask AI
Natural-language analytics over the semantic metric layer, multi-step root-cause plans, comparison questions, evidence panels and follow-up questions that retain analytical context.
April — Collection and traffic quality
The dedicated edge analytics event contract, durable spooling off the request path, Smart Beacon with first-party delivery, route normalisation, campaign-parameter allowlisting, and classification separating people from verified crawlers, AI crawlers, other bots and security traffic.

How entries get added here

One rule, so the changelog stays worth reading.

  • A capability appears here the day it becomes usable by a customer, not the day work starts
  • A change to a metric definition is announced before it takes effect, because it moves numbers people have already reported
  • Breaking API changes are a new version and say so explicitly
  • Anything affecting collection, retention or AI provider selection is announced in advance

Keep reading

The rest of the documentation

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