Booking.com's Ads Repository publishes the ads served in the EEA: the advertised property, the hotel chain, OTA or channel manager that paid, the dates and impressions in total and per country. The official page shows 20 ads at a time and its backend refuses long ranges; the actor searches by payer or by property, or sweeps the whole repository, and splits long periods automatically.
Since 2023 the EU Digital Services Act (DSA, art. 39) requires very large platforms to publish a repository of the ads they serve in the EU: who advertises, who paid, when, how many people it reached and how it was targeted.
| Group | Fields | What it adds |
|---|---|---|
| Ad | advertiser (adName) | The advertised property. |
| Paid by | payer (legalEntity) | Hotel chain, OTA or channel manager. |
| Impressions | reach_min · reach_max · reach_by_country | Booking.com ranges as numbers, total and per country. |
| Period and targeting | first_shown · last_shown · targeting_types | First and last date shown and targeting type. |
It shares the base block of fields with Rastriq's Microsoft, Amazon, Apple and Booking.com actors (platform, ad_id, advertiser, payer, first_shown, last_shown, reach_min, reach_max, targeting_types, countries, quality_flags), so their datasets stack into one table. A field is empty when the platform does not publish it. See the actor on Apify
Selected columns from one row of the README output example (run of 11 November 2026). Company advertisers only.
| Field | Value |
|---|---|
| advertiser | Ramada Plaza by Wyndham Orlando Resort & Suites Intl Drive - Newly Renovated! |
| payer | Wyndham |
| first_shown | 2025-02-10 |
| last_shown | 2026-11-10 |
| reach_min · reach_max | 1000 · 10000 |
| reach_min_DE · reach_max_DE | 1000 · 10000 |
| totalViewsBucket | 1K-10K |
| targeting_types | DEFAULT |
| quality_flags | reach_is_impressions, impressions_updated_quarterly, no_creative_in_source, advertiser_is_property_name |
Nothing is filtered by default. quality_flags marks what deserves a second look, and the decision is yours.
Public sample: 100 real ads and 81 columns, in JSON and CSV, no sign-up.
Better to say it before you build an analysis on top of it.
no_creative_in_source).Hilton finds "Hilton Garden Inn Paris…".payer.Result: which chains and channel managers buy visibility.payer, advertiserpayer, reach_by_countryreach_min, first_shownExamples from the README or from real runs. Paste the input into the actor's JSON tab and press Start.
| Task | Input (JSON) | What it is for |
|---|---|---|
| Two chains, one half-year | {"legalEntities": ["Wyndham", "IHG"], "startDate": "2026-01-01", "endDate": "2026-06-30", "maxItems": 5000} | Everything they paid for in the EEA. |
| One property by name | {"adNames": ["Hilton"], "maxItems": 1000} | Every ad whose property name starts with the text. |
A scheduled weekly run is enough to follow competitors.
Run it yourself, receive it on a schedule or commission the project.
Ads found again in another window or search are free. Start fee, $0.002 per run.
Every ad that received impressions on Booking.com in the EEA, which is what it publishes under the DSA. Ads stay for one year after they were last shown.
Booking.com's backend gives up on heavy searches (the whole repository over ~2 months, or one payer over a year). The actor detects it, splits the period and merges without duplicates.
The payer can be a private individual. Those rows are flagged with is_natural_person_suspected and the name can be pseudonymised.
$0.40 per 1,000 ads on Apify's free plan, plus $0.002 per run. With $5 of credit: about 12,000 ads.