Meta health and wellness tracking for telehealth and clinicsConversion tracking for health businesses, built around Meta's own rules.

Meta prohibits health information in the data you send it, and its core setup cuts URLs down to the domain. HelloConversions sends your booked consults and new patients from GoHighLevel server-side, strips every query string, hashes identifiers, and with its Health & Wellness setting sends only your website's address.

7-day free trial · Money-back guarantee · About 90 seconds to connect

Activity logSample events

What Meta receives

  1. Patient lead · Consult requested

    URL: yourclinic.com
    MetaleadsentGoogle Adsgenerate_leadsent
  2. Patient lead · Consult booked

    URL: yourclinic.com
    Metacomplete_registrationsentGoogle Adsbook_appointmentsent
  3. Patient lead · Consult attended

    URL: yourclinic.com
    Metaqualified_leadsentGoogle Adsqualified_leadsent
  4. Patient lead · Started care

    + $299
    MetapurchasesentGoogle Adspurchasesent

Sent server-to-server, hashed contact details attached, every event logged.

GoHighLevel businesses using HelloConversions

  • RMI Health
  • Campbell Health Center
  • BioHealth Wellness
  • VYVE Wellness
  • Abundant Health
  • Longevity Health 360
  • AlphaOmega Wellness
  • The Modern Way Lactation

The problem

The pixel sends more than you think. Meta notices.

A browser pixel on a health site sends the full page address, campaign tags and all. Meta's systems block what they detect, and sharing prohibited information can bring data restrictions.

The page address
Browser pixel: The full URL, path and query string, on every event.
With HelloConversions: The query string removed always; with Health & Wellness on, only your website URL.
Who the event is about
Browser pixel: Whatever the browser can see, if the pixel fires at all.
With HelloConversions: Email, phone, name, city and state from GoHighLevel, SHA-256 hashed before they leave.
What gets counted
Browser pixel: Page views and form fills that survive ad blockers and privacy settings.
With HelloConversions: The stages you choose, server-to-server: consult booked, attended, started care.
Checking what was sent
Browser pixel: Only what Events Manager shows after the fact.
With HelloConversions: A log of every event sent, its fields and Meta's response.

How it works

Consults and patients, sent without the page.

The moment a patient lead moves in your GoHighLevel pipeline, HelloConversions sends that stage to Meta's Conversions API and Google Ads, server-to-server, with identifiers hashed and the URL reduced to what you allow.

HelloConversions

  • Hashes contact details
  • Dedupes against your pixel
  • Adds the sale value
  • Logs every send
  1. Contact created

    Consult requested

    Meta learns who is looking for care

    MetaleadSent

    Google Adsgenerate_leadSent

  2. Pipeline stage

    Consult booked

    Meta learns who books

    Metacomplete_registrationSent

    Google Adsbook_appointmentSent

  3. Pipeline stage

    Consult attended

    Meta learns who shows up

    Metaqualified_leadSent

    Google Adsqualified_leadSent

  4. Subscription started

    Started care

    Meta learns who becomes a patient

    MetapurchaseSent

    Google AdspurchaseSent

    + sale value attached

Example mapping. Each stage is sent as a Meta event such as lead or purchase, and you choose which stages are sent.

Meta's rules, in Meta's words

We built it the way Meta's documentation describes.

Meta publishes what health businesses may and may not send through its Business Tools. HelloConversions follows it, so you aren't choosing between tracking and compliance on your own.

  1. Meta rule 1

    Health information is prohibited

    Meta's Business Help Center lists medical conditions, treatments, prescription medications and places of treatment as information you must not share, including in URL parameters, custom event names and custom data.

    Meta Business Help Center: About prohibited information
  2. Meta rule 2

    Core setup cuts the URL to the domain

    For health businesses, Meta's core setup restricts custom parameters and “anything in a URL following the domain”.

    Meta Business Help Center: About prohibited information
  3. Meta rule 3

    Website events still need a URL

    Meta's Conversions API documentation says event_source_url is required for website events.

    Meta for Developers: Server Event Parameters

So every event HelloConversions sends carries a URL, with the query string removed. Turn on the Health & Wellness setting and that URL is your website's address on every event, never the page a patient was on.

What HelloConversions does

  • Removes the query string from every event source URL, so UTM tags and campaign names never reach Meta
  • With the Health & Wellness setting on, sends your website URL on every event instead of the page
  • Hashes email, phone, name, city, state, postal code and country with SHA-256 before they leave
  • Maps each GoHighLevel stage to a Meta event such as lead or purchase, sent server-to-server
  • Logs every event it sends, with the fields and Meta's response, so you can check them

What stays your call

  • Product names. Purchases carry the product titles from GoHighLevel, so name products without a condition, treatment or medication in them.
  • Custom conversion and audience names in Meta. Meta's terms cover every name you choose.
  • Your dataset's category in Meta Events Manager, and whether Meta has placed it in core setup.
  • Your own compliance review. Meta says its filters are not a substitute for one, and neither is ours.

See exactly what's sent

One booked consult, before and after.

Flip the Health & Wellness setting and watch the event source URL change. Everything else is the same either way: identifiers hashed, query string gone.

One booked consult

Sample patient and clinic

In GoHighLevel

