How to track Healthie bookings as conversions in Meta and Google Ads
Curve Compliance tracks Healthie bookings as conversions in Meta and Google Ads without forwarding the booking's details to either platform. Healthie bookings reach Curve through Keragon, a separate HIPAA-compliant automation service. Curve matches each booking to the patient's original ad visit, credits it to the ad click that started it and sends the conversion server-side, with only each platform's fixed list of fields, under a BAA Curve signs on every plan.
Healthie BAA status: Signs a BAA. Entered into when your account is created. See Healthie in the BAA Directory.
See how Curve Compliance tracks Healthie bookings on your own funnel.
How a Healthie booking becomes an ad conversion
Step 1
One script replaces your ad pixels
Curve's team installs the Curve Compliance script on your site in place of your browser ad pixels, so conversions reach your ad platforms from Curve's servers.
Step 2
Healthie bookings reach Curve through Keragon
When a patient books in Healthie, Keragon, a separate HIPAA-compliant automation service, sends the booking to Curve Compliance. Keragon has its own account and its own BAA.
Step 3
Curve credits the booking to the ad click
Curve matches each booking to the patient's original ad visit and credits it to the ad click that started it. Event Logs show what Curve sent to each ad platform and what the platform accepted.
Step 4
The conversion goes out server-side
Curve forwards the booking as a conversion to Meta, Google, TikTok, Microsoft and LinkedIn. Campaign Reporting then puts your Meta and Google Ads spend next to the tracked bookings for each campaign.
What Meta and Google receive from a Healthie booking
Meta and Google receive the Healthie booking as a conversion sent from Curve's servers and credited to the ad click that started it. The booking payload itself is not forwarded. TikTok, Microsoft and LinkedIn receive it the same way.
- Each ad platform receives only a fixed list of fields.
- Page titles, free text and form answers are never sent.
- Contact identifiers are off by default on Meta, Google Ads and TikTok.
- The event can use a neutral name such as "Lead" in place of a treatment or condition.
- Curve checks every event for PHI-like patterns, such as condition names, form answers and emails in URLs, and removes PHI before anything is sent to an ad platform.
- Event Logs show what Curve sent to each platform and what each platform accepted.
Read more about Meta Conversions API and Google Ads with Curve Compliance.
Does Healthie sign a BAA?
Yes. Healthie's Business Associate Agreement is entered into when your Healthie account is created.
Healthie's agreement is between you, as the covered entity, and Healthie Inc, as the business associate, and sets out each party's responsibilities for the privacy and security of certain health information.
A BAA with Healthie covers the patient data Healthie holds for you. It does not cover what an ad pixel on a Healthie page sends to an ad platform, because the ad platform is a separate recipient that has not signed your BAA. Keragon works under its own agreement with you.
Curve Compliance signs its own BAA with you on every plan.
We checked Healthie's own pages on October 1, 2026. The quotes and source links are on the Healthie entry in the BAA Directory.
Healthie booking tracking FAQ
Can I track Healthie appointments in Meta Ads?
Yes. Healthie bookings reach Curve Compliance through Keragon, and Curve credits each one to the ad click that started it, then sends it from Curve's servers to Meta Conversions API. Meta receives only a fixed list of fields, contact identifiers are off by default on Meta, Google Ads and TikTok, and the event can use a neutral name such as "Lead". The same booking can also go to Google, TikTok, Microsoft and LinkedIn.
Does the Healthie booking payload reach Meta or Google?
No. The booking payload itself is not forwarded: each ad platform receives only its fixed list of fields. Curve Compliance checks every event for PHI-like patterns and removes PHI before anything is sent to an ad platform.
Does Healthie tracking need a Keragon account?
Yes. Keragon has its own account and its own BAA. It is a separate HIPAA-compliant automation service that sends each Healthie booking to Curve Compliance, and it works under its own agreement with you. Event Logs show what Curve sent to each ad platform and what the platform accepted.
Can I see what Curve sent for a Healthie booking?
Yes. Event Logs in Curve Compliance show what Curve sent to each platform and what the platform accepted, so you can follow a Healthie booking from Curve to Meta or Google.
Does Healthie sign a BAA?
Yes. Healthie's Business Associate Agreement is entered into when your Healthie account is created. That BAA covers the patient data Healthie holds for you, not the ad platforms that receive your conversions. Curve Compliance signs its own BAA with you on every plan.
How long does setup take?
About a week; it varies case by case. Curve's team does the setup: it replaces your browser ad pixels with one script and turns on forwarding to your ad platforms. Event Logs show what Curve sent to each platform. Curve signs a BAA on every plan.
Track Healthie Bookings as Conversions
Curve's team sets up how Healthie bookings arrive through Keragon and server-side delivery to your ad platforms, with a BAA on every plan.
- BAA on every plan
- Set up by Curve's team
- Server-side delivery