Pull Public Ad Creatives With One Scraping API
Advertising research usually starts with a simple question: what is actually on the page right now, in the market I care about?
A general-purpose scraping API answers that by fetching a public URL, rendering its JavaScript, and returning either the rendered HTML or structured JSON you define. This page explains how that workflow applies to display ads, sponsored search results and on-page creatives, what the request options do, and how credits are consumed.
What this API does — and what it does not
The API fetches a public page you name, handles bot-detection challenges and JavaScript rendering, and returns content you can parse. For ad research that means you can collect display creatives, sponsored search results and on-page ad placements from pages and SERPs you are already monitoring, including copy, image, video and landing-page URL where those are present in the markup.
It is not an ad-network reporting tool. It does not log into ad platforms, read private campaign dashboards, or return impression and spend figures that only the advertiser can see. What you get is what a public visitor would see, rendered and returned. Any performance metric you extract is therefore a public signal on the page, not a first-party measurement.
Three common ad-research workflows
Most teams arrive with one of three goals. Each maps to the same endpoint with different parsing rules.
- Competitor display creatives. Point the API at competitor landing pages and publisher sites, then extract image sources, headline copy and destination URLs. This builds a creative library you can review over time.
- Sponsored search results. Fetch a search engine results page and extract the sponsored block separately from organic results. This shows which advertisers bid on a term and what copy they use.
- On-page ad placements. Fetch publisher pages and record which ad slots are filled, what creative appears, and which landing page it points to. Useful for placement audits and brand-safety reviews.
In all three cases the API returns the rendered page; the extraction rules decide which parts become fields.
Request options that matter for ad pages
Ad slots are frequently injected by JavaScript after the initial HTML loads, so rendering is usually the first option to enable. The table below maps the options most relevant to ad collection to what they do and what they cost.
- render_js: executes page JavaScript so dynamically inserted creatives appear in the response. Each successful request with JS rendering costs 5 API credits.
- stealth_proxy: routes through a stealth proxy for tougher bot protection. Costs 75 credits per request.
- premium_proxy: costs 10 credits without JS rendering, or 25 credits with it.
- country_code: routes the request through a residential IP in the chosen country, which matters when ad content varies by geography.
- extract_rules: CSS or XPath selectors mapped to field names, returned as parsed JSON.
- ai_extract_rules: a natural-language description of the fields you want, also returned as parsed JSON.
- screenshot: captures a full-page image, useful for visual review of creative layout.
A practical default for ad pages is render_js on, extract_rules for the fields you already know, and country_code set to the market you are studying.
Worked example: a geo-targeted sponsored-results pull
Suppose you want to see which advertisers appear on a search results page for a term in a specific country. The sequence is:
- Send a GET request with the search URL, your API key, render_js enabled and country_code set to the target market.
- Add extract_rules that map the sponsored block's container to a field such as sponsored_results, with child selectors for headline, display URL and landing URL.
- Read the parsed JSON response and store each sponsored entry with the date and country you requested.
If the sponsored block is rendered inconsistently, switch that field to ai_extract_rules and describe it in plain language, for example: return each sponsored result with its headline, visible URL and destination link. The response shape stays JSON either way, so downstream storage does not change.
Because country routing changes which ads a visitor sees, record the country_code alongside every row. A creative captured without its market context is hard to compare later.
Telling failures apart
Three different problems look similar in a failed run, and each has a different fix.
- Blocked by the target. The response is a challenge page or empty body. Enable stealth_proxy or premium_proxy, and confirm render_js is on.
- Throttled by concurrency. Requests queue or fail while others succeed. The API enforces concurrency limits per plan rather than per-target rate limits; reduce parallel workers or spread requests over time.
- Selector miss. The page loads but your fields are empty. The markup changed or the ad slot was not filled on that load. Inspect the rendered HTML before rewriting rules, and consider ai_extract_rules for unstable layouts.
Checking which of these occurred before changing configuration saves credits and debugging time.
Plans and credit consumption
The plan-comparison table below is a dated reference to the published plan data and should be re-checked before purchasing. Prices, credit allowances and concurrency limits are shown as published at the time of writing and should be confirmed as current commercial terms before any purchase decision. Credit validity and rollover follow the provider's stated policy; requests start at 1 credit each. JavaScript rendering adds 5 credits per successful request; premium proxies add 10 credits without JS rendering or 25 with it; stealth_proxy costs 75 credits. The 1,000-credit trial offer and its conditions are governed by the provider's current trial terms and should be verified before relying on them. The credit-costs table below shows the per-request cost of each option. When estimating monthly volume, multiply your expected request count by the credit cost of the options you will actually use, not by the base rate alone.
Compliance and practical limits
Collect only public ad placements and respect the terms of the sites you fetch. Data-handling practice — including whether personal data from scraped sites is collected or stored unless the user explicitly requests it — should be confirmed against the provider's current policy before relying on it. Proxy rotation and headless browser rendering reduce IP-based blocking, and scalability and speed figures should be treated as published claims rather than guarantees, but no scraping setup guarantees access to every page. Plan for retries and for pages where an ad slot simply was not served.
Credit cost per request by option
The table below shows how many credits each successful request consumes depending on the options enabled. Base requests start at 1 credit; JavaScript rendering adds 5; premium proxies add 10 without JS rendering or 25 with it; stealth_proxy costs 75.
Plan comparison (dated reference)
The table below lists the published plan tiers with their prices, credit allowances, concurrency limits and inclusion flags. Treat it as a dated reference and confirm current terms before purchasing.
| Plan | Price | API credits | Concurrent requests | JS rendering | Rotating & premium proxies | Geotargeting | Screenshots & extraction rules | Priority email support | Dedicated account manager | Team management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Tax treatment follows the provider's stated VAT policy and should be confirmed before purchase. Credit validity and rollover follow the provider's stated policy. This table is a dated reference to the published plan data; prices, credit allowances and concurrency limits should be confirmed as current before purchasing.
| Option | Credits per successful request |
|---|---|
| Base request | 1 |
| JavaScript rendering | 5 |
| Premium proxy (no JS rendering) | 10 |
| Premium proxy with JS rendering | 25 |
| stealth_proxy | 75 |
Credit costs are per successful request and depend on the options enabled. Credit validity follows the provider's stated policy; confirm current rates before estimating volume.
Frequently asked questions
Do I need an account to scrape ad data?
No external ad-platform account is required. You sign up for an API key, then send the URL of the public page you want to fetch. The API handles rendering and bot detection. The 1,000 free credits and any no-card condition are governed by the provider's current trial terms and should be verified before relying on them.
Can I scrape ad data from a specific country?
Yes. Set country_code on the request to route through a residential IP in that country. This matters when ad content or sponsored results vary by geography.
What's the rate limit for scraping ad data?
Limits are expressed as concurrency per plan rather than per-target rate limits. If a target throttles aggressive patterns, space out requests or use multiple sessions.
How do I get structured JSON from ad data?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description of the fields. Either way the response is parsed JSON.
Which programming languages can I use to scrape ad data?
Any language that can make an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works as well.
How much does it cost to scrape ad data?
The 1,000-credit trial and any no-card condition are governed by the provider's current trial terms and should be verified before relying on them. The starting monthly price is governed by the provider's current plan pricing and should be confirmed before purchase. Per-request credit cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.
Should I use extract_rules or ai_extract_rules for ad creatives?
Use extract_rules when the ad markup is stable and you know the selectors; it is deterministic and cheap to maintain. Switch to ai_extract_rules when creatives are injected with changing class names or when you want to describe fields in plain language. Both return parsed JSON, so you can mix them across fields in one pipeline.
Why did my ad fields come back empty even though the page loaded?
An empty field usually means the ad slot was not filled on that load, or the selector no longer matches the rendered markup. Check the rendered HTML first. If the slot is genuinely empty, record the absence rather than treating it as an error; if the markup changed, update the selector or move that field to ai_extract_rules.