> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/email-and-marketing/klaviyo.md). # Klaviyo **Klaviyo** is a marketing automation platform built for e-commerce brands. It enables personalized campaigns, automated flows and audience segmentation across email and SMS using behavioral and transactional data. This destination forwards all track events to Klaviyo's Events API and syncs user profiles through identify events. ## Getting started This destination sends events from Chord's servers. Before connecting, generate a **private API key** in Klaviyo with the following scopes: * **Events**: Read/Write * All other scopes: Read is sufficient To create the key, go to **Settings > Account > API Keys > Create Private API Key** in Klaviyo. Set the scopes above, then click **Create**. ## Settings * **Destination Name** (required): a name to tell this destination apart. * **Klaviyo API Key** (required): your Klaviyo private API key. * **API Version** (optional): the Klaviyo API revision Chord uses, such as `2025-10-15`. Choose from `2023-09-15` to `2025-10-15`. There is no default. If you leave it empty, Chord uses the latest version it supports. Klaviyo supports each revision for 2 years. See [Klaviyo's API versioning policy](https://developers.klaviyo.com/en/docs/api_versioning_and_deprecation_policy). * **Include External ID** (optional): if on, Chord sends the `userId` to Klaviyo as the profile's `external_id`. Turn it off if you don't want user IDs in Klaviyo. On by default. * **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md). ## Connect Add **Klaviyo** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps. ## Event mapping | Chord event | Klaviyo event | Notes | | ---------------------------------------------------------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `track` (any event) | Create event metric | Event name passed as-is. Custom events need no setup | | `track`: [`Order Completed`](/collect-data/tracking-plan/order-completed.md) | Create event metric + individual `Ordered Product` events | Chord sends one `Ordered Product` event for each item in `properties.products[]`, after the main event succeeds. Each carries the order's `properties` and the item's fields | | `identify` | Upsert profile | Creates or updates the Klaviyo profile; handles 409 duplicate conflicts automatically | | `page`, `screen` | *(ignored)* | Not forwarded | Chord only forwards an event when it finds an `email` or a `phone` (see Profile data below). Events with neither are skipped. ## Track event fields | Chord source (priority order) | Klaviyo field | Notes | | -------------------------------------------------------------- | ------------- | ----------------------------- | | Chord event name | `metric.name` | Passed as-is | | `timestamp` | `time` | | | `messageId` | `unique_id` | Used for deduplication | | `properties.value` > `properties.revenue` > `properties.total` | `value` | Defaults to `0` | | `properties` | `properties` | All event properties included | ## Profile data Chord sends profile data on every event. | Chord source (priority order) | Klaviyo field | Notes | | ------------------------------------------------------------------------------ | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `properties.email` > `context.email` > `context.traits.email` > `traits.email` | `email` | | | `properties.phone` > `context.phone` > `context.traits.phone` > `traits.phone` | `phone_number` | Converted to E.164 format. Chord uses the country in the address traits, or `US` if there is none. The country must be a 2-letter code such as `GB`. If Chord can't convert the number, the event fails and Chord retries it | | `properties.first_name` > `context.traits.firstName` > `traits.firstName` | `first_name` | If there is no first or last name, Chord uses the text before the first space in `context.traits.name` or `traits.name` | | `properties.last_name` > `context.traits.lastName` > `traits.lastName` | `last_name` | In that same case, Chord uses everything after the first space | | `userId` | `external_id` | Only included when **Include External ID** is enabled (default: on) | | `anonymousId` | `anonymous_id` | | | `context.locale` | `locale` | | | `context.traits` and `traits` | `properties` | Every trait not listed in this section is sent as a custom profile property. If a trait is in both, `traits` wins. Chord skips empty values | ## Address and location Chord reads the address from traits only, using `context.traits.address`, or `traits.address` if there is none. It ignores `properties.address`, so a shipping address on an `Order Completed` event can't overwrite the address on the profile. | Chord source (priority order) | Klaviyo field | Notes | | -------------------------------------------------------- | ------------- | ------------------------------------------------------------- | | `address.address1` > `address.street` | `address1` | | | `address.address2` > `address.street2` | `address2` | | | `address.city` | `city` | | | `address.state` | `region` | | | `address.zipcode` > `address.postalCode` > `address.zip` | `zip` | | | `address.country` | `country` | Also sets the country for phone formatting | | `context.ip` | `ip` | Chord sends the IP address only when the event has an address | ## Custom events Chord sends every `track` event to Klaviyo under its own name, so custom events need no setup. Chord skips an event that carries no email or phone number. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/activate/event-streaming/destinations/email-and-marketing/klaviyo.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.