Get Domains Report
Get a report on Source Domains.
Aggregation Formulas
When aggregating results across multiple rows/dimensions, use the following formulas:
- citation_rate:
sum(citation_count) / sum(retrieval_count) - retrieval_rate:
sum(retrieval_count) / sum(total_chat_count) - retrieval_percentage:
sum(retrieved_chat_count) / sum(total_chat_count)
filters vs having
filters are pre-aggregation row filters (applied as WHERE before GROUP BY) on the source-row table. Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, domain, domain_classification, url, url_classification, mentioned_brand_id, mentioned_brand_count, gap.
- Population (
model_id,model_channel_id,country_code,prompt_id,tag_id,topic_id,chat_id) shrink both numerator and denominator (total_chat_count). - Source-side (
domain,domain_classification,url,url_classification) and per-row mentioned-brand predicates (mentioned_brand_id,mentioned_brand_count,gap) shrink the source-row scope feeding aggregation.total_chat_countis computed from a chat-level table that doesn’t carry these columns, so the denominator narrows only on chat-level fields.
having are post-aggregation row filters (applied as HAVING after GROUP BY). Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, domain, domain_classification, mentioned_brand_id, mentioned_brand_count, gap. They select which aggregated rows are returned and do not affect denominators.
Authorizations
Query Parameters
Required if using a company api key
"or_f45b94ba-5e35-4982-93ed-285e72ee14eb"
Body
Required if using a company api key
"or_f45b94ba-5e35-4982-93ed-285e72ee14eb"
1 <= x <= 10000x >= 0full-date notation as defined by RFC 3339, section 5.6, for example, 2017-07-21
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$"2025-09-22"
full-date notation as defined by RFC 3339, section 5.6, for example, 2017-07-21
^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$"2025-09-22"
Dimensions to break down the report by.
prompt_id, model_id, model_channel_id, tag_id, topic_id, date, week, month, country_code, chat_id ["tag_id", "model_id"]Pre-aggregation row filters (applied as WHERE before grouping). Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, domain, domain_classification, url, url_classification, mentioned_brand_id, mentioned_brand_count, gap. Population fields (model/country/prompt/tag/topic/chat) shrink both numerator and denominator. Source-side fields and per-row mentioned-brand predicates shrink the source-row scope feeding aggregation; total_chat_count comes from a chat-level table that doesn't carry these columns, so they narrow the numerator only. Multiple filters are AND'd.
Deprecated: use model_channel_id filter instead
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
- Option 13
- Option 14
[
{
"field": "model_id",
"operator": "in",
"values": ["gpt-4o-search"]
}
]Post-aggregation row filters (applied as HAVING after grouping). Select which aggregated domain rows are returned. Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, domain, domain_classification, mentioned_brand_id, mentioned_brand_count, gap — population fields require the matching value in dimensions. Multiple filters are AND'd.
Deprecated: use model_channel_id filter instead
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
- Option 9
- Option 10
- Option 11
- Option 12
[
{
"field": "domain",
"operator": "in",
"values": ["example.com"]
}
]Sort results by one or more fields. Multiple entries create a multi-key sort. Direction defaults to desc. When omitted, a default ordering is applied.
[
{
"field": "citation_rate",
"direction": "desc"
}
]Response
Success
Success
