Meta Ad Library Search as a Buying Signal

A Meta Ad Library search matches your keywords against an ad's text, its images, the audio from its video and its call-to-action button. Meta's API reference says so directly, and adds that it does not translate your search terms, so you have to write them in the language of the ads you are looking for.

The disclosure first. We build Keaz Signals, which sells ecommerce store data with live buying signals attached, and two of the events we detect are about Meta advertising specifically. We are a competitor to plenty of tools in this space, though not to this one. The Ad Library is Meta's, and we sell nothing that competes with it. We do have an interest in you concluding that reading ad activity one store at a time is slow work, so read the rest with that in mind.

What follows is a reading of Meta's own Graph API reference for the Ad Library, version 26.0, retrieved 13 September 2026, and of our own product behaviour. No scraped benchmark, no third-party coverage study. Where the reference states something plainly it is quoted; where it is silent, this article says so instead of filling the gap.

Whether an ecommerce store's ads are in the result set at all is decided by one line in the reference, under the required country parameter. It is easy to skim past, and it governs the whole exercise for anyone doing commercial prospecting rather than political research.

Note: Ads that did not reach any location in the EU will only return if they are about social issues, elections or politics.

Read that in the direction that matters for a store. An ordinary product ad — a skincare brand promoting a serum, a homeware shop pushing a bundle — is not about social issues, elections or politics. So the API returns it only if the ad reached somewhere in the EU. A store advertising to the United States and Canada only, with no EU delivery, sits outside the set the API will hand back.

That is a structural property of how the archive is scoped, not a claim about anyone's transparency or anyone's compliance. Meta publishes a broad archive where it is required to and a narrow one elsewhere, and the API reference is candid about the boundary. But it means an empty result is genuinely ambiguous: the store may not be advertising, or the store may be advertising to a market the archive does not cover. Those two are not the same finding, and nothing in the response distinguishes them.

Some filters work on any ad and some are marked, in the reference itself, as available only for political and issue ads. The split matters, because the fields most people assume they can read off a store's advertising are all on the political side of it.

Available for any ad type: active status, which defaults to ACTIVE and can be set to INACTIVE or ALL; a delivery date range; media type across image, meme, video or none; language; and publisher platform, where the enum runs Facebook, Instagram, Audience Network, Messenger, WhatsApp, Oculus, Threads and streaming services. You can search up to ten Facebook Page IDs in one query. Search terms are capped at 100 characters, and a blank space is treated as a logical AND.

Marked available only for political and issue ads: the paid-for-by byline, the region breakdown of where accounts were located when an ad was shown, and the minimum and maximum estimated audience size. So for a store's commercial ads there is no spend figure, no reach figure, no audience-size band and no regional split. You get that the ad exists, roughly when it ran, and what is in it.

There is also a rate limit, error 613, which is the practical ceiling on treating this as a monitoring loop rather than a lookup.

A store running Meta ads has a budget and someone accountable for how it performs. That is what the signal is evidence of, and it is a lower bar than qualification. It does not tell you the store is profitable or in any position to hire you. It tells you money is moving and a person is watching a number.

The stronger reading is the change, not the state. A store that was not advertising and now is has made a decision this week. A store whose active ad count is climbing is scaling something. Both carry a date, and the date is the only part of an outreach message that could not have been written a month ago.

Those two events are live signals we detect. The list behind the first is at ecommerce stores running Meta ads right now; working them across a week is covered in How Meta Ads Agencies Find Stores Worth Pitching.

The Ad Library answers a question about one advertiser at a time. Prospecting asks the inverse question: which stores changed this week. You cannot get from one to the other by searching harder, because the search box takes a keyword and a country and hands back ads, not a diff against last Tuesday.

You can search up to ten Page IDs per query, which suits a watchlist of accounts you already care about. It does not suit discovery. To notice that a store started advertising you have to have known the store before it started, checked it on a day when it was not advertising, and checked it again after. The archive holds ads; it does not hold your previous reading of it.

Our side of that is a pool and a schedule rather than a clever query. As of September 2026 we watch 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly, with roughly 41,200 carrying a fresh signal in any seven-day window. Those are our own moving figures and they move, which is why they are dated. Stores arrive with contacts attached in the ecommerce leads database, and sending runs through your own Instantly workspace.

We are not going to tell you how often a store that starts running Meta ads goes on to hire an agency. It is the number you would most want from an article like this, we did not measure it, and we are not aware of a defensible published version of it. An invented one would be worse than none.

We are also not going to tell you what share of ecommerce stores are visible through the Ad Library API, or how much of a given market the EU clause removes from view. That would take a sampling study against a known population, and we have not run one. The clause itself is quoted above because Meta publishes it; the size of its effect is a measurement, and measurements we did not take do not go in our articles.

And no reply rates. Not for signal-led outreach in general and not for Meta ad activity in particular. A reply rate is a property of your offer, your segment and your domains together, and a vendor controls one of those at most. A figure produced under someone else's conditions is not evidence about yours.

For looking closely at one advertiser, the Ad Library beats us and it is not close. It shows you the creative itself — the copy, the image, the video, the call to action, run across a date range. If you are preparing for a call with a specific store, or want to see what a brand's current angle is before you pitch a new one, open the Ad Library. We do not show you creative and we are not going to start.

The rest of where we lose is worth stating in the same breath. We do not export: leads move into campaigns and stay there, which for some teams is disqualifying and should be. There are no LinkedIn signals and no LinkedIn sending, and none are planned. We watch Shopify and WooCommerce stores in Europe and North America and nothing else, so a store on another platform or in another market is invisible to us whatever its ads are doing. Registry and firmographic triggers and hiring signals are marked planned, not shipped. We are GDPR-conscious by design and will not claim more than that; responsibility for what you send stays with you.

If what you want is a picture of who is spending, the honest answer is a search box and an afternoon. If what you want is which stores moved this week, that is a different instrument. Signups start with 1,000 free leads, which is enough to check whether the signal fires often enough in your segment to be worth a workflow.

• Graph API Reference v26.0: Ads Archive, Meta for Developers. Every quoted clause, parameter and error code above comes from this page, retrieved 13 September 2026.
• Our own product behaviour as published on the buying signal catalogue, retrieved 13 September 2026.
• Own pool figures: 4.1 million Shopify and WooCommerce stores under watch across Europe and North America, re-scraped weekly, approximately 41,200 carrying a fresh signal in a seven-day window. As of September 2026. These figures move and are not permanent.
• No competitor coverage figures, no third-party benchmarks and no reply rates are cited here. That is deliberate, and the reason is in the section above.