On this page
Telehealth marketing without pixels works by sending conversions from a server instead of the browser: Meta says server events sent through its Conversions API “are processed like events sent using the Meta Pixel,” and Google Ads adds its click ID, the GCLID, to the landing URL so a later conversion can be matched to the click. Curve Compliance does this for telehealth brands, keeping the ad click through intake, booking and prescription steps and sending conversions server-side with PHI stripped before data reaches an ad platform. Meta can still limit or fully restrict event sharing for websites it places in a restricted category, so the setup has to work inside those limits.
Book a call. Running telehealth ads with the pixel off? Show Curve's team your intake flow and how patients book, and see what each ad platform can receive with PHI stripped first. Book a call with Curve.
How do telehealth brands measure ads without pixels?
The general method, for any clinic told to take its pixels down, is in Told to Remove All Tracking Pixels? How to Still Measure Ads: conversions go to the ad platforms from a server, and the ad click is kept so the result can be matched to it later. Meta built its Conversions API for that route, and says server events “may be used in measurement, reporting, or optimization in a similar way as other connection channels” (Meta for Developers). Google Ads works from its click ID: to track offline conversions from clicks, “you'll save these IDs along with whatever lead information you collect from the person who clicked your ad” (Google Ads Help).
Telehealth adds three layers on top of that method. Meta names telemedicine platforms in its Health and wellness category, and Google lists Health among its sensitive interest categories, each with its own limits. The funnel runs through intake, booking and prescription steps that often live on other domains and behind a patient login. And prescription ads carry their own authorization rules. The rest of this guide covers those three.
What does Meta still restrict when the pixel is gone?
Meta's restrictions follow the data source, not the pixel, and Meta names telehealth directly. Its Health and wellness category lists examples including “a patient portal, wellness tracker, telemedicine platform, pharmacy, health insurance marketplace, or condition-specific support group” (Meta Business Help). The categories apply to “data sources like websites, apps and offline sources that share data with us through Meta Business Tools,” and Meta's Business Tools Terms list the ad products as including “Meta Pixel, Conversions API, Facebook SDK for App Events, Offline Conversions and App Events API” (Meta Business Help; Meta Business Tools Terms). Moving events to the server doesn't move a telehealth site out of its category. Here is what each of the three restrictions Meta lists means, from its help page checked November 20, 2026:
| Restriction | Meta's wording | What it means for a telehealth account |
|---|---|---|
| Core Setup | “Restricts the sharing of custom parameters and parts of URLs following the domain.” | Campaign tags and page paths may not reach Meta; Meta says most campaigns should continue to run as expected |
| Certain standard events | “Restricts the sharing of specific mid and lower funnel events.” | Intake, booking and purchase events sit mid and lower in the funnel, so some may not reach Meta |
| Full restrictions | “Meta Business Tools cannot be used for ads purposes where restrictions are in place.” | Optimize for objectives that don't rely on shared events |
Two more lines matter. When a data restriction is in place, “custom events are automatically blocked until you review and confirm them” (Meta Business Help). And Meta's terms say “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” health information and other sensitive categories (Meta Business Tools Terms). Renaming a consult or prescription event is not a workaround; see does server-side tracking get around health restrictions? and Meta Core Setup for health and wellness.
What do Meta and Google ad policies require of telehealth advertisers?
Measurement and ad policy are separate gates, and telehealth brands meet both. On Meta, “Promoting prescription drugs is not allowed without authorization from Meta. Eligibility for authorization is limited to online pharmacies, telehealth providers, and pharmaceutical manufacturers” (Meta Business Help). Authorized advertisers may “Only target people 18 years or older” and only in the countries where they are certified, and Meta's help page lists two application processes, Meta's internal review and LegitScript. Meta also says advertisers don't need authorization for ads that only “Promote telehealth services generally.” For certification itself, see LegitScript certification: who needs it to run health ads.
On Google, Health is one of the sensitive interest categories, and Google says “Advertisers promoting products and services that fall within sensitive interest categories are unable to use advertiser-curated audiences” (Google Ads policy). Google's list of those audiences includes Customer match and your data segments. For a telehealth brand whose ads fall in Health, the pixel's audience-building role on Google was already limited; the conversion data tied to the GCLID is what still matters. For how platform policies differ across ad networks, see telehealth advertising compliance for virtual care platforms.
How do intake, booking and prescription handoffs get credited to the ad?
A telehealth funnel rarely ends on the landing page. The patient clicks the ad, starts an intake questionnaire, books a visit or waits for an asynchronous review, and may then receive a prescription filled by a partner pharmacy. Those steps can sit on several different domains, and a pixel on the landing page sees none of them. Pick the step that matters to the business, usually the booked visit or the completed consult, and credit that to the ad, rather than each intake answer.
The later steps are the sensitive ones. HHS says tracking inside logged-in pages “may even have access to an individual’s diagnosis and treatment information, prescription information, billing information, or other information within the portal” (HHS). So prescription and pharmacy outcomes should come back from a system record, through a webhook or an offline upload, not from a script running in the patient portal.
Curve Compliance keeps ad attribution when a visitor leaves to book. Plain links to IntakeQ, Calendly, Acuity, Jane App, OptiMantra, Boulevard, ZocDoc, Mindbody, Vagaro, Square, Setmore and Booker are handled automatically; GoHighLevel and embedded widgets are set up by Curve's team. Bookings made days later still match. Curve receives outcomes from booking systems, CRMs and call tracking through incoming webhooks, from EHR and intake tools such as Healthie, Athenahealth, OptiMantra, IntakeQ and Jane through Keragon, and through offline conversion uploads from a CRM or EHR, then credits each to the original ad click. Campaign Reporting puts Meta and Google Ads spend next to those conversions per platform and campaign. See IntakeQ, Calendly, Jane App and telehealth attribution across virtual and in-person visits.
What should a telehealth intake flow never send to an ad platform?
Anything about the patient's health or identity. HHS names telehealth directly: user-authenticated webpages “require a user to log in before they are able to access the webpage, such as a patient or health plan beneficiary portal or a telehealth platform,” and “Tracking technologies on a regulated entity’s user-authenticated webpages generally have access to PHI” (HHS). HHS also says a cookie banner doesn't fix this: “Website banners that ask users to accept or reject a website’s use of tracking technologies, such as cookies, do not constitute a valid HIPAA authorization.”
The FTC has acted on telehealth advertising data too. In March 2023, the FTC announced a proposed order against the online counseling service BetterHelp; according to the FTC's complaint, the company revealed email addresses, IP addresses and health questionnaire information to Facebook and other platforms for advertising. The proposed order would “ban BetterHelp from sharing consumers’ personal information with certain third parties for re-targeting” (FTC, March 2, 2023). See also the Cerebral settlement and telehealth compliance gaps.
A practical list of what stays out of every event, URL and audience:
- Questionnaire and intake answers, including symptoms, medications and history.
- Condition, treatment, medication or dosage names in event names, page paths or campaign tags.
- Names, emails and phone numbers in URLs.
- Prescription status, refill dates and pharmacy details.
- Anything from pages behind the patient login.
Whether your company is a HIPAA covered entity or business associate, and which of your pages count as authenticated, shapes which rules apply, so talk to your counsel before you decide what any platform may receive. For where intake forms leak, see medical intake forms and tracking.
How Curve Compliance helps
Curve Compliance replaces browser ad pixels with one script and sends conversions server-side from Curve's servers to the Meta Conversions API, Google Ads, TikTok, Microsoft Advertising and LinkedIn. Each platform receives only a fixed list of fields. Curve detects PHI-like patterns, such as condition names, form answers and emails in URLs, before data reaches an ad platform, and flags them so they can be stopped at the source. Event Logs show what Curve sent to each platform and what the platform accepted, and the free website scan lists the pixels and trackers still loading on your intake and booking pages.
For telehealth funnels, the booking handoff keeps the ad click through IntakeQ, Calendly, Acuity, Jane App and other schedulers, and outcomes from intake tools, EHRs and CRMs come back to the original click. Curve signs a BAA on every plan, is SOC 2 Type II, and its team does the setup, typically live in about a week. See Curve for telehealth, or book a call to walk through your intake flow with Curve's team.
Sources, checked November 20, 2026: Meta for Developers: Conversions API; Meta Business Help: data sharing restrictions; Meta Business Help: data source categories; Meta Business Help: Prescription Drugs advertising policy; Meta Business Tools Terms; Google Ads Help: About offline conversion imports; Google Ads policy: Personalized advertising; HHS OCR: Use of Online Tracking Technologies; FTC: BetterHelp proposed order (March 2, 2023).
Frequently Asked Questions
Can a telehealth company run Meta ads without the pixel?
Yes, conversions can go to Meta from a server through the Conversions API, which Meta says processes server events like pixel events. Meta may still limit or fully restrict event sharing for websites it places in a restricted category, whichever route the events take.
Does server-side tracking get around Meta's health restrictions?
No. Meta's restrictions apply to the data source, and the Conversions API is one of the Meta Business Tools they cover (Meta Business Tools Terms); see does server-side tracking get around health restrictions?
What is Meta's Core Setup restriction?
It is the first of the three data sharing restrictions Meta lists: “Core Setup: Restricts the sharing of custom parameters and parts of URLs following the domain” (Meta Business Help). Meta says most campaigns should continue to run as expected, with fewer details reaching Meta.
Do telehealth companies need Meta authorization to advertise prescriptions?
Yes. Meta says “Promoting prescription drugs is not allowed without authorization from Meta,” and telehealth providers are among the eligible advertisers; ads that only promote telehealth services generally don't need it (Meta Business Help).
How does Google Ads track conversions without a pixel?
Through the GCLID. Google provides “unique IDs, called Google Click ID (GCLID), for every click that comes to your website from an ad” (Google Ads Help); you keep the ID with the lead and give it back to Google Ads when the visit is booked.
Do bookings made days later still count?
With Curve Compliance, yes. The booking handoff keeps the original ad click, and bookings made days later still match.
Does HHS allow tracking on telehealth intake pages?
HHS says tracking on authenticated pages, including telehealth platforms, generally has access to PHI, and that “Regulated entities must ensure that all tracking technology vendors have signed a BAA and that there is an applicable permission prior to a disclosure of PHI” (HHS).
Talk to Curve Compliance
Book a call. Want telehealth bookings and prescriptions tied to the ads that produced them, without browser pixels? Curve's team sets up server-side conversions and the intake and booking handoffs, typically live in about a week, under the BAA Curve signs on every plan. Book a call with Curve.