Telehealth and pharmacy Facebook ads: how to send the completed consultation without the condition

Telehealth has a wonderfully awkward tracking setup. The whole product is a private conversation about health, and the ad platform wants a conversion.

Let's break down the funnel, because the funnel is where the answer is.

An ad brings someone to a landing page. They fill in a short intake. A clinician reviews it and holds a consultation. Then, if it's suitable, a prescription is issued or a subscription starts. Four steps, and only the first is visible to the ad platform.

Where are the useful signals? Not the ad click, and not even the intake. The valuable moments are the completed consultation and the filled prescription. That's the person who actually became a patient. Everything before that is a hope.

Where's the risk? Everywhere else. The intake form asks about symptoms. The landing page names a condition. The URL includes the medication. Each of those is data that, if it travels with an event, describes a person's health.

So there are two jobs, and they're separate.

Job one: keep the condition off everything that leaves. Cut the link to your domain, use neutral event names, send only a hashed email and phone plus the ad click. Don't send intake answers. Don't send the medication.

Job two: send the later stage. When a consultation is completed or a prescription is filled, tell the ad platform, with the original ad click attached and the identity hashed. This is the job most telehealth advertisers skip, and it's where the biggest gain is. It's the difference between optimising for "people who fill in an intake" and "people who become patients".

A made-up example. 500 intakes. 200 are suitable and book. 150 complete a consultation. 90 have a prescription filled. If the ads see intakes, they learn from 500 examples, 410 of which never became patients. If the completed consultation is sent, they learn from 150, and if the filled prescription is sent, from 90, all of them real. The volume is lower, and the signal is far better.

The plumbing matters. Your consultation platform or clinical system has to push a status to a CRM or a webhook, and each status change has to keep the click ID or a hashed identity so it can be matched. In many telehealth stacks, that link is the real project, not the ad platform side. Also time it well: send the status the same day, because Meta rejects events sent more than 7 days after they happened.

Here's how I'd split what to send at each step of a telehealth funnel, so the boundaries are clear.

At the ad click: the ad click ID, captured on landing. Nothing else.

At the lead form: a hashed email and phone and the click. The form should collect only what's needed to contact the person, and the clinical questionnaire should live in a secure system after that step.

At the booked consultation: a neutral booked event, matched by hashed identity and the click.

At the completed consultation: a neutral completed event, same match keys. No notes, no reason for the consult.

At the filled prescription or started subscription: a neutral purchase event, with the value, same match keys. No product or drug name.

Notice that each step adds a stage and not any clinical content. That's the design principle: the funnel gets richer in outcomes and stays empty of health details.

Which stage would you send: the intake, the completed consultation, or the filled prescription?