Choosing Acquire new customers in a Meta Sales ad set now adds an exclusion you cannot remove: people who fired your purchase event in the last 730 days, by default. Jon Loomer reported it on October 13, 2026; Meta has not documented it. Here is what the list counts, what it misses, and how to decide before Black Friday.
The setting itself is official. Meta made Customer Lifecycle Strategy available to all advertisers on October 6, and for acquisition campaigns it now suggests excluding existing customers. The automatic list is the part only seen in Ads Manager so far, and it arrives just as Black Friday ad sets are being planned.
What changed, and when
Jon Loomer wrote about the setting on April 2, from a screenshot shared on LinkedIn: a Customer Lifecycle Strategy choice at the top of the ad set in Sales campaigns, with two options, Reach new and existing customers and Acquire new customers. The second option's description, as he relayed it, said it may increase your cost per result.
In his June 4 test, Acquire new customers did not exclude anyone by itself. The exclusion field read None selected, and every past-buyer audience had to be added by hand.
On October 6, Meta's Advertising Week New York announcement said: "Customer Lifecycle Strategy is now available to all advertisers." The same paragraph says acquisition campaigns get suggested exclusions of existing customers, and that Meta is testing a way to exclude a whole group of existing customers with a single Audience Label.
On October 13, Loomer published screenshots dated the day before. With Acquire new customers selected, a new row sat under the existing customer exclusions: Automatically created: Customers from your conversion data (730 days). That row is what this post is about, and it rests on his report, not on Meta documentation.
It extends a run of changes to how Meta handles existing customers. The Existing Customer Budget Cap in Advantage+ sales campaigns is gone, and Meta's help page now explains how to replicate it by hand, with an exclusion or with two ad sets. Placement controls also left ad sets. This time Meta adds a control instead of removing one, but it is a control you cannot switch off once you pick the option.
Where the setting is, and what each option does
Meta's Help Center article on the setting is titled "Create a campaign to acquire new customers". We could not load its body while writing this, so the details below come from Loomer's October screenshots.
In a Sales campaign, the choice sits at the top of the ad set. In those screenshots the dropdown offers Get conversions from all audiences and Acquire new customers; in April, the first option read Reach new and existing customers.
| Setting | Get conversions from all audiences | Acquire new customers |
|---|---|---|
| Who the ad set can reach | New and existing customers | People outside your excluded past buyers |
| Automatic exclusion | None | Customers from your conversion data, built from your purchase event (reported) |
| Can you remove it | Nothing to remove | No, while the option is selected (reported) |
| Window | Not applicable | 730 days by default; 180, 90, 60 or 30 (reported) |
| Your own exclusions | Audience section, Legal and operational custom audience exclusions | Custom audiences can still be added on top (reported) |
| Option description | Not reported | May increase your cost per result (relayed in April) |
If you want the old behaviour, Loomer's suggestion is to stay on Get conversions from all audiences and add your customer audiences under Legal and operational custom audience exclusions in the Audience section. The field's name says what it was built for, so treat this as a workaround rather than a documented method. He also doubts that a fixed exclusion is what Meta intends, so the behaviour may change; check the ad set before you rely on either path.
What Meta counts as a past buyer, and what it misses
As reported, the automatic list is everyone who fired your purchase conversion event inside the window, taken from the ad account's own conversion data rather than from your custom audiences. Loomer calls 730 days the "relatively new maximum available for purchase events". That makes the list only as complete as your purchase event.
These buyers are missing unless their sale reaches Meta as a purchase event:
- Phone, in-store and other offline sales
- Marketplace orders that never touch your site
- Renewals your billing system records off-site
- Purchases your pixel missed, for example after a consent refusal, that the Conversions API did not send either
Loomer's fix is a customer list custom audience added as an extra exclusion, and he notes that people who buy both online and offline need data from both sources. Before you rely on the automatic list, compare purchases in Meta with orders in your own system for the same week. The Meta ads audit checklist puts that reconciliation in its first, measurement block, and Meta Pixel vs Conversions API covers which tag sees which sale.
Meta has not said whether Conversions API, offline or in-app checkout purchases count, or how the list relates to the existing customers segment in Advertising Settings. One consequence follows from how the list is built, and it is our reading rather than a reported fact: because the list follows the purchase event, not a product, a buyer of anything you sell is excluded, not only a buyer of the product in the ad.
Who it affects
Online stores running Sales campaigns with a purchase event are the main group. Agencies should check each client account separately, because each list comes from that account's own conversion data.
SaaS companies that send paid sign-ups as a purchase event fall under the same logic. That is our inference; nothing in the reports covers SaaS, so look at your own ad set. For Leads and App promotion campaigns Meta has not documented the option at all. Its audience segments can define existing customers from lead forms, but that is a reporting setting, and its link to this exclusion is not stated.
The Black Friday decision
There is no single right answer, so decide per account. The table below is our reading, not Meta guidance; the windows are the five reported ones.
| Account type | Choice | Window | Why |
|---|---|---|---|
| One-time purchases, such as a mattress | Acquire new customers | 730 days | A past buyer rarely needs a second one |
| Consumables and refills | Get conversions from all audiences, plus a retention campaign | Not used, or 30 to 90 days on a prospecting-only ad set | The buyers you want back in November sit inside a 730-day list |
| Subscriptions | Acquire new customers on acquisition ad sets | 730 days, plus a subscriber list | Renewals billed off-site may be missing from the list |
| Small accounts, a few purchases a week | Get conversions from all audiences; test the option on one ad set | Match your repeat cycle | With few purchases, results take longer to read |
| Returning buyers carry your BFCM sales | Get conversions from all audiences, plus a retention budget you set | Not used | Keep them reachable, with spend you decide |
Say you run a coffee brand that also sells grinders, in one ad account. A grinder ad set on Acquire new customers with the 730-day window looks right, since a past grinder buyer is unlikely to want another. But the list follows your purchase event, so everyone who bought beans in the last two years is excluded too, including people who might well want a grinder. The coffee ad sets have the opposite problem: September's bean buyers are exactly who you want back in November. One way out is to keep both on Get conversions from all audiences, exclude past grinder buyers yourself with a customer list, and give returning coffee buyers their own retention campaign and budget.
If you follow our 28-day BFCM calendar, audience structure locks on October 30, so make this call before then. An exclusion acts before delivery does: excluded people are never eligible for the ad set, so Andromeda's retrieval and the ranking after it never consider its ads for them. With past buyers out, plan new angles for people who have never bought from you; creative generation turns a product page into concepts to test.
Five checks before you change an ad set
Run these before switching any Sales ad set, and write down what you chose:
- 1.Define audience segments in Advertising Settings: an engaged audience and existing customers.
- 2.Turn on the audience segments breakdown in Ads Manager (Breakdown, By demographics, Audience segments) to see results from new, engaged and existing customers.
- 3.Compare purchase events in Meta with orders in your own system for the same week, and add a customer list exclusion for whatever does not reach Meta.
- 4.Pick the window by how often your customers buy again.
- 5.Give returning buyers their own campaign or ad set with a budget you set, which is also how Meta's help page replicates the old budget cap.
Steps one and two follow Meta's help pages on creating audience segments, which can draw on website, app, catalog, customer list, offline, shopping and lead form sources, and on the audience segments breakdown. Meta notes that the breakdown may not be available to every account yet.
How to read the result
Expect a higher cost per result in Ads Manager; the option's description, as relayed in April, says it may increase. A drop in in-platform ROAS after the switch is not a verdict on its own. Read three numbers together for the same period: cost per new customer from your own order data (spend divided by first-time buyers), MER (total revenue divided by total ad spend) and the audience segments split in Ads Manager.
A smaller audience can also see the same ads more often, so watch frequency and the other creative fatigue signals in the weeks after the change. Annotate the date you switch in any report you will still read in December.
If your Meta account is connected to AdRiseLab, the AI Media Buyer reads its data before and after the change and recommends what to adjust; budget or status changes apply only after you approve them. It does not split results into new and existing customers; that breakdown comes from Meta's audience segments. AdRiseLab is Meta-only, and plans start at $39 a month.
What Meta has not said yet
Until Meta documents the automatic exclusion, these stay open:
- Whether the row is intended, and whether an off switch is coming
- Which purchases count: pixel only, or Conversions API, offline and in-app checkouts too
- How the list relates to the existing customers segment in Advertising Settings
- Whether it behaves the same with Advantage+ on or off, and whether it reaches Leads or App promotion
- Whether every account has it
- Whether switching an existing ad set to Acquire new customers resets learning
- What the Audience Label test covers, and when it ships
The same week brings three more dated changes: Marketing API changes that apply to all versions on October 27, product browsing in existing ads on October 28 and new ad terms on October 30.
Sources
Jon Loomer, Meta Adds Automatic Customer Exclusions, October 13, 2026, screenshots dated October 12. Jon Loomer, Customer Lifecycle Strategy, Attribution Updates, and More, April 2, 2026. Jon Loomer, Customer Lifecycle Strategy Is Not What Advertisers Thought, June 4, 2026. Meta for Business, Advertising Week New York 2026, October 6, 2026. Meta Business Help Center, Create a campaign to acquire new customers, title only, body not read. Meta Business Help Center, How to replicate existing customer budget cap. Meta Business Help Center, Create audience segments in Meta Ads Manager. Meta Business Help Center, Use audience segments to enable breakdown reporting. Meta for Developers, Marketing API v26.0 changelog. Meta Help Center pages carry no dates and were read on October 21 and 23, 2026. The automatic exclusion, its windows and the fact that it cannot be removed are reported by Jon Loomer and not confirmed by Meta.
Related reading
Meta turns on product browsing in existing ads on October 28 and Meta's ad terms update on October 30 are the previous changes in this series. Event match quality covers how well your purchase events match people to Meta accounts; a buyer Meta cannot match cannot be excluded either.