Google Shopping

DataPipeline is ScraperAPI's no-code dashboard for scheduled scraping. In this tutorial, you will use DataPipeline to monitor Google Shopping prices for any query list. By the end, you will have shopping results with price, retailer, and delivery options for every query you track, refreshed on your schedule, so you can spot pricing shifts and new entrants before they affect your positioning.

Step 1: Create the project

Click DataPipeline in the left sidebar.

Select New project.
Select the Google shopping tile.

Step 2: Configure input settings

Under Input settings, choose List and enter your search queries, one per line:

running shoes
running shoes men
running shoes women
trail running shoes

For larger query lists, switch to Upload file and upload a CSV with one query per row.

Step 3: Configure output settings

Under Output settings, choose Download. Results will be available in the dashboard when the job completes. For automated pipelines, enter a Webhook URL instead so results are posted to your server as they arrive.

JSON gives you the full structured response including delivery options and badges. CSV flattens each result to a row — position, title, price, source, and extracted_price become columns.

Step 4: Set scraping frequency

Under Scraping frequency, select Just scrape once. To monitor prices on a recurring basis, switch this to Daily, Weekly, or another interval. Recurring schedules require a paid plan.

Step 5: Review and start

Click Review & start scraping. The Job summary panel shows the estimated credit cost before you confirm.

Step 6: Review results

Click into the project after the run completes and click Download results. Results are retained for 30 days.

Each query produces a set of rows with position, title, price, extracted_price, and source. Compare extracted_price across runs to spot price movements by retailer.

Additional options

Under Additional options & filters you can fine-tune your requests:

Country code: targets a specific country's Google Shopping results.
Domain: sets the Google domain to search (e.g. co.uk, com.au).
UULE: encodes a specific city for local search results.
Number of results: sets how many shopping results to return per page.

Some parameters increase the cost per request. Check the Cost per Job panel before committing to a configuration at scale.

Prefer to set this up in your own codebase? Try the API playground instead.