First, confirm who is seeing the ads and which ad set serves them
Start with the report, not the screenshot. Ask the customer or colleague which ad they saw and where, then find it in Ads Manager and note the campaign, the ad set and the ad. Open that ad set's audience section and write down three things: who it includes, who it excludes and the window each one uses. For a catalog ad set, add the retargeting option and the product set it draws from. Only then is it clear whether a buyer was meant to be in the audience at all.
Several sightings look like a fault and are not.
| What you see | Why it can be expected | What to check instead |
|---|---|---|
| A buyer sees a replenishment or cross-sell ad | Retention ad sets are built to reach customers | That the ad is not for the item just bought |
| A buyer sees an ad from a prospecting ad set | Prospecting under Advantage+ audience can reach customers when nothing stops it | The diagnosis for Advantage+ audience reaching existing customers |
| Only one colleague, who is also a customer, reports it | A single feed is not a pattern | Whether other buyers report it and what the ad set's exclusions say |
| The buyer describes an ad on another network or in an email | Meta's exclusions apply only to Meta's ad sets | The other channel's own suppression rules |
If the ad comes from a retargeting rung or a catalog retargeting ad set that should have excluded the buyer, the fault is real. Before changing anything, make a test purchase with a product from the catalog and watch it in Test Events: whether the purchase event arrives, and which content IDs it carries, narrows the search to two of the five causes at once. If no events arrive at all, the diagnosis for pixel events not showing comes first.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Buyers see the same retargeting ad they saw before buying | The rung's exclusions for a purchaser or converter audience | No purchaser exclusion, or one narrower than the rung's audience | Exclude one shared converter audience from every rung buyers have passed |
| Catalog ads keep showing the item bought; Test Events shows an order code or no purchase | The purchase event in Test Events and the catalog's event matching report | A purchase event that never reaches Meta or carries unmatched content IDs | Send the purchase event with the catalog's item ID as the content ID |
| Buyers drop out of the ads for a while, then the same ad returns | The exclusion window against the rung's inclusion window | An exclusion window shorter than the retargeting window | Make each exclusion window at least as long as the inclusion window |
| Complaints come from phone, shop or other-channel buyers | Whether a customer list sits behind the exclusion, and its upload date | Buyers the pixel never sees | Add a current customer list to the exclusion and replace it on a schedule |
| Buyers see cross-sell or upsell ads featuring the item they bought | The product set the cross-sell or upsell ad set draws from | A product set that still contains the purchased item | Rebuild the set so it holds only complementary or higher-tier items |
Fix, verify and prevent each cause
No purchaser exclusion, or one narrower than the rung
The exclusions and overlap guide sets out who counts as a converter for an online shop: anyone who triggered the purchase event in the chosen window, plus anyone on the customer list. It also sets the rule that buyers are excluded from prospecting and from every retargeting rung they have passed, and kept only in the retention rung built for them. A rung with no purchaser exclusion has nothing stopping a buyer, and a rung that excludes only some converters, such as purchasers of one product line while the rung includes viewers of the whole range, lets the rest through. A Custom AudienceAn ad audience built from the advertiser's own sources: customer lists, site visitors or engagers. can also carry include and exclude logic inside itself, as the custom audiences guide explains, so check the audience definition as well as the ad set.
Fix: build one shared converter audience from the purchase event and the customer list and exclude it from every rung buyers have passed, rather than maintaining the subtraction ad set by ad set.
Verify: each retargeting ad set's audience section lists the converter audience under exclusions, and buyer complaints stop.
Prevent: keep exclusions on the same row as each audience in the paid social campaign build sheet, so a missing one is caught in review rather than by a customer.
A purchase event Meta never receives or cannot match
Dynamic RemarketingAdvertising to previous visitors or engagers. depends on events. The catalog ads guide describes the standard commerce events, ViewContent, AddToCart and Purchase, each carrying content identifiers that tell Meta which catalog items were involved, and notes that each retargeting rung excludes purchasers within its window through the format's own options. That exclusion only works when the purchase reaches Meta and names the same items. Where identifiers do not match the catalog's item IDs, the system cannot tell which products were involved, so a buyer can still look like someone who viewed the item and did not buy it. The diagnosis for catalog products not showing treats the same mismatch from the other side, where it hides items.
Fix: send the purchase event from the confirmation step with the catalog's exact item ID as the content ID, matching what the view and basket events send.
Verify: a test purchase in Test Events shows content IDs that exist in the catalog, and the event matching report in Commerce Manager shows purchase events matched.
Prevent: define one ID rule for the feed and every product event, and run the Meta catalog setup checklist after any change to the shop platform, theme or checkout.
An exclusion window shorter than the retargeting window
Website audiences are built from events, URL rules and a retention window, the number of days back that a qualifying action counts. When a rung includes basket adders over one window but excludes purchasers over a shorter one, a buyer ages out of the exclusion while still inside the inclusion, and the rung picks them up again. The exclusions guide names this as a common mistake: windows that do not match release people from one audience before the other lets them go.
Fix: set every purchaser exclusion window to at least the length of the rung's inclusion window, and longer where the product's buying cycle calls for it.
Verify: the build sheet lists both windows side by side for each rung and none is shorter than the window it guards.
Prevent: change windows in pairs: whenever an inclusion window is lengthened, the matching exclusion changes in the same edit. The maximum window a website audience allows is set out in Meta's help centre; this page does not repeat it.
Buyers the pixel never sees
A purchase-event audience holds only buyers whose purchase reached Meta from a browser that allowed it. The exclusions guide adds the customer list to the converter definition for that reason: the pixel misses buyers who declined consent or bought through another channel. The guide to uploading a customer list adds phone orders and other devices, and stresses that a list stays exactly as uploaded until it is replaced. A converter exclusion without a current list works like a Suppression ListA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. that only records some opt-outs.
Fix: upload a list of recent buyers from every channel, with every identifier you may lawfully use, and add it to the shared converter audience.
Verify: the list's audience shows the new upload date, and its estimated size has grown against the previous upload; Match RateShare of the records in an uploaded customer or account list that an ad platform matched to its own users or companies. is read by that comparison rather than against a fixed figure, as the upload guide advises.
Prevent: replace the file on a schedule rather than appending to it, and keep one definition of a customer across platforms, as the guide to customer lists across ad platforms recommends.
A cross-sell or upsell set that still holds the item bought
The catalog ads guide describes the cross-sell option as reaching people who bought from one product set and showing them a different, complementary set, and upsell as moving people from one set towards another. Both depend on the set they show being different from the set that qualified the person. A cross-sell ad set that draws from the full catalog, or from a set that overlaps the purchased one, can show a buyer the item they just bought.
Fix: rebuild the shown set so it holds only complementary or higher-tier items, using the attributes and labels the feed already carries.
Verify: the set preview no longer lists the purchased item, and the ad's product breakdown shows only items from the intended set.
Prevent: record which feed field each set depends on, and review the cross-sell and upsell sets whenever the range or the labels change, as the catalog ads guide advises for every product set.
Prevention: a purchaser-exclusion review with every audience change
Every cause above appears when something changes: a new rung, a longer window, a theme update, a new sales channel, a new product set. None of them produces a warning in Ads Manager, so the defence is a review attached to those changes, plus a light routine between them.
| When | Check | What it prevents |
|---|---|---|
| Every new or edited retargeting ad set | The converter audience is excluded and its window covers the inclusion window | Missing and short exclusions |
| Every site, checkout or theme release | A test purchase in Test Events with catalog content IDs | Purchase events that stop arriving or stop matching |
| Every new sales channel or change to the order system | Whether its buyers reach the customer list behind the exclusion | Buyers the pixel never sees |
| Every change to the range or the feed's labels | Cross-sell and upsell sets against the sets that qualify people | Sets that show the item just bought |
| On the list's replacement schedule | A fresh customer list replaces the old one | Exclusions that age quietly |
Name the rungs by stage. The See-Think-Do-Care framework gives each rung a job, and the Care stage is where buyers belong: one retention ad set for replenishment and Cross-SellingOffering a customer a related product alongside the one they are buying; upselling offers a higher-value version instead., with its own budget and message, so the question of who sees what is answered by structure rather than by luck. The exclusions guide's funnel table sets out which rung excludes which audience; keep that table as the account's rule and check every change against it.
Watch FrequencyAverage times a person saw an ad. on the smallest rungs too. A retargeting audience that keeps recycling buyers stays small and sees the same ads too often, and the guide to frequency and creative fatigue explains how to tell wear-out from a structural problem. If an exclusion leaves a rung too small to deliver, the page on a custom audience too small covers the options. Where the shop also sends basket reminder emails, the comparison of abandoned cart emails and remarketing ads shows how to split abandoners between the two channels and suppress one against the other. The guide to prospecting and remarketing explains why remarketing's reported return includes sales it did not cause, which is why ads reaching people who have already bought can look profitable while wasting money. Where the same question arises for prospecting, the existing customer exclusion test compares matched regions with and without customer exclusions rather than assuming the answer. Excluded custom audiences stay a hard control even under Advantage+ audience, as the Advantage+ audiences guide documents, so the same converter audience protects automated ad sets too. The Meta Ads troubleshooting collection routes any other delivery or audience symptom.
A lighting shop stops chasing its own buyers (illustrative)
Nimbrowe Lighting
Nimbrowe Lighting, an invented lamp and lighting shop, hears from 14 customers in a month that the lamp they bought keeps following them in Instagram ads. The ad set behind most complaints is the basket rung of its catalog retargeting ladder, which includes basket adds over 30 days but excludes purchasers over only 7. A test purchase in Test Events shows the purchase event sending the shop's order code as the content ID, while the view and basket events send the catalog's product IDs, so purchases match no item. About a fifth of orders come by phone and never reach Meta at all. The shop aligns every exclusion window with its rung, makes the purchase event send the catalog's product IDs, adds a weekly customer list of all buyers to one shared converter audience excluded from every rung, and rebuilds the cross-sell set, which had drawn from the full catalog, around shades, bulbs and fittings only. In the following month no customer reports the problem, and the shop's own estimate of retargeting spend reaching buyers from the previous 30 days falls from 22% to 4%.
Common mistakes
- Changing the audience before reading the ad set. Find which ad set served the ad and what it excludes first; a prospecting or retention ad set needs a different fix.
- Trusting the purchase event without a test purchase. An event that arrives with an order code instead of the catalog's item ID looks healthy and matches nothing.
- Lengthening an inclusion window alone. Every inclusion window needs an exclusion window at least as long.
- Relying on the pixel alone. Phone, shop and declined-consent buyers only leave the pool through a customer list.
- Appending to the customer list. Replace the file on a schedule so recent buyers are always in it.
- Drawing cross-sell from the full catalog. The shown set must differ from the set the buyer bought from.
- Judging the problem from one feed. A single colleague's sighting is a prompt to check, not proof of a leak.
