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 typically powered by client side tracking and events, and Elevar can help boost performance of the flows with our server side tracking of events and session enrichment.

❗️

Email Capture Pop-Up Integration for Elevar:

To ensure that Elevar enhances the performance of your browse, cart, and checkout abandonment flows, we need to capture the dl_subscribe event when customers submit their email address through the email capture pop-up on your homepage.

• Native Pop-Up Support: If you are using Klaviyo, Attentive, or Postscript native pop-ups, Elevar supports them out of the box, and no additional action is required.
• Third-Party Pop-Ups: For pop-ups from platforms like Amped.io, ConvertFlow, Justuno, or any other third-party email capture solutions, you will need to add extra code to the pop-up to ensure compatibility with Elevar’s data layer.

Follow this guide to learn more information on email sign up tracking!

To leverage Elevar’s server-side tracking and boost performance of the browse, cart and checkout abandonment flows is a 4 step process:

1. Clone each existing client side flow to create a server side version.
2. Change the trigger on the newly created server side flow to use Elevar's server side trigger.
3. Add a profile filter to the newly created server side flow to exclude customers who are already enrolled in the equivalent client side flow.
4. Create a custom report to view the performance of the client side flows and boost in performance from the server side flows powered by Elevar.

The standard triggers for the flows are:

• Browse Abandonment: - "Viewed Product"
• Cart Abandonment: - "Added to Cart"
• Checkout Abandonment: - "Started Checkout"

The Elevar server side event triggers to use for the cloned flows are:

• Browse Abandonment: - "Viewed Product- Elevar SS"
• Cart Abandonment: - "Added to Cart - Elevar SS"
• Checkout Abandonment: - "Begin Checkout - Elevar SS"

After cloning each flow and changing the trigger on the cloned flow, you should have at minimum 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"

Once each flow is cloned, and the trigger is changed to the Elevar server side equivalent, the last step is to add in a profile filter to exclude customers from enrolling in the server side flow if they were already enrolled in the equivalent client side flow.

• Elevar Server Side Browse Abandonment Flow Profile Filter
  • (See Figure 1)

_Figure 1_

• Elevar Server Side Cart Abandonment Flow Profile Filter Example
  • (See Figure 2)

_Figure 2_

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".
  • (See Figure 3)

_Figure 3_

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.

In the example screenshot above, each of the flows in the flows section of the Klaviyo admin was tagged with "Elevar", Then when selecting to run the report, an additional filter was added based on tag "Elevar". Now when the report is generated, it's easier to see the performance of the client side flows directly against the boost in performance from Elevar's server side flows.

👍

Prefer to watch a video?

Follow this video from one of our customer success leaders at Elevar for a step by step guide on how to set up browse and cart abandonment flows in Klaviyo!

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.
  • (See Figure 4)

_Figure 4_

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.
    • (See Figure 5)

_Figure 5 _

• 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.
  • (See Figure 6)

_Figure 6 _

• Once inside the Flow then you can also see the trigger.
  • (See Figure 7)

_Figure 7 _

• 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.
  • (See Figure 8)

_Figure 8 _

• Then when the Clone window pops up select the Elevar add to cart event as shown here and update the name of flow.
  • (See Figure 9)

_Figure 9 _

• Hit Clone Flow.
• Now inside the Flow add one additional flow filter to filter out users who will hit your pre-existing flow.
  • (See Figure 10)

_Figure 10 _

• 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.
  • (See Figure 11)

_Figure 11_

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.
  • (See Figure 12 and 13)

_Figure 12_

_Figure 13_

👍

Have any questions? Just let us know!