Get Brands Report
Get a report on Brands.
Aggregation Formulas
When aggregating results across multiple rows/dimensions, use the following formulas:
- sentiment:
((sum(sentiment_sum) / sum(sentiment_count)) / 2 + 0.5) * 100 - position:
sum(position_sum) / sum(position_count) - visibility:
sum(visibility_count) / sum(visibility_total) - share_of_voice:
mention_count / sum(mention_count)
filters vs having
filters are pre-aggregation row filters (applied as WHERE before GROUP BY). They shrink both the numerator and the denominator of ratio metrics. Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, brand_id. Note that brand_id in filters shrinks share_of_voice’s denominator too — so filtering to one brand collapses SoV to 1.0. Use having for brand_id if you want SoV preserved.
having are post-aggregation row filters (applied as HAVING after GROUP BY). They select which aggregated rows are returned and do not shrink ratio-metric denominators. Filtering {field: "brand_id", values: [X]} here returns only brand X’s row, but share_of_voice still divides X’s mentions by mentions across all in-scope brands — so SoV stays in [0, 1]. Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, brand_id.
Population fields (model_id etc.) are also allowed in having but require the matching value in dimensions so the column appears in GROUP BY; otherwise the request is rejected.
When dimensions are requested, the share_of_voice denominator follows the same grouping as the numerator. Requesting prompt_id as a dimension produces per-(brand × prompt) rows whose share_of_voice is the brand’s mentions in that prompt divided by all brands’ mentions in that prompt.
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). Shrinks both the numerator and the denominator of ratio metrics. Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, brand_id. Filtering by brand_id here also shrinks share_of_voice's denominator — so SoV collapses to 1.0 when scoping to a single brand. If you want SoV preserved (X's share against all in-scope brands), put brand_id in having instead. 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
[
{
"field": "model_id",
"operator": "in",
"values": ["gpt-4o-search"]
}
]Post-aggregation row filters (applied as HAVING after grouping). Allowed fields: model_id (deprecated), model_channel_id, country_code, prompt_id, tag_id, topic_id, chat_id, brand_id — population fields require the matching value in dimensions so the column appears in GROUP BY. Selects which aggregated rows are returned without shrinking ratio-metric denominators. Multiple filters are AND'd together.
Deprecated: use model_channel_id filter instead
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
- Option 7
- Option 8
[
{
"field": "brand_id",
"operator": "in",
"values": ["kw_abc123"]
}
]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": "visibility",
"direction": "desc"
}
]Response
Success
Success
