How to Advertise GLP-1 on Meta in 2026 Without Restrictions

How to Advertise GLP-1 on Meta in 2026 Without Restrictions

Summary / TL;DR

GLP-1 brands face a harder version of Meta's health and wellness restriction than any other vertical. Your domain is not just flagged under one restricted category — it triggers two: Health & Wellness and Drugs & Pharmaceuticals. That dual classification compounds the restriction, and it means the standard playbook for supplement or skincare brands does not fully apply to you.

If you are a telehealth platform prescribing semaglutide, a med spa offering GLP-1 weight loss injections, a DTC brand selling GLP-1-adjacent supplements, or an online pharmacy dispensing compounded tirzepatide — your Meta pixel is either already restricted or operating on borrowed time.

This post is the step-by-step operator playbook for advertising GLP-1 products on Meta in 2026 without losing your pixel, your purchase events, or your ability to optimize for conversions.

Key Takeaways

  • GLP-1 brands trigger dual classification under Meta's Health & Wellness and Drugs & Pharmaceuticals categories. Each category applies its own layer of restrictions — and they stack.

  • FDA-approved branded GLP-1 products (Ozempic, Wegovy, Zepbound) require LegitScript Healthcare Merchant Certification and Meta's prior written authorization before any ad referencing the drug can run. Compounded GLP-1 formulations face near-total prohibition in most advertising contexts.

  • Ad creative approval and domain-level data restrictions are evaluated by entirely separate Meta systems. Your GLP-1 ads can be approved and delivering while your purchase events are simultaneously blocked in Events Manager.

  • In March 2026, the FDA issued warning letters to 30 telehealth companies for misleading compounded GLP-1 claims. In December 2025, 35 state attorneys general wrote to Meta demanding stricter enforcement against GLP-1 advertising. Enforcement pressure is rising from both directions — regulatory and platform.

  • The fix is architectural: server-side payload cleansing and neutral custom event architecture restore events for Level 1-2 restrictions on your existing domain. For Level 3 or disabled accounts, a clean intermediary domain is additionally required. If you are advertising prescription GLP-1s, LegitScript certification is a separate prerequisite for ad creative approval.


Before You Read the Playbook: Find Out How Meta Sees Your Domain

GLP-1 classification triggers are specific and often non-obvious. A URL path containing /semaglutide-weight-loss, a product name that reads "GLP-1 Metabolic Support," or even a blog post titled "How Tirzepatide Works for Weight Management" on your domain can trigger classification; even if your ads never mention the drug by name.

Run the free audit below. Paste your URL and see exactly how Meta's automated systems are categorizing your domain across four compliance pillars: Domain, Category, Product, and Text. You cannot fix what you cannot see. Start here.


Why GLP-1 Is the Hardest Vertical to Advertise on Meta

Every health and wellness brand faces Meta's domain classification system. GLP-1 brands face a version of it that is structurally more severe.

The dual classification problem

Most supplement brands get classified under a single category: Health & Wellness, either "Other," "Condition," or "Provider." That classification triggers data sharing restrictions on your conversion events.

GLP-1 brands frequently trigger two categories simultaneously:

Health & Wellness - Condition, because your product or service is associated with weight management, obesity, or metabolic conditions. And Drugs & Pharmaceuticals, because semaglutide, tirzepatide, liraglutide, and their compounded variants are prescription medications that Meta gates behind LegitScript certification and written authorization.

Meta Data Sharing Restricitons on GLP-1 brands

Each category applies its own set of restrictions. Health & Wellness restricts your event data. Drugs & Pharmaceuticals restricts your ability to run the ad at all. When both are active, you face data layer degradation and creative rejection simultaneously, a combination that makes diagnosis difficult because the symptoms look like two different, unrelated problems.

What makes GLP-1 signals different from general health signals

Meta's classifier does not just look for the word "GLP-1." It evaluates contextual patterns across your entire domain. Here is what we consistently see triggering classification in GLP-1 accounts:

