Skip to main content
Outcomes shows what happened after completed actions and detected content changes. It uses page-level before-and-after measurements and reports correlations, not proof that an action caused a change.

​
Open Outcomes

  1. Open a project
  2. Select Outcomes in the project sidebar
  3. Choose Measured actions or Unclaimed changes
Use the 7 days, 30 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.

​
Measured actions

The Measured actions tab is the default view. Its scoreboard summarizes:
  • Conclusive measurements: actions whose complete comparison has usable evidence
  • Wins: conclusive actions that clear the win floor
  • Win rate: wins divided by conclusive measurements, unavailable when there are none
  • Still measuring: actions awaiting a change or a complete window
  • Unmeasured: actions without a usable comparison
A win requires at least +1 citation per day, or both +5 answer fetches and +25% fetch growth, comparing the 14 days after the change with the 14 days before. Citation comparisons require probe evidence in both windows. The citation-lift qualifier sums citation wins only. A qualifying rise does not prove that the action caused it. Each row shows the action, result, citations per day, presence change, answer fetches when available, and measurement date. Select a row to inspect its evidence. Use the result filter and page-size control to explore the ledger. Previous and Next preserve the selected range and filter across reloads.

​
Result and confidence

  • Win: the closed comparison clears the win floor with usable evidence
  • Loss: the closed comparison has usable evidence but does not clear the floor; a small positive change can still be a loss
  • Still measuring: the comparison is pending
  • Unmeasured: no usable comparison exists; missing evidence never counts as a loss
Confidence describes sensor coverage, not causality:
  • observed — the sensor covered the full measurement window
  • directional — the sensor covered part of the window
  • still measuring — the measurement window or its data is not ready
  • unavailable — no comparable sensor evidence 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 Result available
  • 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, 30, and 90 days
  • Content hashes, crawl evidence, and a link to page history
Open windows remain labeled window open until enough time has passed. Measured actions receive citation and presence updates after new probe results arrive, through day 90 after the detected change. Results remain available afterward and can be corrected when late evidence arrives.

​
Unclaimed changes

Crawls detect content edits whether or not an action was recorded. Unclaimed changes lists those edits, newest first, beside any measured action that claims them. Filter by URL path and use the page-size, Previous and Next controls to review the full list. When the page has a measured action completed within 14 days of the detected change, select View existing measured action to open it. The change stays unclaimed until it is associated with an action. Claim prevents a duplicate measurement for that change. Later independent edits can still be claimed. Select Claim as measured action to create a completed action dated to the detected change. Select the claimed action to open its measurement detail. Unclaim archives an unchanged manually claimed action and removes its measurement from measured totals. The action, evidence and claim history remain. Claiming it again restores the same action and measurement, including its original title and description. DevTune rejects Unclaim when the action has been edited or gained other linked work. Automatic associations cannot be unclaimed here. Older claims without reversible history also cannot be safely reversed. No action is deleted. Unclaimed-change comparisons update daily through day 14 after the detected change. Their results remain available afterward; late evidence can still correct them. Claiming an older change succeeds immediately while its longer comparisons fill in. Those comparisons show Updating until ready; missing historical evidence remains a coverage gap. The list shows 14-day before/after citation and presence differences. These differences are correlation, not proof of what caused the change. Summary totals cover the selected date range. The path filter affects only the list and its count. The same list is available through GET /api/v2/projects/{projectId}/outcomes/changes and devtune_get_content_changes. Claim and Unclaim use the corresponding /claim and /unclaim POST routes and devtune_claim_content_change / devtune_unclaim_content_change MCP tools. The list returns existingMeasurementId for an unclaimed change on an already measured page; Claim returns 409 when the existing action was completed within 14 days of the detected change. Mutations require actions.write; listing requires outcomes.read. Unclaim requires the current claimToken returned by the list, so an old request cannot undo a later claim. Agents must obtain human approval before changing a claim.

​
Next steps