PathwAI's Klaviyo integration sends data from flow steps to Klaviyo using only your public API key, the 6-character site ID. Three actions can be placed on any step's Entry or Exit: Upsert Profile writes contact details and properties, Track Event sends a metric that can start a Klaviyo flow, and Subscribe to List adds a person to a list for email or SMS.
What data moves
- PathwAI to Klaviyo only, through Klaviyo's client endpoints, which write data and cannot read your profiles.
- Upsert Profile: email, phone or external ID to match on, plus the properties you map.
- Track Event: a metric name and properties, deduplicated with a unique ID.
- Subscribe to List: an email subscription, an SMS subscription or both, to the list you choose.
Where it is configured
Integrations → Klaviyo holds the public API key and an optional default list ID. The actions are added under a step's Events in the flow editor.
Use cases
Follow-up email after a quiz
Put Upsert Profile and Track Event with a metric such as Quiz Completed on the last step, then start a Klaviyo flow from that metric.
Grow the list at the contact step
Add Subscribe to List on the Exit of the step that collects email and SMS consent.
Segment by plan or product
Write the plan or product a person chose as a profile property for segmentation.
How to set it up
- In Klaviyo, copy your public API key from Settings → API keys, and a list ID if you will subscribe people.
- In PathwAI, open Integrations → Klaviyo, paste the key, add a default list ID and save.
- In a step's Events, add a Klaviyo action on Entry or Exit and fill in its fields with variables.
- Run the flow once so the metric appears in Klaviyo, then build the Klaviyo flow on it.
Good to know
- Actions run once per visitor per step by default, so going back and forward does not create duplicates.
- PathwAI's Klaviyo guide says Klaviyo does not sign a BAA. Do not write health answers, diagnoses or medications to Klaviyo.
Klaviyo integration FAQ
Why does PathwAI only need the public key?
The actions use Klaviyo's client endpoints, which only write data. A private key that can read every profile is never needed.
Will a visitor who goes back trigger the action twice?
No. Actions run once per visitor per step by default.
What should not be sent to Klaviyo?
Health answers, diagnoses, medications or anything you treat as protected health information. Send marketing fields such as name, email and the plan chosen.
Want to see Klaviyo in a flow?
We can walk through where Klaviyo fits in your funnel and exactly which data it would receive.