Unrestrict your
Health & WellnessSupplementsWeight LossGLP-1Sexual WellnessMaternity CareFemTechCBDHealth & Wellness
brand.

Meta reviews ads and data separately. Ad review checks what an ad says. Data source categories are about your website: Meta assigns a category “based on the topics related to the data source and the products and/or services provided”, and some categories restrict which events you can share. So an ad can be approved and running while the Purchase events that train it are restricted.

Events Manager shows “Data sharing restrictions applied” on your dataset. Purchase, AddToCart or Lead carry a red warning that the event is blocked because of how your data sources are categorised. Orders in your store outnumber the purchases Meta reports. And Meta may email you that additional data sharing restrictions start soon.

Meta's definition is a website or app that “is associated with medical conditions or specific health statuses, provider/patient relationships, services for accessing personal health information, or health-related products and services”. Its own examples are a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace or condition-specific support group.

Yes. Meta's definition covers “health-related products and services” and anything associated with “specific health statuses”, not only medicine. Maternity and nursing bras, pelvic floor trainers or hair regrowth serums say something about the buyer's health or life stage, so their product names and URLs can lead Meta to categorise the whole website.

Meta can apply data-sharing restrictions to websites and apps it classifies in restricted categories, including Health & Wellness. The classification is influenced by the products or services you offer and by the health-related signals on your site and in your event data. The restriction affects what data Meta can receive and use for advertising — it does not mean your ads are rejected.

Health and wellness activity can reveal sensitive information about a person's health or medical interests. A purchase of a weight-loss product, for example, can say something about someone's condition or treatment. Meta therefore limits the health-related data businesses can share through its Business Tools. This is Meta's own data-sharing policy rather than a legal determination that your data is protected health information.

It means Meta has classified your data source in a restricted category and is limiting what information it can receive through Meta Business Tools. Depending on the restriction, Meta may limit custom parameters and URL data (core setup), restrict certain mid- and lower-funnel events such as Purchase and Lead (restrictions on certain standard events), or fully restrict event sharing in specific regions or worldwide (full restrictions).

Go to Events Manager → select your Pixel or Dataset → Settings → Manage Data Source Categories. Meta shows whether your data source has been assigned a restricted category and which restrictions apply. You can also run the free Health & Wellness Restriction Audit on this page to see which signals on your site are contributing to the classification.

Meta describes three types of data-sharing restriction. Core setup (Level 1) limits custom parameters and parts of URLs following the domain. Restrictions on certain standard events (Level 2) limit specific mid- and lower-funnel events. Full restrictions (Level 3) can prevent all event sharing in specific regions or worldwide, and where they apply, Meta Business Tools cannot be used for ads purposes.

Yes — supplements fall into Meta's Health & Wellness category. That does not make the ads themselves prohibited. The distinction is between ad approval and data sharing: your ads can keep running while Meta limits the conversion and event data your website can send. Product names, health claims, website content, and event data all contribute to how Meta classifies a business.

Yes. GLP-1 medications, medical weight-loss services, and weight-loss products all involve health-related information, so your landing page, product descriptions, event data, and ad creative are all in scope. Weight-loss advertising also carries separate creative rules, including restrictions on before-and-after body-change comparisons.

Both are, under different rules. Meta prohibits ads promoting the sale of illegal, recreational, or certain controlled drugs, which covers THC products. CBD advertising faces additional restrictions depending on the product and the claims made about it, and health or disease claims create further compliance problems. The two are not interchangeable categories.

Yes. Meta restricts certain products and services involving sexual health and reproductive disorders, including some non-surgical genital enhancement products. ED treatments, testosterone products, and sexual-wellness supplements can face both advertising and data-sharing restrictions, depending on what is promoted and how it is presented.

Some are. Meta restricts certain cosmetic procedures and products, particularly those intended to alter or restore the structure or function of the body. Injectables, plastic surgery, body-contouring services, and some skin treatments receive additional scrutiny. Before-and-after transformation imagery adds a second layer of advertising-policy risk.

