Zalando Ads Repository Scraper: Sponsored Ads avatar

Zalando Ads Repository Scraper: Sponsored Ads

Pricing

from $0.90 / 1,000 results

Go to Apify Store
Zalando Ads Repository Scraper: Sponsored Ads

Zalando Ads Repository Scraper: Sponsored Ads

Extract sponsored-content ads from Zalando's Ads Repository (DSA Art. 39): advertiser, reach, markets, targeting and dates. Residential proxy included.

Pricing

from $0.90 / 1,000 results

Rating

0.0

(0)

Developer

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Features

Limited permissions

Share

Zalando Ads Repository Scraper

Zalando Ads Repository Scraper extracts sponsored-content ads from Zalando's public Ads Repository, the ad library Zalando must publish under Article 39 of the EU Digital Services Act (DSA). Search by keyword in any Zalando market and get advertiser, delivery dates, reach, markets, targeting and creatives as structured data. You don't need an API key or a Zalando account.

🔍 What is Zalando Ads Repository Scraper?

Zalando is Europe's largest online fashion platform, and brands pay to promote their products on it. Zalando's Ads Repository lists those sponsored placements, but it is a single-page app with no export.

Zalando Ads Repository Scraper opens Zalando's sponsored-content archive in a real browser, reads the archive's own GraphQL responses page by page and returns one clean record per ad. Typical uses:

  • 👟 Brand and competitor monitoring: which fashion brands advertise on Zalando, where and when.
  • 📊 Retail-media intelligence: track sponsored-content activity per market and month.
  • 🧾 DSA research and compliance: audit advertiser disclosures and targeting parameters.

📦 What data does Zalando Ads Repository Scraper extract?

FieldDescription
🆔 adIdAd identifier on Zalando
🏷️ advertiserAdvertiser / brand
💳 adPayerPayer, when Zalando discloses it (otherwise null)
📅 firstShownDate / lastShownDateDelivery period
📣 reachReach reported by Zalando (impressions is null, because Zalando reports reach)
🌍 searchCountry, markets, marketNamesMarket searched and markets where the ad ran
📝 title, text, languageCreative copy, in the interface language when available (else English)
🎯 targetingParametersTargeting parameters declared by Zalando (e.g. contextual, personal)
🖼️ imageUrlCreative image
✅ isActiveWhether the ad is currently active
🛡️ is_natural_person_suspectedtrue if the advertiser name looks like a private individual
🕒 scrapedAt, source, sourceUrlExtraction metadata

The common fields (adId, advertiser, adPayer, firstShownDate, lastShownDate, impressions, searchCountry, scrapedAt, source) match our other DSA ad library scrapers.

🚀 How to use Zalando Ads Repository Scraper

  1. Open Zalando Ads Repository Scraper in Apify Console and click Try for free.
  2. Choose a market (e.g. DE, FR, ES).
  3. Optionally enter a search query (brand or product) and a month (YYYY-MM).
  4. Click Start, then download the results as JSON, CSV or Excel.

⚙️ Input parameters

ParameterTypeDefaultDescription
searchQuerystringall adsFull-text search
marketstringDEZalando market (EU countries, plus CH, NO and UK)
monthstringallOnly ads whose delivery period overlaps this month (YYYY-MM)
languagestringenInterface language
maxResultsinteger200Maximum number of ads
proxyConfigurationobjectbuilt-inOptional. A residential proxy is included; add your own URLs to override it

Example input

{
"searchQuery": "sneakers",
"market": "DE",
"maxResults": 50
}

📄 Output example

{
"adId": "98515f464bc2e37236f559e2660cb2b8",
"advertiser": "NIKE Retail B.V.",
"adPayer": null,
"firstShownDate": "2025-04-17",
"lastShownDate": "2025-05-16",
"impressions": null,
"searchCountry": "DE",
"sourceUrl": "https://sponsored-content-archive.zalando.com/?lang=en-DE&fullText=Nike&markets%5B0%5D=DE",
"scrapedAt": "2026-11-12T21:52:00Z",
"source": "zalando_ads_repository",
"is_natural_person_suspected": false,
"id": "98515f464bc2e37236f559e2660cb2b8",
"title": "Nike Vomero 18 | Max cushioning for the ultimate ride",
"text": "Shop now",
"language": "en-GB",
"startDate": "2025-04-17",
"endDate": "2025-05-16",
"isActive": false,
"reach": 1614,
"markets": ["DE"],
"marketNames": [],
"targetingParameters": ["contextual", "personal"],
"imageUrl": "https://img01.ztat.net/crt/creative-content/....jpg",
"searchQuery": "Nike"
}

🛡️ Proxy and limitations

  • A residential proxy is included. Zalando's bot protection (Akamai) blocks datacenter IPs, so Zalando Ads Repository Scraper routes its traffic through a built-in EU residential proxy. You don't have to configure anything.
  • If you prefer your own proxy, add its URLs in proxyUrls and they will be used instead.
  • The archive returns 50 ads per page. Zalando Ads Repository Scraper follows the pagination until it reaches maxResults (up to 200 pages per run).
  • The month filter is applied by the scraper, not by Zalando: it keeps ads whose delivery period overlaps that month. Searching a narrow month over a broad query may need to read many pages.

💰 How much does it cost to scrape the Zalando Ads Repository?

Zalando Ads Repository Scraper uses pay-per-event pricing, so you only pay for the ads you get:

EventPrice
Actor start (per GB of memory; the default 2 GB = 2 events)$0.0005
Each ad record in the dataset$0.0009

That works out to roughly $0.90 per 1,000 ads, with platform compute and residential proxy traffic included. Use Max ads to cap what a run can cost.

❓ FAQ

Is it legal to scrape the Zalando Ads Repository? The repository is published to meet DSA Article 39 transparency obligations and is publicly accessible. Zalando Ads Repository Scraper only collects public ad records. You remain responsible for complying with Zalando's terms of use and applicable law.

Does the output contain personal data? Advertisers are typically brands. If a name looks like a private individual, the record is flagged with is_natural_person_suspected: true. Treat flagged records as personal data under GDPR: minimise them and do not republish them.

Do I need my own proxy? No. A residential proxy is included. Add your own in proxyUrls only if you prefer.