Overview

You can boost sales using Elevar's server-side tracking and session enrichment alongside Klaviyo's browse, cart, and checkout abandonment flows. By combining Elevar’s tracking with Klaviyo’s flows, you can capture more customer interactions to ultimately drive more conversions.

Follow this guide to learn how the events captured by Elevar and Klaviyo abandonment flows to work seamlessly alongside other tracking solutions. Using a data-driven and evidence based approach, you can assess the impact of Elevar’s tracking on your sales, to further optimize your workflows and get the most out of your Klaviyo account.

How to View Raw Event Data from All Tracking Solutions in Klaviyo

To optimize your Klaviyo flows, it’s important to first understand how to view the raw data from Elevar’s server-side tracking as well as the native client-side tracking and other server-side solutions integrated into Klaviyo. This data gives you visibility into what’s being tracked, and how different systems are capturing customer behavior.

Accessing Raw Data in Klaviyo:

• Begin on your Kaviyo 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.
• Once in the Metrics section of your Klaviyo account, you can view all the events being tracked by the various integrations, including:
  • Klaviyo’s native client-side tracking
  • Elevar’s server-side tracking
  • Other server-side tracking technologies.
    • (See Figure 1)

_Figure 1_

Viewing Raw Data for an Event:

To view the raw data for a specific event, like "Viewed Product", click into the event to see which tracking system recorded it. By reviewing the raw data, you can understand which provider tracked the event and what specific data points were captured.
While you may see data sent by Elevar, that does not necessarily mean that other tracking solutions didn’t capture the same event. The goal is to identify which events Elevar is tracking exclusively and not captured by the other solutions.

How to Identify Additional Events Captured Exclusively by Elevar

After viewing the raw data from multiple providers, the next step is to isolate the events that Elevar is capturing exclusively, which aren’t tracked by the other solution to better understand the unique value Elevar brings to your business.

Creating a Dynamic Segment to Track Elevar Specific Events:

In Klaviyo, you can create a dynamic segment to filter out customers who have been tracked by other technologies.

• Begin on your Klaviyo homepage and use the left-hand navigation menu to click on the "Auidance" tab. An additional drop-down menu will appear, locate and click on the "Lists & Segmants" tab.
• Once on the Lists & Segments section of your Klaviyo account, you can create a new dynamic segment.
• Use these filter rules to track customers who have been captured only by Elevar (and not by the other systems).
  • “Can receive email marketing in the last 30 days”: Ensures the customer is eligible to receive marketing emails.
  • “Viewed Product 0 times in the last 30 days”: Excludes customers tracked by Klaviyo’s client-side technology for viewing a product.
  • “Viewed Product (other server-side tech) 0 times in the last 30 days”: Excludes customers tracked by other server-side technologies.
  • “Viewed Product - Elevar SS at least once in the last 30 days”: Ensures the customer has been tracked exclusively by Elevar for viewing a product.

📘

Understanding the Dynamic Segment in Klaviyo to Track Elevar Specific Events:

By applying these rules filters, you can isolate customers who have been tracked by Elevar’s server-side tracking but missed by other solutions, allowing you to understand the additional events Elevar is capturing.

• For example, over the past 30 days, Elevar might have tracked 8,799 product view events that weren’t tracked by the client-side or other server-side technologies. This insight helps you understand the unique contribution Elevar is making to your data collection.

How to Optimize Elevar’s Abandonment Flows in Parallel with Other Tracking Solutions

Once you have identified the additional events captured by Elevar, you will need configure your Klaviyo abandonment flows so they work alongside the other tracking solutions you are using. The goal is to avoid duplicating efforts, such as sending multiple emails to the same customer.

Determine Flow Prioritization:

If you are using more than one server-side tool, you should assign a priority order to your abandonment flows. Think of them as a tracking waterfall: each level only engages users who weren’t already handled by a higher-priority layer.

• Recommended priority:
  • Klaviyo Client-Side Flows: These are native flows triggered by events like Viewed Product, Added to Cart, and Checkout Started via the browser. They're your first line of engagement and typically generate the highest volume of revenue.
  • Other Server-Side Flows: These flows are often powered by email capture or identity resolution tools. Because they operate independently of browser-side tracking, they can catch missed users—but may overlap with client-side flows if filters aren’t managed carefully.
  • Elevar Server-Side Flows: Elevar’s flows should be positioned last. This ensures they only trigger when both client-side and other server-side flows fail to capture a user. Despite being third in line, Elevar often picks up missed events due to its enriched server-side data pipeline.

Set Up Profile Filters in Klaviyo:

Once you have decided your flow order, you can configure profile filters in Klaviyo to ensure customers only receive one version of each abandonment email.

For example, in an Elevar-powered Browse Abandonment Flow, you should:

• Exclude users who triggered the client-side event: Viewed Product (Client-Side) — zero times in the last 7 days
• Exclude users who triggered the competing server-side event: Viewed Product – Reclaim — zero times in the last 7 days
• Exclude users who already placed an order or started checkout:
  • Placed Order: Zero times since starting the flow
  • Started Checkout: Zero times since starting the flow
• Add a “skip if recently enrolled” condition: Has not been in flow in the last 14–30 days

How to Compare Results and Measure the Impact of Elevar’s Tracking

Now that you have set up your flows and ensured they are not overlapping, you can measure the results. Klaviyo’s performance metrics make it easy to evaluate the effectiveness of Elevar’s server-side tracking.

Comparing Flow Performance

• In the Klaviyo Flows Section, you can compare the performance of all your flows side-by-side.
  • The key metric to track is "Placed Order", which shows how many customers who received an abandonment email ended up making a purchase.
• You can also create a custom report in Klaviyo, focusing on the specific dimensions you want to compare (e.g., Elevar’s server-side tracking, client-side tracking, and other server-side technologies). This report will allow you to see the performance of each tracking system.

👍

Understanding Klaviyo’s Smart Sending Technology:

Klaviyo's smart sending technology helps prevent sending multiple emails too quickly. The default setting for Smart Sending is 16 hours, but you can adjust this time frame as needed.

Read this guideto learn more about Klaviyo's smart sending technology.