How do you get advertising-library data into a research workflow?
Ten advertisers, four ad libraries, every route we can reach, one day. Raw responses published.
100 calls · 100 valid · $1.58
run 2026-09-15
Decision guides
Choose an ad-library API for competitor research
Ten advertisers sent through every third-party ad-library route reachable on one day, across Meta, Google, TikTok and LinkedIn: what each returned, what it cost, how long it took, and which one fits a weekly monitoring agent.
Platform guides
Google Ads Transparency Center: what an API can get you
Google offers an API only for ads served in the EEA, so competitor research elsewhere runs through third-party routes. What two of them returned for ten advertisers on the same day, what the Center shows and does not show, and what it costs.
Meta Ad Library: official API versus third-party routes
What Meta's own Ad Library API returns for commercial advertisers, who can get access, and what the three third-party routes returned for the same ten advertisers on the same day, field by field, with prices and latency.
Field guides
What ad-library data can and cannot tell you
Field by field, what came back on 1,600 ads across ten routes and four platforms: creatives, dates, placements, status, landing pages, and the fields people assume exist and do not, such as spend, targeting and performance.
How this site works
Each platform page says what that ad library exposes, who is allowed to access it, and what every route we can reach returned for the same ten advertisers on the same day, with the raw responses published. No route is scored on ad counts alone: a library that hides spend for commercial ads hides it for every route.
The site is published by the team behind Treg. When a page evaluates Treg it says so at the top. Read the methodology for what these numbers can and cannot tell you, or the about page for who writes here.