EU DSA Ad Transparency: What It Means for Ad Libraries

A DSA ad repository is the public, searchable archive of ads that the EU's Digital Services Act requires from very large online platforms — services with more than 45 million average monthly active users in the EU. Under Article 39 of the regulation, each designated platform must publish every ad it served, keep it available for a year after the ad last ran, and disclose who presented it, who paid for it, when it ran, the main targeting parameters used, and aggregate reach broken down by member state. That is why Meta, Google, TikTok and the other designated platforms now operate ad libraries with EU-specific detail. It is also why most open-web advertising — including every native ad network — has no mandated transparency at all: they sit below the threshold.

What the DSA actually requires#

The Digital Services Act (Regulation (EU) 2022/2065) attaches its heaviest obligations to designated "very large online platforms" (VLOPs) and search engines (VLOSEs). On advertising, three provisions matter to practitioners:

• Article 26 — ad labeling. Every ad on a platform must be identifiable as an ad in real time, with the identity of who presented it, who paid for it, and meaningful information about the main parameters used to target it. Two hard bans ride along: no ads targeted by profiling on sensitive-category data (religion, health, sexual orientation and the like), and under Article 28, no profiling-based ads to minors at all.
• Article 39 — the ad repository. VLOPs that show ads must maintain a public, searchable repository with the content of each ad, the product or service concerned, the advertiser and payer, the running period, whether it targeted specific groups and the main parameters (including exclusions), and the total reach reached per member state. Ads stay in the repository for their entire run plus one year, and the repository must not expose recipients' personal data. Access must include a reliable API, not just a browse page.
• Enforcement. The European Commission supervises VLOPs directly and can fine up to 6% of a provider's worldwide annual turnover. Designations started in April 2023, and ad-repository quality has already featured in formal proceedings against several platforms.

One common confusion: the DSA Transparency Database is a different mechanism — it collects platforms' "statements of reasons" for content-moderation decisions, not ads. The ad repositories live on each platform's own domain.

Which ad repositories exist, and what is in them#

The familiar consumer-facing libraries predate the DSA — Meta's launched in 2019 around political-ads scrutiny — but the EU data layer (targeting parameters, per-country reach, all-category coverage) exists because Article 39 compels it. Our glossary entries on the Meta Ad Library and the Google Ads Transparency Center cover the practical search mechanics of each.

How to actually use DSA repositories for research#

For a media buyer or brand analyst, the EU layer offers things the standard library views do not:

• Targeting strategy, disclosed. The EU view of a competitor's Meta ads shows the main targeting parameters — age bands, geo, interest categories — which the regular library never reveals. That turns "what creative do they run" into "who are they pointing it at."
• Reach as a budget proxy. Member-state reach ranges let you rank a competitor's EU markets by actual delivery, not guesswork — useful before entering a market they already saturate.
• A compliance mirror. If you advertise on a VLOP, your own ads, payer identity and targeting summaries are public. Assume competitors, journalists and regulators read them; audit what your repository entries disclose before someone else does.

The limits are equally real. Repositories show creative and delivery metadata, never performance; coverage of small advertisers can lag; and search interfaces range from good (Meta) to barely usable. Quality is also uneven in ways regulators have noticed — repository completeness and API reliability have featured in Commission scrutiny of several platforms, and independent researchers routinely document ads missing from the archives that should contain them. Treat a repository as strong positive evidence ("this ad ran, this entity paid") and weak negative evidence ("absence does not prove an ad never ran"). For workflows built on top of these libraries, see Meta Ad Library alternatives — most serious teams combine the official repositories with independent tooling.

Three repository recipes worth stealing:

1. Rank a competitor's EU markets by delivery. Pull their ads in the Meta Ad Library EU view, note reach ranges per member state across their active campaigns, and you have their market prioritization — before you commission a single research report.
2. Watch a category for new entrants. Repositories are searchable by keyword and advertiser; a monthly sweep of your category terms surfaces newly registered advertisers and their launch creative while they are still small.
3. Audit your own footprint. Search your brand and your payer entities; verify the beneficiary/payer fields are correct, the targeting summaries match your media plan, and nothing an agency launched under your name would surprise your legal team.

The gap: the open web is not covered#

Here is the structural fact the DSA leaves untouched: the threshold is per-platform user count, and no native ad network crosses it. Taboola, Outbrain, MGID, Revcontent, MediaGo — none is a designated VLOP, so none owes anyone an ad repository. The result is asymmetric transparency: a brand's Instagram ads are public record with targeting detail, while the same brand's advertorial funnels across thousands of publisher sites are invisible to any official archive. What ad transparency means across this whole landscape — laws, libraries and their blind spots — is mapped in what is ad transparency.

Independent observation is the only thing that fills that gap. OpenAdLibrary exists precisely because no native ad library existed until someone built one without a mandate: the index holds 725,000+ live native creatives from 29,000+ advertisers across 49 networks, with 1.3 million traced landing captures (June 2026) — advertiser identity and destination funnels included, which is more than Article 39 requires of the platforms it does cover. The capture methodology — observing publicly served placements, the same principle DSA repositories codify — is documented in how ad spy tools capture native ads, and the searchable result is live in the ad intelligence platform.

What this means depending on who you are#

• Advertisers on VLOPs: your EU ads are public, with payer identity and targeting summaries. Treat repository hygiene as part of campaign QA, and expect competitive analysis of your own account.
• Native advertisers: no repository publishes your ads — but independent libraries observe them anyway, and regulators can subpoena what transparency law does not publish. The compliance rules that actually bite in native are consumer-protection ones (see FTC disclosure rules for advertorials for the US analog).
• Researchers and brand-protection teams: use official repositories for walled-garden platforms and independent indexes for the open web; neither substitutes for the other. Repository APIs plus an independent native index cover most of the paid-media surface a brand needs to watch.

Regulation built the precedent that serving an ad in public creates a public record. The open web just has not been assigned its regulator yet — which, for now, makes independent ad libraries the only DSA-grade record the native channel has.