On this page

A direct-to-patient program can send Meta and Google only what their health data rules allow, by pixel or by server. Meta's Business Tools Terms rule out data that “includes or is based on, directly or otherwise, health information” (Meta Business Tools Terms), Google's customer data policies say “You may not upload conversion information related to sensitive categories” (Google customer data policies), and an FTC complaint names the Conversions API next to the Meta Pixel (allegations; First Amended Complaint). Curve Compliance sends conversions server-side with a fixed list of fields for each platform and strips PHI before data reaches an ad platform. In the measurement method Curve describes for these programs, the drugmaker sees paid fills in aggregate by channel, campaign and partner.

Book a call. Running a direct-to-patient program? Curve replaces browser ad pixels with one script, gives each ad platform only a fixed list of fields, and signs a BAA on every plan. Book a call with Curve.

This page is general information, not legal advice. Rules and filings are described as they read on November 20, 2026.

What do Meta's rules let a direct-to-patient program send?

Meta may assign the websites, apps and offline sources that send it data to categories, and some categories can carry extra data sharing restrictions. Meta's examples for its Health and wellness category are “a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace, or condition-specific support group” (Meta, data source categories). A drugmaker's patient site, a telehealth partner and a pharmacy partner can each fall in that category.

Meta lists three kinds of restriction for those categories (Meta, data sharing restrictions). Core Setup “restricts the sharing of custom parameters and parts of URLs following the domain.” A restriction on certain standard events “restricts the sharing of specific mid and lower funnel events.” Full restrictions block event sharing in some or all regions. For sources under the standard event restriction, Meta suggests “leveraging more upper-funnel events to maintain effective audience targeting and campaign optimization.”

The filter is a backstop, not a permission. Meta says the advertiser is responsible for the data it shares and that “Meta’s systems are not a substitute for your own compliance mechanisms” (Meta, data sharing restrictions). The terms also reach labels: “The names you choose and criteria you establish for your events, conversions, and any custom audiences you create must not reflect, imply or be based on” any of the sensitive categories, health information included (Meta Business Tools Terms). For the wider 2026 changes, see Meta's healthcare ad rules in 2026.

What do Google's rules say about health conversions and audiences?

Google's customer data policies apply to enhanced conversions for web, enhanced conversions for leads, store sales uploads and Google-engaged audiences. They say “Conversions related to sensitive categories can’t be used for measurement in enhanced conversions or store sales (uploads),” and the list of sensitive categories includes “Health or medical information, like purchases of medical services, prescription drugs or medical devices” (Google customer data policies).

Audiences have their own limit. Health is one of Google's sensitive interest categories, and “Advertisers promoting products and services that fall within sensitive interest categories are unable to use advertiser-curated audiences,” a group that includes Customer Match, your data segments and lookalike segments (Google personalized advertising policy). The same policy bars using personally identifiable information “in connection with any anonymous or pseudonymous information, including in your data segments (previously called remarketing), cookies, or data feeds.” Which drug ads may run is a separate question from which data may flow back; for the FDA and FTC side, see DTC pharma advertising in 2026.

What does the FTC allege about server-side tools in the Hims & Hers case?

On July 29, 2026, the FTC, joined by Utah and by California through Los Angeles County Counsel, sued Hims & Hers Health, Inc. in the Northern District of California. The FTC's release says the complaint alleges the company “shared consumers’ sensitive health information about medical conditions with third-party advertising platforms despite claiming its services maintain consumers’ privacy” (FTC press release, July 29, 2026). On November 10, 2026, the FTC filed an amended complaint that “now includes Arizona, Florida, Nebraska, Ohio and Wisconsin in addition to Utah and California, by and through Los Angeles County Counsel” (FTC, November 10, 2026). The FTC's own note says “The case will be decided by the court,” and the FTC case page lists it as pending.

The amended complaint describes two Meta tools, the Meta Pixel and the Conversions API. It says the Conversions API “serves the same purpose of allowing Meta to automatically track Events but operates differently to the extent it creates a direct connection between the advertiser’s server, website, app or other internal software and Meta’s systems,” and that “These two tools automatically tracked and disclosed certain Events to Meta” (First Amended Complaint, paragraph 82). It alleges the Events had standard event names while their parameters combined identifiers, such as email addresses, with the treatment a person sought (paragraph 83), and that treatment code names in audience names were not effective at concealing health information because Hims told Meta what they meant (paragraph 81). For a full reading, see the Meta Pixel and Conversions API in the FTC's Hims case.

Why isn't server-side tracking a shield on its own?

Server-side delivery changes the route data takes, not what the data says. The lesson from the filings is about practices. A standard event name can still carry a health detail in a parameter, a page URL or an audience name, and a server-to-server connection delivers that detail as surely as a browser pixel does. Shumaker's client alert on the case advises companies to “Audit all third-party tracking technologies (pixels, SDKs, cookies, server-side integrations) deployed on websites and mobile applications, with particular attention to pages or flows involving health information” (Shumaker client alert, July 30, 2026).

In a direct-to-patient program the patient moves from the brand site to a telehealth partner and then to a pharmacy partner, and each hop needs the same review of event names, parameters, URLs and lists. For the general case, see why server-side is not a defense and why server-side tracking alone is not HIPAA compliance.

What can a direct-to-patient program send, and what should stay out?

The table puts the platform rules side by side, as a starting point for your privacy and legal teams, not a ruling on any program.

