Klaviyo
Each event reaches Klaviyo already attached to the profile — email, phone and external id in clear text, as an email platform needs to build the customer profile. From there you segment and trigger flows on real behavior.
Data delivered
Data delivered
- Events with named metrics and properties
- Profile with email, phone and external id
- Real timestamps and unique event id
What it is for
What you can do with it
- Trigger the approved-purchase flow with checkout data
- Segment on behavior the site alone cannot see
Why integrate
The business reason, not just the tech
Flows on events the snippet can't see
The gateway-approved purchase, the CRM event, the server-detected cart — none of it touches the site. Arriving in Klaviyo as events, they become flow triggers with the right timing.
A whole profile, not fragments
Email, phone and external id arrive together, in clear text — as an email platform needs. The customer profile stays whole, not scattered across three records.
Segment on real behavior
Segment by "bought X in the last 30 days" with checkout data, not email clicks.
How to connect
Step by step
- Step 1
Create a private API key (pk_) in Klaviyo.
- Step 2
Create the destination with the key.
- Step 3
Create a Delivery with the events that feed your flows.
Frequently asked questions
Why is the email sent unhashed here?
Because Klaviyo is YOUR email platform: the customer profile is the product. Hashing is an ad-platform requirement — here it would destroy the profile.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.