Meta Conversions API integration

Kalman sends your funnel events to Meta's Conversions API from the server. Browser events and webhook events, including approvals and refills that no pixel ever sees, reach Meta as conversions. Every payload goes through the PHI firewall first.

Setup

Paste your Pixel (dataset) ID and a system-user access token from your own Business Manager. You can add an ad account id to import spend. No Meta app or OAuth is needed.

What you control

• Event mapping: choose which Kalman events go to Meta and under which name. Lead, checkout and purchase map to Meta's standard events by default. Approvals and refills can go as custom events, and custom names are checked against a denylist of condition and medication terms.
• Value strategy per event: the event's own value, a product's projected or average lifetime value, a fixed amount, or none.
• Deduplication: each event carries a stable event id, so Meta can match it against a browser pixel that sends the same id.
• Test events: add a test event code and send a test event to see Meta's response before anything counts.

Deliveries are queued, batched and retried with backoff. Events older than Meta's 7-day window are skipped and labelled. Every delivery appears in the Events log.

Read the guide