This is a specification for health tech teams and developers who are wiring a clinic or hospital website to Meta's Conversions API. It assumes you know what server-side tracking is. It answers a narrower question: what is the smallest set of events and parameters worth sending, and what should never leave your server?
The design goal is not to pass as much data as possible. For a health provider, the goal is to send enough for Meta to match a visitor and deduplicate an event, while sending nothing that reveals a condition, a treatment or a patient. If an event is later restricted for your data source, a minimal schema also means you have little to unpick.
Everything below is a proposal to be reviewed with your clinical lead and legal adviser. Meta's rules can change, and the parameter reference is the authority.
Principles before the schema
Meta's policy position is that advertisers are responsible for what they send, and that data revealing health information about people is prohibited. The Conversions API does not change that. Read the Meta help page on restricted information and the parameter documentation before you build.
Three principles follow.
- Send actions, not conditions. "Appointment form submitted" is an action. "Submitted a form for a named diagnosis" is a condition. Only the first is a candidate.
- Send identifiers for matching, never clinical context. Hashed contact details and browser identifiers help Meta match. Reason for visit, department of a specific procedure or symptoms do not belong in any field.
- Treat the restriction as possible. Design so the campaign still functions if the lower-funnel event is limited. See our earlier Meta health and wellness restrictions article for how the restriction tiers work.
The minimal event list
| Event | When to send | Notes |
|---|---|---|
| PageView | Every page load | Browser Pixel; mirror server-side only if you need it |
| ViewContent | Generic service or doctor page viewed | Do not attach a condition or procedure name |
| Contact | Click on phone, WhatsApp or directions | Action only |
| Lead | Appointment or callback form submitted | May be limited for your source; send only if permitted |
| Schedule | Appointment confirmed in the booking system | Optional; only if it can be sent without clinical detail |
Resist the temptation to add custom events named after treatments or symptoms. Each one is a disclosure. If your analytics team needs that level of detail, keep it in your own analytics, not in an ad platform.
Required fields on every server event
The Conversions API reference lists the core fields. For each event you send:
event_name: one of the standard names above.event_time: Unix timestamp of when the action occurred.event_id: a unique string you generate once and share with the Pixel for deduplication.action_source: where the action took place, such aswebsite.event_source_url: the page URL, which should itself be free of condition names.user_data: the customer information block described next.
If a lower-funnel event is restricted, remember that custom parameters and URL detail can be stripped. Do not rely on them to carry meaning.
The user_data block: hash what must be hashed
Meta's customer information parameter reference separates fields that must be hashed from those that must not.
Hash with SHA-256 after normalising: em (email), ph (phone), fn, ln, ct, st, zp, country, db and ge. Normalise first: trim, lower-case emails, and format phone numbers with the country code and no leading zeros. For an Indian mobile number, that means the country code followed by the ten digits.
Do not hash client_ip_address, client_user_agent, fbc and fbp. The reference says the IP address must never be hashed.
external_id is recommended to be hashed. Use an internal identifier that is not a medical record number or any identifier a hospital would use clinically. A random lead ID generated by your CRM is better.
For a clinic, a pragmatic minimum is em or ph, plus fbp, fbc when a click ID is present, client_ip_address, client_user_agent and external_id. Leave out db and ge. They add little to matching for appointment leads and they are personal details you do not need to transmit.
Deduplicate Pixel and server events
If you run both the browser Pixel and the server API, the same action will arrive twice. Meta's deduplication documentation explains the rule: an event is treated as a duplicate when the Pixel's eventID matches the API's event_id and the event name matches event_name. Deduplication applies within 48 hours of the first event with that ID.
Implementation notes:
- Generate the ID once in the browser when the action happens, pass it to the Pixel as the fourth argument of the
fbqcall, and send it to your server in the form submission. - Never generate a fresh ID on the server for an action the browser already reported. That guarantees duplicates.
- The fallback, matching on
event_nameplusfbporexternal_id, works only when the browser event arrives first. Do not design around it. - Two server events with the same content from the same source are both kept. Deduplication does not remove double-submits from your own system, so debounce form submissions.




