Get measured actions with authoritative improved, mixed, no_clear_change, declined, still_measuring and unmeasured results, the evidence behind each result (counts, active days, exposure and the chance of a shift that large), and a conclusive-measurement improvement rate. Each Results item carries method v1 or v2 once closed with evidence, and null while open. Agent Picks rows have null method and retain their own agentPicks.method. A live lookalike action (reporting a site imitating the customer) carries lookalike: the site as text, and answers checked, answers citing it and the rate in the 14 days before and after going live, per platform and overall (overall sums the platforms checked in both windows), with each result; a fall is improved, mixed means platforms moved in opposite directions and otherwise the overall result follows the overall rate, a platform without answers checked in a window is unmeasured, a window older than the 181 retained days is unmeasured, and its method is null. Present only while the account has lookalike sites. Closed results keep their method. New closes use v2: only full-window evidence can conclude, citations compare the same live prompt/platform cohort in both windows, fetch exposure counts sensor-covered days, and the count test allows for daily-count overdispersion. A v2 metric without full coverage keeps its counts with direction null and is not compared. Reporting windows filter actions; comparisons use fixed 14-day before/after windows. Each item includes overlappingActions per page and comparison window, listing other completed actions with actionId, title and completedAt. With interventionId, top-level overlappingActions covers that measurement’s 7, 14, 30 and 90 day comparisons, even outside the selected ledger cohort. Each comparison has state available with an actions array, or unavailable with actions null if the supplementary check failed; measurements still load. Shared page movement cannot be attributed to this action alone. Also returns analytics-attributed conversions for fixed 30 and 90 day windows. If the measurement detail read fails, top-level overlappingActions contains one unavailable entry with actions=null and no page/window metadata. Redirect-shipped missing-page actions include evidence.redirect404 with requestedPath, hosts, before/after 404 request counts and fixed-window bounds, status-coverage day counts, source and generation. Its state uses 404 rows observed before each capture: stopped (observed before, none after), still_happening (observed in both), or unmeasured (incomplete status coverage, unknown request hosts, open window or no baseline 404s). A later counter increase nulls that count with reason counter_changed and preserves a known state. Both windows require coverage on every UTC date for every requested host; the browser snippet cannot measure 404s. This separate metric never changes the overall result. A saved suggested destination identifies a redirect; a saved requested URL requires an observed 3xx response and no 2xx responses across the requested hosts after the window closes. Other actions omit the field. A shipped robots.txt unblock Action includes evidence.agentScope on one active measurement (its earliest page still published): the hosts of its drafted robots.txt files, and for each unblocked provider and bot class the requests across every document path on the hosts whose own robots.txt file unblocked it (agents[].hosts; never a host that still blocks it) in the fixed before/after windows, recorded at window close. Answer fetchers count answer fetches and index bots count crawls; neither is added to the other. Entries merge crawlers of the same provider and class (for example Claude-User and Claude-Web), never per user-agent token. Counts are null with state unmeasured while the window is open (window_open), or unless a Cloudflare log pull on the exact hostname or edge middleware reporting on that exact host every day covered every host for both windows (no_sensor, partial_coverage); a www host and its bare domain are separate hosts; the browser snippet cannot see these requests. coverage (overall, per host in hosts[] and per agent line) is verified when a whole-site Cloudflare log pull covered the exact host, or sensor_reported when edge middleware reported on it every day without proof it sees every path; describe sensor_reported counts as seen by the edge sensor, not verified. A day with no accepted edge event leaves the window unmeasured. Historical (as-of) reads omit agentScope. This separate metric never changes the overall result.