Klaviyo

Klaviyo has a Segment destination that can be connected to both website front-end and server Chord Segment sources. We recommend connecting both sources for maximum reliability.

When the destination is enabled, Klaviyo will receive customer information and tracking events from your Segment sources after an email address has been captured for the user. A customer typically provides their phone number or email address either by logging in, entering this information in some other field like a newsletter signup, or placing an order.

We recommend the following Klaviyo destination configuration, available under Other Settings in the Segment destination settings:

This flag determines whether someone is sent an email with a confirmation link before they are added to the list. Defaults to true (checked). This should only be set to false or unchecked if you have already received explicit permission from that person to add them to this list.

This option is enabled by default to ensure duplicate profiles are not being created inside of Klaviyo. This option ensures email addresses are treated as the unique primary identifier. If this setting is enabled, Klaviyo will ignore any events that don’t have a customer email address attached. This means Chord tracking events received before an email address is known will be ignored.

This option should always be “Off”.

This option should always be “On”.

When Chord sends Segment an Order Completed event, Segment sends Klaviyo a Placed Order event and a Ordered Product event for each item listed in the properties.products array. Segment also attaches customer_properties with the userId set as $id for each of those Klaviyo events.

To add a customer to a Klaviyo list from a server event, pass a second argument to the identify method that looks like this: