How to setting up Klaviyo's browse and cart abandonment flows
Enhance the performance of Klaviyo's flows using our server-side tracking
Setting up Klaviyo's flows with TagFly
Merchants commonly utilize two or three of these Klaviyo flows: browse abandonment, cart abandonment, and checkout abandonment. These flows are generally driven by client-side tracking and events. TagFly can enhance the performance of these flows by implementing our server-side tracking of events and enriching sessions.
To enhance the performance of browse, cart, and checkout abandonment flows using TagFly's server-side tracking, follow these streamlined steps:
Duplicate Existing Flows: Create server-side versions by cloning each client-side flow.
Update Triggers: Switch the trigger on the new server-side flows to TagFly's server-side trigger.
Implement Profile Filters: Add filters to the server-side flows to exclude customers already enrolled in the corresponding client-side flows.
Develop Custom Reports: Construct reports to analyze and compare the efficiency of client-side flows against the enhancements from TagFly-powered server-side flows.
Standard Flow Triggers:
Browse Abandonment: "Viewed Product"
Cart Abandonment: "Added to Cart"
Checkout Abandonment: "Started Checkout"
TagFly Server-Side Event Triggers:
Browse Abandonment: "Viewed Product - TagFly SS"
Cart Abandonment: "Added to Cart - TagFly SS"
Checkout Abandonment: "Begin Checkout - TagFly SS"
After duplicating and updating the triggers, ensure you have at least four distinct flows:
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 - TagFly SS"
Server-Side Cart Abandonment Flow: Triggered by "Added to Cart - TagFly SS"
Finally, ensure to include a profile filter in the server-side flows to prevent customers from being enrolled in both the server-side and client-side flows, maintaining exclusivity in flow participation.
Configuring flows
To evaluate the revenue impact and confirm the effectiveness of TagFly's performance, follow these steps to set up your flows:
Navigate to the Flows section.
Next, locate a flow that uses the "Added to Cart" event as its trigger.
Next, we aim to create a clone of this flow that activates only if the user doesn't trigger your existing flow. Click "Clone" on your existing flow.
When the Clone window appears, select the "Added to Cart - TagFly SS" event as shown, and update the name of the flow accordingly.
Click "Clone Flow." Once inside the flow, add an additional filter to exclude users who will trigger your existing flow.
Ensure that you filter out your legacy event, not the TagFly server-side event.
You now have a new flow that can run alongside your existing flow.
There's no need to maintain two dual flows; this setup is simply to verify that the server-side events function correctly and to measure the additional revenue generated.
Setting up Klaviyo's flows with TagFly
Merchants commonly utilize two or three of these Klaviyo flows: browse abandonment, cart abandonment, and checkout abandonment. These flows are generally driven by client-side tracking and events. TagFly can enhance the performance of these flows by implementing our server-side tracking of events and enriching sessions.
To enhance the performance of browse, cart, and checkout abandonment flows using TagFly's server-side tracking, follow these streamlined steps:
Duplicate Existing Flows: Create server-side versions by cloning each client-side flow.
Update Triggers: Switch the trigger on the new server-side flows to TagFly's server-side trigger.
Implement Profile Filters: Add filters to the server-side flows to exclude customers already enrolled in the corresponding client-side flows.
Develop Custom Reports: Construct reports to analyze and compare the efficiency of client-side flows against the enhancements from TagFly-powered server-side flows.
Standard Flow Triggers:
Browse Abandonment: "Viewed Product"
Cart Abandonment: "Added to Cart"
Checkout Abandonment: "Started Checkout"
TagFly Server-Side Event Triggers:
Browse Abandonment: "Viewed Product - TagFly SS"
Cart Abandonment: "Added to Cart - TagFly SS"
Checkout Abandonment: "Begin Checkout - TagFly SS"
After duplicating and updating the triggers, ensure you have at least four distinct flows:
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 - TagFly SS"
Server-Side Cart Abandonment Flow: Triggered by "Added to Cart - TagFly SS"
Finally, ensure to include a profile filter in the server-side flows to prevent customers from being enrolled in both the server-side and client-side flows, maintaining exclusivity in flow participation.
Configuring flows
To evaluate the revenue impact and confirm the effectiveness of TagFly's performance, follow these steps to set up your flows:
Navigate to the Flows section.
Next, locate a flow that uses the "Added to Cart" event as its trigger.
Next, we aim to create a clone of this flow that activates only if the user doesn't trigger your existing flow. Click "Clone" on your existing flow.
When the Clone window appears, select the "Added to Cart - TagFly SS" event as shown, and update the name of the flow accordingly.
Click "Clone Flow." Once inside the flow, add an additional filter to exclude users who will trigger your existing flow.
Ensure that you filter out your legacy event, not the TagFly server-side event.
You now have a new flow that can run alongside your existing flow.
There's no need to maintain two dual flows; this setup is simply to verify that the server-side events function correctly and to measure the additional revenue generated.
Updated on: 01/12/2024
Thank you!