Meta · Conversions API
Meta Conversions API for telehealth brands
Get your CAC out of Meta jail. Kalman sends paid orders, provider approvals and refills to Meta server-side, with a value and without health details.
Every planBAA included · free scan, about a minute
The problem
Meta's health rules cut off your best signal.
Meta's health restrictions and the browser pixel leave most telehealth campaigns optimizing on form fills. Kalman sends the outcomes that matter, server-side, so Meta can learn which clicks become patients.
What gets sent
What Meta receives, and what it never sees.
Every outbound event is built from an allowlist. Kalman reads each allowed field, checks its format and copies it. Nothing else can leave, whatever the inbound payload contained.
- A neutral event name, time and id.
- Value and currency, when the event has one.
- Hashed identifiers, such as email and phone, as SHA-256 hashes.
- Your site's root URL, never a page path or query string.
Never sent: product names, conditions, medications, doses, intake answers, page paths or free text. Every delivery is in Kalman's outbound event log, so you can see exactly what Meta received. How the firewall works.
Each mapping can be changed or switched off on the Meta destination in Kalman.
Setup
Live on Meta in five steps.
Meta Conversions API is on every Kalman plan. Every plan includes a BAA, signed before any data flows.
- 01
Scan your site. The free scan shows which trackers run where, including the Meta tag, and what to remove from pages where people share health details.
- 02
Sign the BAA in the app.
- 03
Connect your sources: your telehealth platform, Stripe and CallRail.
- 04
Connect Meta as a destination and choose which events it gets.
- 05
Check the outbound event log, then go live.
Meta is a trademark of its owner. Kalman isn't affiliated with, partnered with or endorsed by it.
Also in Kalman
Meta is one channel. Kalman runs all of them.
The same firewall and the same events go to every ad platform you buy, and into analytics built for telehealth.
Built for what legal will ask.
Security at Kalman →- BAA on every plan
- Allowlist PHI firewall
- SHA-256 hashed identifiers
- TLS 1.2+ and AES-256
- Two-factor sign-in
- PHI deleted after 30 days
Meta questions.
Anything else? Email [email protected].
Does Meta see what a patient is treated for?
No. Meta gets an event name, time, id, your site’s root URL, hashed identifiers and a value. Products, conditions, medications, page paths and intake answers are never copied into the outbound event.
Do we have to remove the Meta tag?
From pages where people share health details, yes. Kalman’s first-party tag and server-to-server events replace it there. The free scan shows where it runs.
Is it the same firewall on every channel?
Yes. Every destination uses the same allowlist, hashing and outbound event log.
Do you sign a BAA?
Yes, with every customer, on every plan, before any data flows.
See what your Meta Pixel is sending.
Free scan of your public pages. About a minute.
Free · about a minute · public pages only