Facebook meta ads library

In October 2021, Facebook Inc. rebranded as Meta Platforms. The product brands (Facebook the app, Instagram, Messenger, WhatsApp) kept their names; the parent company name changed. The Ads Library lived through the transition: Meta updated some of the documentation to read 'Meta Ad Library' while leaving the URL on facebook.com and leaving older docs unchanged.

The compound 'Facebook Meta Ads Library' phrasing emerged in two places. First, in B2B and agency marketing materials where writers wanted to acknowledge both the legacy brand recognition ('Facebook' is what clients know) and the current corporate identity ('Meta' is what's technically correct). Second, in trade-press references and SEO-focused content where 'Facebook (now Meta)' style phrasing is editorial standard for any product owned by a company that has rebranded.

Google indexes the compound phrasing as its own query and ranks slightly different results for it than for either 'Facebook Ads Library' or 'Meta Ads Library' alone. We maintain this guide as the landing page for compound-phrasing searchers so they don't get bounced through a SERP optimized for one or the other variant.

Approximately nothing at the product level. The URL is still facebook.com/ads/library. The data shape is unchanged. The access controls are unchanged. The API endpoint is still on graph.facebook.com (not graph.meta.com). The field names in API responses are unchanged. The country partitioning is unchanged. The commercial-vs-political disclosure split is unchanged.

What changed is the documentation tone. Meta updated some of the Ad Library product pages, the developer docs, and the help center to read 'Meta Ad Library' instead of 'Facebook Ad Library'. The update was inconsistent - some pages kept the old name, some flipped, some say both in different paragraphs. Meta's own copy has no internal consistency on the naming question.

Practical implication: if you find a piece of documentation, a tutorial video, or an agency deck using one name, the content is still accurate for the other name. The product is the same. Don't waste time hunting down 'updated' versions of older content - the differences are cosmetic.

The compound naming most often appears in agency contexts - agencies servicing multiple brands, building competitive intelligence reports for client deliverables, or pitching new business with a creative landscape audit. The library is well-suited to this work but the manual UI caps out around 30-50 ads per session before fatigue. At agency scale, that's not enough.

Three patterns that work at scale. Tool stacks: pair the library with Foreplay, Atria, or Motion for AI-assisted tagging and bulk export. Sweep schedules: rotate the agency's competitive monitoring across a roster of 30-50 brands by scheduling 5-8 brand sweeps per day rather than a weekly all-brands audit. Client-deliverable templates: build a standard slide template for the competitive landscape section of pitch decks so the audit becomes a rinse-repeat workflow rather than a from-scratch design exercise per pitch.

Agencies that get this right run their competitive intelligence operation as a discrete service line. Agencies that don't drown in tab-scrolling and stop doing the work after the third client request.

Two small but meaningful library updates shipped between Q4 2025 and Q1 2026. Variant grouping collapses near-duplicate creative variants under a single result entry by default, instead of cluttering result sets. Start-date sort lets you sort results by start date directly - which makes the 'find the evergreen winners' workflow a single click instead of infinite scroll. Neither was announced; both shipped quietly.

Meta's broader Andromeda update (rolled out late 2025) compressed average time-to-fatigue on Reels placements from ~14 days to ~9. The downstream library effect: more ads in the recent-launch bucket, fewer in the long-tail evergreen bucket. If your audit feels noisier than in 2024, that's the macro reason.

Beyond these, nothing structural has changed. The commercial-vs-political disclosure split persists. The API's EU/Brazil-only commercial coverage persists. The gaps - no spend, no engagement, no targeting - persist. Plan around them.