What we ran
- Sources: Meta Ad Library (1,144 ads) and Google Ads Transparency Center (222 ads). Public pages, no login. How to read them yourself: Meta Ad Library, Google Ads Transparency Center.
- Countries: Lithuania, Latvia, Estonia, Poland, Czechia, Romania, Bulgaria, Germany, Hungary.
- Where: our test box, read-only. One row per ad, one row per ad and country (4,666 rows).
- Label: each ad got a category from our own classifier. Not Meta’s, not Google’s.
What we found
| ads | 1,366 |
| advertisers | 572 |
| ads with a landing URL | 1,088 |
| landing domains | 378 |
| ad and country rows | 4,666 |
| still running when collected | 895 |
| ad text captured | 1,102 |
| variants per ad | 1.45 average, 55 at most |
| category (our label) | ads |
|---|---|
| shopping apps | 471 |
| sweepstakes | 237 |
| search feeds | 189 |
| short drama apps | 183 |
| dating | 156 |
| VPN | 130 |
Formats: video 400, dynamic product ads 358, image 196, dynamic creative 150, carousel 25, Google-library formats 222.
One shopping app’s domain is the landing page of 307 ads from 33 advertiser pages. A table like this shows who advertises where, which pages repeat, and where the same landing domain sits behind many advertisers.
The landing pages of 150 of these ads are the sample in cloaking examples.
How you’d use it
- Brand: the same pull on your name and your domain shows who advertises as you: brand bidding monitoring.
- Competitor team: per-competitor ad feed with new, paused and changed ads, weekly. See how to see competitor ads.
- Ad network or regulator: every ad on a landing domain, across countries, with first and last seen. The ad networks page shows what we check.