Reports the Performance page's Overview tab for a date range: one row per funnel stage, each the same number its tab shows. Visibility is Search Console impressions; Visits are Search Console clicks and PostHog site pageviews; AI answers is the Named rate per engine from the latest weekly check in the market (no compare, no target, never one blended number); Leads are first-touch leads Mark recorded, counted on the Pacific Time days Search Console reads. Each row has stage, metric, value, previous and changePercent (with compare), target, dataThrough, connection (ready, or why there is no number, such as not_connected, no_property, no-posthog, no-signal or failed) and appUrl, the tab it opens. A failed Site pageviews row has failure: busy means PostHog didn't answer in time (it runs 3 queries at once per project and queues the rest), so try again in a minute; the PostHog connection is fine. error is any other failure, such as lost access, so check the PostHog connection. target is { month, target, actual, progressPercent }, exactly as the Targets page and get_content_performance compute it, and only when from to to is one target month (a whole past month, or this month from the 1st to today); today only leads have a matching KPI metric. compare adds the window of the same length just before. Does not change anything. Related: get_search_performance, get_visitor_locations, get_ai_visibility, get_content_performance.