> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review distribution-channel visibility

> See which retailer, marketplace, and distributor sources appear in measured answers.

Answer: “Which retailer, marketplace, and distributor pages are being cited for our measured topics?”

## Prepare the scope

Use `list_projects` and `list_runs` to choose the project and completed run. Check readiness, then call `get_results_stability` for the same run and supported filters. For each measurement, preserve the scope, returned confidence interval, and row-quality fields. See [run selection](/developers/guides/07-projects-and-runs) and [decision-grade measurement](/developers/guides/10-stability).

The JSON examples below are MCP `tools/call` parameter objects. Replace ID placeholders and sample selections with values discovered in your account.

## Retrieve the evidence

1. Use `list_dimension_options` to find the measured topics and platforms. Apply only filters that exist in that project.
2. Read URL-level citation coverage across sources.
3. Inspect relevant page URLs and use `analyze_page_performance` to retrieve available citing statements and captured page sections.

```json theme={null}
{
  "name": "get_citation_score",
  "arguments": {
    "project_id": "PROJECT_ID",
    "run_id": "RUN_ID",
    "metric": "coverage",
    "aggregation_level": "url",
    "subject": {
      "kind": "all"
    }
  }
}
```

## Classify the channels

Review each selected source and assign your own channel label, such as retailer, marketplace, distributor, publisher, or owned website. Record the classification basis beside the URL. These are report labels; the interface does not expose a native distribution-channel filter.

## Build the report

List each selected URL, its reviewed channel, citation coverage, confidence interval, and supporting answer evidence. Keep the project's topic and platform scope visible.

Do not sum URL coverage into a channel coverage percentage: the same response can cite multiple pages. This workflow supports a page-by-channel evidence table. It does not supply a deduplicated channel-level metric or prove sales through that channel.

Reference: [citation scores](/developers/tools/get_citation_score), [page evidence](/developers/tools/analyze_page_performance).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.