What Is a Native Ad Library, and How Is It Different From Meta's and Google's?
Meta and Google publish public ad libraries; as far as we found, Taboola, Outbrain and MGID do not. What a native ad library has to capture, how it differs from Meta's and Google's, and what it can show.

If you advertise on Facebook, you can open the Meta Ad Library, type a competitor's name, and see the ads they are running; Meta describes the library as showing all active ads across its products. Try the same move on a Taboola advertiser and you hit a wall. As of October 7, 2026, we found no ad library published by Taboola, by Outbrain (now operating under the Teads name), by MGID or by Revcontent. For a category of advertising this widely used, we found no public record at the source.
That gap is the reason this page exists. Commercial native ad spy tools already sell searchable archives of native ads (AdPlexity Native, for example, has an Internet Archive capture dated April 2018), mostly as paid intelligence products. What we found the networks do not provide is an official public record, and that is the gap a native ad library tries to fill.
What is a native ad library?#
A native ad library is a searchable, dated archive of captured native ads: the "recommended for you" and "around the web" units served by networks like Taboola, Outbrain, MGID, Revcontent, Teads, MediaGo, Yahoo and MSN. It stores each ad's creative image, the advertiser behind it, the supply-chain path that served it, and the landing page it points to. The point is to let you search, filter and track competitors the way you already can on Meta and Google.
The definition is simple. Delivering it is not. Here is what one of those ads actually looks like once it is captured and dated:

The ad above shows why native ads need context: a deadline, a broad promise of "millions forgiven," and an advertiser name ("Fresh Start Information") that does not by itself show who is buying the media. We have not verified its claim, and a capture alone cannot tell you whether the offer behind it matches the headline.
Why Meta and Google have libraries and, as far as we found, the native networks don't#
Meta and Google run official ad libraries, and in the EU the Digital Services Act now makes a public ad repository a legal duty for the largest services. Platforms and search engines designated as very large (those reaching about 45 million users, 10% of the EU population) must keep a public repository of the ads on their services that can be searched on multiple criteria and through an API, covering the ad, who presented and paid for it, when it ran and how it was targeted (Article 39). Facebook, Instagram, YouTube, Google Search and other Meta and Google services are on the European Commission's designation list, so that duty applies to them.
The native networks are not on that list. The Commission's list, last updated August 31, 2026, does not designate Taboola, Outbrain (now Teads), MGID or Revcontent, so the DSA's repository duty does not apply to them. We know of no general law that requires them to publish a public archive of their ads; narrower rules, such as those for political advertising, may apply to particular ads and are outside this article. Microsoft is a partial exception: Bing is a designated search engine, and Microsoft publishes an Ad Library that it describes as designed to meet EU compliance requirements and as covering ads shown on Bing.com in the European Economic Area.
Technically, the networks hold the ads they serve, so publishing a searchable archive would be possible. We found no law that requires it, and the networks have not said why they do not publish one.
A commercial reason is possible. Many advertisers would prefer that competitors not be able to browse their creatives, offers and landing pages, and a public archive would allow exactly that. This is our reading of the incentives, not something the networks have stated.
| Meta and Google | Taboola, Outbrain (Teads), MGID, Revcontent | |
|---|---|---|
| Official public ad library | Yes (Meta Ad Library, Google Ads Transparency Center) | None found (checked October 7, 2026) |
| EU DSA ad-repository duty | Applies: Facebook, Instagram and Google services are designated | Does not apply: not designated (Commission list, August 31, 2026) |
| Searchable by outsiders at the source | Yes | No public archive found |
The official libraries are organized around the ad itself. For native, where the funnel from widget to advertorial to offer matters, the destination is some of the most useful data there is, and a third-party library that traces the click can add it.
Why a native ad library is hard to build#
If the networks do not publish a library, someone outside has to build one, and doing that properly is hard. It helps to know how the native ad supply chain works: before an ad renders, the request can pass through the network's ad server and sometimes exchanges or demand-side platforms, and after the click a visitor can pass through trackers and redirects before reaching the landing page. A native ad library has to reconstruct that chain from the outside. That means four hard jobs, all at once:
- Collecting what the widgets serve. Native units are delivered into publisher pages by a native ad widget, and we found no network-published archive of them. A library has to collect what those widgets serve across many publishers and geographies; OpenAdLibrary does this mainly through direct API requests, with a browser crawler as a fallback.
- Capturing the creative at full quality. A native ad is an image plus a headline. If you do not store the real asset when it is served, it may be gone later, and these placements rotate.
- Identifying the real advertiser. The brand name on the widget can be a label that does not identify the company behind the campaign. Resolving it means reading the supply chain, the same skill set you would use to identify the ad network behind any ad.
- Following the click to the destination. The landing page or pre-lander is where the offer lives, and it is one of the most useful artifacts for understanding a campaign.

