Sylaris OS integration

Kalman has a dedicated source for Sylaris OS, the telehealth platform behind many intake and checkout flows. It uses two channels, each with its own job.

Browser

The Kalman snippet runs on Sylaris's patient-facing pages and records the journey a patient sees:

• intake started, each step completed and intake completed;
• product chosen, checkout started and purchase.

Step events carry only counts and a non-descriptive journey id. They never carry question text or answers.

Server webhooks

Signed webhooks are the source of truth for money, clinical outcomes and fulfillment:

• purchases;
• provider approvals and declines;
• shipments and refills;
• cancellations and refunds.

Each is verified with an HMAC signature. Email and phone are hashed on arrival, and only the hashes are stored.

Joined up

A purchase can arrive from both channels. Kalman dedupes it by order and event, so it counts once, and the second copy fills in anything the first was missing. When the webhook carries the visitor id from the browser, the event is tied to the original ad click. That's how approvals reach Meta with the right attribution.

Products are referenced by neutral ids that you map to names inside Kalman. Those names never go to ad platforms.

If Sylaris sends its own order webhook format, a webhook catcher can take it as-is.

Read the guide