Ads Max
The google_ads
source is optimized to retrieve Google Search (SERPs) and Google AI Overviews results with paid ads at a maximum ad rate. The 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.
source
Sets the scraper.
google_ads
query
The keyword or phrase to search for.
-
- mandatory parameter
Localization
Adapt search results to specific geographical locations, domains, and languages.
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.
-
locale
Accept-Language
header value which changes your Google search page web interface language. More info.
-
Pagination
Controls for managing the pagination and retrieval of search results.
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.
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.
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
Last updated
Was this helpful?