​
Overview

Destination Type:
Client-side
and
Server-side

​
Installation Instructions

  1. Navigate to your Klaviyo Admin Dashboard
    .
  2. In the left-bottom corner of the dashboard, click on your Klaviyo Workspace Name and then on
    Settings
klaviyo-1
  1. Under the Account-tab, choose API keys.
  2. Copy your Public API Key, you will need it later.
  3. Click on Create Private API Key
  4. Give your key a name and select Custom Key in Select Access Level
  5. Select Read/Write Access to the Events scope.
klaviyo-2
  1. Press Create
  2. Copy the newly created Private API Key, you will need it later.
  3. In the Converge sidebar, click on
    Event streams
    and then click Create new Destination.
  4. Select the Klaviyo destination and click Next.
  5. Give your destination a name (e.g. Klaviyo Destination) and click Next.
  6. Fill in the Public API Key and Private API Key you copied from Klaviyo and click Next.
  7. Keep the defaults on the Configuration page and click Next.
  8. Select Use default mapping and click Next.
If you are using any of Klaviyo’s prebuilt integrations, then you will want to make sure not to send Started Checkout and Placed Order events. Otherwise, you will want to send all events. You can disable Started Checkout and Placed Order by selecting Custom Mapping and deactivate them using the toggle next to the event.
You can find the Default mapping for the Klaviyo destination here. For more information on setting up Custom mappings, look here.
  1. Select the sources you want to forward events from, then click Next.
  2. Review any issues and click Submit.

​
Converge functionality

This integration supports the following Converge destination functionality.
Converge FeatureSupported
Custom Events
Filters
Server-side Conversions

​
Using Converge to increase abandoned cart revenue on Klaviyo

You may already be using Klaviyo’s abandoned cart flows based on the Added To Cart events and Started Checkout events tracked by the Klaviyo pixel on the browser. However, Klaviyo’s browser identification is based on a third-party cookie meaning that most customers will not be successfully identified after 7 days (see our section on Cookie Behavior
 ). When Converge is set up with a first-party cookie, it can reliably re-identify customers past that 7-day mark (see: Setting up a server-side first-party cookie). Customers using our pre-built Shopify or Magento integrations already have a first-party cookie as part of their Converge setup. For most customers, we expect an abandoned cart revenue uplift of 20-50%.

​
Adding product URL and image URL to Converge events to power Klaviyo flows

A common use case of the Klaviyo Destination is to build Klaviyo Email Flows based on Converge Events. As such, you might want to include a Product URL or Product Image URL in the Converge Event so you can leverage these in your email flows. To that end, you will want to extend the Converge Event Spec for the following events. Once you add the custom properties to your events, Converge will automatically forward these to the Klaviyo Destination.

​
Extending your Converge Event implementation for Klaviyo

Find code examples below that illustrate where you should add the Product URL and Product Image URL custom event properties.

​
FAQ

​
Event Mapping

Converge automatically maps the following events from the Converge Event Spec to the Klaviyo spec.
Converge Event NameKlaviyo Event Name
$page_load__activity__
Viewed ProductViewed Product
Viewed CollectionViewed Category
Added To CartAdded to Cart
Removed From CartRemoved from Cart
Started CheckoutStarted Checkout
Placed OrderPlaced Order
SearchedSearched Site
This integration also auto-tracks some additional events that are not part of the Klaviyo Base Spec but are so heavily requested that we automatically forward them.
Converge Event NameKlaviyo Event Name
Ordered ProductOrdered Product