Overview
Sonar Send lets you run Triple Pixel–powered browse/cart/checkout flows in parallel with your existing Attentive “Standard Event” flows - without double-sending - to capture targetable site activity that would have been otherwise missed by Attentive.
Journey Setup Walkthrough
Here’s how to build a typical Sonar-powered SMS journey in Attentive.
Step 1: Create a New Journey
In Attentive, go to Journeys > Create Journey > Start from Scratch
Find the Triple Whale labeled trigger (e.g. Added to Cart - Triple Whale) and select “Send a message about something else”. This ensures that the trigger sends to opted in marketing subscribers (and not transactional subscribers looking for updates to their order)
Click the three dots in the top right to re-name the journey. We recommend including a Triple Whale or TW in this journey title:
Step 2: Add Branching Logic and Wait Times
Adjust the “Wait” step to 15 minutes longer than your default flow
Copy over the existing branching logic from your default Attentive flows. Then add in Sonar specific exclusion branching. You should have the following:
Session Abandonment
Has viewed a product at least once since starting this journey > End Journey
Has received a text message (and/or email if you use Attentive for email) at least once since starting this journey where journey is:
Triple Whale Browse
Triple Whale Cart
Triple Whale Checkout
Standard Session
Standard Browse
Standard Cart
Standard Checkout
Browse Abandonment
Has added to cart at least once since starting this journey > End Journey
Has viewed a product at least once since starting this journey > End Journey: this will exclude anyone who entered the standard browse abandonment flow.
Has received a text message (and/or email if you use Attentive for email) at least once since starting this journey where journey is:
Triple Whale Cart
Triple Whale Checkout
Standard Browse
Standard Cart
Standard Checkout
Cart Abandonment
Has started checkout at least once since starting this journey > End Journey
Has added to cart at least once since starting this journey: this will exclude anyone who entered the standard cart abandonment flow.
Has received a text message (and/or email if you use Attentive for email) at least once since starting this journey where journey is:
Triple Whale Checkout
Standard Cart
Standard Checkout
Checkout Abandonment
Has made a purchase at least once since starting this journey > End Journey
Has received a text message (and/or email if you use Attentive for email) at least once since starting this journey where journey is:
Standard Checkout
Step 2: Edit Messages and adjust dynamic content
You’ll need to copy over each message within Attentive from your standard flow (e.g. copy over each message from your standard Cart Abandon to the new Triple Whale Cart journey)
Edit each message name in each journey to include a differentiator (e.g. Cart Abandon 1 - Triple Whale)
When copying over the messages, you’ll need to adjust the dynamic content that is pulling in from the events:
Click the { } button at the bottom of the message builder and select choose variable. Then click on “triggering event” to view and select the dynamic content from the Triple Whale captured events.
Step 4: Adjust Entry Frequency
Click on the Settings icon in the top right of the journey editor to control how often a user can enter this journey. Typically this is 24-48 hours, but up to you to customize:
Step 5: Activate the Journey
Turn the journey live by selecting “Turn On” in the top right hand corner
Once all the journeys are turned on edit session, browse, and cart TW flows to branch out the now turned on down the funnel TW flows
Monitor initial performance (open / click / conversion rates)
Adjust branching or timing as needed
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