Set up Klaviyo flows using Littledata triggers

Installation

1. Login into your Littledata account.
2. Follow this guide to set up the Klaviyo integration.

Configuring Abandoned Cart flows

To make use of the improved "Added to Cart - Littledata" event, you will need to clone an existing flow and then alter the triggers.

Additionally, it's important to update the rules for each flow, ensuring they exclude customers who are already part of your original (client-side) flows.

Once complete you should have 2 separate flows for cart abandonment using the respective Klaviyo and Littledata events:

• "Abandoned Cart Reminder" - Original Cart Abandonment Flow (using Klaviyo Client-side tracking)
• "Abandoned Cart Reminder - Littledata" - New Cart Abandonment Flow (using Littledata server-side tracking)

tip:

 Littledata's tracking schema is fully compatible with Klaviyo's Added to Cart and Checkout Started events. This means you don't need to remap any properties in your email templates.

If you are using custom triggers then consult Littledata's tracking schema to find and match the equivalent properties needed. 

Configuring Abandoned Checkout flows

Another type of flow that makes use of our server-side tracking is an Abandoned Checkout flow. This is basically a copy paste of the abandoned cart flow, but we'll use the "Checkout Started - Littledata" server-side event.

As for the abandoned cart flow, you will need to update rules for each flow and make a copy for each one, ensuring they exclude customers that are part of your original flows.

At the end, you should have 2 flows:

• Abandoned Checkout Reminder - The original flow using Klaviyo's client side tracking
• Abandoned Checkout Reminder - Littledata - The new flow, made using Littledata's server-side tracking.

Configuring Flows to use the new events

1. Accessing Flows:
   a. Start by navigating to the 'Flows' section in your dashboard.

   

2. Identify the Trigger Event:
   a. Locate the cart abandonment flow that is triggered by the 'Added to Cart' or 'Checkout started' event. This can typically be viewed in the flow's overview.

   

3. Creating a Clone of the Flow:
   a. Return to the main page of your 'Flows'.
   b. Find the flow that uses the 'Added to Cart' event as its trigger.
   c. Click on 'Clone' for the chosen flow.

   

4. Setting up the clone:
   a. In the clone setup window, select the 'Added to Cart - Littledata' as the new trigger.
   b. Rename the flow accordingly to differentiate it from the original.
   c. Confirm the settings by clicking on 'Clone Flow'.

   

5. Adding Flow filters:
   a. In the newly cloned flow, add the additional filter:
   b. This filter should be set to exclude users who are captured by your original flow;
   c. Make sure that the metric you choose for this filter is Klaviyo's Added to cart event and not Littledata's;

   note:

   • Condition: What someone has done (or not done)
   • Person has (metric): Added to cart
   • Frequency: zero times
   • Timeframe condition: since starting this flow

   

6. If you want to build an Abandoned Checkout flow, follow the first three steps of the flow explained above, and then:
   a. In the clone flow setup, select 'Checkout Started - Littledata' as the new trigger. Rename the flow accordingly so it differentiates from the other flows you already have

   

   b. Add the new filter in the newly created flow. It's very important to check that this is Klaviyo's event, not Littledata's. As a rule, our events are always sent with Littledata at the end of them.

   

The metric you choose in this step can differ based on the trigger in your original flow as explained in the table below. The other conditions should remain as specified above.

Original flow trigger	Added to Cart	Checkout Started	Placed Order
Littledata flow (clone) trigger	Added to Cart	Checkout Started	Placed Order

By completing these steps, you will have successfully set up a new flow. This flow will function alongside your existing one, allowing you to effectively compare and validate the performance of Littledata's server-side tracking.