How to Set-up Klaviyo's Browse and Cart Abandonment Flows & Analyze Performance

Overview: General Overview to Set-up Flows and Analyze Performance

Setting Up and Analyzing Klaviyo Flows with Elevar Tracking:

Merchants typically use two or three of the following Klaviyo flows: browse abandonment, cart abandonment, and checkout abandonment. Each flow is triggered by specific events. These flows generally rely on client-side tracking. To leverage Elevar’s server-side tracking, you need to clone your existing flows, adjust the triggers, and modify the rules to exclude customers who are already part of your client-side flows.

  • Browse Abandonment: Triggered by Viewed Product
  • Cart Abandonment: Triggered by Added to Cart
  • Checkout Abandonment: Triggered by Started Checkout

Elevar provides three types of data triggers for Klaviyo:

  • Category View: Elevar SS
  • Viewed Product: Elevar SS
  • Added to Cart: Elevar SS

For optimal results:

  • Use Viewed Product: Elevar SS for the server-side browse abandonment flow.
  • Use Added to Cart: Elevar SS for the server-side cart abandonment flow.

After configuring these, you should have four distinct flows, utilizing both client-side and server-side triggers:

  • Client-Side Browse Abandonment Flow: Triggered by Viewed Product
  • Client-Side Cart Abandonment Flow: Triggered by Added to Cart
  • Server-Side Browse Abandonment Flow: Triggered by Viewed Product - Elevar SS
  • Server-Side Cart Abandonment Flow: Triggered by Added to Cart - Elevar SS

Creating a Custom Report to Analyze Performance:

To evaluate the performance and revenue generated by your Klaviyo flows, follow these steps to create a custom report:

  • Navigate to "Custom Reports" in your Klaviyo admin panel and create a new custom report.
  • Set the Report Type to "Flows Performance Report".
  • Name the report "Revenue by Flow".
  • Configure the Conversion Metric to "Placed Order" + "Value" + "SUM".
  • Group the data by "Flow".
  • Set the Timeframe to "Sent in Last 30 Days" and choose "Entire Range".
  • Your final selections should match this setup: Example Screenshot.

Click "Save & Run Report" and review the "Total Placed Order Value" column to analyze the conversion value generated by each flow on a monthly basis. This will help you assess the additional revenue generated from Elevar’s server-side triggers for browse and cart abandonment flows.

πŸ‘

Prefer to Watch A Video?


Learn how to take advantage of your Klaviyo server-side event tracking to increase your Abandoned Flow revenue

Before analyzing pre/post performance, there are a few steps inside of your Elevar settings to deploy Klaviyo server-side tracking and the remainder of the steps will be managed in Klaviyo.

Ensure You Are on Elevar's Shopify Source:

  • In My Tracking > Sources > Find the Shopify Source. If you are not on our Shopify source, follow our Upgrade guide to bring your account to the latest data layer version.

Step 1 screenshot

Create Segments to View Difference:

  • Once you go live you may want to see the additional users who would enter your Flows with Elevar's tracking.
  • You can do this by creating two segments:
    • Add to Cart -- Legacy Event: this will show users that are included in your pre-existing add to cart event
    • Add to Cart - Combined: this shows users who match either of the above. This provides the total # of users that could enter a matching Flow.

  • To get the potential difference using the screenshot above: 18,294 / 14,689= 1.24
  • This means the combined segment has 24% more users that would enter a flow triggered off of this.
  • You can repeat this step for your Viewed Product Events as well.
  • These segments are just used as example data points. You can keep or remove them when you're done.

Configure Flows:

  • To see the difference in revenue and validate Elevar's performance, here's how to create your flows.
  • Go to Flows.
  • Then look for a Flow that is using the Added to Cart event as a trigger which you can see here:

  • Once inside the Flow then you can also see the trigger here:

  • Now we want to create a Clone of this flow that will only trigger IF the user does not trigger your pre-existing flow.
  • Go back to your Flows page and click "Clone" on your pre-existing flow:

  • Then when the Clone window pops up select the Elevar add to cart event as shown here and update the name of flow:

  • Hit Clone Flow.
  • Now inside the Flow add one additional flow filter to filter out users who will hit your pre-existing flow:

  • Be sure to filter out your legacy event -- not the Elevar server-side event.
  • You now have a new flow that can operate in parallel with your pre-existing flow.

πŸ“˜

You don't need to use two dual flows -- this is just so you can validate the server-side events works and quantify the additional revenue

Validate Flow Filters and Product Data:

  • It's possible you are using filters in your flows that rely on product data from the event.
  • For example you have a Trigger Split based on a product name.
  • If this is indeed the case then click into the Trigger Split and update as needed:

QA Emails:

  • Are your emails pulling in dynamic product data? Or are they more generic abandoned recovery emails?
  • If dynamic product data you may also want to double check emails that are using dynamic properties are being populated with the proper data.
  • Here's how to view the properties in Metrics Report > Activity Feed:

πŸ‘

Have any questions? Just let us know!