Klaviyo + Growth Dept CRO

Put each visitor's test group on their Klaviyo profile, so flows and segments can follow what they saw on your store.

A cro_<test id> property on identified profiles
Connected with a private API key
Sent only after the shopper's consent

When a visitor Klaviyo has already identified enters a test, Growth Dept CRO sets a cro_<test id> property on their profile with the group they are in. Build a segment on it, or branch a flow.

At a glance

Does Growth Dept CRO work with Klaviyo?

What reaches Klaviyo?

One profile property per test, named cro_<test id>, set to the visitor's group key.

Which visitors?

Visitors Klaviyo has already identified on your store, once their analytics consent allows it.

How does it connect?

An admin pastes a private Klaviyo API key in Integrations. The key is stored encrypted.

Can Klaviyo segments target a test?

Yes. Add a Klaviyo segment condition on the Targeting tab. It applies from a visitor's second page, once the storefront has asked which of your targeted segments they are in. The key needs Segments read access as well as Profiles.

How it works

How Klaviyo and Growth Dept CRO work together

The visitor is identified

Klaviyo's own onsite script has identified the visitor before.

They enter a test

The storefront notes Klaviyo's id for the visit, after consent.

Their profile is updated

A job sets cro_<test id> on the profile through Klaviyo's profile import.

Get started

To get started

01
Create a private key
In Klaviyo, create a private API key that can update profiles.
02
Connect it
In Growth Dept CRO, Integrations, Klaviyo, paste the key. Only admins and owners can.
03
Use the property
Build segments or flow splits on cro_<test id>.