Impact dashboard

Fix and verify · 12

Impact dashboard

See each month’s fix record and the proof behind every verified fix, find where open issues meet the most visitors, and share the results.

5 min read Updated 4 October 2026

01 / Overview

Show what your fixes achieved

The Impact page turns your issue history into results you can show: what UX Robot found each month, what your team shipped, which fixes a check verified on the live website, and where open issues still meet the most visitors. Open Impact in the organisation menu and choose a month. Months follow the organisation’s timezone, and the current month shows results so far.

It uses no AI and no analysis units: everything comes from your issues, their checks, the page timeline and GA4.

02 / Fix record

The month’s fix record

  • Verified fixed: issues a journey run or spot check saw fixed on the live website this month, with a screenshot.
  • New issues found: issues approved reports opened this month.
  • Marked shipped: issues your team, a ticket tool or a coding agent marked as live.
  • Came back: fixed issues a later check found again.
  • Median days to verify: for this month’s verified fixes, the middle number of days from when the issue was found to when a check verified it.

Below the counts, the page shows how many issues are open, shipped and waiting for a check, and verified fixed to date.

03 / Proof

The proof behind each verified fix

Each verified fix is listed with:

  • the screenshot from the check that verified it;
  • how many days it took from found to verified;
  • the page change that delivered it, from the page timeline: the change in which the proposed wording went live, otherwise the last change to the page between finding the issue and verifying it;
  • GA4 for that page from before and after the change, when GA4 is connected and enough days have passed.

04 / Where to fix next

Where open issues meet the most visitors

With GA4 connected, Where to fix next lists every page that still has open or shipped issues, busiest first, with its views, sessions and key events over the last 28 complete days. Countries you exclude from evidence are excluded here too. The figures refresh a few times a day.

Sessions count every visit that included the page, so one visit can appear on several pages; add up views, not sessions, across pages.

05 / Share

Share the results with stakeholders

Select Create a link to give people without a UX Robot account a private page with the month’s fix record, verified fixes, their screenshots and page changes. It does not include open issue details or GA4 figures for open issues.

  • Copy the link straight away: only a fingerprint of it is stored, so it cannot be shown again.
  • Links expire after 90 days, can be revoked at any time, and show how many times they were opened.
  • The page is built when it is opened, so a link to the current month stays up to date until the month ends.
  • Shared pages ask search engines not to index them, and serve only the screenshots that prove that month’s fixes.

06 / Monthly summary

A summary in Slack or Teams every month

Add Monthly impact summary to a Slack or Microsoft Teams channel in the Alerts panel on the Issues page. From 9am on the 1st, in the organisation’s timezone, the channel receives last month’s verified fixes, median days to verify, new issues, fixes that came back, and what is still open, with a link to the Impact page.

Each channel receives each month once. A channel added part way through a month receives its first summary at the start of the next month, and an organisation with no issues yet is skipped.

Still stuck?

Use the contact form and include the page, action, and exact error message involved. Contact UX Robot.