Meta Conversions API for Sylaris OS brands

Two ways to connect

• Sylaris OS source (dedicated). Kalman has a built-in Sylaris OS source. It gives your clinic a webhook URL and a signing secret; Sylaris signs each event (X-Kalman-Signature, HMAC-SHA256) in Kalman's event format, and the Kalman tag covers on-site steps like intake started and checkout.
• Webhook catcher. Sylaris's existing order webhook can post to a Kalman webhook catcher as it is today. You catch a sample, map its fields once, and each delivery becomes an event. This is the quickest start.

Kalman and Sylaris OS are built by the same founder. That's why Sylaris OS has a dedicated source first; it isn't a reason to choose either product.

Which events to send

Approvals and refills matter most: they're the signal the browser pixel can't see. With the webhook catcher, Sylaris's order events map like this:

You can change each mapping, or turn one off, on the Meta destination in Kalman. Values come from the event amount or the price and projected lifetime value you set for each product.

What Kalman sends Meta

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.

• Event name, time and id. A Meta standard event (like Lead or Purchase) or a neutral custom name (like Qualified). Custom names that contain a condition, medication or body term are rejected.
• Your site's root URL, such as https://northwindhealth.com/. Never a page path or query string.
• Hashed identifiers: email, phone, external id, zip, city, state and country, as SHA-256 hashes, plus Meta's click ids (fbc, fbp). IP address and user agent are added only if you turn that on for the destination.
• Value and currency, when the event has one.

Never sent: product names or ids, 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.

Setup with the webhook catcher

1. Sign the BAA. Kalman signs one with every customer, on every plan, before any data flows.
2. Create the catcher. In Kalman, open Integrations and choose Webhook catcher. It gets its own URL and token and listens for samples for 15 minutes.
3. Point Sylaris at it. Post the order webhook to the catcher with Authorization: Bearer <token>, one event per request, with a stable event_id on every retry.
4. Trim the payload. Leave out patient name, treatment, product name, conditions, medications and any other clinical field. Send a non-descriptive product_id (like program-a) and register it in Kalman with its price.
5. Carry the click. Save the _kl_id cookie on the order at checkout and send it as kl_id on every later event for that order.
6. Map, test, record. Take a test order through paid, approved and shipped, map the fields, test the mapping, then connect Meta and check the outbound event log.

For the dedicated source, choose Sylaris OS under Integrations instead; Kalman shows the webhook URL and signing secret to paste into the clinic's settings in Sylaris.

Related

• Bask Health guide (webhook catcher today)
• Telegra guide (webhook catcher today)
• MDI guide (webhook catcher today)
• Kalman compared (Ours Privacy, Curve)
• Kalman for agencies
• Pricing