Track GoHighLevel bookings as ad conversions, HIPAA-compliant
When a visitor clicks your ad and then leaves your site to book through GoHighLevel, the click ID and UTMs stay behind, so the booking can't be credited to the ad on its own. Curve Compliance carries that attribution across with a bridge token, through a custom handoff that Curve's team sets up for you, and credits the booking when GoHighLevel's webhook arrives. It then sends the conversion server-side to Meta, Google, TikTok, Microsoft and LinkedIn, and a booking made days after the click still matches.
See how Curve Compliance tracks GoHighLevel bookings on your own funnel.
How it works
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
Curve hands GoHighLevel a bridge token
GoHighLevel bookings get a small custom setup from Curve's team. With it in place, Curve keeps the visitor's ad attribution when they go to book: click IDs, UTM parameters, the session and the page the click came from. It passes GoHighLevel a short reference to that attribution, called a bridge token, which carries no form content and is not a patient identifier.
Step 3
GoHighLevel returns the token with the booking
GoHighLevel keeps the token with the appointment and includes it in the webhook it sends when the booking is made. Where a custom field is needed to carry the token into that webhook, Curve's team sets it up.
Step 4
Curve credits the booking to the ad click
The webhook is set up in Curve under Incoming Webhooks to match on the bridge token, and Curve's team configures it with you. When it arrives, Curve credits the booking to the original visit, even when the patient books days after the click.
Step 5
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 ad spend next to the tracked bookings for each campaign.
What reaches Meta and Google
Meta and Google receive the GoHighLevel booking as a conversion sent from Curve's servers and credited to the ad click that started it. TikTok, Microsoft and LinkedIn receive it the same way.
- Each ad platform receives only a fixed list of fields.
- Contact identifiers are off by default, and SHA-256 hashed when you turn them on.
- The event can use a neutral name such as "Lead" in place of a treatment or condition.
- The bridge token passed to GoHighLevel carries no form content and is not a patient identifier.
- Curve detects PHI-like patterns, such as condition names, form answers and emails in URLs, and flags them so they can be fixed at the source.
- 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 GoHighLevel sign a BAA?
Yes, with HighLevel's paid HIPAA add-on. The add-on includes a signed BAA and is open to agencies on any plan.
HighLevel describes it as an optional, account-wide add-on that enables encryption of ePHI, BAAs, audit logging and MFA enforcement, with safeguards that apply to your entire agency once activated.
HighLevel accounts are not HIPAA compliant by default. Agency owners must then turn on HIPAA manually for each sub-account in Advanced Settings to complete the setup for that location.
A BAA with HighLevel covers the data inside GoHighLevel. It does not extend to the ad platform receiving a conversion from it, so what reaches the ad platform should be a neutral event with hashed identifiers.
Curve Compliance signs its own BAA with you on every plan.
We checked HighLevel's own pages on September 29, 2026. The quotes and source links are on the GoHighLevel entry in the BAA Directory.
GoHighLevel booking tracking FAQ
Can I send GoHighLevel bookings to Meta Conversions API?
Yes. Curve Compliance credits each GoHighLevel booking to the ad click behind it when GoHighLevel's webhook arrives, 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 and SHA-256 hashed when enabled, and the event can use a neutral name such as "Lead". The same booking can also go to Google, TikTok, Microsoft and LinkedIn.
Does attribution survive if the patient books days later?
Yes. GoHighLevel keeps the bridge token with the appointment and sends it back in its webhook, so Curve Compliance matches the booking to the original visit, with its click IDs, UTM parameters and the page the click came from, even when the patient books days after the ad click.
Does GoHighLevel sign a BAA?
Yes, with HighLevel's paid HIPAA add-on, which includes a signed BAA and is open to agencies on any plan. Each sub-account then needs HIPAA turned on in Advanced Settings. That BAA covers the data inside GoHighLevel, not the ad platforms that receive your conversions. Curve Compliance signs its own BAA with you on every plan.
What if the GoHighLevel booking page is embedded or opens in a pop-up?
Curve's team sets that up. GoHighLevel bookings already get a small custom setup from Curve's team, and embedded booking widgets, pop-ups and buttons that open the scheduler with JavaScript are set up the same way. Either way, the booking is credited to the ad click that started it.
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, configures the GoHighLevel webhook under Incoming Webhooks, sets up any custom field the token needs and turns on forwarding to your ad platforms. Curve signs a BAA on every plan.
Track GoHighLevel Bookings as Conversions
Curve's team sets up the GoHighLevel handoff, the webhook 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