Klaviyo
An introduction to the Klaviyo Destination
Overview
Connection Type:
Installation Instructions
-
Navigate to your Klaviyo Admin Dashboard.
-
In the left-bottom corner of the dashboard, click on your Klaviyo Workspace Name and then on
Settings
-
Under the Account-tab, choose API keys.
-
Copy your Public API Key, you will need it later.
-
Click on Create Private API Key
-
Give your key a name and select Custom Key in Select Access Level
-
Select Read/Write Access to the Events scope.
-
Press Create
-
Copy the newly created Private API Key, you will need it later.
-
In your Converge dashboard, under Connections, click
Create New Connectionand fill in your Public API Key in the Public Token field and your Private API Key in the API Key-field. -
Click on the Advanced-tab to set up your events.
-
Choose the events for which you want to set up the Converge Connection.
If you are using any of Klaviyo’s prebuilt integrations, then you will want to make sure not to send
Started Checkout
andPlaced Order
events. Otherwise, you will want to send all events. -
Click on Create Connection.
Converge functionality
This integration supports the following Converge connection functionality.
Converge Feature | Supported |
---|---|
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 Name | Klaviyo Event Name |
---|---|
$page_load | __activity__ |
Viewed Product | Viewed Product |
Viewed Collection | Viewed Category |
Added To Cart | Added to Cart |
Started Checkout | Started Checkout |
Placed Order | Placed Order |
This integration also auto-tracks some additional events that are not part of the Meta Base Spec but are so heavily requested that we automatically forward them.
Converge Event Name | Klaviyo Event Name |
---|---|
Ordered Product | Ordered Product |