Domain and URL signals:

  • URL paths containing drug names: /semaglutide, /tirzepatide, /ozempic-alternative, /glp1-weight-loss

  • URL paths containing condition terms: /obesity-treatment, /medical-weight-loss, /bmi-management

  • Blog content on your domain discussing GLP-1 mechanisms, dosing, or clinical outcomes — even if no ads point to those pages

  • The domain name itself: If your root domain carries health or drug semantics — getslim.com, glp1clinic.com, semaglutidedirect.com, leanerbody.co — the restricted signal is embedded in every URL you send to Meta. No amount of payload cleansing on that domain removes it, because the domain string itself appears in every event, every landing page URL, and every crawl. This is the one scenario where an intermediary domain is required regardless of restriction level.

Event payload signals:

  • Product names: "Semaglutide 2.5mg Injection Kit," "GLP-1 Metabolic Support Formula," "Compounded Tirzepatide 10mg"

  • Appointment types: "GLP-1 Consultation," "Weight Loss Intake," "Semaglutide Follow-up"

  • Content categories: "weight-loss-rx," "glp1-program," "medical-weight-management"

Signals most GLP-1 brands miss:

  • Shopify auto-generated URL slugs. When you create a product called "Semaglutide Injection Kit," Shopify generates /products/semaglutide-injection-kit as the permanent URL. Renaming the product later does not change the slug — Shopify creates a 301 redirect from the old URL, but the original path still exists and Meta's crawler can still find it. You have to manually edit the URL handle in Shopify admin for every affected product.

  • Collection and category URLs./collections/weight-loss, /collections/glp-1-supplements, /collections/medical-weight-management — these are separate classification signals from your product pages. If your collections carry health terms, your domain carries health signals even if every product page is clean.

  • Customer reviews and UGC on product pages. A customer writes "I lost 30 lbs in 8 weeks" or "this helped with my diabetes." That text is on your domain. Meta's crawler reads it. You did not write it, but it contributes to your classification. Review moderation is not optional for GLP-1 brands — it is a compliance function.

  • Intake forms and quizzes. "What is your current BMI?" "Do you have Type 2 diabetes?" "What is your weight loss goal?" These form labels are visible text on your landing page — and Meta crawls page content for classification. The form submission data itself (what the user types) can be cleansed server-side before reaching Meta. But the labels on the page contribute to the domain's overall health-signal footprint the same way any other text on your page does.

  • Re-crawl and reclassification. Meta does not scan your domain once. It re-crawls periodically. Even after implementing a fix, if your domain still carries health-adjacent content — blog posts, product descriptions, reviews, form fields — reclassification can happen on the next crawl. The fix is not a one-time event. It is an ongoing compliance posture.

Custom audience and conversion signals (2026 enforcement expansion):

  • Audience names: "GLP-1 Purchasers," "Semaglutide Interest Lookalike," "Weight Loss Drug Leads"

  • Custom conversion names: "GLP-1 Consultation Booked," "Tirzepatide Purchase Complete"

The 2026 enforcement wave specifically expanded automated scanning to audience names and custom conversion names. An audience called "Diabetes Interest – Lookalike" or a custom conversion called "GLP-1 Purchase" will get flagged. This catches brands who had compliant event signals but non-compliant labeling.


The Regulatory Environment You Are Advertising Into

Understanding Meta's policy is necessary but not sufficient. GLP-1 is the only vertical where platform enforcement, federal regulatory action, and state attorney general pressure are converging at the same time.

Meta's policy on GLP-1 advertising

FDA-approved branded GLP-1 products (Ozempic, Wegovy, Mounjaro, Zepbound) can be advertised under Meta's standard prescription drug DTC framework, but only in permitted jurisdictions, only with LegitScript Healthcare Merchant Certification, and only with Meta's prior written permission. Fair balance requirements apply: ads must include risk disclosure, cannot promise guaranteed weight loss outcomes, and must meet country-specific regulatory requirements.

Compounded GLP-1 medications face prohibition in most Meta advertising contexts. This reflects regulatory concerns about the compounded supply chain and the absence of FDA approval for compounded formulations. If your business model depends on advertising compounded semaglutide or tirzepatide directly, Meta's ad policy is a structural blocker, not a fixable restriction.