Page
https://yourclinic.com/weight-loss/glp1-consult?utm_source=facebook&utm_campaign=semaglutide-spring
Contact
Jane Doe · jane.doe@example.com · +1 (555) 010-2233
Location
Austin, TX
Stage
Consult booked

Sent to Meta's Conversions API

event
complete_registration
event_source_url
https://yourclinic.comWebsite URL, on every event
em (email)
86e0b9e56c17cc4d12387e1949b85053fbe73bc3ce5a1188713a9d300cc6133d SHA-256
ph (phone)
368f8c1430713dea76708417829548cb38b66a2db9913bdd82f83ac808c37a21 SHA-256
fn, ln (name)
81f8f6dde88365f3… 799ef92a11af918e… SHA-256
ct, st (city, state)
c7c1319276e936c8… 1b5b9ccb3e8d006a… SHA-256
external_id
GoHighLevel contact ID
ip, user agent
Sent unhashed, as Meta requires
value, currency
0 USD
  • Query string and campaign names removed
  • Page path replaced by your website URL
  • Name, email, phone and location hashed

Your numbers

What does a booked consult really cost you?

Meta lowers the cost of whatever event it's told to optimize for. Type in last month and see how far cost per booked consult and cost per patient sit from cost per lead.

Last month

Example numbers. Type your own; nothing leaves this page.

$
  1. Consult requested · 200

    $20.00per lead

    Meta's target
  2. Consult booked · 60

    $66.67per booked consult

    The cost you're paid to lower
  3. Consult attended · 42

    $95.24per attended consult

  4. Started care · 18

    $222per patient

Meta is optimizing for:

Meta is pushing down your cost per lead: $20.00. Your cost per booked consult is $66.67, 3.3× higher, and Meta never sees it. Send consult booked as a conversion and that becomes the number Meta works on.

That's about 47 leads a week. Meta says an ad set usually leaves the learning phase after about 50 results in a week, so aim each ad set at the deepest stage that still clears it.

What you'll see

New patients and recurring revenue, every morning.

Daily Rev Ops shows new leads, first-time and returning customers, and recurring revenue from GoHighLevel subscriptions, with your ad spend alongside.

  • New and existing recurring revenue, for membership and subscription care
  • Cost to acquire a lead and cost to acquire a patient
  • A weekly email recap of who started care
HelloConversions
HelloConversions Daily Rev Ops for a demo wellness workspace: new leads, first-time and existing customers and their revenue, a recurring revenue block with new and existing MRR customers, and form submissions against revenue over time.
Daily Rev Ops for a demo wellness workspace. Demo workspace; the numbers are sample data.

Proof

Better matches, with less sent.

“we're up to 9.3 on all API events. Highest before using hello conversations was around 8.4/8.6”
Rose · Paid mediaMeta event match quality, out of 10, for the accounts Rose runs. Not a health-only result.

Individual customers, quoted as reported. Not averages, and not a promise of your results.

Common results across HelloConversions accounts

How each is measured
  • 17%Lower cost per lead
  • 22%Better event match quality
  • 4xFaster to set up

Setup

About 90 seconds to connect. No developer.

  1. 1

    Authorize your GoHighLevel account

    One click with OAuth. No API keys, webhooks or code.

  2. 2

    Pick your events and pipeline stages

    The ones your business is paid on. Each becomes a conversion event.

  3. 3

    Choose your ad platforms

    Meta, Google Ads or TikTok. From then on, every event you picked is sent automatically.

7-day free trial · Money-back guarantee · Rather not do it yourself? Our team sets it up on annual plans, or as an add-on.

Questions

What people ask before they start.

What are Meta's health and wellness data restrictions?

Meta prohibits health information in the data businesses send through its Business Tools, including in URL parameters, custom event names and custom data. For some health businesses it applies a core setup that strips custom parameters and everything in a URL after the domain, and its systems block prohibited information they detect. Your dataset's data source category in Meta Events Manager shows where it stands.

Will this stop Meta from restricting my dataset?

No tool can promise that: Meta decides a dataset's category and restrictions. HelloConversions sends data the way Meta's documentation describes, with no query strings, your domain instead of the page when Health & Wellness is on, and hashed identifiers. Check Data Source Categories in Events Manager to see where your dataset stands.

What exactly does the Health & Wellness setting change?

It sends your Meta destination's Website URL as the event source URL on every event, ignoring the page the event came from. Without it, HelloConversions sends the contact's attributed page with the query string removed.

Which patient details are hashed?

Email, phone, first and last name, city, state, postal code and country, with SHA-256, before they leave HelloConversions. The GoHighLevel contact ID goes as external_id, and the IP address and browser user agent are sent as Meta expects them, unhashed.

Does GoHighLevel's built-in Conversions API work for health offers?

It may not. Meta requires an event source URL on website events, and users with health and wellness datasets report on HighLevel's ideas board that Meta is blocking their native events. We compare the two in detail on our GoHighLevel comparison page.

Can I still send Google Ads my booked consults?

Yes: offline conversion import with GCLID matching, plus enhanced conversions with hashed customer data. Each stage you pick becomes a Google Ads conversion such as book_appointment.

Track every consult, the way Meta asks.

Start a 7-day free trial, or book a strategy call and we'll walk through your Meta setup with you.

7-day free trial · Money-back guarantee