Check the impact of a release

Pass your release version

Add version to the snippet from the Setup page:

import { Flamio } from '@flamioai/web-sdk';

Flamio.init({
  projectKey: 'YOUR_KEY_HERE',
  endpoint: 'https://api.flamio.org/api',
  version: 'RELEASE_VERSION',
});

• RELEASE_VERSION — the version you deploy, for example 1.4.2 or a commit hash. Set it at build time, so that every deploy carries a new value.
• YOUR_KEY_HERE — your project key, as in the Setup snippet.

Sessions are grouped by this value.

Deploy and let visits arrive

Deploy your site. New sessions carry the version. From then on, a version multi-select (All versions) appears in the filter bar of every On-Live screen.

Open Analytics

In the sidebar, under Flamio On-Live, click Analytics. The project's Analytics dashboard opens. Set the period in the date picker.

Read the UX score over time

The UX score chart draws the score over time on a 0–100 scale, with good, needs-attention and poor bands. Each release is a dashed vertical line.

Read the release table

Release impact, beside it, lists the newest release first:

• Deployed — when the release first appeared, with its visits under the date.
• UX score — the release's score.
• Change — how the score moved against the release before it.

When the newest release scored clearly lower than the one before, the table opens with UX regression after and that version, with both scores and the number of visits.

Dig into one release

Click a release to list its visits. To scope every chart to some releases, pick them in the version filter. The two panels under the charts — How often visitors return and Scroll depth by page — say which filters they do not follow.

See what changed

Scroll down to Friction by type, Most-struggled elements and Friction over time to see which problems grew with the release.