GLP-1-adjacent supplements - products marketed as "natural GLP-1 support" or "metabolic optimization" that are not prescription medications, can be advertised, but face blanket prohibition if they make weight loss efficacy claims. The creative must focus on the product without claiming clinical outcomes.

The enforcement pressure is increasing, not decreasing

December 2025: A bipartisan coalition of 35 state attorneys general sent a letter to Meta's chief legal officer demanding stricter enforcement against misleading GLP-1 advertising on Facebook and Instagram. The letter cited thousands of ads promoting non-FDA-approved compounded GLP-1 drugs and called on Meta to restrict prescription drug ads to FDA-approved products only, prohibit AI-generated weight loss drug ads, and require risk disclosure on all weight loss product advertising.

February 2026: The FDA announced it intends to restrict the active pharmaceutical ingredients used in unapproved compounded GLP-1 drugs that are being mass-marketed. This signals a tightening supply chain that will affect which products GLP-1 brands can even offer — before the advertising question arises.

March 2026: The FDA issued warning letters to 30 telehealth companies for misleading compounded GLP-1 claims — part of a broader enforcement push that has sent thousands of warnings since September 2025.

If you are a GLP-1 brand planning your Meta advertising architecture, plan for a stricter enforcement environment six months from now, not a looser one.


The 7-Step GLP-1 Compliance Playbook

Step 1: Determine your product type and authorization requirements

Not all GLP-1 businesses face the same ad policy requirements. Your first step is identifying which bucket you fall into:

If you prescribe or sell FDA-approved GLP-1 medications (semaglutide as Ozempic/Wegovy, tirzepatide as Mounjaro/Zepbound): You need LegitScript Healthcare Merchant Certification ($975 application + $2,150/year per website) and Meta's prior written authorization. Without both, any ad referencing these drugs by name is rejected. This is non-negotiable.

If you prescribe or sell compounded GLP-1 formulations: Your advertising options on Meta are severely limited. Compounded formulations cannot be advertised in most contexts. Your compliant path is advertising the consultation or service without naming the specific medication. "Medical weight loss consultation" — not "compounded semaglutide."

If you sell GLP-1-adjacent supplements (natural metabolic support, berberine, inositol, or similar): You do not need LegitScript or Meta written authorization, but you cannot make weight loss efficacy claims. Your domain still faces Health & Wellness classification based on product naming and landing page content.

Step 2: Audit your domain classification across both categories

Go to Events Manager → Data Sources → Select your Pixel → Settings → Manage Data Source Categories.

Check for two classification flags - not one:

  • Health & Wellness (and which sub-category: Other, Condition, or Provider)

  • Drugs & Pharmaceuticals

If both are present, your restrictions are stacking. Your events are subject to Health & Wellness data sharing rules and your ads are subject to Drugs & Pharmaceuticals creative restrictions. These operate independently.

If you want to see exactly what signals are triggering your classification - and which of the four compliance pillars (Domain, Category, Product, Text) is failing - run the audit:

Step 3: Cleanse your event payloads of all GLP-1 signals

This is the foundational fix. Every event your pixel or CAPI sends to Meta must be stripped of signals that imply a health condition or a prescription medication.

What to cleanse:

Signal type

Non-compliant example

Compliant replacement

Product name

"Semaglutide 2.5mg Starter Kit"

"Wellness Program – Starter"

Appointment type

"GLP-1 Weight Loss Consultation"

"New Patient Consultation"

Content category

"glp1-rx" or "weight-loss-medication"

"wellness" or "program"

URL path in payload

/products/semaglutide-injection

/products/item-2847 or stripped entirely

Content ID

"SKU-SEMA-25MG"

"SKU-WP-001"

Meta reads the full semantic content of every event payload. Renaming your Purchase event to "event_01" while leaving content_name: "Tirzepatide 10mg Injection" in the payload changes nothing. The event will be blocked.

