Due to the impact of iOS/ad blockers, many registered users are unable to trigger flow events with Klaviyo's pixel, resulting in a loss of revenue that could be generated from email marketing. We estimate that this type of user accounts for as much as 70%, so using server-side tracking can achieve very good results, and the configuration is very simple.
The Klaviyo Server-side tracking sends 2X customer profiles to trigger your email flows. It dramatically improve your revenue generated by Klaviyo.
Best Practice
Attribuly's powerful first-party data can identify returning visitors for up to 360 days and currently supports five types of server-side events.
Product viewed
Collection viewed
Added to cart
Checkout started
Checkout completed
We recommend configuring at least the 'product viewed' and 'added to cart' events. This way, you can duplicate the existing two flows, resulting in a total of four flows:
Browse abandonment flow
Browse abandonment flow-Attribuly SS
Cart abandonment flow
Cart abandonment flow - Attribuly SS
The flows configured by Attribuly will not be sent repeatedly to the existing flows, making it easy for you to analyze the new revenue brought by the new flows.
โ
Prerequisites
You don't need to remove Klaviyo pixel tracking.
Step 1: Configure Conversion feed
Go to conversion feed, select "Klaviyo" after clicking "Add destination"
Select server-side events, all the available events are recommended to choose.
Click "Next" to Klaviyo setting. Select a connect Klaviyo account, and then click "Save".
That's it!
Step 2: Set up flows in Klaviyo
You will find some new events created in "Metrics".
Clone your existing flow.
In the new flow, select the trigger as Attribuly's events.
The new flow can be named 'Attribuly xxx'. In the profile filters, add an exclusion item. For example, for cart abandonment, add the option shown in the image below. This ensures that users do not re-enter the flow.
You can also completely stop the previous flows and only run Attribuly's flows.