This guide walks you through creating Omnisend automations powered by Triple Pixel events. By duplicating your existing Omnisend automations and replacing triggers with Triple Pixel counterparts, you can run both versions side by side—letting you measure incremental lift while capturing up to 40% more events than standard client-side tracking.
How It Works
Triple Whale's Sonar Send delivers server-side events to Omnisend as custom events. You'll create a parallel version of your existing automations using these events as triggers, then configure exit conditions and contact skipping rules to prevent overlap and ensure clean attribution.
The naming convention -- triple_pixel at the end of each automation name allows you to track performance and compare results against your original Omnisend automations directly in Triple Whale.
Before You Begin
Make sure:
Sonar Send is connected to Omnisend and actively sending events
You've enabled the relevant events in your Sonar configuration
Your original Omnisend automations are active and working
Available Triple Pixel Events
Omnisend Native Event | Triple Pixel Counterpart |
Viewed Product | Viewed Product - Triple Pixel |
Added to Cart | Added to Cart - Triple Pixel |
Started Checkout | Checkout Started - Triple Pixel |
Active on Site | Active on Site - Triple Pixel |
Step-by-Step Setup
Step 1: Copy Your Existing Automation
In Omnisend, navigate to Automations and find the automation you want to duplicate (for example, your Browse Abandonment or Cart Abandonment automation).
Click the Copy button to create an exact duplicate of the automation.
Step 2: Rename the Automation
Open the copied automation and update the name by adding triple_pixel at the end.
Examples:
Browse Abandonment -- triple_pixelCart Abandonment -- triple_pixelCheckout Abandonment -- triple_pixel
This naming convention is essential for tracking incremental lift in Triple Whale's reporting.
Step 3: Replace the Trigger with a Triple Pixel Event
Click on the trigger block and change it from the native Omnisend event to its Triple Pixel counterpart.
Select Custom Event as the trigger type, then choose the appropriate Triple Pixel event from the list.
Step 4: Configure Exit Conditions
Add exit conditions to ensure contacts leave the automation when they progress further down the funnel. Omnisend allows a maximum of 4 exit conditions per automation.
For Browse Abandonment (-- triple_pixel): Include exit conditions for:
Added to Cart - Triple Pixel
Viewed Product (native Omnisend event)
Placed Order
Added to Cart (native Omnisend event)
For Cart Abandonment (-- triple_pixel): Include exit conditions for:
Checkout Started - Triple Pixel
Placed Order
Started Checkout (native Omnisend event)
Add to cart (native Omnisend event)
For Checkout Abandonment (-- triple_pixel): Include exit conditions for:
Placed Order
Order Confirmed
Started Checkout (native Omnisend event)
The goal is to exclude all automations that are equal or further down the funnel from the trigger event.
Step 5: Configure Contact Skipping Rules
Use Omnisend's "Skip contacts who are currently in or have recently completed other automations" feature to prevent overlap and duplicate messaging.
Exclude the following automations:
The Triple Pixel version itself — Prevent re-entry into the same automation
The native Omnisend alternative — Exclude contacts in the original (non-Triple Pixel) version of the same automation
All down-the-funnel automations — Both Triple Pixel and native versions
Example for Cart Abandonment (-- triple_pixel):
Exclude contacts who are in or recently completed:
Cart Abandonment (native Omnisend)
Cart Abandonment -- triple_pixel
Checkout Abandonment (native Omnisend)
Checkout Abandonment -- triple_pixel
Post-Purchase (if applicable)
This ensures contacts only receive one abandonment message per session, regardless of which tracking method captured their activity.
Step 6: Replace Attributes in Universal Content
If your automation uses dynamic content blocks (universal content) that pull in product or customer attributes, update them to use Triple Pixel attribute equivalents where applicable.
Common attributes to check:
Original Attribute | Triple Pixel Attribute |
Product Name | [[item.productTitle]] |
Product Image | [[item.productImageURL]] |
Product Price | [[item.productPrice]] |
Checkout URL | [[event.abandonedCheckoutURL]] |
Review each email or SMS block in your automation and ensure the dynamic content pulls from the correct event properties.
Step 7: Activate the Automation
Once you've completed all configuration steps:
Review the trigger, exit conditions, and skip rules
Test with a sample contact if possible
Click Start Workflow to activate
Your Triple Pixel-powered automation is now running alongside your original Omnisend automation.
Automation Setup Summary
Browse Abandonment (-- triple_pixel)
Setting | Configuration |
Trigger | Viewed Product - Triple Pixel |
Exit Conditions | Added to Cart - Triple Pixel, Viewed Product (native), Placed Order, Added to Cart (native) |
Skip Contacts In | Browse Abandonment (native), Browse Abandonment -- triple_pixel, Cart Abandonment (both versions), Checkout Abandonment (both versions) |
Cart Abandonment (-- triple_pixel)
Setting | Configuration |
Trigger | Added to Cart - Triple Pixel |
Exit Conditions | Checkout Started - Triple Pixel, Placed Order, Started Checkout (native), Added to Cart (native) |
Skip Contacts In | Cart Abandonment (native), Cart Abandonment -- triple_pixel, Checkout Abandonment (both versions), Post-Purchase |
Checkout Abandonment (-- triple_pixel)
Setting | Configuration |
Trigger | Checkout Started - Triple Pixel |
Exit Conditions | Placed Order, Order Confirmed, Started Checkout (native) |
Skip Contacts In | Checkout Abandonment (native), Checkout Abandonment -- triple_pixel, Post-Purchase, Order Confirmation |
Why It Matters
Running Triple Pixel automations alongside your native Omnisend automations lets you capture customers that client-side tracking misses—typically 30-40% more events. The -- triple_pixel naming convention enables clear performance comparison in Triple Whale, so you can measure the incremental revenue generated by server-side tracking.
Best Practices
Keep both versions running. The goal is to capture incremental lift from events that native tracking missed, not to replace your existing automations entirely.
Use consistent naming. Always append -- triple_pixel exactly as shown. This enables accurate reporting and comparison in Triple Whale.
Review exit conditions carefully. Missing an exit condition can result in customers receiving messages after they've already converted.
Check skip rules regularly. As you add new automations, update the skip rules in your Triple Pixel versions to prevent overlap.
Monitor performance in Triple Whale. Use Sonar's Delivery Overview to track how much incremental revenue your Triple Pixel automations are generating compared to native flows.
Troubleshooting
Automation not triggering?
Confirm Triple Pixel events are enabled in Sonar Send settings
Check that the automation is active (not paused)
Verify the contact has a valid email or phone number in Omnisend
Customers receiving duplicate messages?
Review your skip rules—ensure both native and Triple Pixel versions of related automations are excluded
Check exit conditions are properly configured
Verify you're not running the same automation type twice without skip rules
Dynamic content not populating?
Confirm the attribute names match what Triple Pixel sends
Check that the event is passing the expected properties
Test with a known contact to verify data flow
Can't find Triple Pixel events in trigger list?
Verify Sonar Send is connected and active
Ensure events are enabled in your Sonar configuration
Wait a few minutes after initial setup for events to appear