GLP-1 Pricing Pages: What Ad Review Looks For

Ad reviewers treat your GLP-1 pricing page as part of the ad, so it is checked for the same things the creative is checked for: branded prescription drug names, unsupported outcome claims, before and after imagery, missing price and subscription disclosure, and misleading framing of compounded products. Curve is the HIPAA-compliant tracking layer for the other half of the problem, which is that a pricing page is usually the most sensitive tracking surface a GLP-1 clinic operates. Meta requires prior authorization before any prescription drug advertising runs at all. Curve includes a signed Business Associate Agreement on every plan.

Most GLP-1 rejections we see traced back to a page nobody thought was in scope. The ad copy was carefully written, the creative was cleared, and then the landing page said something the ad was never allowed to say. Reviewers follow the link. Policy applies to the destination.

The pricing page is in scope, and it is the page reviewers read most closely

Both major platforms evaluate the full ad experience: the creative, the copy, the destination URL, and what that destination actually says. For a GLP-1 clinic the pricing page is where the most policy-relevant claims live, because it is the page that has to explain what the patient gets and what it costs. That forces the page to name things.

It is also the page most likely to be edited without review. Marketing updates a price, adds a plan tier, or drops in a testimonial, and the page drifts out of the state that was approved. Ads that ran fine for months get rejected after a copy change nobody flagged, and the account-level consequences of repeated rejections are worse than the individual disapproval.

Prescription drug advertising authorization comes first

Before any of the page-level detail matters, check whether you are permitted to advertise at all. Meta requires prior written authorization for prescription drug advertising, and eligibility is limited to pharmaceutical manufacturers, online pharmacies, and telehealth providers. If you are not in one of those categories, the pricing page cannot be fixed into compliance because the underlying advertising permission is missing.

Meta also rejects branded pharmaceutical weight-loss terms outright, and rejects most before and after weight-loss imagery. Both restrictions apply to the landing page, not only the ad. A pricing page that lists plans by brand name, or that carries a transformation gallery above the pricing table, is carrying two of the most reliable rejection triggers in this category. We track the current state of platform policy in our GLP-1 advertising policy update for Google and Meta.

What reviewers actually look for on the page

Branded drug names used as product names

Naming a plan after a branded medication is the single most common failure. It converts a clinical service into a drug advertisement, and it triggers prescription drug policy on a page that was probably never authorized for it. Describe the program by what the clinic provides: clinical evaluation, ongoing provider oversight, medication when clinically appropriate. The medication decision belongs to a prescriber after an evaluation, and the page should read that way because that is also what is true.

Outcome claims stated as expectations

Weight-loss figures, timelines, and guarantees are read as claims about what the product does. That is true whether the number appears in a headline, a testimonial, or a small-print comparison. Statements framed as typical results attract the most scrutiny, and a disclaimer under them does not neutralize the claim above them. If the page promises a result, expect the review to treat it as a promise.

Before and after imagery and body-focused visuals

Transformation imagery is restricted on Meta and is a persistent rejection cause across the category. Close crops of bodies, scales, and measuring tapes fall into the same family of personal-attribute and body-image concerns even when no explicit claim is made. Pricing pages accumulate this imagery because it converts, which is exactly why it gets reviewed.

Compounded product framing

Compounded GLP-1 products are not FDA-approved drugs, and pages that blur that line draw regulatory as well as platform attention. The FDA sent 30 warning letters to telehealth companies over compounded GLP-1 claims on 3 March 2026, and 25 more the week of 15 June 2026. Presenting a compounded preparation as equivalent to, or a generic version of, an approved product is the specific framing that draws letters. Our deeper treatment of this is in compounding pharmacy GLP-1 advertising under FDA and FTC restrictions.

Price and subscription disclosure

This is where consumer protection rules bite rather than health policy. A pricing page has to make clear what recurs, how often, what happens after any introductory period, what is and is not included, and how to cancel. Common failures: a large introductory price with the ongoing price in small type, medication cost excluded from the headline figure without saying so, and a cancellation path that is harder to find than the signup path. Reviewers and regulators both read the page the way a first-time visitor would, not the way someone who already knows the offer does.

Consultation framing and eligibility language

Pages that imply anyone who pays will receive medication create a second problem: they suggest the clinical evaluation is a formality. Say plainly that eligibility is determined by a licensed provider and that not everyone qualifies. It is more accurate, it survives review better, and it reduces refund pressure downstream.

The half of the pricing page nobody reviews

Everything above is about what the page says. The other half is what the page sends, and it is the part that creates legal exposure rather than a rejected ad.

A GLP-1 pricing page is a health-context page by definition. Anyone loading it has demonstrated interest in weight-loss treatment, and anyone selecting a plan on it has done something considerably more specific. If a client-side pixel is running on that page, several things typically leave the browser without anyone deciding they should:

• The page URL and title, which usually name the medication category or the program.
• Plan selection events, which say which program a specific person chose.
• Form field values, when a checkout or qualification form sits on the same page.
• Referrer data carrying the campaign or ad name, which frequently encodes the service line.
• Persistent browser identifiers, which let the receiving platform tie all of that to a known person.