It depends on what you promote and how you describe it. General fitness services can run without restriction, but weight-loss claims, body-transformation messaging, before-and-after imagery, or claims about treating a health condition all create exposure. The difference usually lies in the specific claims and signals on your site and in your ads.

Prohibited content cannot be advertised on Meta at all. Restricted content can be advertised, but additional rules or limitations apply. For Health & Wellness data-sharing restrictions the distinction matters: your ads can keep running while Meta limits the website data available for tracking, reporting, audience building, and campaign optimization.

No. Meta's classifier is inferential, not keyword-based. Brands selling ergonomic pillows, fitness apparel, breast pumps for lactating mothers, immigration-law services flagged under "nationality," and supplement brands without overt health claims have all been classified. If buying your product implies the buyer has a health condition, life situation, or protected attribute, you are at risk regardless of whether you use clinical language.

Yes. Meta's advertising policies restrict before-and-after body-change comparisons in a weight-loss context, particularly where the content could make people feel negatively about their appearance. If your creative relies on transformation photos, review the image and the copy around it — the restriction is not limited to the words in the ad.

Focus on the product or service rather than making health claims about the viewer. Avoid language implying you know someone's condition, symptoms, or body concerns, and take particular care with before-and-after transformations. The aim is to communicate the benefit without making the person feel identified by a sensitive attribute.

The personal-attributes policy filters anything that could make a viewer feel bad about their body, age, weight, skin, or appearance. Before-and-after framing is the canonical example.

No. Cosmetic surgery, injectables, body contouring, skin whitening, and laser treatments cannot use before-and-after framing. Even non-clinical "transformation" results trigger the same filter.

Not as before/after framing. You can use customer testimonials in writing or video that describe feelings ("more energy", "less bloated") without showing body changes.

Yes. Any body-change comparison, including weight, fitness, posture, or skin appearance, falls under personal-attributes and is rejected.

Lifestyle photography that does not compare two states is allowed. A single image of a person feeling good in their body, doing an activity, is fine. The comparison is what triggers the policy.

Google and TikTok enforce similar but not identical policies. TikTok's weight-loss policy is stricter on transformation framing. Google flags health/medical before-and-after with platform-specific exemptions for licensed clinical advertisers.

The personal-attributes filter catches creative that implies the viewer has a flaw (weight, skin, age, hair) and that the product fixes it. Reframe the hook around what the customer wants, not what they want to fix.

Customer voiceover testimonials, ingredient stories, lifestyle imagery without comparison, ASMR-style product shots, and benefit copy that does not reference outcomes. Most compliant DTC brands moved to UGC-style talking heads.

Purchase is a lower-funnel event, so it is restricted when Meta applies restrictions on certain standard events (Level 2). That is why Purchase is usually the first event a business notices missing. Your website still records the sale and your ads can still be approved and delivered — the restriction affects what Meta can receive and use from the event.

Yes, at Level 2. Purchase is a lower-funnel event, so it falls inside what Meta restricts when it applies restrictions on certain standard events. The exact effect depends on how Meta has classified your data source and which restrictions apply in your region. An event can fire correctly in your own systems and still be unavailable to Meta for advertising.

Appointment-related events sit in the mid- and lower-funnel, so they are restricted when Meta limits standard events for a health-related data source. The appointment still books successfully on your site; Meta simply does not receive or use the corresponding conversion signal.

If your data source is under standard-event restrictions, Meta does not receive or use Purchase events even though Shopify records every sale. Your store and Meta therefore report different numbers: the sale happened, but the conversion signal was restricted before Meta could use it for reporting or optimization.

Shopify stores are subject to the same rules as any other website. Meta evaluates signals from your domain, your product and collection content, your URLs, and the event data your tracking setup sends. A store selling health-related products can therefore be restricted even when the Shopify integration itself is working correctly.

It depends on the restriction. Core setup mainly limits custom parameters and URL information, so custom events still flow. Restrictions on certain standard events target specific mid- and lower-funnel events. Full restrictions prevent all event sharing in the affected regions. Custom events are not a guaranteed workaround.

