Growth · lower CAC
Lower CAC without breaking the rules.
Ad platforms restrict the events health brands used to optimise on. Halden puts the signal on the steps that are allowed, sends nothing health-related, and measures revenue on your own data.
Funnel · a visitor in real time
- Health boundary
Sent to ad platform
Allowlist only- Waiting for the visitor…
Kept inside Halden
First-party, encryptedHover a step to see what it sends.
The pipeline
Four steps between a click and an ad platform.
One enforcement point, tested on every release, with no client-side pixel to slip past it.
- 01
Collect first-party
The storefront talks only to Halden on your own domain. No third-party script runs on any patient page.
- 02
Check the boundary
Every funnel has a marked first health question. Anything at or after it cannot reach the ad path.
- 03
Filter to the allowlist
Per platform and per data source. The payload is built from a fixed set of permitted fields, so an unknown field cannot leak.
- 04
Send and record
Allowed events go server-side. The exact payload is stored, and anything dropped is logged with the reason.
The allowlist
What can leave, and what never does.
Can be sent
- Landing page view: event time and domain
- Content view before the quiz
- Quiz started, before any health question
- Non-health steps such as state of residence
Never sent
- Intake answers, conditions, symptoms, weight
- Medications, treatments, products or doses
- Lead, checkout or purchase events, under any name
- Order values tied to a prescription
- URL paths, query strings, referrers
- Patient lists for audiences or lookalikes
Ad event evidence log
Sample data- 09:41:02PageViewLanding pageSent to Meta
- 09:41:19quiz_startedBefore health questionsSent to Meta
- 09:42:05intake_stepAfter health boundaryDropped
- 09:44:31PurchaseNever allowlistedDropped
Fields sent: event time, domain. No URL path, no answers, no treatment.
Measurement
Measure CAC on what actually happened.
Revenue stays in first-party data and is joined to spend by time and geography, not by sending conversions to ad platforms.
Ad spend import
First releaseSpend by campaign, day and region from the ad platform, read-only and aggregate.
CAC by channel, state and week
First releaseSpend divided by new paying patients, from your own orders, not platform-reported conversions.
How did you hear about us
First releaseA post-purchase question stored first-party, as a directional check.
Geo holdout tests
PlannedPause or scale spend in matched regions and read incremental patients from real orders.
Marketing mix modelling
PlannedSpend and outcomes modelled together once a brand has months of varied spend.
Pre-reviewed creative library
PlannedAd templates checked against platform policy before they reach your account.
The rules
What the platforms say.
Meta
Data sources for telemedicine platforms and pharmacies fall in the Health and wellness category, where mid and lower-funnel events can be restricted.
Meta Business Tools Terms
Data based on health information may not be shared, by pixel or Conversions API, and event names must not imply it.
Google Ads
Health is a sensitive interest: no remarketing, customer match or lookalikes, and no health conversions through enhanced conversions.
TikTok
Health information may not be shared through the Pixel or Events API.
Summarised from each platform's published policy pages as of November 2026. Rules change; check the current versions.
What Halden will never build.
- Rename a restricted event so it gets through
- Fire a custom event at the same moment as a purchase
- Encode treatment, dose or plan in any field
- Route events through a second, cleaner domain
- Upload patients or purchasers as audiences
On health data sources, ad platforms already restrict lower-funnel events for everyone in the category. Halden gives you the strongest signal that is allowed and measures the result on your own orders.
Grow inside the rules.
We are working with a small group of design-partner operators. Tell us what you sell and where it hurts.