Overview

In certain setups, Klaviyo's default client-side tracking can be supplemented by one or more server-side tracking tools to capture more abandonment data and increase triggered email opportunities. While this can dramatically improve performance, overlapping flows can cause issues like over-emailing or inflated attribution unless properly structured. Follow this guide to learn more about setting up abandonment flows when using multiple tracking sources, including Elevar, to maximize both performance and clarity.

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

📘

Tip: Use longer timeframes (e.g., 30 days) if you want to avoid re-triggering flows too frequently.

Analyze Flow Revenue with Klaviyo Custom Reports

To properly evaluate the lift provided by each flow (especially Elevar’s), set up a Flow Performance Report in Klaviyo:

Create Report:

• Begin on your Klaviyo homepage and use the left-hand navigation menu to click on the "Analytics" tab.
• An additional drop-down navigational menu will appear, click on the "Custom Reports" tab.
• Click on the "Create from scratch" button located in the upper-right hand corner of the page.
  • (See Figure 1)

Figure 1

Configure Report:

• Here you will need to configure a new report to help you analyze flow revenue within Klaviyo.
  • Navigate to the section of the page titled "Report Type" and use the drop-down menu to select the "Flows Performance Report" option.
  • Navigate to the section of the page titled "Report Name" and use the text box to enter an easily identifiable name (e.g., Flow Performance)
  • Navigate to the section of the page titled "Conversion Metric" and use the drop-down menu to select the "Placed Order" option. Additionally, change the conversion metric to "Value".
  • Navigate to the section of the page titled "Group by" and use the drop-down menu to select the "Flow" option.
  • Navigate to the section of the page titled "Timeframe" and use the drop-down menu to select the "Send in Last 30 Days" option which will allign with Elevar’s typical billing cycle, helping you evaluate return on investment.
• Once you have entered all of the required information to create a custom report, click on the "Save and Run Report" button located at the bottom of the page. This report allows you to compare revenue across all abandonment flows, see which system is generating the most impact and track trends over time as filters and logic are refined.
  • (See Figure 2)

Figure 2

Common Issues and Troubleshooting

Overlapping Flows Sending Duplicate Emails:

To resolve overlapping flows sending duplicate emails, check all profile filters. Ensure each flow explicitly excludes users from other active flows using different event sources.

No Revenue Reported for Client Side Flow:

To resolve no revenue being reported for client side flows, confirm that the flow is actually live, have a proper trigger, and sends emails (not just push notifications or manual actions).

Server Side Flows Reporting More Revenue than Client Side:

To resolve server side flows reporting more revenue than client side flows, investigate whether client-side tracking is firing correctly. Some Shopify setups or custom apps (like Tapcart) may interfere with email triggers.