Each of those is a hard engineering problem on its own. Doing all four continuously, across each major native ad network and many geographies, is why a native ad library is hard to build and keep current. Even then, coverage is partial: a library sees the publishers, geographies and times it collects from, not the whole market.
Commercial spy tools such as Adbeat, AdPlexity Native and Anstrex Native already sell searchable archives of native ads as paid subscriptions. On October 7, 2026 their listed monthly prices ranged from US$79.99 (Anstrex Native) to US$249 (AdPlexity Native) and US$249 to US$399 (Adbeat). AdSpy, sometimes grouped with them, describes itself as covering Facebook and Instagram ads. OpenAdLibrary sells a competing product and has not tested these tools for this article, so compare their coverage and features yourself.
What an actual native ad library has to do#
One way to separate a "spy tool" from a library is whether it gives you a dated, auditable record rather than a stream of examples. Concretely, that means capturing and keeping:
- The creative as served, stored at full quality, not a degraded thumbnail.
- The real advertiser, resolved from the supply chain and landing page rather than taken from the display name alone.
- The full supply path: which SSP, which DSP, which trackers, so you can tell who is buying ads on a website and through which intermediaries.
- The click destination, captured by following the redirect trail to the landing page without clicking live ads (a click on a pay-per-click ad can cost the advertiser money and distort their data).
- Longevity and spread, the dates and geos where each creative showed up.
That last point is what turns an archive into intelligence, within limits. A single snapshot tells you an ad exists. A dated, repeated capture tells you when and where it kept appearing, which is useful context; it does not tell you which ads work, because spend, clicks and conversions are not visible from outside.
Here is a concrete example. In our June 2026 captures, the longest observed spans for native creatives were about 28 days. One of them was this Outbrain finance ad from SmartAsset:

Twenty-eight days was the ceiling of our June 2026 observation window, not the ad's lifetime; the ad may have run before or after it. Talk of "90-day winners" is industry lore that our data does not confirm. An ad still being captured after weeks, across many publishers, tells you the advertiser kept it in circulation. It does not tell you the ad was profitable: brand budgets, ongoing tests and slow optimization keep ads running too. A "My IQ" quiz ad and a "Hidden Hearing" next-gen hearing-aid ad were in the same 28-day group on the Microsoft Audience Network; we have not verified either advertiser's claims.
Where OpenAdLibrary fits#
OpenAdLibrary, which publishes this blog, is one attempt to fill that gap. It collects public native ads from networks including Taboola, Outbrain, MGID, Revcontent, Teads, MediaGo, Yahoo and MSN, mainly through direct API requests with a browser crawler as a fallback. It stores the creative at full quality, classifies the ad-tech supply chain behind each placement, and follows the redirect trail to the advertiser's landing page without clicking live ads, capturing the destination where it loads. The result is a dated archive of native advertising, searchable on the paid Founders plan. It is a third-party archive of what its collection captured, not an official network library or a complete record.
Coverage is not even across networks, geographies or verticals. Capture counts, whether ours or another tool's, describe what was collected, not the size of each network or where a vertical's advertisers spend. When you research a vertical, check how much the library holds for your networks and markets before reading too much into an absence.

Pricing and tools: OpenAdLibrary sells access to this archive. Its free plan ($0, no card) shows the 20 newest Meta, TikTok and native ads, the top three results on intelligence pages, ad detail with the supply chain behind native ads, and the redirect trail and captured landing pages for native ads. Search, filters, saved research and the API require the Founders plan ($29.99/month), which also includes funnel tracing and real-advertiser resolution for native ads, Copy DNA, Creative Studio AI and publishing, Track, and an ad intelligence REST API with a hosted MCP server. If you are new to the wider category, the ad transparency tool explainer maps how independent libraries fit alongside the regulatory ones, and the ad transparency pillar covers the laws and libraries end to end.
It is worth placing this inside the broader practice of native advertising and the general idea of an ad library. For the walled gardens, the platform publishes the library and third parties can build tools on top of it. For native, as far as we found, the networks do not publish the source data, so the record has to be assembled from the outside.
The takeaway#
As far as we found, the networks themselves do not publish a native ad library. Meta and Google publish ad libraries, and in the EU the Digital Services Act makes a public ad repository a legal duty for their designated services; Taboola, Outbrain and MGID are not designated under it. Closing the gap from outside means rebuilding the record: collecting what the widgets serve, archiving the creatives, resolving the advertisers and following the redirect trail without clicking. That is a high bar, and any library that clears it still covers only part of the market.
Start free to browse the 20 newest captured ads, or use the Founders plan to search the archive of captured native ads.







