Before you continue...
Make sure you first attempt to follow the steps outlined in this guide.
The steps outlined in this article are really to be used in a small number of cases where:
Our configuration wizard wasn't able to automatically configure a Sonar powered version of your standard flow (it hit an error) which means you have to clone the flow manually.
You want to retain full control over how these flows are configured and handing over that power to an auto-configure button in our platform isn't something you're comfortable with.
For all other situations we recommend going through the auto-configure wizard since it will automatically account for any issues that could arise (ex: Klaviyo not integrated, Triple Pixel not installed properly, etc.).
Overview
Sonar Send lets you run Triple Pixel–powered browse/cart/checkout flows in parallel with your existing Klaviyo “Standard Event” flows - without double-sending - to capture targetable site activity that would have been otherwise missed by Klaviyo.
Step-by-Step Guide
Step 1 - Which flow should you duplicate?
Identify each of your Standard Event flows (if you have them).
Browse Abandonment Flow: Purpose is to engage customers who visited your site, viewed your product(s), but then didn’t add to cart, start checkout, or make a purchase.
Abandoned Cart Flow: Purpose is to engage customers who visited your site, viewed your product(s), added >1 to their cart, but didn’t start checkout or make a purchase.
Abandoned Checkout Flow: Purpose is to engage customers who visited your site, viewed your product(s), added >1 to their cart, and started checkout, but didn’t finalize their purchase.
For those of you who would rather watch step-by-step videos for each flow you'll find those here!
Step 2 - Clone this flow
In Klaviyo → Flows, open the … menu for the Standard flow you’ve identified.
Click Clone.
Update [Flow Name] to include “(TW)” or “(Sonar)” so that they are easily identified.
Change [Trigger] to the Triple Pixel metric:
Browse = “Viewed Product – Triple Pixel”
Cart = “Added to Cart – Triple Pixel”
Checkout = “Checkout Started – Triple Pixel”
Click Clone Flow.
Step 3 - Increase Wait Time Block (+15)
Immediately after the trigger, add 15 minutes to the first time delay so your “Received Email/SMS = 0 since starting this flow (where Flow = Standard flow)” filters can evaluate true and avoid a “race condition.”
If the standard flow waits 30 min, set the TW flow to 45 min.
If the standard flow waits 4 hr, set the TW flow to 4 hr 15 min.
Step 4 - Update SMS/Email Titles
Rename each message so reporting clearly shows Sonar-driven sends. You do this by opening each email or SMS in the flow and append (TW) or (Sonar) to the end of the message name
Example:
Before = “Abandoned Cart: Email #1”
After = “Abandoned Cart: Email #1 (TW)”
Step 5 - Update Profile Filters
The most important step here is to update the various profile filters used in the Sonar version of your flow. This is where we ensure that profiles that enter and receive emails from the standard version of your flow, don’t also receive emails from the Sonar-powered versions we’re creating.
Broadly speaking there are three sets of filters to add on top of the filters copied over from the Standard Flow.
Exclude anyone who already received messaging (email or SMS) from the Standard Flow
Preventing send overlap between your Standard and Sonar flows. If you aren't running SMS, then you don't have to add SMS filters to your Sonar-powered flows.
Exclude anyone who triggered the non-Sonar version of your trigger event
An additional way to prevent send overlap between your Standard and Sonar flows.
Exclude anyone who progressed further down the funnel
Stops a higher-funnel flow (like Abandoned Browse) from sending to a profile who’s already taken the down-funnel next step (ex: Add to Cart or Checkout); according to both Klaviyo or Sonar.
Keep your original Standard filters (e.g., Placed Order = 0, Not in flow in last 30 days). Then add the following profile filters to each flow:
Profile Filters to add for “Abandoned Browse (TW)” Flow
Profile Filters to add for “Abandoned Browse (TW)” Flow
By adding these filters, our desired outcome is that...
...anyone who got an email or SMS from the standard Browse Abandonment flow, added something to their cart, started checkout, or who only trigger the standard “Viewed Product” metric, will not enter the Sonar-powered Browse Abandoned flow.
Filter #1: User has not received email message from standard flow.
Filter #1: User has not received email message from standard flow.
Filter #2: User has not received SMS message from standard flow.
Filter #2: User has not received SMS message from standard flow.
Filter #3: User has not triggered the standard version of the event.
Filter #3: User has not triggered the standard version of the event.
Filter #4: User has not triggered the Sonar versions of the down-funnel events.
Filter #4: User has not triggered the Sonar versions of the down-funnel events.
In this case this would be ”Added to Cart - Triple Pixel” and “Checkout Started - Triple Pixel”.
Profile Filters to add for “Abandoned Cart (TW)” flow
Profile Filters to add for “Abandoned Cart (TW)” flow
By adding these filters our desired outcome is that...
...anyone who got an email or SMS from the standard Abandoned Cart flow, started checkout, or who triggered the standard “Added to Cart” metric, will not enter the Sonar-powered Abandoned Cart flow.
Filter #1: User has not received email message from standard flow.
Filter #1: User has not received email message from standard flow.
Filter #2: User has not received SMS message from standard flow.
Filter #2: User has not received SMS message from standard flow.
Filter #3: User has not triggered the standard version of the event.
Filter #3: User has not triggered the standard version of the event.
Filter #4: User has not triggered the Sonar versions of the down-funnel event(s).
Filter #4: User has not triggered the Sonar versions of the down-funnel event(s).
In this case, this would be the user has not triggered the "Checkout Started - Triple Pixel" event.
Profile Filters to add for “Abandoned Checkout (TW)” Flow
Profile Filters to add for “Abandoned Checkout (TW)” Flow
By adding these filters our desired outcome is that...
...anyone who got an email or SMS from the standard Abandoned Checkout flow, or who triggered the standard “Checkout Started” metric, will not enter the Sonar-powered Abandoned Checkout flow.
Filter #1: User has not received email message from standard flow
Filter #1: User has not received email message from standard flow
Filter #2: User has not received SMS message from standard flow
Filter #2: User has not received SMS message from standard flow
Filter #3: User has not triggered the standard version of the event
Filter #3: User has not triggered the standard version of the event
Step 6 – Confirm accurate dynamic content in your messages
Before finishing setup, you need to ensure that dynamic content in your Emails or SMS renders correctly. While Sonar events are designed to mirror Klaviyo’s standard event schema, it’s still important to verify:
✅ Product names and images display correctly
✅ Prices show the correct amount + currency
✅ Links click through to the right product or cart page
✅ Any survey-based personalization fields populate as expected
This is mostly a spot-check process. If you’ve added any custom configurations, you may need to adjust how the event data maps into your message templates.
Here's a quick reference sheet for these dynamic variables, should you get stuck.
Step 7 - Setting your Sonar-powered flows “Live”
If you followed all the above steps, your Sonar-powered flows are now ready to be set to Live! Quick reminder, but keep your Standard Event flows ON. The TW flows are designed to run in parallel with the Standard ones; your filters and the additional +15 min wait time you added prevent collisions between the two.
Conclusion
By following the steps above, you’ve created Sonar-powered flows in Klaviyo that work in parallel with your existing Standard flows—eliminating double sends, preventing audience overlap, and ensuring cleaner attribution in both Triple Whale and Klaviyo. With the correct profile filters, adjusted wait times, and clear naming conventions, you’ll have a streamlined setup that’s easy to maintain and scale.
From here, monitor your Sonar-powered flows closely during the first few sends to confirm that filters are working as intended. Continue to refine based on performance data, and keep your Standard flows active so you always have a baseline for comparison. Over time, this dual-flow approach will help you maximize engagement while leveraging the precision of Triple Pixel tracking