Audit History

Audit History is where every audit your project has ever run is kept, together with a timeline that shows how your ASO Readiness Score moved between them. It answers two questions on one page: how has the score changed, and which audits (and listing changes) produced those changes.

Why it matters

A single audit is a snapshot. The value of running audits repeatedly is the trend: whether a listing edit actually moved the score, whether a competitor shift or a store-side change quietly cost you ground, and whether the work you shipped is holding. Audit History turns a pile of one-off reports into a record you can reason about over time.

How to read it

Open Audit History from the project. The page stacks two views:

The score timeline (top) — a time series of your overall ASO Readiness Score, with the pillar scores overlaid and per-engine trend charts below.
The Audits Archive (bottom) — a dated list of every audit. Click any row to open that full audit report.

The score timeline

The timeline needs at least two audits to draw trends. Until then it shows a lighter state:

No audits yet — a prompt to run your first audit.
One audit — your First Audit Score and a note that trends need at least two audits.
Two or more audits — the full timeline: delta cards, the overall score chart, per-engine charts, and an event list.

At the top, delta cards summarize the net score change across the window and the most recent audit-to-audit change. The main Overall ASO Score chart plots the readiness score over time, with Discoverability, Conversion, and Trust pillar lines overlaid. Below it, each scored engine (Keywords, Store Text, Screenshots, Icon, Sentiment, Intent, AI Discoverability) gets its own trend chart with its current score and the change since the previous audit.

Click any point on a chart to jump straight to the audit that produced it.

Controls

Three controls shape what you see:

Locale — for a multi-locale project, switch which locale’s score series you’re viewing. The timeline compares audits within a single locale, so this matters when your listing differs by market.
Period — the lookback window (for example, the last 90 days, or all of it).
Group by — collapse points to daily, weekly, or monthly.

Reading the events

The timeline marks meaningful moments so a score change has an explanation next to it:

Revision published — a draft you published took effect. Where a measured KPI lift was captured for that revision, its badge appears on the marker.
Store change detected — the listing content changed between two audits without a Revision you published through Apptonomy — someone edited the live listing directly, or the store changed something.
Change tracking starts from this audit — the first audit that carried a content fingerprint. Earlier audits can’t be diffed for content changes, so tracking begins here.
Engine updated — the audit engine version changed between two audits, which can shift scores independently of anything you did to the listing.

When you see a score move, look at the nearest event first. A jump that lines up with a Revision published marker is your change working; a move next to Store change detected or Engine updated has a different cause.

The Audits Archive

Below the timeline, the archive lists every audit by date, newest first. Each row opens that audit’s full report — the same report you’d see right after running an audit, preserved. Scheduled audits and manual audits both land here.

How it connects to what you do

Run audits on a cadence so the timeline stays populated — set one up in Scheduled Audits.
When a listing edit lands, run an audit and watch for the Revision published marker to confirm the change registered.
Open any archived audit to work its recommendations, or to compare what changed against a later run.