DataForSEO — Keywords Data / Google Ads / Ad Traffic By Keywords / Live

Retrieve keywords Data Google Ads Ad Traffic By Keywords Live with the DataForSEO API. The sample response includes keywords. Use it in campaign or creative research.

Selected price
$0.09 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body* array
body[0]* object | null
the maximum custom bid required field the collected data will be based on this value it stands for the price you are willing to pay for an ad; the higher value you specify here, the higher values you will get in the returned metrics learn more in this help center article
keywords* array
keywords required field The maximum number of keywords you can specify: 1000 The maximum number of characters for each keyword: 80 The maximum number of words for each keyword phrase: 10 the keywords you specify will be converted to a lowercase format Note: Google Ads may return no data for certain groups of keywords visit our Help Center to learn more Also note that Google Ads doesn't allow using certain symbols and characters (e.g., UTF symbols, emojis), so you can't use them when setting a task; to learn more about which symbols and characters can be used, please refer to this article learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article
keywords match-type required field can take the following values: exact, broad, phrase
Optional parameters (10)
starting date of the forecasting time range required field if you specify date_to if you indicate date_from and date_to, you don't need to specify date_interval minimum value is tomorrow's date the value you specify in date_from shouldn't be further than date_to date format: "yyyy-mm-dd" example: "2021-10-30"if Status endpoint returns false in the actual_data field, date_from can be set to the month before last and prior; if Status endpoint returns true in the actual_data field, date_from can be set to the last month and prior
forecasting date interval optional field if you specify date_interval, you don't need to indicate date_from and date_to possible values: next_week, next_month, next_quarter default value: next_month
ending date of the forecasting time range required field if you specify date_from if you indicate date_from and date_to, you don't need to specify date_interval minimum value is date_from +1 day maximum value is current day and month of the next year date format: "yyyy-mm-dd" example: "2022-10-30"
search engine language code optional field you can receive the list of available languages of the search engine with their language_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_ads/languages example: en
full name of search engine language optional field you can receive the list of available languages of the search engine with their language_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_ads/languages example: English
search engine location code optional field if you do not indicate the location, you will receive worldwide results, i.e., for all available locations; if you use this field, you don't need to specify location_name or location_coordinate; you can receive the list of available locations of the search engines with their location_code by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_ads/locations example: 2840
GPS coordinates of a location optional field if you do not indicate the location, you will receive worldwide results, i.e., for all available locations; if you use this field, you don't need to specify location_name or location_code; location_coordinate parameter should be specified in the "latitude,longitude" format; the data will be provided for the country the specified coordinates belong to; example: 52.6178549,-155.352142
full name of search engine location optional field if you do not indicate the location, you will receive worldwide results, i.e., for all available locations; if you use this field, you don't need to specify location_code or location_coordinate you can receive the list of available locations of the search engine with their location_name by making a separate request to https://api.dataforseo.com/v3/keywords_data/google_ads/locations example: London,England,United Kingdom
results sorting parameters optional field Use these parameters to sort the results by relevance, impressions, ctr, average_cpc, cost, or clicks in the descending order default value: relevance
user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response
Forecast Google Ads campaign impressions, CPC and clicks for the supplied keywords and selected future period.

Sample response

{
  "cost": 0.075,
  "status_code": 20000,
  "status_message": "Ok.",
  "tasks": [
    {
      "cost": 0.075,
      "data": {
        "api": "keywords_data",
        "bid": 999,
        "function": "ad_traffic_by_keywords",
        "keywords": [
          "buy laptop",
          "cheap laptops for sale",
          "purchase laptop"
        ],
        "language_code": "en",
        "location_code": 2840,
        "match": "exact",
        "se": "google_ads"
      },
      "id": "11251525-0696-0094-0000-7f236bb489d3",
      "path": [
        "v3",
        "keywords_data",
        "google_ads",
        "ad_traffic_by_keywords",
        "live"
      ],
      "result": [
        {
          "average_cpc": 452.45,
          "bid": 999,
          "clicks": 8803.42,
          "cost_micros": 3983135.48,
          "ctr": 0.0842,
          "date_interval": "next_month",
          "impressions": 104575.28,
          "keyword": "buy laptop",
          "language_code": "en",
          "location_code": 2840,
          "match": "exact",
          "search_partners": false
        },
        {
          "average_cpc": 384.19,
          "bid": 999,
          "clicks": 782.13,
          "cost_micros": 300486.83,
          "ctr": 0.116,
          "date_interval": "next_month",
          "impressions": 6744.02,
          "keyword": "cheap laptops for sale",
          "language_code": "en",
          "location_code": 2840,
          "match": "exact",
          "search_partners": false
        },
        {
          "average_cpc": 402.33,
          "bid": 999,
          "clicks": 311.69,
          "cost_micros": 125403.39,
          "ctr": 0.0722,
          "date_interval": "next_month",
          "impressions": 4318.71,
          "keyword": "purchase laptop",
          "language_code": "en",
          "location_code": 2840,
          "match": "exact",
          "search_partners": false
        }
      ],
      "result_count": 3,
      "status_code": 20000,
      "status_message": "Ok.",
      "time": "6.4505 sec."
    }
  ],
  "tasks_count": 1,
  "tasks_error": 0,
  "time": "6.5059 sec.",
  "version": "0.1.20210917"
}

Response result

Response structure

Inferred from examples
  • costnumber
  • status_codeinteger
  • status_messagestring
  • tasksobject[]
    • costnumber
    • dataobject
      • apistring
      • bidinteger
      • functionstring
      • keywordsstring[]
      • language_codestring
      • location_codeinteger
      • matchstring
      • sestring
    • idstring
    • pathstring[]
    • resultobject[]
      • average_cpcnumber
      • bidinteger
      • clicksnumber
      • cost_microsnumber
      • ctrnumber
      • date_intervalstring
      • impressionsnumber
      • keywordstring
      • language_codestring
      • location_codeinteger
      • matchstring
      • search_partnersboolean
    • result_countinteger
    • status_codeinteger
    • status_messagestring
    • timestring
  • tasks_countinteger
  • tasks_errorinteger
  • timestring
  • versionstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use DataForSEO — Keywords Data / Google Ads / Ad Traffic By Keywords / Live with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.