This must happen server-side. Your server intercepts every event before it reaches Meta and replaces or removes the signals listed above. The browser pixel cannot do this - it sends data directly from the user's browser to Meta without an interception layer.

Step 4: Rename and register custom events with neutral labels

Standard event names like Purchase, Lead, and Schedule carry semantic weight that Meta's system recognizes. For GLP-1 accounts under Level 1-2 restrictions, custom events with coded names reduce the surface area for detection.

Requirements for custom events to work:

  1. The event name must be genuinely neutral - not "lead," "generate_lead," or any variant that describes data collection. Use coded labels: "conv_a," "signal_01," "event_rx1."

  2. The payload must be fully cleansed (Step 3).

  3. The event must be registered in Events Manager and mapped to a campaign objective before use.

  4. Custom events require a training period. Set them up while your standard events are still flowing so Meta's algorithm accumulates conversion data before you switch.

At Level 3, custom events alone are not viable. You need Step 5.

Step 5: Route ads through a clean intermediary domain (Level 3 and disabled accounts)

For most Level 1 and Level 2 restrictions, Steps 3 and 4 — payload cleansing and neutral custom events on your existing domain — are sufficient to restore your conversion events. Meta is filtering what you send, not blocking everything. Clean the signal, and the events flow.

If your domain is at Level 3 — where all event sharing is blocked regardless of payload content — or if your account has been disabled, same-domain cleansing structurally cannot work. Meta rejects every event from that domain. A clean intermediary domain is the only documented path to restoring purchase events at this level.

The domain-name exception: There is one scenario where an intermediary domain is required even at Level 1 or Level 2 — when your root domain name itself carries health or drug semantics. If your domain is getslim.com, glp1direct.com, semaglutideclinic.com, or anything where the URL string implies a health condition or a restricted product, that signal is baked into every event you send and every URL Meta crawls. Payload cleansing cannot strip your own domain name from your own URLs. In this case, routing through a clean intermediary domain is not an escalation — it is the starting point.

How it works for GLP-1 brands:

Your Meta ads point to a clean marketing domain — a separate root domain with no restriction history, no GLP-1 product names on its pages, no prescription language, and no connection to your flagged domain in Meta's pixel or CAPI history.

The user lands on this domain. A branded verification page or compliant landing page loads. Your server captures _fbp, _fbc, UTMs, and click IDs on this clean domain. The user is then passed to your real website. Their journey is unchanged.

When the user converts — purchases a product, books a consultation, submits a lead form — your server stitches the session data from the clean domain to the conversion on your real site and sends a single, cleansed event to Meta via CAPI.

What Meta sees: A conversion event from a clean, unclassified domain, with a neutral event name, carrying no GLP-1 product names, no drug references, and no condition-adjacent signals.

What actually happened: A real user clicked your ad, visited your store, and bought your product. The conversion signal is real. The data is compliant.

A subdomain of your existing domain will not work. Meta's restrictions apply at the root domain level. shop.yourbrand.com inherits the classification of yourbrand.com.

For a deeper walkthrough of the intermediary domain architecture, read: Purchase Events Blocked on Meta? Here's How to Fix It →

Step 6: Build compliant ad creative for GLP-1

Your data infrastructure can be perfect and your ads will still be rejected if your creative violates Meta's advertising policies. GLP-1 creative restrictions are more specific than general health and wellness rules.

