Do we need to budget for a tracking-app plan upgrade (e.g., to a server-side tier) at the same time we migrate to Checkout Extensibility?
A tracking-app upgrade belongs in the same budget cycle only when your purchase tracking lives in the additional scripts box. The new thank you and order status pages accept app pixels and web pixels only, so a hardcoded GA4 or Meta tag has no home. Elevar, now sold as Audiense Online, starts at $225 per month for 2,000 orders (Audiense, September 2026).
The mechanism that creates the forced spend
Shopify's position on the new pages is not a preference. "The new Thank you and Order status pages support app pixels for tracking and analytics," and direct script injection is no longer an option (per Shopify Help Center, September 2026). There is no supported route for a raw tag.
So the question resolves into an inventory question. Where does your purchase event currently fire from?
| Current setup | Does the migration force a spend? |
|---|---|
| Purchase tracking already in Customer Events as an app or custom pixel | No. Nothing changes. These were never script tags |
| Shopify's native Meta data sharing at Enhanced or Maximum | No. The Conversions API purchase event is included at no extra cost |
| GA4 or Meta tag pasted into Additional scripts | Yes, in effect. The tag needs an app that publishes a pixel, and some vendors gate that behind a tier |
| A tag manager loaded on the order status page | Yes, and the replacement is usually a bigger change than a like-for-like swap |
| Post-purchase upsell app with its own tracking | Depends on the vendor. Ask whether their pixel ships on your current plan |
Check the free path before you budget anything
Shopify already sends purchase events to Meta server to server at the Enhanced and Maximum data-sharing levels, at no additional cost. For a large share of mid-market stores that covers the single most valuable channel without a line item. Enable it, measure what comes back, then scope the rest.
What the paid tier actually costs, when you need it
Elevar is the reference point most Shopify teams reach for, and it is worth knowing that getelevar.com/pricing now redirects to Audiense. The product is sold as Audiense Online, powered by Elevar (verified 14 September 2026). Published tiers:
| Plan | Price | Order volume |
|---|---|---|
| Core | $225/month | up to 2,000 orders/month |
| Advanced | $650/month | up to 10,000 orders/month |
| Premium | $1,250/month | up to 30,000 orders/month |
| Elite | from $3,000/month | up to 75,000 orders/month |
(per audiense.com, September 2026, with a 15-day free trial on all four.)
The number that catches budgets out: there is no free or basic Data Layer plan. A team that remembers a lightweight Elevar tier from a few years ago is budgeting against a product that no longer exists at that price. The floor is $225 per month, and a mid-market store doing 10,000 orders a month is scoping $650.
How to sequence it so you only buy once
- Inventory the order status page first. Shopify generates an app audit in Settings then Apps for exactly this (per Shopify Help Center, September 2026).
- Enable native Meta server-side sharing if it is not already on. It is free and it covers the largest channel for most stores.
- List the channels still fed from a tag, and for each one check whether the vendor publishes a Shopify app pixel and on which tier.
- Then price the tool. Buying before step three is how teams end up paying $650 a month to replace one tag that a free app pixel would have covered.
- Re-verify at week two after cutover. Pixel-based purchase events and script-based ones do not always reconcile on day one, and the gap is easier to diagnose while the migration is fresh.
When NOT to fold this into the migration budget
- When the tracking already runs through Customer Events. No date in the checkout timeline touches it.
- When the motivation is page speed. App pixels run in a strict sandbox using web workers and custom pixels in a sandboxed iframe, so the main-thread saving you are imagining was mostly already made.
- When finance and marketing disagree about what a conversion is. No transport layer settles that, and a new tool inherits the argument at $225 a month.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: The migration does not force a tracking-tier upgrade. Your existing implementation choice does. Stores that never pasted a tag into Additional scripts pay nothing extra, which is a real and under-stated reward for having done it properly the first time.
- What we’ve seen: The spend usually gets discovered late, in the week the parity map is signed, because tracking sits with marketing while the migration sits with engineering. Ask the tracking question in the audit, not in the build.
- Where we disagree: Vendors frame this as the moment to upgrade to server-side. The honest framing is that the migration removes one delivery mechanism and you need a supported one, which is not the same as needing a server-side tier. Buy the pixel you need; the server-side case has to stand on accuracy grounds of its own.
- What this page adds: that app pixels are the only supported tracking route on the new pages, that Elevar now bills as Audiense Online with no free Data Layer tier and a $225 floor, and that Shopify's native Meta server-side sharing already covers the largest channel at no cost.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-14.
Where we worked this out
Our decision records