Skip to main content

Comparisons

How to Switch From Triple Whale Without Losing Tracking: Sonar, Your Reports and the 12-Month Term

Switching from Triple Whale means moving two jobs: Sonar, which sends server-side events to Meta, other ad platforms and Klaviyo, and the attribution reporting. Move Sonar's sends in one short cutover so Meta never counts an order twice, run the reports side by side for a few weeks, and time it all to your contract. Paid plans are 12-month subscriptions, and Triple Whale asks for 30 days' notice to cancel.

If you haven't picked a replacement yet, our Triple Whale alternatives guide compares nine. This guide covers the move itself: whether to replace all of Triple Whale or part of it, when you can cancel, what to export, how to move Sonar's events and flows, how to keep your reporting history, where the Triple Pixel leaves code, and what to check afterwards. Upstack is our product and covers both jobs, but the steps for turning Triple Whale off work whatever you move to. We checked Triple Whale's pricing page and help center, and Meta's developer pages, on October 24, 2026.

Should you replace Triple Whale, or only part of it?

Start with what you use. Triple Whale is a large platform, and Upstack, like most replacements, covers only part of it. Stay on Triple Whale if you rely on:

  • Moby's automations and actions in your ad accounts. Upstack has no AI agent like Moby.
  • Marketing mix modeling or incrementality tests through Compass. Upstack offers neither.
  • Total Impact, the model that weights channels with post-purchase survey answers. Upstack's Attribution has three click-based models: first click, last click and any click.

You can also split the move. Triple Whale's own Meta setup guide describes running another Conversions API provider for standard events while Sonar sends only its attribution passback. So you can move server-side events to a new tool now and decide about the reporting at renewal.

Our take. Many brands use Triple Whale for two things: the dashboard they check each morning and the server-side events Meta optimizes on. If that's you, the switch is worth planning. If your team lives in Moby or Compass, keep Triple Whale and fix the events underneath it.


When can you cancel Triple Whale?

Contract timing decides the rest of the plan, so start here. Triple Whale's pricing FAQ says Foundation, Automate and Enterprise are 12-month subscriptions, billed monthly or annually. Its billing help article adds three things:

  • No pause mid-contract. If you signed up with a 12-month contract, you can't pause the subscription during it.
  • 30 days' notice. Cancellation needs 30 days' notice. Access and billing continue through the notice period, then the subscription ends.
  • Price follows revenue. Pricing is based on your Order Revenue over the last 365 days.

So the date that matters is the end of your current term. Ask Triple Whale support to confirm it in writing, then work backwards:

WhenWhat to do
About 8 weeks before the term endsConfirm the end date; export reports; install the new tool and let it collect
About 6 weeks beforeMove Sonar's ad platform sends to the new tool in one cutover
6 to 2 weeks beforeRun the reports side by side; move the Klaviyo flows
At least 30 days beforeSend the cancellation notice
When the term endsRemove the Triple Pixel and uninstall the app

The same help article says brands that aren't on a 12-month contract can downgrade to the free plan, which it calls Founders Dash, and keep their tracked data. Ask whether that applies at the end of your term before you cancel outright.


What should you record and export first?

What to recordWhereWhy it matters
The attribution model and window you report onTriple Whale's attribution settings; the default window is 28 days, per its attribution model guideYou'll compare the new tool against it like for like
Channel and campaign results for recent monthsYour dashboards; CSV export is on every planNo new tool can rebuild click journeys from before its own pixel was installed
The cost settings behind profit reportingTriple Whale settingsYou'll re-enter product costs, shipping and fees in the new tool
Sonar Optimize settings for each ad platformData > Sonar Enrichment > IntegrationsWhich standard events, custom events, attribution passback and profit optimization each platform gets
Campaigns using Meta's Custom AttributionAds ManagerThey optimize on attribution Triple Whale passes back, which stops with Sonar
Sonar Send flowsKlaviyo flows named "(TW)" or "(Sonar)"They stop getting entries when Sonar Send stops
A baseline weekShopify online orders, Meta's Purchase count and Event Match QualityYou need a before to judge the after