What gets rejected:

  • Naming prescription GLP-1 drugs without LegitScript certification and Meta authorization

  • Before-and-after weight loss imagery (prohibited under Meta's body image policies)

  • Specific weight loss numbers ("Lose 30 lbs in 12 weeks")

  • Medical claims about drug efficacy ("Semaglutide reduces appetite by 40%")

  • AI-generated imagery depicting dramatic body transformations — under active enforcement following the AG coalition letter

  • Claims implying guaranteed access to compounded formulations

What works:

  • Lifestyle-led creative that implies transformation without showing it: "Ready to feel like yourself again?" paired with an image of someone active and confident — no body comparison

  • Service-led framing: "Physician-supervised weight management. Personalized plans. Virtual visits." — no drug names, no weight promises

  • Consultation-first CTAs: "Book a free consultation" or "See if you qualify" rather than "Buy semaglutide" or "Start your GLP-1 journey"

  • Testimonial-style creative focusing on the experience ("The process was easy, and the support team was incredible") — not on weight outcomes

For brands with LegitScript certification and Meta authorization, you can reference FDA-approved drug names — but fair balance requirements apply: risk disclosure, no guaranteed outcomes, adult targeting only.

Step 7: Audit and rename your custom audiences and custom conversions

This is the step most GLP-1 brands miss. The 2026 enforcement expansion scans audience names and custom conversion names for restricted signals. This is a separate classification vector from your domain or your event payloads.

Go to:

  • Audiences → Review every custom audience name

  • Events Manager → Custom Conversions → Review every custom conversion name

Rename anything containing:

  • Drug names (semaglutide, tirzepatide, Ozempic, Wegovy, Mounjaro, Zepbound)

  • Condition terms (weight loss, obesity, diabetes, metabolic syndrome, BMI)

  • Treatment references (GLP-1, injection, prescription, compounded)

Replace with neutral labels: "High Intent Audience Q2," "Conv Signal A," "Program Interest Segment."

A flagged audience or custom conversion does not just affect new campaigns — existing campaigns using flagged audiences may see reduced delivery and performance over time unless resolved.


What This Playbook Restores

Restriction Level

What the 7-step playbook restores

Level 1: Core Setup

Custom parameters and URL data pass through cleanly. Audiences rebuild with compliant signals. Advanced matching restored. Same-domain payload cleansing is sufficient.

Level 2: Events Blocked

Purchase, Lead, and Schedule events are restored through server-side payload cleansing and neutral custom events on your existing domain. Meta's algorithm regains conversion signal and can optimize for actual conversions. If same-domain cleansing does not restore events, escalate to a clean intermediary domain.

Level 3: Full Restriction

Requires the full architecture: clean intermediary domain with no restriction history, server-side stitching, payload cleansing, and neutral custom events. Same-domain cleansing cannot work here — Meta blocks all events from the flagged domain regardless of payload.

In the accounts we have worked with that implemented this architecture correctly, Event Match Quality recovered from approximately 5/10 to 8.5–9/10 after the correct fix was applied.


What Not to Do: GLP-1-Specific Mistakes

These are the most common mistakes we see from GLP-1 brands specifically — beyond the general myths we documented across 75+ accounts.

Do not advertise compounded GLP-1 by name. This is a policy violation, not a data restriction. No amount of server-side infrastructure fixes a creative that Meta's ad review system rejects. If your business dispenses compounded formulations, advertise the consultation or service — not the compound.

Do not assume LegitScript certification fixes your data restrictions. LegitScript lets you run ads that reference FDA-approved drugs. It does not affect your domain's Health & Wellness classification or your event data restrictions in Events Manager. These are separate systems. You need both the certification (for ad creative) and the infrastructure (for data compliance).

Do not leave GLP-1 blog content on your ad-facing domain unaddressed. Meta's crawler scans your entire domain — not just the pages your ads point to. A blog post titled "How Semaglutide Works for Weight Loss" on your domain contributes to classification even if no ad ever links to it. Either move educational content to a separate domain or rewrite it with neutral language.

Do not use "GLP-1" in your custom audience or custom conversion names. This is the 2026-specific enforcement gap that catches brands who had compliant signals but non-compliant labeling.

Do not rename a Shopify product and assume the URL changed. Shopify generates URL handles from the original product name. If you created "Semaglutide Injection Kit," the URL /products/semaglutide-injection-kit persists even after you rename the product to "Wellness Program Starter." Shopify creates a redirect from the old URL — it does not delete it. You must manually edit the URL handle in Shopify admin under each product's SEO settings. Check every product, every collection.

Do not ignore customer reviews on your product pages. A review that says "I lost 30 lbs in 8 weeks" or "this finally helped with my insulin resistance" is health-signal text on your domain. You did not write it, but Meta's crawler reads it. For GLP-1 brands, review moderation is not a nice-to-have — it is a compliance function. Filter or remove reviews that reference specific conditions, weight outcomes, or drug names.

Do not overlook health-related form labels on your ad-facing landing page. Intake forms asking "What is your BMI?" or "Do you have Type 2 diabetes?" — the submitted data can be cleansed server-side before it reaches Meta. That part is handled. But the form labels themselves are visible text on your page, and Meta's crawler reads page content when classifying your domain. If your landing page is covered in health-condition language through form labels, that text contributes to the same classification signal as any other health-adjacent copy on the page. Where possible, move detailed health intake to a step after the user has left the ad-facing surface — or use neutral form labels ("Tell us about your goals" rather than "Describe your weight loss history").


Ready to Fix Your GLP-1 Tracking on Meta?

If your GLP-1 brand is restricted — or if you want to prevent restriction before it hits — the fix is architectural. For Level 1-2, that means server-side payload cleansing, neutral event architecture, and compliant creative on your existing domain. For Level 3 or disabled accounts, add a clean intermediary domain with session stitching. If you advertise prescription GLP-1s, LegitScript certification is a separate requirement for ad creative.

We build this end to end for GLP-1 brands: telehealth platforms, med spas, DTC supplement brands, and online pharmacies.

Strugling with Meta Category Restriciton?
Get unrestricted with server-side infrastructure, Conversion API delivery, and restricted-category best practices.

Frequently Asked Questions

Do I need LegitScript certification to advertise GLP-1 on Meta?

If your ads reference FDA-approved GLP-1 medications by name — semaglutide, Ozempic, Wegovy, tirzepatide, Mounjaro, Zepbound — yes. LegitScript Healthcare Merchant Certification and Meta's prior written authorization are both required. The current fee structure is $975 application plus $2,150 annually per website. If your ads do not name prescription drugs and instead promote consultations or wellness services, LegitScript is not required for the ad creative — but your domain may still face Health & Wellness classification, which is a separate issue requiring infrastructure changes.

Can I advertise compounded semaglutide or tirzepatide on Meta?

In most contexts, no. Compounded GLP-1 formulations are not FDA-approved, and Meta's Drugs & Pharmaceuticals policy prohibits advertising of non-approved prescription medications in most advertising contexts. The compliant path is advertising the service — "physician-supervised weight management consultation" — without naming the specific compounded medication. Your landing page and event payloads must also avoid referencing compounded drugs, as these trigger both ad rejection and domain classification.

My GLP-1 ads are approved but my purchase events are missing. What is happening?

Your ads are evaluated by Meta's ad review system against advertising policies. Your domain is classified separately by Meta's automated crawler based on your landing page content, product descriptions, and event payloads. These two systems do not communicate. Your ads can be approved and delivering while your domain is simultaneously classified under Health & Wellness and your purchase events are being silently suppressed. Check Events Manager → Data Sources → Settings → Manage Data Source Categories for classification status.

Will renaming my events fix the restriction on my GLP-1 account?

No. Meta evaluates the full content of the event payload — product names, appointment categories, content IDs, URL paths — not just the event name. An event named "signal_01" that carries content_name: "semaglutide injection kit" in the payload will be blocked. The fix is payload cleansing: removing or neutralizing every sensitive signal in the event data before it reaches Meta, not just changing what the event is called.

Does switching to CAPI fix GLP-1 domain restrictions?

No. Meta's data sharing restrictions apply at the domain level, not at the delivery method level. Events sent via the Conversions API from a restricted domain are filtered and blocked the same way browser pixel events are. CAPI is the correct infrastructure for a compliant setup, but it must be paired with payload cleansing — stripping sensitive product names, condition terms, and health signals from every event before it reaches Meta. For Level 1 and most Level 2 restrictions, same-domain payload cleansing via CAPI is sufficient to restore your conversion events without changing your domain. A clean intermediary domain is only required when the domain itself is fully blocked at Level 3 or disabled — where Meta rejects all events from that domain regardless of what the payload contains. CAPI alone, without payload cleansing, on a restricted domain is not a fix.

How is the GLP-1 restriction different from general health and wellness restrictions?

GLP-1 brands frequently trigger two restricted categories simultaneously: Health & Wellness (based on domain content implying weight management or metabolic conditions) and Drugs & Pharmaceuticals (based on references to prescription medications). These restrictions stack. Health & Wellness blocks your event data. Drugs & Pharmaceuticals blocks your ad creative. A supplement brand dealing with Health & Wellness only has one layer to fix. A GLP-1 brand has two — and each requires a different solution.

What happens if I do not have LegitScript certification and still run GLP-1 ads?

If your ad copy, images, or landing page reference FDA-approved prescription GLP-1 drugs by name, the ad is rejected during review. If you use indirect language and avoid drug names, the ad may be approved — but your domain can still be classified under Health & Wellness based on your landing page and product descriptions, resulting in event data suppression. Running ads without required certifications also creates regulatory exposure, particularly as FTC and state AG enforcement activity in the GLP-1 space intensifies through 2026.

Is it possible to remove the Health & Wellness category from my GLP-1 domain?

Not through Meta's appeal process in most cases. The classification reflects reality — your domain sells or promotes products associated with medical conditions. Across the 75+ accounts we have reviewed, no genuine health and wellness brand successfully reversed its classification through appeal. The practical path is routing your tracking data through a clean intermediary domain that Meta has not classified, restoring your conversion events without relying on a reclassification that is unlikely to happen.

How long does it take to restore purchase events for a GLP-1 brand after implementing the fix?

Once the clean domain, landing page, server-side infrastructure, and payload cleansing are live, events begin flowing to Meta immediately. Meta's algorithm typically needs 7 to 14 days of clean conversion data before campaign performance recovers to pre-restriction levels. The learning phase requires sufficient signal volume to re-optimize delivery. The timeline varies depending on your campaign spend and conversion volume, but GLP-1 brands with consistent ad spend typically see stabilization within 2 to 3 weeks.

Are GLP-1 supplements (non-prescription) also affected by these restrictions?

Yes. Even non-prescription GLP-1-adjacent supplements — berberine, inositol, or products marketed as "natural GLP-1 support" — can trigger Health & Wellness classification if their product names, landing pages, or event payloads imply a health condition. "Blood Sugar Support Formula" and "Metabolic Optimization Supplement" both carry signals that Meta's classifier reads as health-adjacent. The ad policy rules for supplements are different from prescription drugs (no LegitScript needed, no written authorization), but the domain classification and data restriction mechanics are identical.

Frequently Asked Questions

Do I need LegitScript certification to advertise GLP-1 on Meta?

If your ads reference FDA-approved GLP-1 medications by name - semaglutide, Ozempic, Wegovy, tirzepatide, Mounjaro, Zepbound - yes. LegitScript Healthcare Merchant Certification and Meta's prior written authorization are both required.

The current fee structure is $975 application plus $2,150 annually per website. If your ads do not name prescription drugs and instead promote consultations or wellness services, LegitScript is not required for the ad creative, but your domain may still face Health & Wellness classification, which is a separate issue requiring infrastructure changes.

Can I advertise compounded semaglutide or tirzepatide on Meta?

In most contexts, no. Compounded GLP-1 formulations are not FDA-approved, and Meta's Drugs & Pharmaceuticals policy prohibits advertising of non-approved prescription medications in most advertising contexts. The compliant path is advertising the service - 'physician-supervised weight management consultation' - without naming the specific compounded medication. Your landing page and event payloads must also avoid referencing compounded drugs, as these trigger both ad rejection and domain classification.


My GLP-1 ads are approved but my purchase events are missing. What is happening?

Your ads are evaluated by Meta's ad review system against advertising policies. Your domain is classified separately by Meta's automated crawler based on your landing page content, product descriptions, and event payloads. These two systems do not communicate. Your ads can be approved and delivering while your domain is simultaneously classified under Health & Wellness and your purchase events are being silently suppressed. Check Events Manager → Data Sources → Settings → Manage Data Source Categories for classification status.


Will renaming my events fix the restriction on my GLP-1 account?

No. Meta evaluates the full content of the event payload - product names, appointment categories, content IDs, URL paths - not just the event name. An event named 'signal_01' that carries in the payload will be blocked. The fix is payload cleansing: removing or neutralizing every sensitive signal in the event data before it reaches Meta, not just changing what the event is called.

Does switching to CAPI fix GLP-1 domain restrictions?

No. Meta's data sharing restrictions apply at the domain level, not at the delivery method level. Events sent via the Conversions API from a restricted domain are filtered and blocked the same way browser pixel events are. CAPI is the correct infrastructure for a compliant setup, but it must be paired with payload cleansing - stripping sensitive product names, condition terms, and health signals from every event before it reaches Meta. For Level 1 and most Level 2 restrictions, same-domain payload cleansing via CAPI is sufficient to restore your conversion events without changing your domain.

A clean intermediary domain is only required when the domain itself is fully blocked at Level 3 or disabled - where Meta rejects all events from that domain regardless of what the payload contains. CAPI alone, without payload cleansing, on a restricted domain is not a fix.

How is the GLP-1 restriction different from general health and wellness restrictions?

GLP-1 brands frequently trigger two restricted categories simultaneously: Health & Wellness (based on domain content implying weight management or metabolic conditions) and Drugs & Pharmaceuticals (based on references to prescription medications). These restrictions stack. Health & Wellness blocks your event data. Drugs & Pharmaceuticals blocks your ad creative. A supplement brand dealing with Health & Wellness only has one layer to fix. A GLP-1 brand has two — and each requires a different solution.


What happens if I do not have LegitScript certification and still run GLP-1 ads?

If your ad copy, images, or landing page reference FDA-approved prescription GLP-1 drugs by name, the ad is rejected during review. If you use indirect language and avoid drug names, the ad may be approved — but your domain can still be classified under Health & Wellness based on your landing page and product descriptions, resulting in event data suppression. Running ads without required certifications also creates regulatory exposure, particularly as FTC and state AG enforcement activity in the GLP-1 space intensifies through 2026.


Is it possible to remove the Health & Wellness category from my GLP-1 domain?

Not through Meta's appeal process in most cases. The classification reflects reality - your domain sells or promotes products associated with medical conditions. Across the 75+ accounts we have reviewed, no genuine health and wellness brand successfully reversed its classification through appeal. The practical path is routing your tracking data through a clean intermediary domain that Meta has not classified, restoring your conversion events without relying on a reclassification that is unlikely to happen.


How long does it take to restore purchase events for a GLP-1 brand after implementing the fix?

Once the clean domain, landing page, server-side infrastructure, and payload cleansing are live, events begin flowing to Meta immediately. Meta's algorithm typically needs 7 to 14 days of clean conversion data before campaign performance recovers to pre-restriction levels. The learning phase requires sufficient signal volume to re-optimize delivery. The timeline varies depending on your campaign spend and conversion volume, but GLP-1 brands with consistent ad spend typically see stabilization within 2 to 3 weeks.


Are GLP-1 supplements (non-prescription) also affected by these restrictions?

Yes. Even non-prescription GLP-1-adjacent supplements - berberine, inositol, or products marketed as 'natural GLP-1 support' - can trigger Health & Wellness classification if their product names, landing pages, or event payloads imply a health condition. "Blood Sugar Support Formula" and 'Metabolic Optimization Supplement' both carry signals that Meta's classifier reads as health-adjacent. The ad policy rules for supplements are different from prescription drugs (no LegitScript needed, no written authorization), but the domain classification and data restriction mechanics are identical.

Get the Next Playbook in Your Inbox

One email. No noise. Only real-world growth systems, when we publish.

Zappush

We help modern digital brands build signal-first marketing systems by activating first-party data, server-side tagging, and automation to scale across internet platforms.