LLM mention metrics for many keywords or domains, grouped

Inputs

• tagstring, optional

  em user-defined task identifier /em br optional field br em the character limit is 255 /em br you can use this parameter to identify the task and match it with the result br you will find the specified code tag /code value in the code data /code object of the response

• limitinteger, optional

  em the maximum number of returned objects /em br optional field p default value: code 100 /code br maximum value: code 1000 /code

• offsetinteger, optional

  em offset in the results array of the returned mentions data /em br optional field p default value: code 0 /code br example: if you specify the code 10 /code value, the first ten mentions objects in the results array will be omitted and the data will be provided for the successive objects; br

• filtersarray, optional

  em array of results filtering parameters /em br optional field br strong you can add several filters at once (8 filters maximum) /strong br you should set a logical operator code and /code , code or /code between the conditions br the following operators are supported: br code = /code , cod

• targetsarray, optional

  array of objects containing target entities with aggregation keys. Required field. Between 2 and 10 keyed target sets (else upstream 40501: "The number of 'targets' items must be between 2 and 10."). Each nested target array can contain up to 10 domain/keyword entities. Requests must include at least one domain_entity or keyword_entity with search_filter: include. Metrics are grouped by targets[].key. This live endpoint returns a rolling trailing window (~4-5 months), not calendar-month buckets;

• order_byarray, optional

  em results sorting rules /em br optional field br you can use the same values as in the code filters /code array to sort the results br possible sorting types: br code asc /code - results will be sorted in the ascending order br code desc /code - results will be sorted in the descending orde

• platformstring, optional

  target platform. Optional field. Possible values: chat_gpt, google. When omitted, DataForSEO defaults to google only (not both platforms). chat_gpt data is available for the United States and English only (location 2840 / US + language en; else task status 40501).

• language_codestring, optional

  em search language code /em br optional field br if you use this field, you don't need to specify code language_name /code ; br you can receive the list of available languages of the search engine with their code language_code /code by making a separate request to the code https://api.datafors

• language_namestring, optional

  em full name of search language /em br optional field br if you use this field, you don't need to specify code language_code /code ; br if you don't specify this field, the code language_code /code with code class="long-string" en /code value will be used by default; br you can receive the li

• location_codeinteger, optional

  search location code. Optional field. If you use this field, you don't need to specify location_name. Default is 2840 (United States). With platform=chat_gpt, only 2840 is valid; any other code (e.g. 2036) returns task status 40501 Invalid Field: 'location_code'. The HTTP envelope may still be 200 / top-level status_code 20000 Ok with items_count=0 — always check tasks[].status_code / status_message.

• location_namestring, optional

  full name of search location. Optional field. If you use this field, you don't need to specify location_code. Default is United States (location_code 2840). With platform=chat_gpt, only United States is valid; other names return the same task status 40501 Invalid Field on location. The HTTP envelope may still be 200 / top-level status_code 20000 Ok with items_count=0 — always check tasks[].status_code / status_message.

• internal_list_limitinteger, optional

  em maximum number of elements within internal arrays /em br optional field br you can use this field to limit the number of elements within the following arrays: br code sources_domain /code br code search_results_domain /code br minimum value: code 1 /code br maximum value: code 10 /code

• initial_dataset_filtersarray, optional

  em array of filter expressions applied before aggregation /em br optional field br you can use this array to filter expressions applied to the raw mentions database before aggregation to limit the rows contributing to the result; p strong you can add several filters at once (8 filters maximum) /s