Why Your Meta Custom Audiences Stopped Working (Health and Wellness Brands)

Last updated: November 11, 2026 · By Jason Garrett, Founder, Coast Studio. Not legal advice — review claims with counsel.

Short answer: On a health or wellness data source, Meta's data restrictions are a common reason custom audiences shrink, stall, or become unusable. This page covers five restriction-related causes: Core Setup, a restriction on certain standard events, full restrictions, custom events awaiting review, and a flag on the audience itself. Audiences fail for other reasons too, so confirm your cause in Events Manager and in Audiences before you rebuild.

Find the possible cause

What you see	Possible cause	Where to check
Website audiences built on URL rules shrink or stop updating	Core Setup	Events Manager, dataset Settings tab
Purchaser or lead audiences stop growing	Restriction on certain standard events	Events Manager, Manage data source categories
Website or app audiences stop populating in a region	Full restrictions	Events Manager, Manage data source categories, affected regions
Audiences built on custom events stall	Custom events awaiting review, or blocked	Events Manager, custom event review
An audience is flagged and cannot be added to a campaign	The audience includes information Meta prohibits	Audiences, or the campaigns table in Ads Manager

Each row is a clue. Establish the restriction from Meta's notice, the dataset's settings, the affected events, and the affected regions.

Core Setup: the rule lost its input

Core Setup stops custom parameters and everything in a URL after the domain. A product URL with a path and a query string reaches Meta as the bare domain. An audience rule that reads the path has nothing to read.

Meta lists the effects. Audiences that rely on custom parameters or URLs cannot be prefilled and may populate slowly or become unavailable. Audiences that combine device rules or aggregation values with custom parameters or URLs cannot be created and stop updating. Ad sets that depend on a shrinking audience can lose delivery.

What to do. Rebuild on inputs Core Setup leaves alone: the domain, and standard events with standard parameters. Then open each rebuilt audience in Audiences and confirm that it populates and is available for delivery. Automatic advanced matching may also switch off under Core Setup, and Meta's answer is to set up advanced matching manually.

Standard-event restriction: the event stopped arriving

Under a restriction on certain standard events, Meta refuses specific mid- and lower-funnel events from your data source. Audiences seeded by those events can stop growing.

What to do. Read your notice to learn which events are restricted. Rebuild on events Meta still accepts, and check each one in Audiences. An event that arrives in Events Manager has been received. Its availability as an audience source is a separate check. Our purchase-event guide covers the event side.

Full restrictions: no events for ads in the affected regions

Full restrictions stop all event sharing from the data source in the regions they cover. Meta states that Business Tools cannot be used for ads purposes where full restrictions are in place, so audiences built on that data source's events are unavailable there, and custom events may be unavailable too. Meta points fully restricted advertisers to objectives that need no Business Tools data: Awareness, Engagement, and Traffic. Check which regions your notice names.

Custom events: review comes first

Meta requires a review of every new custom event, on any dataset. When a dataset carries a data restriction, Meta also blocks custom events until someone with full control of the business asset confirms them. Confirm an event only if its data follows the Meta Business Tools Terms. After confirmation, check that the event is available as an audience source. Under full restrictions, custom events may be unavailable.

Flagged audiences: the audience itself broke the rule

Meta flags custom and lookalike audiences that include information its terms prohibit. Its example is a reference to a specific health condition. A flagged audience cannot be used in a new campaign, and Meta tells you to edit or pause active campaigns that use one. A flag is separate from a data source restriction and has its own resolution.

What to do. Review the audience and the information attached to it, including its name and its rules, and remove every condition reference. Or build a new audience that carries none. For a flagged lookalike, repair the seed audience first. If Meta flagged the audience in error, request a review from the campaigns table in Ads Manager or from the audience's summary tab.

FAQ

Did Meta delete my custom audiences?
Meta's help pages describe audiences that stop updating, become unavailable, or cannot be used. They do not describe deletion. Check each audience's status in Audiences.

Can I still retarget website visitors under Core Setup?
Often. Core Setup restricts custom parameters and the part of a URL after the domain. Audiences that need neither can continue to work, and rules that read a URL path or a custom parameter stop working. Confirm each audience in Audiences.

Do lookalike audiences still work?
A lookalike follows its seed. If the seed is flagged or has stopped updating, fix or replace the seed, then rebuild the lookalike.

Can I name an audience after a condition?
No. Meta flags audiences that reference specific health conditions. Name audiences by funnel stage or event.

Will a category review bring my audiences back?
A changed category lifts the restrictions tied to it. Audience flags and blocked events are separate matters and can need their own resolution. Check each audience after Meta's decision. Our category-removal guide explains the review.

Sources

Not legal advice. Review claims with counsel.