Integration · Lifecycle
Klaviyo
Audit-mode connector for the e-commerce / subscription CDP. By default we read events + metrics + profiles as a pure outcome source — pairs with our SDK or another connector that supplies the assignment side. Optional campaign-A/B ingest treats Klaviyo's flow-level experiments as ExperimentAssignment rows with assumed_uniform propensity (Klaviyo doesn't expose per-recipient bucket weights).
The contract
What flows in
- Events API: every event the customer tracks in Klaviyo (purchase, signup, churn signals)
- Profiles API: user-level attributes for CATE cohorting
- Metrics API: native conversion + revenue metrics for outcome attribution
- Optional: Campaign-A/B exports for campaign-as-treatment ingest
What flows out
- DR + ESS readout on every imported Klaviyo flow / campaign experiment
- Profile-cohort CATE for paywall / upgrade decisions the SDK serves
- Disclosed propensity quality (assumed_uniform for campaigns) so the readout is honest
Setup
- 01Connect: OAuth into your Klaviyo account (no API key handling on the customer side)
- 02Select which flows / campaigns to mirror as audit-mode experiments — defaults to active campaigns with A/B variants
- 03Map outcome metrics: revenue, ARPU, retention proxy, whatever your reward_spec needs
- 04Pair with the SDK or another assignment source for billable decision-mode lift
The DTC subscription bridge
Klaviyo's the spine of the e-commerce + DTC subscription stack. The connector unlocks the integrate-then-replace narrative for every brand that runs lifecycle email through Klaviyo and an upgrade flow through their own paywall — the same brands that need cohort-level causal readouts but won't rip out Klaviyo to get them.
Read-only by design. We never write campaigns or modify flows in Klaviyo. The audit number is the value; the customer's Klaviyo install is untouched.
Other lifecycle integrations
Wire Klaviyo in a 30-minute call.
We pair with your engineer, ship the integration live, and run the first decision on your stack.