Setup Guide
3 minute read
This guide will help you set up Klaviyo as a destination in the RudderStack dashboard. It also lists the configuration settings required to correctly send data from the supported sources to Klaviyo.
Connection compatibility
| Destination Information | |||
|---|---|---|---|
| |||
Domain allowlisting for web device mode
In web device mode, RudderStack loads the Klaviyo native SDK from https://static.klaviyo.com. The script URL includes your company ID in its query string. Depending on your Content Security Policy, allow these sources in script-src.
You can monitor vendor scripts with a report-only Content Security Policy.
Setup
In your RudderStack dashboard, add a source. Then, from the list of destinations, select Klaviyo.
Connection settings
| Setting | Description |
|---|---|
| Name | Assign a name to uniquely identify the destination. |
| Public API Key | Enter the unique public API key from your Klaviyo dashboard (under Settings > Account). |
| Private API Key | Enter the private API key from your Klaviyo dashboard (under Settings > Account). This key lets you add users to a list or subscribe them using personalised emails/SMS. |
| API Version to use | Select the relevant API version from the dropdown:
|
New connections use API version 2026-04-15 by default. Existing connections keep their saved API version until you change this setting.
Configuration settings
Configure the below settings to receive your data correctly in Klaviyo.
| Setting | Description |
|---|---|
| List ID | Enter the default list ID to which you want to add or subscribe the identified users. |
| Consent | Select the consent type from E-mail, SMS, or both. consent is a Klaviyo-specific property that you need to include in your events if you run a GDPR-compliant business.Note: You can also override this setting by specifying the consent field in your event properties. |
| Enable this option to make email or phone as primary identifier | Turn on this setting to set a custom attribute _id and $email as the primary identifier when passed in traits.email/properties.email. RudderStack does not set $id field to the userId while sending the events.When disabled, RudderStack uses userId (anonymousId, if userId is absent) for mapping the user with a unique identifier. In case userId and anonymousId are absent, RudderStack sends email or phone as the user’s primary identifier.Note that: |
| Enable to flatten user/event properties | Turn on this setting to flatten the following data before sending it to Klaviyo: |
Important considerations for API version 2026-04-15
For API version 2026-04-15, the selected Consent channel must match an identifier in subscription events: E-mail requires an email identifier and SMS requires a phone identifier. The event fails if no selected channel can be resolved.
Consent settings
Configure the below settings for cloud or web device mode based on your setup:
| Setting | Description |
|---|---|
| Consent management provider | Select the relevant consent management provider from the dropdown. Note: You can add multiple consent management providers by clicking Add group condition. |
| Enter consent category IDs | Enter the consent category IDs you defined while setting up the consent management provider. |