That combination, an identifiable person plus evidence of interest in a specific treatment, is health information. It is the pattern behind the healthcare pixel litigation that has cumulatively crossed $100M in settlements. Neither Meta nor Google signs a BAA for their advertising products, so there is no contractual structure that makes that transfer acceptable after the fact.

Worth stating plainly: passing ad review and being compliant are different tests. A page can be approved by every reviewer and still be leaking protected health information on every load.

How Curve handles pricing page tracking

Curve is HIPAA-compliant ad tracking, attribution, and analytics for healthcare. The tracking script installs in place of the Meta Pixel or a raw Google tag, and events go to Curve's US-hosted infrastructure instead of directly to ad platforms. That is the structural change: there is now a point where decisions can be made before anything leaves.

On a pricing page specifically, four mechanisms matter.

Per-destination field mapping. Only fields you explicitly map are forwarded to a given destination. The default is that nothing goes. Page URL, page title, and plan identifiers stay behind unless you deliberately map them, which on a pricing page you generally should not.

Neutral event aliases. The ad platform sees a neutral event name rather than one that names the program or the medication. Internally the event keeps its descriptive name so your own reporting still tells you which plan converted. This matters more on pricing pages than anywhere else, because plan-level event names are the most disclosive thing a clinic routinely sends.

Identifier hashing. Contact identifiers are SHA-256 hashed to each platform's conversion API requirements before they are forwarded, so match quality survives without raw identifiers traveling.

PHI-pattern detection. Curve inspects payloads for PHI-shaped values such as SSNs, MRN-style identifiers, dates, and long numeric sequences, and flags them. It is a monitoring layer rather than the protection itself. The protection is the field mapping. Detection is how you find out that a checkout form started sending a field it did not send last month.

Curve forwards clean conversions server-side to Meta CAPI, Google Ads Enhanced Conversions, TikTok Events API, Microsoft, LinkedIn, and others, and includes a signed BAA on every plan. If payment is happening on the same page, our note on Stripe and HIPAA for patient payments covers the billing side of the same surface.

A pre-submission checklist for the page

1. Confirm advertising authorization before anything else. Without prescription drug authorization where it is required, page fixes will not help.
2. Remove branded medication names from plan names, headings, meta titles, and the URL slug. Reviewers read the URL.
3. Strip outcome numbers and timelines, including inside testimonials and comparison sections.
4. Remove transformation imagery and body-focused visuals from the page and its social preview image.
5. State compounded status accurately where compounded preparations are offered, without equivalence framing.
6. Make the recurring charge unmissable: amount, interval, what is included, what happens after any introductory period, and how to cancel.
7. Say that eligibility is a clinical decision and that not everyone qualifies.
8. Audit what the page sends. Open the network tab, filter to ad platform domains, and read the actual outbound requests including URL and custom parameters.
9. Re-run steps two through eight after every edit. Drift is the most common cause of a sudden rejection on an ad that ran for months.

Step eight is the one that is almost always skipped, and it is the only step that addresses the exposure that survives a successful ad review.

Frequently asked questions

Can I name the medication anywhere on a GLP-1 pricing page?

Editorially, naming a branded prescription medication turns the page into prescription drug advertising, which requires authorization you may not hold, and Meta rejects branded pharmaceutical weight-loss terms. Describing the clinical program without brand names is both safer and more accurate, since the prescribing decision follows an evaluation.

Why did an ad that ran for months suddenly get rejected?

In most cases the page changed rather than the policy. A new testimonial, a new plan tier, an updated hero image, or a revised headline is enough. Review is re-run against the current destination, not the version that was originally approved. Keep a change log for the page so you can identify what moved.

Does a disclaimer make an outcome claim acceptable?

Rarely. A disclaimer qualifies a claim, it does not remove it, and reviewers read the prominent statement rather than the footnote. If the headline promises a result, the page promises a result.

Is a pricing page safe if it has no form on it?

Not automatically. The page view itself, joined to a browser identifier, already carries the health context. A pricing page with no form and a standard pixel can still transmit that a specific identifiable person is shopping for GLP-1 treatment.

How should I show price when medication cost varies?

Show the recurring clinical fee clearly, state explicitly that medication cost is separate where it is, and give a real range rather than a lowest-possible figure presented as typical. The failure mode is a headline price that almost nobody actually pays.

Can I still track which plan a visitor selected?

Yes, in your own analytics. What should not travel to an ad platform is an event name or parameter that identifies the specific program a specific person chose. Neutral aliases let the platform receive a usable conversion signal while your internal reporting keeps the plan-level detail.

Where to start

Treat the pricing page as two separate audits that happen to share a URL. The editorial audit asks what the page claims, and it determines whether your ads run. The technical audit asks what the page sends, and it determines whether you have a disclosure problem. Passing the first tells you nothing about the second.

Curve handles the second: server-side collection, per-destination field mapping with a deny-by-default posture, neutral event aliases, SHA-256 identifier hashing, PHI-pattern monitoring, and a signed BAA on every plan. Run the free compliance scanner against your pricing page to see what is currently loading on it, read our guide to GLP-1 landing pages that convert without collecting PHI, or visit curvecompliance.com to review your funnel with us.

Reviewed August 2026. Platform advertising policies and FDA guidance on compounded GLP-1 products change frequently. Verify current policy and regulatory requirements before publishing or submitting ads.