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

General Overview to Set-up Flows & Analyze Performance

Generally speaking merchants are using two or three of the following flows: browse abandonment, cart abandonment and checkout abandonment. Every Klaviyo flow uses a trigger: for browse abandonment it's "Viewed Product", for cart abandonment it's "Added to Cart" and for checkout abandonment it's "Started Checkout".

These flows are powered based on client side tracking. In order to take advantage of Elevar's server side tracking to power your Klaviyo flows, it requires you to clone your existing flows, change the triggers, and update the rules for each flow to not include customers who have enrolled in your client side flows.

Elevar sends three different types of data to Klaviyo with the following triggers: "Category View - Elevar SS", "Viewed Product - Elevar SS", and "Added to Cart - Elevar SS". For the browse abandonment flow we most commonly see the trigger used be "Viewed Product - Elevar SS". For the cart abandonment flow we most commonly see the trigger used be "Added to Cart - Elevar SS".

Once complete you should have 4 separate flows for browse and cart abandonment using the respective client and server side triggers:

  1. "Viewed Product" - Client Side Browse Abandonment Flow
  2. "Added to Cart" - Client Side Cart Abandonment Flow
  3. "Viewed Product - Elevar SS" - Server Side Browse Abandonment Flow
  4. "Added to Cart - Elevar SS" - Server Side Cart Abandonment Flow

Once those 4 flows are set-up, then it's possible to create a custom report to view the performance and revenue generated from all of your Klaviyo flows following the steps below:

  1. Within your Klaviyo admin, go to "custom reports" and build a new custom report.
  2. Set the Report Type to be "Flows Performance Report".
  3. Report Name - Revenue by Flow
  4. Conversion Metric: "Placed Order" + "Value" + "SUM"
  5. Grouped by "Flow"
  6. Timeframe "Sent in Last 30 Days" by "Entire Range".

When you're done, all of your selections will look like this here: https://www.awesomescreenshot.com/image/44946526?key=9ec2b8f250195e017bf9f62fef1ba8aa

Then you can "Save & Run Report" and look to the "Total Placed Order Value" column to see the conversion value generated by each flow on a monthly basis. That way, you'll be able to see the additional revenue that Elevar is generating for you a monthly basis from the Browse and Cart Abandonment flows that work based on the Elevar specific triggers.

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.

Step 1: Ensure you're 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 2: 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:

  1. Add to Cart -- Legacy Event: this will show users that are included in your pre-existing add to cart event
  2. 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.

Step 3: 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

Step 4: Validate Flow Filters & 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:

Step 5: 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.