Change in LLM mentions between two dates for a target

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

• targetarray, optional

  array of objects containing target entities. Required field. You can specify up to 10 entities (objects) in the target field. One target entity can contain either one domain or one keyword and related parameters. All target entities are AND-combined into one filter / one metrics series (not one series per brand). To compare brands: use dataforseo.x.ai-optimization-llm-mentions-multi-target-metrics-live, or one call per brand.

• date_tostring, optional

  em end date of the time range /em br strong required field /strong br strong Note: /strong the value specified in code date_from /code cannot exceed the value in code date_to /code br date format: code "yyyy-mm-dd" /code

• 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).

• date_fromstring, optional

  em start date of the time range /em br strong required field /strong br minimal value: code 2025-08-01 /code br date format: code "yyyy-mm-dd" /code

• group_rangestring, optional

  em timeseries delta range /em br strong required field /strong br possible values: br code day /code , code week /code , code month /code , code year /code

• 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.