Overview

This guide outlines how to enhance Klaviyo’s default browse, cart, and checkout abandonment flows by cloning them and leveraging Elevar’s server-side event tracking and session enrichment. This guide will walk you through the key areas you can check and configure to get the most out of your Elevar and Klaviyo integration.

Why This Matters:

Klaviyo’s default flows often rely solely on client-side tracking. As a result, events like Viewed Product, Added to Cart, and Checkout Started can be missed due to:

• Ad blockers
• iOS/browser restrictions
• Poor network conditions

Elevar fills in these gaps by sending events server-side and enriching them with session data—improving customer identification and attribution accuracy, and increasing conversion performance.

Cookie Expiration: Client-Side vs. Server-Side Tracking

Klaviyo’s default flows rely on client-side tracking, which sets cookies in a user’s browser. These client-side cookies typically expire after just 7 days, meaning that if a customer returns to your site more than a week after their initial visit, Klaviyo may no longer be able to identify them and your abandonment flows won’t trigger. For example:

• A customer clicks an ad and visits your site.
• They enter their email into a popup (e.g., “Get 20% off”).
• If they return and abandon their cart within 7 days, Klaviyo’s client-side cookie is still valid and they receive a cart abandonment email. But if they return after 7 days, the cookie has expired. Klaviyo can’t recognize them, so no abandonment email is sent and a potential sale is lost.

How Elevar Helps:

Elevar enhances your flows with server-side tracking, which allows you to set a persistent cookie that lasts up to a year. This means:

• Customers returning weeks or even months later can still be identified.
• Events like Viewed Product, Added to Cart, and Checkout Started are captured and enriched with session data.
• Your browse, cart, and checkout abandonment flows stay active for a longer window helping to recover more sales.

How to Boost Performance of Klaviyo’s Standard Flows with Elevar’s Server Side Tracking Technology and Session Enrichment

Clone and Customize Your Flows:

• Begin by duplicating your existing Klaviyo flows (Browse Abandonment, Cart Abandonment, Checkout Abandonment). Be sure to rename the flows something to make them identifiable (e.g., Cart Abandonment – Server Side, Browse Abandonment – Elevar).
• This keeps your original flows intact while you test and validate the boosted versions.
  • (See Figure 1)

_Figure 1_

Use Server-Side Events as Triggers:

• Once you have updated the clone name, navigate to the section titled "Tigger" and use the drop-down menu to select the appropriate Elevar-tracked event (e.g.,Viewed Product - Elevar SS, Added to Cart - Elevar SS, Checkout Started - Elevar SS)
• Once you have updated the trigger for the flow, click on the "Clone Flow" button located in the bottom right-hand corner of the window
  • (Figure 2)

_Figure 2_

📘

Note: Klaviyo does not have native server-side support for browse events, so Elevar is essential.

Add Proper Exclusions:

• To prevent customers from entering multiple flows for the same funnel step, ensure that you review the profile filters for each flow.
• Once you have accessed a specific flow, locate and click on the "Trigger" box.
• Navigate to the section of the window titled "Profile Filters" to view and edit the trigger so that it applies to only certain profiles.
  • (See FIgure 3)

_Figure 3_

(Optional) Review Flow Delays and Email Settings:

• Review your email timing strategy to ensure flows are spaced appropriately for the customer journey:
  • Browse Abandonment: 3–7 hour delay
  • Cart Abandonment: 2–4 hour delay
  • Checkout Abandonment: ~1 hour delay
    • Note: These delays are most effective when your profile filters check whether a customer has or hasn’t received a previous email (e.g., “Don’t send if they’ve already received Cart Abandonment”). If your flow uses event-based filters instead (like a specific action triggered the flow), these delay settings may be less relevant.
• Disable Smart Sending to ensure emails are sent as soon as the trigger conditions are met.
• Confirm the flow status is set to “Live.”

(Optional) Test and Monitor Performance:

• After launching your server-side flows you should monitor Flow Analytics to track email sends, open rates, and revenue.
• Compare performance against your original client-side flows.
• If you see one of your flows showing $0 revenue, double check:
  • Trigger metric is firing
  • Exclusions aren't too restrictive
  • The flow isn’t in "Draft" status

📘

Need Help with Rendering or Setup?

If you're seeing issues like:

• Product images not rendering properly in checkout emails
• Flows showing no activity even though events are firing

Send us a message at [email protected] ! If you manage multiple stores with Elevar, let us know. We can group your stores in our system to streamline future support.

How to Check Which Events Are Firing

Access Metrics Settings:

• Begin on the Klaviyo homepage and use the left-hand navigation menu to click on the "Analytics" tab.
• An additional drop-down menu will appear, locate and click on the "Metrics" tab.
  • (See Figure 4)

_Figure 4_

📘

Learn More: Metrics in Klaviyo

When looking at the Metrics report in Klaviyo, there are several different icons. Here is what they mean for your tracking:

• Gear Icon: Client Side Events
• Bag Icon: Shopify Server Events
• Elevar Icon: Elevar Server Events

View Metrics:

• Once on the Metrics page in Klaviyo, use the search function to locate each event (e.g., “Added to Cart”).
• Once viewing the specific metric, navigate to the "Measurement" filter and use the drop-down menu to select the "Unique" tab.
• Here you will be able to compare the events. You’ll often see that Elevar events are tracking at much higher volumes, especially for Browse and Cart.
  • (See Figure 5)

_Figure 5_