Skip to main content
Build a dashboard that keeps each API surface’s metric scope visible. This guide uses the reusable client from the Quick start.

Fetch the overview

Request performance, competitors, and source domains with the same period. Keep the returned methodology with the displayed scores so readers can see the response and provider scope.
The Python client in the Quick start does not expose the relationship argument. Filter the returned list as shown, or extend the wrapper to pass that query parameter.

Label the metrics by surface

Do not replace these definitions with similarly named dashboard, export, MCP, or Looker Studio formulas. Show methodology.responsesTotal, methodology.promptsCount, and methodology.providers near the score cards. A change in those values can make two periods non-comparable.

Add response diagnostics

The Answers endpoint applies hasSelfSource=true, but currently ignores the inverse value false. Request SELF-mentioned answers and filter the returned hasSelfSource flag in your client.
JavaScript
The answer diagnostic is limited to the requested page. Its length is not the total number of matching answers. Paginate before calculating a complete count.

Verify the dashboard

  1. Display the selected period and API methodology.
  2. Confirm that SELF and DIRECT relationships are not mixed with other competitor types.
  3. Treat a Share of Voice gap as a difference in the selected answer set, not market share.
  4. Keep answer citations, query fan-out, and competitor mentions as separate observations.
  5. Compare equivalent filters and prompt sets before labeling a trend.