AI audit findings across the connected ad accounts (Meta, Google, Yandex Direct): issues ranked by priority (severity high/med/low) with a stable status. Can be scoped to one client.

Workspace ad KPIs for a date window: spend, impressions, clicks, conversions, revenue, CTR, CPC, CPM, ROAS, CPA, reach, frequency. reach/frequency are Meta-only (null for older data and non-Meta accounts); frequency = impressions/reach and is not additive across days. entityRef narrows to a single campaign/adset.

Daily metric series for the workspace over a date window (date, spend, impressions, clicks, conversions, revenue, reach, frequency) — for trends and charts. reach/frequency are Meta-only (null for older data and non-Meta accounts); daily reach must not be summed across days. entityRef narrows to a single campaign/adset.

Metrics broken down by dimension: audience | placement | platform | country | region | device | dma | hourly. Returns segments with metrics (including reach/frequency — Meta-only, null for older or non-Meta data) as of the latest snapshot date (asOf) inside the window.

Per-campaign or per-adset metrics and KPIs for a date window (spend, CTR, CPC, ROAS, CPA, reach, frequency…), sorted by spend. reach/frequency are Meta-only (null for older or non-Meta data). dataSince is the earliest date entity-level data has been collected since: a window earlier than that comes back empty.

Workspace conversions broken down by action type for a date window: raw — the plain action-type → value map, buckets — canonical buckets (purchase, lead, add_to_cart, complete_registration, landing_page_view, engagement…). Buckets are NOT additive: engagement is an aggregate and reactions/comments/shares are its components (summing them double-counts).

Workspace clients with their context (name, niche, margin, status) — for analysis scoped to a specific client.

Leaderboard of competitor creative tags from the Meta Ad Library: which formats/angles/offers are used most and live longest (days_live is a proxy for what wins). This is intel the plain metrics tools do not have.

Search stored competitor creatives from the Meta Ad Library: by keyword (query — hook/headline/tags) and/or by brand (brand — exact page-name filter). Empty input returns the top by days_live. Returns hook, headline, format, tags, country and ad_archive_id for a follow-up Vision analysis. days_live is a proxy for what wins.

Vision analysis of one competitor creative by ad_archive_id: hook, angle, format, strengths and risks, plus a video transcript when available. Analysis the plain metrics tools do not have. Find the creative with roasr_spy_search first; if it has not been analysed yet, start the analysis inside the app.

Rich signals for a date window by kind: Google search terms, keyword quality score, impression share, auction insights, conversion actions by category, asset performance, landing pages, shopping, video funnel, bidding, asset groups; Meta — ad quality rankings. Per-account latest snapshot inside the window (payloads of different accounts are not aggregated); the response is capped by limit (default 50) — this is intel the plain metrics tools do not have.

Pause or resume one advertising campaign (Yandex Direct). This CHANGES the live ad account. It only works if the account owner granted your API key permission for this operation and listed this campaign as allowed; otherwise it returns a permission error naming what to enable. Returns a command with a state: applied (confirmed), verifying/unknown (not confirmed yet — poll roasr_command_get), partial, failed, conflict or rejected. On a timeout or network error, retry with the SAME idempotencyKey: the repeat returns the original command instead of changing the campaign twice.

Status and attempt history of a write command created by roasr_campaign_set_state: final state, per-target results, the ad platform request id and the API points it consumed. Use it to resolve a command left in verifying or unknown.

Yandex Direct only, read-only. One of the Direct-specific breakdowns collected as signals: search_queries (search terms with spend/conversions — same data as roasr_yandex_search_queries), keywords (keyword-level state, bids, impressions/clicks by search vs network), ads (ad status and metrics — same data as roasr_yandex_ads), bidding (per-campaign daily budget and bid strategy). Errors if accountId points to a non-Yandex account. For campaign/adset totals or device/region/audience/placement splits on a Yandex account, use roasr_metrics_campaigns / roasr_metrics_breakdown instead — those already work for any platform.

Yandex Direct only, read-only. Search queries for a date window: query text, campaign/ad group, match type, impressions, clicks, spend, conversions. The most valuable Direct signal — use it to find what share of spend went to queries with zero conversions. Errors if accountId points to a non-Yandex account.

Yandex Direct only, read-only. Ads with moderation status and metrics for a date window: state/status/statusClarification, whether the ad has a second headline, sitelinks, UTM markup, an image, a turbo page, plus impressions/clicks/spend/conversions/ctr. Use it to find rejected ads, or ads missing a second headline or link markup. Errors if accountId points to a non-Yandex account.

Yandex Direct only, read-only. Which Yandex.Metrika goals are selected for an account, and hence which goals its conversions are counted against — no window, this is current config, not a metric series. Empty goals means that account's conversions cannot be attributed to a goal; do not treat its conversion numbers as trustworthy. Errors if accountId points to a non-Yandex account.

Subscription plan, its limits (ad accounts, AI audits, competitors), the API rate tier, and the remaining Yandex Direct daily quota per account. Call this before heavy report pulls: Direct enforces a daily unit budget per login, its report service does not report unit usage at all, and only five reports may be queued at once.