Skip to main content
Outcomes shows what happened after completed actions and detected content changes. It uses page-level before-and-after measurements and labels improvements as correlated, not proven.

​
Open Outcomes

  1. Open a project
  2. Select Outcomes in the project sidebar
  3. Choose Ledger, Attribution, or Timeline
Use the 7 days, 28 days, or 90 days control to choose which measured actions or changes appear. Row deltas always compare the 14 days after a detected change with the 14 days before it; the reporting-window control does not change that comparison.

​
Ledger

The Ledger tab is the default view. Its scoreboard summarizes:
  • Actions tracked — measured, in-flight, and unmeasured actions in the selected range
  • Measured wins — changed pages where citations rose by at least 1, or answer fetches rose by both at least 5 and 25%
  • Win rate — measured wins divided by measured actions
  • Median time to signal — time from action completion to measurement
  • Unmeasured — actions with unmatched URLs or missing sensor coverage
A measured win is a correlation rule: usable measurements must show either a citation increase of at least 1 or an answer-fetch increase of both at least 5 and 25% in the 14 days after the change compared with the 14 days before. A smaller positive change does not count toward Measured wins or Win rate. A qualifying rise does not prove that the action caused it. Each ledger row shows the action, measurement status, citations per day, presence change, answer fetches when available, and measurement date. Select a row to open its measured-action detail.

​
Status and confidence

Outcomes uses the same status vocabulary throughout the ledger and timeline:
  • Pending detection — waiting to detect the page change
  • Pending URL match — no crawled page matches the action links yet
  • Change detected — the before-and-after window is open
  • Correlated — a supported signal improved after the change; correlated, not proven
  • No change — the measurement closed without a qualifying improvement
Confidence describes sensor coverage, not causality:
  • observed — the sensor covered the full measurement window
  • directional — the sensor covered part of the window
  • insufficient window — there was not enough covered time for a complete comparison
  • not observable — no comparable sensor window exists
Cells use states such as measuring · day N of 14, awaiting next crawl, and window open instead of treating incomplete measurement as zero.

​
Measured action detail

Select a ledger row to review:
  • The lifecycle from Action completed through Measured
  • Citation and presence changes
  • Answer-fetch changes and their sensor basis
  • AI referrals as unavailable when no comparable GA4 measurement exists
  • A daily page-signals chart with the detected-change marker
  • Impact windows for 7, 14, 28, and 90 days
  • Content hashes, crawl evidence, and a link to page history
Open windows remain labeled window open until enough time has passed.

​
Attribution

The Attribution tab links detected content changes to completed DevTune actions. The tab name describes that record linkage; its signal deltas remain correlations, not causal attribution. Use it to:
  • Compare detected changes with the actions that claim them
  • Find Unattributed changes, meaning no completed action currently claims the edit
  • Filter changed pages by URL path
  • Select Claim change to create a completed measured action for an unclaimed change
The table shows 14-day citation and presence deltas for the changed page. Unattributed lift is the sum of those page-level citation changes for unclaimed edits; it does not assign the change to a person, campaign, or channel.

​
Timeline

The Timeline tab places content changes and outcome measurements on one chronology.
  • Switch the line between Presence rate and Citations / day
  • Compare that line with Content changes / day bars
  • Use Action measured markers to find completed measurements
  • Filter the event feed by Measurements, Changes, or Signals
The feed includes measurement openings and closures, detected and unattributed changes, answer-fetch signals, coverage drops, and URL-match failures. Selecting an event highlights the corresponding point on the chart when one is available.

​
Next steps