Ads

The google_ads source is optimized to retrieve Google Search results page (SERP) with paid ads. This source will return only ten results per page, ensuring the highest chances of paid results showing up. Other than that, it supports the same parameters as regular Web Search.

Request samples

In this example, we make a request to google.nl to retrieve search results for the keyword adidas.

curl 'https://realtime.oxylabs.io/v1/queries' \
--user 'USERNAME:PASSWORD' \
-H 'Content-Type: application/json' \
-d '{
        "source": "google_ads", 
        "domain": "nl", 
        "query": "adidas",
        "parse": true
    }'

We use synchronous Realtime integration method in our examples. If you would like to use Proxy Endpoint or asynchronous Push-Pull integration, refer to the integration methods section.

Request parameter values

Generic

Basic setup and customization options for scraping Google ads.

ParameterDescriptionDefault Value

source

Sets the scraper.

google_ads

query

UTF-encoded keyword.

-

render

Enables JavaScript rendering when set to html. More info.

-

parse

Returns parsed data when set to true. Explore output data dictionary.

false

callback_url

URL to your callback endpoint. More info.

-

user_agent_type

Device type and browser. The full list can be found here.

desktop

- mandatory parameter

Localization

Adapt search results to specific geographical locations, domains, and languages.

ParameterDescriptionDefault Value

geo_location

The geographical location that the result should be adapted for. Using this parameter correctly is extremely important to get the right data. For more information, read about our suggested geo_location parameter structures here.

-

domain

Domain localization for Google. The full list of available domains can be found here.

com

locale

Accept-Language header value which changes your Google search page web interface language. More info.

-

context: results_language

Results language. List of supported Google languages can be found here.

-

Pagination

Controls for managing the pagination and retrieval of search results.

ParameterDescriptionDefault Value

start_page

Starting page number.

1

pages

Number of pages to retrieve.

1

Filtering

Options to filter and refine search results based on various criteria.

ParameterDescriptionDefault Value

context:

udm

udm parameter allows switching between different search tabs, such as images, places, or videos, to customize the type of results displayed. Find the accepted values here.

-

context: tbm

To-be-matched or tbm parameter. Accepted values are: app, blg, bks, dsc, isch, nws, pts, plcs, rcp, lcl

-

context: tbs

tbs parameter. This parameter is like a container for more obscure google parameters, like limiting/sorting results by date as well as other filters some of which depend on the tbm parameter (e.g. tbs=app_os:1 is only available with tbm value app). More info here.

-

Other

Additional advanced settings and controls for specialized requirements.

ParameterDescriptionDefault Value

context: nfpr

true will turn off spelling auto-correction

false

Context parameters

All context parameters should be added to the context array as objects with key and value pairs, e.g.:

...
"context": [
    {
        "key": "filter",
        "value": "0"
    }
]
...

Structured data

Explore output data dictionary for each Web SERP feature (including paid results), offering a brief description, screenshot, parsed JSON code snippet, and a table defining each parsed field.

Last updated