Sources: Triple Whale's Sonar Optimize overview, Meta setup guide and plan comparison, checked October 24, 2026.


How do you move Sonar's events to the new tool?

Sonar Optimize sends server-side events to ten ad platforms, among them Meta, Google Ads, TikTok, Snapchat and Pinterest, and can pass Triple Whale's attribution back to Meta. Moving those sends keeps your pixel. As we put it on onboarding calls, "You're just switching the sender of the data, not the actual pixel itself." The pixel's audiences and your ad sets' learning stay put; our guide to moving campaigns to a new Meta pixel explains why a new sender isn't a new pixel.

What you can't do is leave both sending. Triple Whale's Meta guide tells you to turn off another tool's overlapping server-side sends before switching on Sonar's, and the same applies in reverse. Meta deduplicates two events only when the event names match and the pixel's eventID matches the server's event_id, and it discards a repeat only when the same pair reaches the same pixel within 48 hours. Sonar tags its events to match the browser pixel's, but a new tool's events carry their own IDs. While both send Purchase to one pixel, Meta counts most orders twice.

Pick one of two ways:

  • Compare first. Point the new tool at a separate test dataset, or keep its Meta destination inactive, and compare match rates and new-customer counts for a week or two. Meta's developer docs say events sent with test_event_code are not dropped, so a test code on your live pixel isn't a sandbox.
  • A short overlap. Run both for two or three days at most, make no decisions on those days' numbers, and judge the new tool on full weeks after cutover.

To turn Sonar off for Meta, go to Data > Sonar Enrichment > Integrations, open the Meta row with View, and under Integration Settings switch off the standard events, the custom events and attribution passback, then use Disconnect under the connection overview. Repeat for each platform Sonar sends to, in the same sitting that the new tool's destination for that platform goes live.

Two settings need a decision before cutover:

  • Sonar's custom events. Sonar can send New Customer Purchase, Return Customer Purchase, Initial Subscription Order and events you define. If an ad set optimizes on one, the new tool has to send an equivalent, and pointing the ad set at a different event counts as a significant edit: Meta lists any change to optimization event as one, and it restarts learning.
  • Meta Custom Attribution. Triple Whale's Custom Attribution guide describes campaigns that optimize on attribution Sonar passes back. When Sonar stops, those campaigns lose that input, so list them and decide their attribution setting first.

If Upstack is the replacement, onboarding is managed: we set it up with you on a call, setup takes under 20 minutes, and we turn off the old sender so nothing double counts. Upstack Signal sends Meta, Google, TikTok and Klaviyo events with each visitor resolved against our identity graph of 750M+ devices and 150M+ customers.


How do you replace Sonar Send in Klaviyo?

Sonar Send feeds Triple Pixel events to Klaviyo, Attentive and Omnisend. Triple Whale's Klaviyo flow guide has you clone your browse, cart and checkout abandonment flows, add "(TW)" or "(Sonar)" to their names, and trigger them on "Viewed Product – Triple Pixel", "Added to Cart – Triple Pixel" and "Checkout Started – Triple Pixel". Once Sonar Send stops, those flows stop getting entries.

Build the new tool's flows first, keep your standard Klaviyo flows on as Triple Whale's guide also advises, and switch the (TW) flows off once the new flows are receiving entries.

How do you move the reporting without losing history?

Run both tools side by side for two to four weeks. Compare order counts first, then channel totals, and use the same model and window in both, or the numbers won't line up: last click against last click, with the same lookback. Upstack Attribution reports against the revenue in your Shopify account rather than summing what each platform claims, with first click, last click and any click models, MER, new-customer ROAS and CAC, LTV and contribution margin from CM1 to CM4. It has nothing like Total Impact, so drop survey-weighted comparisons from the side-by-side.

For history, export what you'll want before access ends. Most tools can import past Shopify orders, but none can recover click journeys from before its own pixel was installed.


Where does the Triple Pixel leave code?

Triple Whale's uninstall guide and install guide list where the pixel can sit:

