Comparisons
How to Switch From Elevar Without Losing Tracking: What to Record, Where Elevar Leaves Code and When to Cancel
Switching from Elevar keeps your Meta pixel, its audiences and its learning, because only the sender changes. Record what Elevar sends, test the replacement on a separate dataset or run it beside Elevar for two or three days, then take Elevar's destinations offline and remove its code from your theme, Shopify's Customer events and Google Tag Manager. Cancel the plan inside Elevar last.
If you're still choosing a replacement, start with our Elevar alternatives comparison. This guide is the Elevar migration itself: what to record first, two ways to run the switch, where Elevar leaves code and how to remove each piece, what to check in Meta Events Manager and Shopify afterwards, and when to cancel. Upstack is our product and one of the tools you might move to, but every removal step below works whichever replacement you choose. We checked Elevar's help docs, its Shopify App Store listing and Meta's developer pages on October 24, 2026.
Should you switch from Elevar at all?
Not always. Elevar is a capable product with 4.8 stars from 170 reviews on the Shopify App Store, and a switch means real work plus a week of watching numbers. Stay if:
- Your team builds custom tags in Google Tag Manager on Elevar's data layer. A replacement without GTM takes that away.
- GA4 accuracy is the main job. Elevar sends server-side events to GA4. Upstack doesn't send to GA4 at all.
- Some of your destinations aren't on the replacement's list. Elevar's pricing page lists 46, including affiliate networks and BigQuery; check each one you use against the new tool.
- You're under 100 orders a month, where Elevar's Base plan is free.
Our take. Replace Elevar when the reason is structural: nobody maintains the GTM container, you pay for destinations you need but can't add on your plan, or you want shoppers recognized across devices rather than through one browser's cookie. A slightly lower invoice on its own rarely pays for the work.
What should you record before you switch from Elevar?
Write down what Elevar does today, including the settings it changed outside its own app. Most problems after a switch come from something nobody listed.
| What to record | Where to find it | Why it matters |
|---|---|---|
| Every destination and the events it receives | Elevar, under My Tracking | The replacement has to cover each one, or a channel goes quiet at cutover |
| Custom events, such as new and returning customer purchases | Elevar's destination settings and Meta Events Manager | Any ad set that optimizes on one needs the same event from the new tool |
| GTM tags, triggers and variables built on Elevar's data layer | Your GTM web container | They stop when Elevar's data layer does, and some may be tags you still need |
| Native pixels you switched off for Elevar | Shopify's sales channels and your theme's App embeds | Elevar's guides walk you through turning off Shopify's Meta, Google, TikTok and Pinterest pixels, and on GTM setups, Klaviyo's base snippet |
| Klaviyo flows triggered by Elevar events | Klaviyo flow triggers ending in "Elevar SS" | They stop getting entries once Elevar stops sending |
| A baseline week | Shopify online orders, Meta's Purchase count and Event Match Quality, Elevar's Channel Accuracy Report | You need a before to judge the after |
Sources: Elevar's guides to the cart abandonment flow, Klaviyo's base snippet and removing Elevar, checked October 24, 2026.
Pay most attention to custom events. Moving the sender doesn't touch your ad sets, but changing what an ad set optimizes on does: Meta lists any change to optimization event as a significant edit, which sends the ad set back into learning. If an ad set optimizes on an Elevar custom event, either have the new tool send an event with the same name, or plan the change as an edit and make it on a quiet week.
Will you lose Meta pixel learning when you replace Elevar?
No. A server-side tool sends events to your existing pixel's ID, so the pixel, its audiences and your ad sets' learning stay where they are. As we put it on onboarding calls, "You're just switching the sender of the data, not the actual pixel itself." Our guide to moving campaigns to a new Meta pixel covers the rare case where a brand does need a new pixel, and why a new sender isn't one.
Two things can still move. Reported purchases can change if the new tool matches more of them to people, and anything built on Elevar's custom events needs the care above.
How do you run the switch from Elevar?
There are two ways to do it. Both end with exactly one server-side sender on each pixel.
Compare first
Run the new tool without letting it touch your live pixel: point its Meta destination at a separate test dataset, or leave its destinations inactive and read its own dashboard. Compare match rates and new-customer counts on your own traffic for a week or two, then switch. Don't use Meta's test event code on the live pixel as a sandbox. Meta's developer docs say events sent with test_event_code are not dropped; they flow into Events Manager and are used for targeting and measurement.
A short overlap
Upstack's own migration guide runs both tools for two to three days, then removes Elevar. If you overlap, expect inflated numbers while it lasts. Meta deduplicates a browser event and a server event 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. Two different tools rarely share event IDs, so while Elevar and the replacement both send Purchase to one pixel, Meta counts most orders twice. Keep the overlap short, make no budget decisions on its numbers, and judge results on full weeks after cutover.
Cut over one destination at a time
Each Elevar destination has a Go Offline button (My Tracking, then the destination). Take Elevar's Meta destination offline in the same sitting that you switch the new tool's Meta destination on, then repeat for Google Ads, TikTok and Klaviyo.
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 resolves each visitor against our identity graph of 750M+ devices and 150M+ customers before the event leaves, needs no GTM container, and comes with a 21-day free trial and a 60-day 4x ROI guarantee.
Where does Elevar leave code, and how do you remove it?
Uninstalling the app doesn't remove everything. Elevar's removal guide and theme guide list where it puts code. Work through them in this order once the new tool is live:
| Where | What Elevar left | How to remove it |
|---|---|---|
| Elevar's destinations | Server-side sends to Meta, Google Ads, Klaviyo and the rest | My Tracking, open each destination, Go Offline, then Remove destination |
| Theme app embed | The Elevar app embed, on every theme it was enabled on | Online Store > Themes > Customize > App embeds, toggle Elevar off and save; repeat for each theme |
| Theme code | Four Elevar snippets, and three render tags in theme.liquid for elevar-head-listener, elevar-head and elevar-body-end | Edit code: delete the snippets, then the three render lines |
| Older installs | Code in Shopify Plus checkout.liquid, landing page templates such as Zipify or Shogun, and Order status page additional scripts | Search for the comments <!-- Begin Elevar --> and <!-- End Elevar -->; on older data layers, remove the scripts under Settings > Checkout |
| Shopify Customer events | The "Elevar - Checkout Tracking" app pixel | Settings > Customer events, open it and click Disconnect |
| Google Tag Manager | Tags, triggers and variables built on Elevar's data layer | Pause them, publish, and delete them once the new setup is confirmed |
| Klaviyo | Cloned flows triggered by Elevar's server-side metrics | Turn them off once the new tool's flows are running |
| The app | Elevar Conversion Tracking | Settings > Apps and sales channels > Uninstall, after you cancel the plan |
Sources: Elevar's removal, theme and legacy code guides, checked October 24, 2026.
Two cautions on Google Tag Manager. First, Elevar's removal guide warns that tracking you run through GTM stops working once Elevar is removed. List every tag in the web container and decide what replaces each one; Elevar's own suggestions are Shopify's native integrations, another app, hardcoded scripts, or GTM without Elevar's data layer. Second, Google says pausing a tag takes effect only after you save and publish, and the paused tag stays in the container, ready to unpause. Pause first and delete later.
Then check what Elevar's setup switched off. Its Klaviyo guide has GTM setups turn off Klaviyo's base snippet in the theme's App embeds and run it through GTM instead. If you remove those GTM tags, turn Klaviyo's app embed back on. The same goes for Shopify's channel pixels: decide which tool fires each one. For Meta, our guide to Shopify's Facebook & Instagram data sharing explains what each level sends and why the app double counts beside another server-side sender.
What should you check in Events Manager and Shopify after cutover?
| Check | Where | What you want to see |
|---|---|---|
| Purchase count | Events Manager, Purchase, against Shopify's online orders for the same days | At or below your orders, never above |
| One server-side sender | The Purchase event's Event Deduplication tab and Sampled Activities | One event ID format, from the new tool only |
| Match quality | Event Match Quality on Purchase | At or above your baseline after a few days |
| No Elevar pixel | Shopify Settings > Customer events | No "Elevar - Checkout Tracking" |
| No Elevar in the theme | App embeds, and a code search for "elevar" on every published theme | Nothing left |
| Shopify's Meta channel | Sales channels > Facebook & Instagram > data sharing | Off, unless it's your only server-side sender |
| Klaviyo | Flow entries | The new tool's flows receiving entries; Elevar's flows off |
| Business results | Shopify revenue and new-customer CAC | Judged on full weeks after cutover |
If Purchase runs above your orders after cutover, something is still sending. Our guide to Meta event duplication on Shopify traces the usual sources.
When should you cancel Elevar?
After the cutover checks pass, and before your next charge. Elevar's plans on the Shopify App Store are billed every 30 days, and its pricing page shows no annual term, so there's no renewal date to wait for unless your brand signed a separate agreement.
Cancel inside Elevar, not only in Shopify: go to Settings > Plan and Usage and click Cancel Website Plan. Elevar's guide says this is how you make sure you aren't billed on the next cycle. Some of Elevar's low-star reviews mention charges after uninstalling, so cancel the plan first, keep the confirmation, then uninstall. Analyst services are a separate monthly line on Elevar's pricing page; check them too.
Frequently asked questions
How do I cancel Elevar?
In the Elevar app, go to Settings > Plan and Usage and click Cancel Website Plan. Do it after the new tool is live and Elevar's destinations are offline, and before your next 30-day charge. Then uninstall the app and remove its code.
Does uninstalling Elevar remove its code?
No. Elevar's guides list code in your theme (four snippets and three render tags), the Elevar app embed, the "Elevar - Checkout Tracking" pixel in Shopify's Customer events, older checkout and landing page scripts, and anything built in Google Tag Manager on its data layer. Remove each one.
Will replacing Elevar reset Meta's learning phase?
Not if you keep the same pixel. Changing the sender isn't an ad set edit. Changing an ad set's optimization event is, so if an ad set optimizes on an Elevar custom event, have the new tool send the same event or plan that change separately.
How long should Elevar and the new tool run together?
As briefly as you can verify the new tool. Upstack's migration guide uses two to three days. While both send purchases to the same pixel, Meta counts most orders twice, because the two tools' event IDs don't match. To avoid the overlap entirely, compare first on a separate test dataset.
Can I keep Google Tag Manager after leaving Elevar?
Yes. Elevar lists reusing GTM without its data layer as one way to keep tags you still need. Tags triggered by Elevar's data layer events need new triggers, because those events stop when Elevar goes.
Key takeaways
- A new sender keeps your pixel, its audiences and its learning. A new optimization event doesn't, so list Elevar's custom events first.
- Compare first on a test dataset, or overlap for two or three days and ignore the inflated numbers.
- Uninstalling the app leaves code behind: destinations, the app embed, theme snippets, the Customer events pixel, GTM tags and Klaviyo flows each need removing.
- Cancel the plan inside Elevar before you uninstall.
Compare Upstack with Elevar
If you're replacing Elevar's data layer with server-side tracking that resolves the customer and needs no GTM container, see our Upstack vs Elevar comparison.
About the author
Want similar results?
Start free for 21 days and see what clean signal does for your performance. No card, no contract.