Report history
The Report History screen, what it counts, what its Export All button really does, and where the old Activity timeline went.
Last updated 2026-08-11
Summary#
Report History is the at-a-glance view of how much analysis you have run: four counters, a 14-day chart, and a chronological list of your runs. It answers "how much have we been doing", not "where is the thing I ran". For that second question, go to Saved Work — see Saved Work.
Purpose#
"Where is my report" and "how much have we run this month" feel like the same question and are not. One wants a specific artefact back; the other wants a shape over time. Saved Work holds the artefacts. Report History holds the shape.
This article used to describe a third screen as well, an Activity timeline inside the Library. It has been removed — see What happened to Activity below.
Requirements#
- A signed-in account.
- At least one recorded analysis run, or the screen shows its empty state.
- No plan requirement.
Permissions#
Report History is scoped to your workspace and is read-only. Nothing on it changes data. What a team member can see is described in What teammates share.
Navigation Path#
Dashboard → Track & Report → Report History
It is also reachable from the user menu in the top right of the app.
Step-by-Step Guide#
Read the screen#
- Open
Dashboard → Track & Report → Report History. - The four counters at the top summarize your analysis activity: Total Runs, Unique Domains, Most Recent and Last 7 Days.
- The card below charts Analysis Activity (Last 14 Days).
- Under the filter row, the timeline lists your runs in chronological order.
- With no analyses recorded yet the screen shows No analyses yet with the note that every report you run in Metric Vault is saved here so you can review trends and re-run with one click, plus a Run your first analysis button that takes you back to the Dashboard and puts the cursor in the Quick Preview box.
About the Export All button#
Report History carries an Export All button in its header. Pressing it downloads report-history.json, containing your latest 100 saved runs. It does not go through the platform's export engine, so there is no CSV or PDF option here.
When you want a real file, use one of these instead:
| You want | Use |
|---|---|
| A file of one report's contents | The Export PDF / Excel / CSV / JSON buttons on the tool itself. See Exporting results |
| The raw data of a past run | Download JSON in the saved-result viewer. See Saved Work |
| A record of usage for billing | The usage figures in your account. See Tracking your usage |
What happened to Activity#
The Library used to carry a second tab called Activity: a filterable timeline of everything that had happened on the account, with summary tiles, category chips and a detail panel. It has been removed.
It answered "what happened", and that was not the question people opened the Library with. They came to find a result they had already paid for, which is what the Saved Work file explorer does — and the timeline sat in front of that job rather than helping with it. Removing it left one screen doing one thing well.
Where its answers live now:
| You used to ask Activity | Now |
|---|---|
| Where is the report I ran last Tuesday? | Saved Work, which was always the right screen for this — Saved Work |
| How much have we run? | The counters and chart on this screen, and Tracking your usage |
| Did that scheduled run fail? | Why didn't my alert fire?, and the failure notifications in Notification preferences |
| Who changed that setting, and when? | Not available to customers. Support can check the admin audit log — Audit log |
Nothing stopped being recorded. The events are still written, and the admin Run Log still reads them, so if you need something proven from the record, support can look it up. Only the customer-facing timeline is gone.
Which record to use#
| Question | Screen |
|---|---|
| Where is the report I ran last Tuesday? | Saved Work — Saved Work |
| How many analyses did we run this month? | Report History counters, and Tracking your usage |
| Has our analysis volume gone up? | The 14-day chart on Report History |
| Did that scheduled run fail? | Why didn't my alert fire? |
| What has changed on a competitor's site? | Not here — Competitor Monitor |
Screen states#
| State | What you see |
|---|---|
| Nothing recorded yet | No analyses yet with the Run your first analysis button |
| Runs recorded | Four counters, the 14-day chart, and the run list below them |
Examples#
Example: Your team wants to know whether audit volume is rising before renewing a plan. Open Report History, read Last 7 Days against Total Runs, and check the 14-day chart for the trend. Confirm the billable figure in Tracking your usage, which is the authoritative one.
Example: A client asks for the audit you ran for them in June. Report History tells you it happened; Saved Work gives you the report itself. Go straight to Saved Work, open the Domain Overview folder, and reopen it for free.
Screenshots#
 chart, and the Export All button.)
Tips#
- Report History is a summary. If your question ends in "…and I need to open it", the answer is Saved Work.
- The counters cover recorded analysis runs, not every action, so they will not match your credit usage exactly.
- Export the underlying reports you care about on the day you make them. A history screen records that a run happened; only an export holds what it said.
Best Practices#
- Use Report History for volume questions and Saved Work for retrieval questions.
- Check the 14-day chart before a plan change, so the decision is based on your real pattern rather than a hunch.
- Do not rely on history to hold results: saved results are purged after 90 days, so a history entry can outlive the result it refers to.
Common Mistakes#
- Expecting Export All to download a spreadsheet. It opens the browser print dialog. Use the per-tool export buttons for files.
- Reading the counters as your billable usage. See Tracking your usage.
- Looking for the Activity tab. It has been removed; see above.
Limitations#
- The screen does not let you reopen a result directly; use Saved Work.
- There is no filtering on this screen. Filtering by tool, date or domain is not built; the timeline shows your most recent runs and nothing narrows them.
- Clicking a timeline row does nothing. There is no replay from this screen.
- Export All writes JSON only; there is no CSV of the history list itself.
- There is no customer-facing audit log of settings changes or sign-ins.
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
| Report History shows No analyses yet | No analysis runs have been recorded for this account yet | Run a tool, then reopen the screen |
| The counters look lower than your real usage | The counters cover recorded analysis runs, not every action | Check Tracking your usage for the authoritative figure |
| Export All opened a print dialog | That is what the button does | Use the per-tool export buttons for files. See Exporting results |
| The Activity tab is missing | It was removed | Use Saved Work for results and this screen for volume. See above |
| A run is listed here but not in Saved Work | The result was not stored: the run failed, or its payload was over the storage limit | See Saving a result |
FAQs#
Is Report History the same as Saved Work? No. Saved Work holds results you can reopen and re-run. Report History summarizes analysis activity over time.
Where did the Activity timeline go? It was removed. Saved Work answers the retrieval question it was getting in the way of, and this screen answers the volume question. The underlying records are still kept for support.
Can I export the activity log? Not from this screen, and there is no customer-facing log any more. Administrators have their own audit tooling; see Audit log.
Does Report History show what a teammate did? It is scoped to the workspace you are in. What a member can see is described in What teammates share.
How far back does it go? The counters and list cover your recorded runs. Note that saved results themselves are removed after 90 days, so an entry can refer to a result that is no longer openable.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.