WhereWhat's thereHow to remove it
Theme app embedThe Triple Pixel app embedOnline Store > Themes > Customize > App embeds, toggle it off and save
theme.liquidThe pixel script, if you used Triple Whale's older Auto-InstallEdit code, delete the script; Triple Whale says Shopify no longer lets third parties edit theme files through its API, so this one is manual
Order status pageThe pixel snippet in Additional scriptsIn Triple Whale, Pixel Settings > Installation Status > Checkout > Uninstall, or delete it under Settings > Checkout
Post-purchase pageThe upsell snippet in Additional scriptsDelete it under Settings > Checkout
Shopify Customer eventsTriple Whale's Web Pixel ExtensionCheck Settings > Customer events after you uninstall the app
Pages outside your themeSnippets on landing page apps, third-party checkouts, headless storefronts, or GTM tags if the pixel went in through GTMRemove them by hand
SonarAd platform integrations and Klaviyo flowsAs in the two sections above

Sources: Triple Whale's help center, checked October 24, 2026.

Remove the pixel when the term ends, not before: while you're still paying, its reports are your comparison.


What should you check after cutover?

CheckWhereWhat you want to see
Purchase countEvents Manager, Purchase, against Shopify's online ordersAt or below your orders, never above
One server-side senderThe Purchase event's Event Deduplication tab and Sampled ActivitiesOne event ID format, from the new tool only
Match qualityEvent Match Quality on PurchaseAt or above your baseline after a few days
Shopify's Meta channelSales channels > Facebook & Instagram > data sharingOff, unless it's your only server-side sender
Custom Attribution campaignsAds ManagerNone still relying on Triple Whale's passback
KlaviyoFlow entriesThe new tool's flows receiving entries; (TW) flows off
ReportingThe new tool against ShopifyOrder counts that match Shopify for the same days

Triple Whale's guide suggests lowering Shopify's Facebook & Instagram data sharing to a browser-only level when Sonar sends server events. With Sonar gone, decide which tool sends what; our guide to Shopify's Facebook & Instagram data sharing explains each level and why the app double counts beside another server-side sender.


Frequently asked questions

How do I cancel Triple Whale?

Send your cancellation at least 30 days before your term ends. Triple Whale's billing help article says cancellation needs 30 days' notice, with access and billing continuing through it. Paid plans are 12-month subscriptions, so confirm your end date with support in writing and give notice before it.

Can I cancel Triple Whale before my 12-month term ends?

Triple Whale's pricing FAQ says Foundation, Automate and Enterprise are 12-month subscriptions, and its help center says you can't pause during a 12-month contract. Plan the move for renewal rather than paying for two tools.

Will turning off Sonar hurt my Meta campaigns?

Not if the new tool takes over Purchase on the same pixel in the same sitting. The pixel and its learning stay. The exceptions are ad sets that optimize on a Sonar custom event and campaigns using Custom Attribution, which both need a decision before cutover.

Can I keep Triple Whale and use another tool for the Conversions API?

Yes. Triple Whale's own guides describe keeping Sonar's standard-event toggles off while another provider sends standard events, so only one tool sends Purchase server-side. Some brands keep Triple Whale's dashboards and move only the events.


Key takeaways

  • Treat it as two moves: Sonar's server-side events in one short cutover, the reporting over two to four weeks.
  • Work back from your term end date: Triple Whale needs 30 days' notice, and paid plans run 12 months.
  • Never leave Sonar and the new tool both sending Purchase to one pixel for long; their event IDs don't match.
  • Decide about Sonar custom events and Custom Attribution campaigns before you turn Sonar off.

Compare Upstack with Triple Whale

If you're replacing Triple Whale mainly for attribution and the events Meta optimizes on, our Upstack vs Triple Whale comparison sets the two side by side, including what Triple Whale has that we don't.

About the author

Michael Alt

Founder & CEO, Upstack Data

Michael Alt is the founder and CEO of Upstack Data, the server-side tracking, identity resolution and attribution platform for Shopify and DTC brands.

Want similar results?

Start free for 21 days and see what clean signal does for your performance. No card, no contract.