Start here: Residential · Rotating

Market Research Solution

Collect public pricing, reviews, and listings as a local shopper would see them. This is analyst-scale collection — not a 24/7 crawl farm and not seller-account logins.

Recommended: rotating residential. Reach for Web Scraping API only on JS-heavy sources that return empty shells over HTTP.

Purchase residential traffic Hard pages via API →
Who it's for

Analysts building multi-region market datasets

Strategy consultants

Competitor pages across continents in one engagement.

Pricing analysts

Local-currency shelves, not HQ-IP prices.

VC / PE associates

Category snapshots without a scraping platform team.

Research vendors

Regional HTML into a warehouse on a deadline.

Pain Points

Research vs scraping vs SEO

Data Scraping is for engineers with a crawler. SEO Monitoring is SERPs only. This page is public market pages for humans who need geo-correct HTML.

🌍

Geo-gated catalogs

The product grid from HQ is not the product grid in-market.

🚫

Corp IP throttle

Publishers notice a research firm’s NAT.

📄

Empty SPA shells

Review widgets hydrate in JS — raw curl is useless.

🔐

Login creep

Do not collect behind customer logins on rotating IPs.

📊

One-off vs pipeline

A 200-URL audit should not wait on a full crawler build.

💸

Buying mobile + DC + API

Pick residential first; add API only for the URLs that fail.

What to buy

Default buy for research briefs

Recommended: rotating residential. Alternative: Web Scraping API for the handful of JS-heavy sources in the brief.

Product Billing Use it when…
Residential · Rotating Recommended Pay per GB Recommended — public listings, reviews, pricing pages, geo-correct.
Web Scraping API Credits · pay per success Alternative — JS widgets, anti-bot pages, no local browser.
Recommended path

How to start (one recommended path)

Path A — Analyst laptop + residential

Browser or light script, geo endpoints.

  1. Buy rotating residential.
  2. Generate one endpoint per market in the brief.
  3. Browse or script public pages only.
  4. Export HTML/CSV; do not log into seller tools on this IP.
Residential proxies →

Path B — Hard pages via API

When Path A returns empty DOM.

  1. Test the failing URL in API Center with render.
  2. If it works, fetch that source class via API only.
  3. Keep easy sources on residential GB.
  4. Do not re-buy the same page on both products.
Web Scraping API →
Decision guide

Pick one — do not mix these on the same job

Use rotating residential when

  • Pages are public and mostly server-rendered.
  • You need many countries, modest volume.
  • Analysts can run a browser or a small script.

Use Web Scraping API when

  • The page is empty without JavaScript.
  • Anti-bot blocks residential curl.
  • The brief is a few hundred hard URLs, not millions.
Getting started

First-week checklist

FAQ

Common questions

Same as Data Scraping?

Same recommended SKU, different job. This page is analyst briefs; that page is production crawlers.

Static IP?

No — research should look like many shoppers, not one identity.

Mobile?

Only for in-app stores — see Mobile App Data.

Legal?

Public pages you are allowed to collect. Follow site terms.

Datacenter?

Skip unless the source is a permissive open dataset.

Resources

Go deeper

Residential proxies Data scraping (crawlers) SEO monitoring Pricing

Pull one in-market product page

Rotating residential is the research default. Add API only after a URL fails.

Purchase residential traffic Hard pages via API →