Partly. Core setup removes the URL and custom-parameter information many audiences rely on. Restrictions on standard events reduce the conversion data available for audience building, so your highest-intent buyers become harder to identify. Under full restrictions, event-based audiences stop refreshing in the affected regions.

Meta applies data-sharing restrictions through its systems rather than the process that approves individual ads, so an ad can be approved while the underlying data source is restricted. Most businesses find out only after checking Events Manager and noticing missing events or reduced conversion data.

It depends on the restriction level. Under core setup, events keep flowing while Meta strips custom parameters and URL information. Under restrictions on certain standard events, upper-funnel events such as PageView and ViewContent generally keep working while mid- and lower-funnel events such as Purchase and Lead are restricted. Under full restrictions, all event sharing is restricted in the affected regions.

When Meta loses access to conversion signals, its ability to optimize toward buyers weakens. Your ads keep running and your business keeps making sales, but Meta has less conversion data to learn from, which can push acquisition costs up. A restriction is not the only possible cause of a rising CPA, so confirm your status in Events Manager before assuming it is.

Pixel is a browser-side script that sends events from the user's browser. CAPI (Conversions API) is a server-side endpoint that sends events from your server. They are different delivery methods for the same Meta event system.

Where Meta permits the event and the underlying data, Zappush can map outcomes such as profit value, new-customer purchases, and AOV tiers into a server-side event strategy. We confirm the permitted fields and optimization options during the audit.

CAPI is Meta's server-to-server event endpoint. You send events from your backend with hashed user data and event metadata. Meta deduplicates against pixel events using event_id. It bypasses ad blockers and iOS ITP, not domain restrictions.

Not always. We first audit the existing Pixel or dataset, domain classification, event status, and permitted data. A new Pixel does not remove a policy restriction by itself, so we only recommend one when the implementation and account history justify it.

EMQ is Meta's diagnostic for how effectively permitted customer information matches events to Meta accounts. It can fall when identifiers are missing, malformed, duplicated, or restricted. Improvement depends on consent, implementation quality, event volume, and the fields Meta permits you to send.

We remove prohibited health context from permitted event payloads, apply consent rules, and hash allowed identifiers in Meta's required format before delivery. Hashing is a security measure, not permission to send sensitive health information.

Yes. You can keep running catalog ads with Zappush in place.

No. Your existing campaigns keep running while we set everything up.

No. Removing the health context applies to what Meta receives. Your Google, TikTok and other tracking is not affected.

We haven't seen a Zappush setup restricted again so far. Zappush passes no health data or health context to Meta, so there is nothing for a health category to act on. If Meta changes its policy, we update the setup to comply with the new policy.

Yes. Meta's own guidance for restricted categories is to keep “ensuring that you are not sharing potentially prohibited information”, and it reminds businesses that “you are ultimately responsible for your integration, your use of the Meta Business Tools, the data you share with Meta”. Removing health details from every event is in line with that. Your ads, creative and landing pages still need to follow Meta's advertising standards.

Shopify, WooCommerce, Wix, GoHighLevel and custom websites. Nothing on your website changes: no new pages, copy or images.

Health and wellness plans start at $99 a month on Starter, for up to 50K events a month. Plans scale with your monthly event volume, and the pricing page lists every tier.

Start by identifying what Meta is restricting and why. Audit your website for sensitive health claims, then review the data your Pixel and Conversions API send. Remove unnecessary health-related information from your event payloads and make sure your tracking follows Meta's Business Tools requirements. Renaming an event or changing a few words will not remove the classification. Zappush does this server-side in three steps: we scrub the URLs, clean the payload ("Weight Loss Gummies" becomes "product-1"), and remove the health context of the data source. Send the data via your clean and compliant domain, so Meta sees the buyer and the sale, not a condition. Nothing changes on your website.

No. The Conversions API is another way of sending data to Meta; it does not override a restriction applied to the underlying data source. If Meta restricts an event or a category, sending the same sensitive information through CAPI does not exempt it. CAPI is how a cleaned event reaches Meta, not a way around a restriction.

