Comparisons
How to Switch From Blotout EdgeTag Without Losing Tracking: Channels, DNS Records and Your Contract
Switching from Blotout keeps your Meta pixel and its learning, because only the sender changes. Move each EdgeTag channel to the new tool, Meta first, then remove EdgeTag in reverse order: delete the channels, switch off the theme app embed, strip its code from landing pages and external checkouts, uninstall the app, and delete the TXT and CNAME DNS records last. Check your plan before you start: Growth and Professional are annual commitments.
If you're still choosing a replacement, our Blotout alternatives guide compares seven. This guide covers the move off Blotout's EdgeTag: when to stay, when you can leave your plan, what to record, how to run the switch without double counting, how to remove every piece of EdgeTag, and what to check afterwards. Upstack is our product and one of the tools you might move to, but the removal steps work whichever replacement you choose. We checked Blotout's pricing page, the EdgeTag docs, its Shopify App Store listing and Meta's developer pages on October 24, 2026.
Should you leave Blotout at all?
Blotout does things most Shopify tracking apps don't, and for some brands those settle it. Stay if:
- You need HIPAA terms or a signed BAA. Blotout sells HIPAA plans and says it can sign a Business Associate Agreement. Upstack doesn't offer a BAA. This isn't legal advice; ask any vendor for its terms in writing.
- You need single-tenant or self-hosted infrastructure. EdgeTag runs a dedicated database and infrastructure per brand, managed or self-hosted.
- You send to analytics tools such as Amplitude or Mixpanel. EdgeTag lists 55+ integrations; Upstack has no Amplitude or Mixpanel destination.
- You also run stores on Salesforce Commerce Cloud, BigCommerce or WooCommerce, which EdgeTag installs on too.
- You're a small store on Starter sending to several channels, where an event-priced plan can cost less than one priced per order.
Our take. The usual reasons to leave are the ones built into how Blotout charges and installs: a bill that grows with pageviews and destinations, DNS records to manage, and annual terms above Starter. If those are your reasons, the switch is worth planning around your contract.
When can you cancel Blotout?
Check which plan you're on, because Blotout sells two price lists with different terms:
| Your plan | Terms | When to move |
|---|---|---|
| Starter, on blotout.io | Monthly, pay as you go | Any time; cancel after cutover |
| Growth or Professional, on blotout.io | Annual commitment invoiced monthly, with a 30-day trial and an opt-out in the first 60 days | Inside the first 60 days, or at renewal |
| Basic or Maintenance, on the Shopify App Store | Billed every 30 days through Shopify | After cutover, before the next charge |
Sources: Blotout's pricing page and its Shopify App Store listing, checked October 24, 2026.
Neither page says how to give notice or how renewal works on the annual plans, so ask Blotout in writing for your term end date before you plan the move. If you're on Growth or Professional and past the first 60 days, set the switch up to finish before renewal rather than paying for two tools.
What should you record before you switch from Blotout?
| What to record | Where to find it | Why it matters |
|---|---|---|
| Every channel and its settings, with dataset and account IDs | EdgeTag dashboard, under Channels | The replacement has to cover each one |
| Whether EdgeTag also fires your browser pixel | The Meta channel's Enable Browser Pixel setting | If it's on, deleting the channel removes your browser pixel too |
| Rewritten or extra conversion events, such as new-customer, category, margin or keyword conversions | Channel settings, and custom conversions in Events Manager | Ad sets that optimize on one need an equivalent from the new tool |
| Klaviyo metrics and flows | Klaviyo metrics prefixed "Blotout_" and flows such as "Abandoned Browse - Blotout" | They stop getting entries when EdgeTag stops sending |
| Code outside your Shopify theme | Landing page builders, pre-checkout builders, external checkouts and headless storefronts | Uninstalling the app won't reach them |
| Custom code you wrote in the app | The EdgeTag app's Custom Code, Theme code and Newsletter Selectors settings | You may want it again in the new tool |
| Test channels still connected | Channels, any secondary or test pixel | EdgeTag says events to a test pixel count toward your usage until you delete it |
| A baseline week | Shopify online orders, Meta's Purchase count and Event Match Quality, EdgeTag's Channel Errors | You need a before to judge the after |
Sources: EdgeTag's docs on the Shopify app, testing and switching Meta, Klaviyo and custom landing pages, checked October 24, 2026.
The third row needs the most care. Moving the sender doesn't edit an ad set, but changing its optimization event does: Meta lists any change to optimization event as a significant edit, which restarts learning. If an ad set optimizes on an EdgeTag event, have the new tool send an event with the same name, or plan the change as an edit.
Will you lose pixel learning when you leave Blotout?
No. The new tool sends to the same pixel 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 needs a new pixel.
Health and wellness brands should take one extra step. If EdgeTag feeds a clean pixel, the replacement has to keep it clean: server-side only, product names, URLs and categories stripped, sent from a neutral domain, with nothing else connected. Our health and wellness setup sets out each part. A replacement that sends unfiltered product data to that pixel undoes the setup.
How do you run the switch from Blotout?
EdgeTag's own onboarding is a good template, run in reverse. Its Meta switching guide has new customers send EdgeTag's events to a test pixel for 7 to 10 days, compare Event Match Quality and purchase volume with the main pixel, then switch the main pixel over and disable the previous source. Do the same with your replacement: point it at a separate test dataset, compare on your own traffic, then switch. Don't use a test event code on your live pixel instead; Meta's developer docs say events sent with test_event_code are not dropped and are used for targeting and measurement.
If you overlap on the main pixel instead, keep it to two or three days. EdgeTag can send each event from both the browser and the server, which Meta pairs by event ID. Meta deduplicates 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. A new tool's events carry their own IDs, so while EdgeTag and the replacement both send Purchase to one pixel, Meta counts most orders twice. Make no decisions on those days' numbers.
Then cut over channel by channel. Switch the new tool's Meta destination on and delete EdgeTag's Meta channel in the same sitting, then Google Ads, then the rest. Before you delete the Meta channel, check the browser side: if Enable Browser Pixel is on, EdgeTag is firing your pixel in the browser as well, and that stops with the channel. Decide which tool fires it from then on, unless you run server-side only by design.
Klaviyo can move last. EdgeTag's Klaviyo guide runs its "Blotout" flows beside your standard flows, so build the new tool's flows, check they receive entries, then turn the Blotout flows off.
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 installs as a Shopify app with no DNS records and resolves each visitor against our identity graph of 750M+ devices and 150M+ customers.
How do you remove EdgeTag?
We found no removal guide in EdgeTag's docs, so work from where its installation guides put things. In this order, once the new tool is live:
| Step | Where | What to do |
|---|---|---|
| 1. Channels | EdgeTag dashboard, under Channels | Open each channel and delete it from its edit page, test channels included |
| 2. Klaviyo | Klaviyo flows and account users | Turn off the Blotout flows; remove cx@blotout.io if you invited Blotout's team |
| 3. Theme app embed | Online Store > Themes > Customize > App embeds | Toggle Blotout EdgeTag off and save, on every theme where it's on |
| 4. Pages outside the theme | Landing page builders such as Webflow, Unbounce or Wix; pre-checkout builders such as Replo, Funnelish or Fermat; checkouts such as Checkout Champ or Cartrush; headless storefronts | Remove the EdgeTag script or SDK calls by hand |
| 5. Shopify Customer events | Settings > Customer events | Confirm nothing from Blotout is still connected |
| 6. The app | Settings > Apps and sales channels | Uninstall Blotout EdgeTag, then confirm billing has stopped |
| 7. DNS | Your DNS provider | Delete EdgeTag's TXT record and CNAME record |
Sources: EdgeTag's Shopify installation guide and the docs above, checked October 24, 2026.
Leave DNS for last. EdgeTag's installation guide describes the two records: the TXT record proves you own the domain, and the CNAME routes traffic from the first-party subdomain to your EdgeTag infrastructure. Delete them only when nothing on any of your sites still loads from or sends to that subdomain, or those pages will call an address that no longer answers.
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 | 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 |
| Browser events | Events Manager, browser events on your main pixel | Present if you want them, from the source you chose |
| Match quality | Event Match Quality on Purchase | At or above your baseline after a few days |
| No EdgeTag in Shopify | App embeds and Settings > Customer events | Nothing from Blotout 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; Blotout flows off |
| Business results | Shopify revenue and new-customer CAC | Judged on full weeks after cutover |
Shopify's own Facebook & Instagram app is the most common second sender. Our guide to its data sharing settings explains what each level sends and why it double counts beside another server-side tool.
Frequently asked questions
Do I need to delete Blotout's DNS records?
Yes, once nothing uses them. EdgeTag's setup adds a TXT record for domain ownership and a CNAME that routes a first-party subdomain to its infrastructure. Delete both at your DNS provider after the app, its app embed and any landing page code are gone.
Is switching from EdgeTag the same as switching from Blotout?
Yes. Blotout is the company and EdgeTag is its tracking product. The Shopify app is listed as Blotout EdgeTag, and its docs are at docs.edgetag.io.
Will removing EdgeTag stop my Meta pixel?
It can stop the browser side. If EdgeTag's Meta channel has Enable Browser Pixel switched on, EdgeTag fires your pixel in the browser too, and deleting the channel ends that. The pixel itself, its history and its audiences stay in Meta.
Can I leave Blotout's annual plan early?
Blotout's pricing page lists Growth and Professional as annual commitments with an opt-out in the first 60 days. Past that window, plan the switch for your renewal date and confirm the date with Blotout in writing.
Key takeaways
- A new sender keeps your pixel and its learning; check EdgeTag's custom events and browser pixel setting before you delete anything.
- Test the replacement on a separate dataset, as EdgeTag's own onboarding does, or overlap for two or three days at most.
- Remove EdgeTag in reverse: channels, Klaviyo flows, app embed, outside pages, the app, then the DNS records.
- Starter is monthly; Growth and Professional are annual, with an opt-out in the first 60 days.
Compare Upstack with Blotout
If you're weighing Blotout's event-based pricing and DNS setup against tracking priced per order with no DNS records, see our Upstack vs Blotout 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.