links.10x.in/docs/end-user/ad-qa-and-reports Published:

Ad Q&A and Reports

Note

This is a draft stub. Report templates and QA playbooks will be expanded in a follow-up documentation pass.

Role and auth requirements

  • Primary roles: OWNER, OPERATOR
  • Auth mode: JWT (Authorization: Bearer <token>)

UI flow (draft)

  1. Run ad QA checks.
  2. Review anomalies and recommendations.
  3. Generate and export reports.

API fallback (draft)

  • POST /v2/handles/{handle}/ad-intelligence/qa
  • POST /v2/handles/{handle}/ad-intelligence/report

Input validation rules

  • Ad Q&A body must be a JSON object with question (required) and optional period (7-90 days).
  • Report query supports type=weekly|monthly|custom; custom requires numeric period (7-90 days).
  • Non-object JSON payloads (for example null) are rejected as invalid input.

Reporting window behavior

  • Period-over-period comparisons use equal-length windows.
  • Example: period=7 compares the current 7-day window (including today) with the immediately preceding 7-day window.

Failure and remediation (draft)

  • 400 invalid_json: request body is missing, malformed, or not a JSON object.
  • 400 invalid_period: period must be a finite numeric value in accepted bounds.
  • 400 question is required: provide a non-empty question field for Q&A.
  • 401 unauthorized: re-authenticate.
  • 403 forbidden: confirm role access on handle.
  • 503 unavailable: retry after upstream dependency recovery.