Advertising
The campaign tree and its performance. Requires campaigns:read.
Each level pairs a structure resource with a metrics one: /v1/campaigns lists what exists, /v1/campaign-metrics lists what it did over a date range.
Servers
List the authenticated account's advertising campaigns
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Page size. The default is enough to explore; raise it only when you need to walk a whole collection.
20201100Cursor for the next page: the id of the last record you received. Returns the records after it.
Cursor for the previous page: the id of the first record you received. Returns the records before it.
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Case-insensitive substring match over the campaign name. Use it to find a record by name when you do not have its id, instead of paging through the whole list. Regex metacharacters are matched literally.
1200Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""ENABLED""PAUSED""ARCHIVED""OTHER"Responses
200
GET /v1/campaigns/{id}
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Responses
200
Changes the workflow actually applied to this campaign
Only changes that were APPLIED, and only for real: a dry-run simulation never appears here, under any parameter. Aggregated to a net per entity — data carries one row per target whose bid was moved, with the bid from before the first change against the bid after the last one, so a target raised then capped back down reports direction: unchanged with change_count: 2. That is the reading a flat decision list hides, and it is usually the answer to whether the optimization is doing anything. Proposals are excluded: the optimizer computes a bid the economic ceiling can then cut, and only what reached Amazon is reported. Non-bid changes (harvested keywords, negatives, placement adjustments, blocked or quarantined targets) do not share the table because they have no previous bid — they are counted in other_changes. Monetary amounts are decimal strings. The window is capped at 90 days, which is the retention of the underlying records.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
"^\\d{4}-\\d{2}-\\d{2}$""^\\d{4}-\\d{2}-\\d{2}$"Page size, up to 500. Paginate with offset, not with a cursor: these rows are aggregated changes, not records with an id. Narrow the window with start_date / end_date instead of walking every page.
1001500009007199254740991"asc""desc""desc"Responses
200
campaign-metrics
Advertising performance per campaign, aggregated from the account's report history. Requires campaigns:read.
Operations
Advertising performance per campaign, from the account's report history
Aggregated from the report history over a required start_date/end_date window. Unlike the rest of the API, this resource paginates with limit/offset (an aggregated row has no id to use as a cursor) and has_more tells whether another page follows. Monetary amounts are decimal strings; ratios are fractions (0.1642 = 16.42%) and are null, never 0, when their denominator is zero.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-01""^\\d{4}-\\d{2}-\\d{2}$"Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-31""^\\d{4}-\\d{2}-\\d{2}$""total""daily""total""total"Page size. For a top-N, combine order_by with a small limit instead of raising it: limit/offset bound the response, not what ClickHouse scans.
100100110000009007199254740991"asc""desc""desc""desc"Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""SP""SB""SD""cost""sales""impressions""clicks""orders""units""acos""roas""ctr""cpc""conversion_rate"Responses
200
List the authenticated account's ad groups
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Page size. The default is enough to explore; raise it only when you need to walk a whole collection.
20201100Cursor for the next page: the id of the last record you received. Returns the records after it.
Cursor for the previous page: the id of the first record you received. Returns the records before it.
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Case-insensitive substring match over the ad group name. Use it to find a record by name when you do not have its id, instead of paging through the whole list. Regex metacharacters are matched literally.
1200Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""ENABLED""PAUSED""ARCHIVED""OTHER"Responses
200
GET /v1/adgroups/{id}
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Responses
200
Advertising performance per ad group, from the account's report history
Aggregated from the report history over a required start_date/end_date window. Like the rest of the metrics resources it paginates with limit/offset (an aggregated row has no id to use as a cursor) and has_more tells whether another page follows. Monetary amounts are decimal strings; ratios are fractions (0.1642 = 16.42%) and are null, never 0, when their denominator is zero.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-01""^\\d{4}-\\d{2}-\\d{2}$"Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-31""^\\d{4}-\\d{2}-\\d{2}$""total""daily""total""total"Page size. For a top-N, combine order_by with a small limit instead of raising it: limit/offset bound the response, not what ClickHouse scans.
100100110000009007199254740991"asc""desc""desc""desc"Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""SP""SB""SD""cost""sales""impressions""clicks""orders""units""acos""roas""ctr""cpc""conversion_rate"Responses
200
List the authenticated account's advertising targets
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Page size. The default is enough to explore; raise it only when you need to walk a whole collection.
20201100Cursor for the next page: the id of the last record you received. Returns the records after it.
Cursor for the previous page: the id of the first record you received. Returns the records before it.
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Case-insensitive substring match over the target's expression (keyword, ASIN or category, chosen by targetType) and its matchType; with targetType set, only that type's field is searched. Use it to find a record by name when you do not have its id, instead of paging through the whole list. Regex metacharacters are matched literally.
1200Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""ENABLED""PAUSED""ARCHIVED""OTHER""AUTO""KEYWORD""PRODUCT_CATEGORY""PRODUCT""PRODUCT_CATEGORY_AUDIENCE""PRODUCT_AUDIENCE""AUDIENCE""THEME""true""false"Responses
200
GET /v1/targets/{id}
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Responses
200
Advertising performance per target, from the account's report history
Aggregated from the report history over a required start_date/end_date window, with the target type and keyword resolved from the catalog. This is one of the two heaviest resources, so its window is capped shorter: 93 days for granularity=total and 31 for daily. Paginates with limit/offset and has_more tells whether another page follows. Monetary amounts are decimal strings; ratios are fractions (0.1642 = 16.42%) and are null, never 0, when their denominator is zero.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-01""^\\d{4}-\\d{2}-\\d{2}$"Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-31""^\\d{4}-\\d{2}-\\d{2}$""total""daily""total""total"Page size. For a top-N, combine order_by with a small limit instead of raising it: limit/offset bound the response, not what ClickHouse scans.
100100110000009007199254740991"asc""desc""desc""desc"Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""SP""SB""SD""cost""sales""impressions""clicks""orders""units""acos""roas""ctr""cpc""conversion_rate"Responses
200
List the authenticated account's advertising product ads
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Page size. The default is enough to explore; raise it only when you need to walk a whole collection.
20201100Cursor for the next page: the id of the last record you received. Returns the records after it.
Cursor for the previous page: the id of the first record you received. Returns the records before it.
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Case-insensitive substring match over the advertised ASIN and SKU. Use it to find a record by name when you do not have its id, instead of paging through the whole list. Regex metacharacters are matched literally.
1200Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""ENABLED""PAUSED""ARCHIVED""OTHER"Responses
200
GET /v1/product-ads/{id}
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Responses
200
Advertising performance per product ad, from the account's report history
Aggregated from the report history over a required start_date/end_date window. Only Sponsored Products and Sponsored Display have product ads; Sponsored Brands does not, so ad_product accepts SP and SD only. Paginates with limit/offset and has_more tells whether another page follows. Monetary amounts are decimal strings; ratios are fractions (0.1642 = 16.42%) and are null, never 0, when their denominator is zero.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-01""^\\d{4}-\\d{2}-\\d{2}$"Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-31""^\\d{4}-\\d{2}-\\d{2}$""total""daily""total""total"Page size. For a top-N, combine order_by with a small limit instead of raising it: limit/offset bound the response, not what ClickHouse scans.
100100110000009007199254740991"asc""desc""desc""desc"Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""SP""SD""cost""sales""impressions""clicks""orders""units""acos""roas""ctr""cpc""conversion_rate"Responses
200
List the authenticated account's advertising search terms
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Page size. The default is enough to explore; raise it only when you need to walk a whole collection.
20201100Cursor for the next page: the id of the last record you received. Returns the records after it.
Cursor for the previous page: the id of the first record you received. Returns the records before it.
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Case-insensitive substring match over the shopper search term text. Use it to find a record by name when you do not have its id, instead of paging through the whole list. Regex metacharacters are matched literally.
1200Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Responses
200
GET /v1/search-terms/{id}
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Path Parameters
24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"Query Parameters
Inline related records instead of returning just their ids. Repeat the param for several (expand[]=connection&expand[]=country) and nest with dot notation (connection.country), up to 4 levels.
Trim the response to the fields you need, comma-separated and keyed by ENTITY TYPE rather than by resource name: fields[campaign]=id,name. A key that matches no entity is ignored silently and the full object comes back.
Responses
200
Advertising performance per shopper search term, from the account's report history
Aggregated from the report history over a required start_date/end_date window, with the shopper query resolved from the catalog into query. Answers "which searches do I spend most on?" — use order_by=cost with limit instead of paging. This is the heaviest resource in the API, so its window is capped shorter: 93 days for granularity=total and 31 for daily. Rows are grouped per search term AND target, because the same text can be matched by different targets. Only Sponsored Products and Sponsored Brands produce search terms, so ad_product accepts SP and SB only. Monetary amounts are decimal strings; ratios are fractions (0.1642 = 16.42%) and are null, never 0, when their denominator is zero.
Authorizations
Client API key (POST /api-keys). Send as Authorization: Bearer epk_live_....
Parameters
Query Parameters
Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-01""^\\d{4}-\\d{2}-\\d{2}$"Both ends are included in the range. The window is capped, and the cap depends on the resource AND on granularity — daily allows a much shorter span than total, and target-metrics and search-term-metrics are stricter than the rest because limit/offset bound the response but not what ClickHouse scans. Going over returns a 400 naming the exact limit for your request.
"2026-07-31""^\\d{4}-\\d{2}-\\d{2}$""total""daily""total""total"Page size. For a top-N, combine order_by with a small limit instead of raising it: limit/offset bound the response, not what ClickHouse scans.
100100110000009007199254740991"asc""desc""desc""desc"Set to true to also receive total_count: how many records match every filter of this request, ignoring starting_after/ending_before/offset - the size of the whole result set, not of what is left. has_more is always returned regardless. It costs an extra count query, so ask for it once, on the first page, to decide whether the set is worth walking. On metrics resources with granularity=daily it counts entity-days, not entities. total_count comes back null when the count could not finish in time; the list is still returned, so treat it as unknown, never as zero.
"true""false"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$"24-character hexadecimal Mongo ObjectId.
"^[a-f0-9]{24}$""SP""SB""cost""sales""impressions""clicks""orders""units""acos""roas""ctr""cpc""conversion_rate"Responses
200