Meta flagged my custom conversion for health information

Why Meta flagged it

Meta's rule for custom conversions is short: "Advertisers must ensure their custom conversions do not suggest information not allowed under our terms. For example, references to specific health conditions, such as arthritis, or financial status, such as credit score, aren't allowed." Its wider rule reaches past the name to the logic behind it: "the names you choose and criteria you establish for your events, conversions, and Custom Audiences must not reflect, imply, or be based on any prohibited information."

According to LiveRamp's announcement of the change, Meta began rolling out "proactive restrictions on custom audiences and conversions" on September 2, 2025, and said the change could affect ongoing campaigns. On a clinic or telehealth account, check these first:

• A URL rule that matches a condition or treatment in the page path, such as a thank-you page inside a condition-named folder.
• A name that states the condition, treatment or medication the person booked for.
• A rule built on a custom event or parameter whose value names a condition.

What the flag does to your campaigns

• New campaigns: "You won't be able to use flagged custom conversions when creating new campaigns."
• Running campaigns: Meta says you "should either create a new campaign or duplicate your campaign and use a non-impacted custom conversion to avoid performance and optimization issues."
• Conversion data: LiveRamp's relay of Meta's notice says "Custom conversions will stop receiving new conversion data", and that the change "May cause reduced delivery and performance in ongoing campaign (but Meta will not pause your campaigns)". A campaign can keep spending while the conversion it optimizes for stops counting.
• No swapping: Meta says "Once the campaign is published, you cannot remove or select a different custom conversion." That is why the fix is a new or duplicated campaign, not an edit.

How to resolve a flagged custom conversion

1. In Events Manager, open the Custom conversions tab and select each flagged conversion. Read its name, its rule and the event it is built on.
2. Decide whether the flag is right. If the name or the rule names a condition, treatment or medication, it is.
3. Build a replacement that counts the step rather than the condition: a confirmed booking or a completed purchase, on a page or event whose URL, parameters and name carry no condition. Meta's option is to "Use a new custom conversion and make sure that it does not include information that is not allowed under our terms."
4. For each running campaign on the flagged conversion, duplicate the campaign, select the unflagged conversion, then publish. This is Meta's own advice, and it happens at campaign level inside the same ad account.
5. If you believe the flag is wrong and the conversion doesn't include non-permitted information, request a review "via Ads Manager under the campaigns table, or in Events Manager under the custom conversions page."

A new name on the same rule is the same conversion

Renaming "Diabetes consult booked" to "Conversion A" clears nothing if its rule still matches a URL in a diabetes folder. Meta's test covers the criteria you establish as well as the names you choose, and a conversion defined by a condition page is based on that condition. Swapping the condition for a code or ID that maps back to it changes nothing either.

The clean version counts a step every patient takes, whatever they booked for. If your booking confirmation sits at a different condition-named URL for each service, change that on the site itself, so the condition never leaves in the first place. Where condition data hides on a clinic site and why renaming isn't a fix cover the rest.

Talk to Curve

A flagged custom conversion often points to condition data somewhere in what your site sends, and it's worth finding before the next one is flagged. Curve's team will review your conversions and site data with you, show what's likely triggering the flag, and rebuild your conversion tracking server-side so your campaigns keep optimizing on bookings that carry no condition. To get started, book a call with Curve.

Frequently asked questions

Sources

• Meta Business Help Center: Understand restrictions on certain custom conversions
• Meta Business Help Center: About prohibited information
• LiveRamp: Upcoming Meta Restrictions on Certain Custom Audiences and Custom Conversions (7/17/25)

Last verified September 29, 2026

Related pages

• Meta Flagged My Custom Audience or Lookalike: Next StepsWhy Meta flags custom and lookalike audiences that reference a health condition, what the flag stops, and how to fix the seed or request a review.
• Event Parameters Blocked in Meta: Unblock or Keep Blocking?What Meta's "Event parameters blocked" diagnostic means, how to review it, when to unblock or keep blocking, and why repeats lead to core setup.
• Meta Removed Potentially Prohibited Information: Next StepsWhat Meta's prohibited information notice means for a health business, where to find what was removed, how to fix it, and why you must never re-send it.
• Meta Blocked My Custom Events Until I Review ThemWhy Meta blocks every custom event once a dataset has data restrictions, which events to confirm, which to keep blocked, and why renaming is not a fix.
• Meta Conversions Stopped: Restriction or Broken Tracking?Meta conversions dropped. How to tell a data restriction from broken tracking or a page change, event by event, and which layer to fix first.
• Does Server-Side Tracking Get Around Health Restrictions?No. Meta restricts health data by data source, not by route, and forbids re-sending removed data. Here is what server-side tracking is really for.