DataWhat the rules sayPractice to adopt
Event namesMeta: names for events, conversions and custom audiences must not reflect, imply or be based on health informationNeutral names for site events, and no renaming used to disguise a health event
Custom parameters such as product, dose or conditionMeta: Core Setup restricts custom parameters for restricted data sourcesKeep them out of every event, whichever system sends it
Page URLs and campaign valuesMeta: Core Setup restricts URL parts after the domainKeep condition and drug words out of paths and UTM values
Contact identifiersFTC complaint alleges identifiers were combined with treatment detailsSend each platform only the fields it needs, with nothing about health attached
Customer lists and audiencesGoogle: no advertiser-curated audiences, Customer Match included, when promoting in a sensitive interest categoryKeep patient lists out of ad platform audiences
Lower-funnel standard eventsMeta: mid and lower funnel events can be restricted for health and wellness sourcesPlan around the upper-funnel events that remain
Prescription and paid fill outcomesGoogle: no conversion information related to sensitive categories; Meta: no data based on health informationDecide with counsel, and measure them in aggregate reporting either way

Two questions need a lawyer in every program. First, whether any prescription or fill outcome may reach an ad platform at all, under any name and without contact details. Second, whether a partner that is a HIPAA covered entity may share a given event with the drugmaker in the first place. Before you settle either one, talk to your counsel.

How can a program measure paid fills without the ad platforms?

Ad platforms see clicks and the upper-funnel events they accept. The outcomes a drugmaker cares about, such as consults, prescriptions, paid fills and refills, happen at the partners. In the method Curve describes for direct-to-patient programs, each partner sends a stripped-down event at each step (visit, consult, prescription, paid fill) carrying the campaign that brought the patient, with no name or contact details. The drugmaker receives aggregate results by channel, campaign and partner.

Partners can deliver those step events through an incoming webhook or a file upload, and each one is credited to the original ad click. Campaign Reporting puts Meta and Google Ads spend next to Curve-tracked conversions per campaign, which gives cost per paid fill by campaign.

How Curve Compliance helps

Curve replaces browser ad pixels with one script and sends conversions server-side from Curve's servers to Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn (conversion tracking). Each platform receives only a fixed list of fields, contact identifiers are off by default and SHA-256 hashed when enabled, and events can use neutral names.

Curve strips PHI before data reaches an ad platform and flags PHI-like patterns so they can be stopped at the source. Event Logs show what Curve sent to each platform and what the platform accepted, a record your privacy and legal reviewers can check.

On the measurement side, Campaign Reporting shows cost per paid fill by campaign against Meta and Google Ads spend. Curve signs a BAA on every plan, holds SOC 2 Type II, and its team does the setup, typically live in about a week, case by case. Book a call to see the fixed field list and Event Logs for each platform.

For measuring a program from ad to paid fill, see direct-to-patient pharma attribution.

For the OIG's January 2026 bulletin on manufacturer direct sales, see pharma direct-to-patient programs.

For the data a drugmaker receives from its partners, see HIPAA expert determination and recipient-held data.

Sources, checked November 20, 2026: Meta Business Tools Terms; Meta, About data source categories; Meta, Data sharing restrictions by data source category; Stape, updated March 3, 2026; Google Ads, Customer data policies; Google Ads, Personalized advertising policy; FTC press release, July 29, 2026; FTC, November 10, 2026; FTC case page; FTC v. Hims & Hers, First Amended Complaint (November 10, 2026); Shumaker client alert, July 30, 2026.

Frequently Asked Questions

What data can a direct-to-patient program send to ad platforms?

Only what each platform's health data rules allow, by pixel or by server: Meta's terms rule out data based on health information, and Google's customer data policies bar uploading conversion information related to sensitive categories. In practice that means neutral names for site events, no condition or drug details in parameters, URLs or audiences, and paid fills measured in aggregate reporting.

Does the Conversions API get around Meta's health data restrictions?

No. Stape's summary of the rules says “Conversions API does not bypass the data sharing rules” (Stape), and Meta's Business Tools Terms name the Conversions API among the products they cover, next to the Meta Pixel (Meta Business Tools Terms).

What does the FTC complaint against Hims & Hers say about the Conversions API?

The First Amended Complaint of November 10, 2026 alleges that Events were shared with Meta through both the Meta Pixel and the Conversions API, which it describes as a direct connection between the advertiser's systems and Meta's (First Amended Complaint). These are allegations, and the case is pending.

Can conversions about prescription drugs be uploaded to Google Ads?

Google's customer data policies say conversions related to sensitive categories can't be used for measurement in enhanced conversions or store sales uploads, and they list purchases of prescription drugs as health or medical information (Google customer data policies).

Do Meta's restrictions cover telehealth and pharmacy partners?

They can. Meta's Health and wellness data source category lists a telemedicine platform and a pharmacy among its examples, so a partner's site can carry the same restrictions as the brand site (Meta, data source categories).

Should prescription or paid fill outcomes go to an ad platform?

That is a legal decision for each program, weighed against Meta's terms on health information and Google's customer data policies. Either way, a drugmaker can measure paid fills in aggregate reporting by channel, campaign and partner.

Talk to Curve Compliance

Book a call. Want a record of each event Curve sends to Meta and Google for your program? Event Logs show what Curve sent to each platform and what it accepted, Curve strips PHI before data reaches an ad platform, and its team does the setup, typically live in about a week, case by case. Book a call with Curve.