No. Renaming an event does not change the data being sent. Meta's restrictions apply to the data source and to the information in the event payload, not to the event's name. A neutral name carrying the same sensitive information is not a solution.

Separate ad compliance from data-sharing compliance. Your creative and landing page need to follow Meta's advertising policies, while your tracking needs to avoid sending restricted or unnecessary health information. Keep claims conservative, avoid prohibited transformation imagery, and audit your Pixel and CAPI payloads before they go out.

Usually not, and moving to a new domain to get around a restriction is not a durable compliance strategy. First work out whether the restriction can be addressed through a compliant data-sharing setup, or through a review if the classification is wrong. If you genuinely operate a restricted business, the same content on another domain does not change the underlying policy position.

Not on its own. A subdomain that sends the same health details is classified the same way. What matters is the data: Zappush cleans it server-side in three steps, scrubbing the URLs, cleaning the payload and removing the health context of the data source.

Server-side tagging gives you control over the payload before it reaches Meta. You can inspect it, remove unnecessary sensitive information, and send only what the measurement use case requires. It improves data governance, but it does not automatically remove a Meta restriction or make prohibited data acceptable.

It helps you build better data-handling practices, but it does not remove a Meta restriction. HIPAA and Meta's Business Tools policies are separate requirements, so you need to satisfy both where they apply. For healthcare organizations, Zappush signs Business Associate Agreements (BAAs). Zappush is HIPAA compliant, with our compliance program monitored through Vanta.

Yes, through Events Manager, if you believe the classification is wrong. An appeal makes most sense when it is genuinely inaccurate — an unrelated business placed in a restricted category, for example. If your business does operate in Health & Wellness, changing the underlying data practices is usually more productive than relying on an appeal alone.

Yes, though your options depend on the restriction. You may need to optimize toward an eligible upper-funnel event, use other compliant measurement signals, or redesign your tracking so it is not sending unnecessary sensitive data. Renaming events, switching Pixels, or moving everything to CAPI will not restore a restricted Purchase event.

Confirm the restriction in Events Manager first, and note which regions and events are affected. Then audit your website, Pixel, CAPI implementation, URLs, and event payloads for unnecessary health-related data. At Level 2, expect to change your optimization strategy while you correct the data flow. At Level 3, plan around Meta not receiving website events at all in the affected regions, and consider whether an appeal or a broader tracking redesign is appropriate.

Zappush can support multiple authorized datasets or Pixels when the business has a legitimate operational need. We review ownership, consent and destination requirements before we set it up.

Zappush cleans each event server-side before delivery, in three steps. We scrub the URLs: instead of yourbrand.com/products/weight-loss-gummies, Meta receives yourbrand.com. We clean the payload: instead of "Weight Loss Gummies", the event says "product-1". And we remove the health context of the data source. Send the data via your clean and compliant domain, so Meta sees the buyer and the sale, not a condition. Meta still receives the purchase and its value. Cleaning never fabricates an outcome or changes what the customer did.

Yes. Everything happens server-side, so you change nothing on your website: no new copy, no new images, no new landing pages, no renamed products. Your customers click your ad and land on your website exactly as before. Your ads and landing pages still need to follow Meta's advertising policies, which is a separate review from data sharing.

Most setups go live in under 24 hours. Setups that need custom work take longer, and we confirm that timeline on the call before we start.

Eligible implementations include a 30-day money-back guarantee subject to the conditions in the service agreement. We document the agreed scope, verify delivery, and investigate implementation failures during that window. Meta's independent enforcement decisions cannot be guaranteed.

Signal diagnostics may improve after clean, permitted events begin flowing, but there is no universal recovery window. Timing varies with event volume, account history, spend, consent rates, implementation quality, and Meta's learning systems.

We can audit an already-restricted setup, but the recommendation depends on the restriction, account history, destination, consent state, and permitted event data. We do not promise a fixed recovery period or a specific enforcement outcome.