What spend data does the DSA force Meta to publish?
The Digital Services Act forces Meta to publish a bucketed spend range and an impression range for any ad that reached a user inside the European Union, attached to a public page in the Ad Library. That page shows who paid, the spend band, the reach band, and a demographic split by age, gender, and country. Coverage extends to every commercial advertiser running EU-visible ads, not just political ones; the older disclosure rules covered only political and social-issue campaigns.
The spend figure is never a single euro amount. Meta reports it as a band — a few hundred euros at the low end, running up through an open-ended top bucket north of a million for heavily-funded campaigns. The exact cutoffs between bands have shifted since the DSA's transparency obligations took effect across 2023 and 2024, so treat any specific boundary you find written elsewhere as approximate until you confirm it on the live Ad Library page.
Impressions carry the same range treatment, broken out by the EU countries where those impressions actually landed. Divide the spend band by the impression band and you get a rough implied CPM for the campaign. That derived number, not the raw spend figure, is usually the most useful thing on the page when you're sizing how committed a competitor is to an offer.
How do you pull EU transparency data on any advertiser?
Open Meta's Ad Library, set the country filter to an EU member state, and search the advertiser's Facebook or Instagram Page name directly. That single search returns every ad Meta classifies as currently or recently active for that Page, no login and no EU IP address required.
Set the ad category to "All ads" rather than the political filter, since most affiliate and e-commerce offers fall outside that narrower classification. Pick a populous, English-friendly market first — Germany, France, or Ireland — to get a wide enough ad set, then open an individual ad card and click through to "Ad details" to see the spend range, impression range, and audience targeting for that specific creative.
Run the same search across three or four EU countries rather than one, because Meta buckets the range per country when an advertiser breaks out geo-targeting, and a single-country pull can undersell total EU spend. Recheck the page every one to two weeks if you're tracking a live competitor; the Ad Library reflects Meta's own ad-serving records, but it isn't instantaneous.
Does this work for US-only campaigns?
Only indirectly, because the DSA obligation covers ads that actually reach EU users; a campaign built for the US with the EU excluded from targeting produces zero rows in the Ad Library. No EU impressions means no EU disclosure, full stop.
Plenty of media buyers running a US or BR offer still push a parallel EU test batch anyway, to season a pixel, hold down a quality signal, or test a hook cheaply, since CPMs across several EU markets sit below US CPMs for the same vertical. When a US-focused advertiser does this, their page shows up in the EU library, and that gives you a proxy read on their total budget commitment even though the dollar figures you're reading are EU-only spend.
Check for EU presence before you build anything on this method. Search the advertiser's Page with the country filter set broadly across the EU first; if nothing returns, the technique gives you zero signal and you should fall back to a different spy method entirely.
How do you estimate global spend from EU numbers?
You scale the EU spend band using population and CPM ratios between the sampled EU country and your target market. This is an order-of-magnitude estimate for deciding whether an offer justifies its entry cost, not a figure you'd put in a media plan.
Take the midpoint of the spend range and the midpoint of the impression range to get an implied CPM for the EU campaign. Compare that CPM against your own benchmark CPM for the US or Brazil in the same vertical, then apply the ratio to the EU spend figure to get a rough equivalent budget for the market you actually care about.
| Market | Rough CPM index (EU average = 1.0) | Confidence |
|---|---|---|
| European Union, blended average | 1.0 | Baseline derived from Ad Library ranges |
| Germany / France / Netherlands | 1.1–1.4x EU average | Directional only, verify per vertical |
| Poland / Romania / Bulgaria | 0.5–0.8x EU average | Directional only, verify per vertical |
| United States | 1.3–1.8x EU average | Needs verification per vertical and quarter |
| Brazil | 0.4–0.7x EU average | Needs verification per vertical and quarter |
What are the data's blind spots?
The ranges are bucketed, not exact, and that single fact is the method's biggest limitation. Two advertisers sitting at opposite ends of the same band look identical on the page, so a small operator can look indistinguishable from a much bigger one until you cross-reference with something else.
- Buckets get coarser as spend rises, so the top band tells you almost nothing beyond "a lot"
- Non-EU spend is invisible; a campaign running mostly in the US shows only its small EU slice, if any
- Ads with zero EU targeting never appear in the library at all, regardless of scale
- The range midpoint is a convenient proxy, not a verified real spend figure
- One advertiser can split real budget across several Pages or ad accounts, fragmenting the true total across multiple library entries
- Library data can lag live campaign activity by days, so a just-launched or just-paused ad may not reflect current reality
How do pros build spend dashboards from this?
Pros pull Meta's Ad Library API on a recurring schedule and store the range midpoints as a time series per advertiser Page, instead of rechecking the interface by hand. The API is free but requires app registration and identity verification, and it returns the same range and targeting fields you'd see manually, just structured for repeat pulls.
A typical setup snapshots each tracked Page weekly, computes the delta between snapshots, and flags a jump between bands as a signal that a competitor is scaling. Layered against creative-level metadata — new ad IDs, changed copy, new landing pages — that delta becomes a rough scaling curve for the offer, even though every point on it is still a range rather than a hard figure.
Most operators in this space trust a paid spy tool's confident-looking dollar figure over Meta's vague range, and that's backwards. A spy tool infers spend from creative frequency and a modeled CPM with an unstated error margin; the DSA range, coarse as it is, comes directly out of Meta's own ad-serving and billing system because a regulator forced its publication. Use the Ad Library number as the anchor and treat the spy tool's precise-looking figure as the adjustment, not the other way around.
Quick decision checklist
Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.
Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.
- Start with the TL;DR if you need the direct answer.
- Use the table to compare trade-offs quickly.
- Use the FAQ for answer-engine-ready summaries.
- Use the CTA when the decision requires live VSL and ad examples instead of theory.
Daily Intel's coverage advantage
Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.
This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.
Blackhat, whitehat, and multilingual signal coverage
Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.
The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.
| Research need | Generic ad archive | Daily Intel Service |
|---|---|---|
| Creative volume | Large raw databases with mixed relevance | Curated VSL and ad examples selected for direct-response usefulness |
| Blackhat and whitehat awareness | Often flattened into screenshots or URLs | Explicit attention to compliance spectrum, cloaking risk, and claim style |
| Post-click context | Usually limited or inconsistent | VSL, transcript, funnel path, checkout, upsell, UTM, and recovery notes where available |
| Language coverage | Search filters may exist, but context is thin | 14+ language and international idiom coverage for global affiliate research |
| Best use case | Broad browsing and historical lookup | Nutra, supplement, GLP-1, VSL, and direct-response campaign decisions |
How to use the intelligence responsibly
The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.
A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.
- Model structure, not protected creative assets.
- Separate whitehat durability from blackhat persuasion pressure.
- Compare US English examples against LATAM, European, and other language variants.
- Use transcripts and funnel notes to build original briefs.
- Keep compliance review separate from market research.
Methodology and source context
Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.
For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Google helpful content guidance, Google SEO link best practices, and Meta Ad Library. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.
For deeper evaluation, continue through Daily Intel research methodology, Launch Day: The First 24 Hours of a Nutra Campaign, Is It Too Late for the GLP-1 Wave? A Saturation Timing Read, The GLP-1 Economy: A Market Map for Media Buyers, The Compounded Semaglutide Crackdown, Explained for Affiliates, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.
Founding rate — locked forever
Access curated VSL intelligence for $29.90/mo
- 50–100 manually validated VSLs every day at 11PM EST
- major niches niches, 14+ languages, blackhat-to-whitehat pattern coverage
- live catalog VSL/ad catalog, transcripts, UTMs, full funnel maps
- Cancel anytime — founding rate stays yours forever
Daily Intel Service delivers manually curated research around active-scaling VSLs, Meta creatives, UTMs, funnels, and nutra market movement.
Frequently asked questions
Does the EU Ad Library show an exact spend number for an ad?
No, it shows a bucketed range rather than a precise figure, by design under the DSA. The range narrows at low spend levels and widens dramatically at the top, so a heavily-funded campaign and a moderately-funded one can land in the same open-ended top band.Do I need an EU account or VPN to see this data?
No, the Ad Library is public and accessible from any location without an EU IP address or login. You only need to set the country filter inside the tool itself to an EU member state before searching an advertiser's Page.How current is the spend range shown on an ad's detail page?
It tracks close to live activity but can lag by roughly a few days depending on Meta's update cycle. Treat a just-launched or just-paused ad's numbers as provisional and recheck the page after a week if the figure matters to a decision.Does this cover Instagram ads or only Facebook?
It covers both, since the DSA transparency requirement applies to Meta's ad-serving across its platforms, not to one app alone. An advertiser's Ad Library entry aggregates ads regardless of whether they ran on Facebook, Instagram, or both.Is there an equivalent transparency rule for TikTok or Google Ads?
Both platforms carry some disclosure obligation as designated Very Large Online Platforms under the DSA, but the format and depth of what each publishes differs from Meta's implementation. Verify the current state of each platform's own ad library directly before relying on a cross-platform comparison.
Continue the research path