Marketing tools

Klaviyo

Write each lead's source, medium, campaign and channel to its Klaviyo profile, and send an OrcLink event for the lead and the stages you pick.

Built, not yet tested liveBuilt. Not yet tested against a live Klaviyo account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Integrations > Klaviyo > Configure: paste a private API key (scopes accounts:read, profiles:read, profiles:write, events:write). OrcLink checks it before saving and stores it encrypted.

What OrcLink reads

Only what it needs to find the profile: a profile by exact email.

What OrcLink writes back

For each new lead with a matched ad click: the click's source variables as profile properties orclink_<name> (only properties the profile does not hold yet, unless overwrite is on). A lead from the Conversions API may create the profile; a lead from a site form or chat is written only to a profile created within 24 hours of that lead and never creates one, and one event "OrcLink <stage>" with the value and currency when present. Then one event per later stage change for the stages you pick. Runs while the scheduled job jobs runs (your OrcLink operator schedules it).

Never stored

Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
The raw payload: only its SHA-256, for provenance.
Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).

Known limits

Profiles are found by email only: a lead with a phone number only is not written.
Two or more profiles with the same email: nothing is written.
Never in strict consent mode or for a visitor who refused consent; in HIPAA mode only after the workspace records a BAA with Klaviyo.
The email is kept only encrypted, until the write is done and at most 24 hours.