Why teams move from Elevar
Teams usually move from Elevar when the original Shopify tracking problem has expanded into a broader attribution problem. The store may still run on Shopify, but the business now has headless pages, landing pages, wholesale portals, subscriptions, retail media, lifecycle flows, and reporting destinations outside the Shopify ecosystem. At that point, a Shopify-first data layer can become a constraint because every new destination needs a local mapping, a platform exception, or a GTM workaround.
TrackLayer replaces that pattern with one canonical event model and destination-aware routing. The migration is not a rejection of the Elevar work already in place. It is a way to preserve the good parts, remove brittle data-layer glue, and give marketing operations a live view of whether platforms accepted events, which identifiers improved match quality, and where schema or consent issues are reducing signal.
| Capability | Elevar | TrackLayer |
|---|---|---|
| Shopify-specific vs platform-agnostic | Built around Shopify data collection, Shopify checkout behavior, and common Shopify app workflows. | Runs one canonical event layer across Shopify, custom storefronts, headless commerce, lead funnels, and backend events. |
| Event schema breakage | Custom dataLayer pushes and partner-specific event names can drift when themes, checkout extensions, or GTM mappings change. | Normalizes incoming commerce activity into stable canonical events before routing to each platform. |
| Attribution window limits | Reporting and reconciliation often stay tied to Shopify order context and the platform windows configured downstream. | Keeps event-level routing, match diagnostics, and destination responses visible so attribution issues can be diagnosed per platform. |
| Pricing model | Pricing can rise with order volume, event volume, or higher-service packages as the store scales. | Flat pricing keeps the tracking bill predictable while event volume and destination count grow. |
| Support quality | Useful for Shopify-specific implementation questions, especially when the issue sits inside the store theme or app stack. | Support focuses on end-to-end event quality: schema, identity, consent, destination acceptance, and match quality. |
Before you start
The migration is straightforward when access is ready. Gather store, workspace, destination, and GTM permissions before the first validation window. If your team runs multiple Shopify Plus stores, treat each store as its own migration with its own event counts, consent behavior, market settings, and checkout path.
Step-by-step migration
Keep the migration in three phases: observe, route, then remove. Observing proves TrackLayer sees the same commerce reality as Elevar. Routing proves destinations accept the new payloads. Removing Elevar comes last, after duplicate conversion risk is gone and the new stream has survived real orders.
Audit current Elevar config
Start by documenting the Elevar setup before installing anything new. Export the current event list, data-layer event names, custom endpoints, consent rules, ad platform mappings, and any GTM tags that listen for Elevar pushes. The goal is to separate required business events from historical implementation details. Keep purchases, refunds, subscription renewals, checkout starts, product views, cart changes, and lead events. Mark old test events and retired pixels for removal.
Elevar audit checklist
dataLayer events → dl_view_item dl_add_to_cart dl_begin_checkout dl_purchase
custom endpoints → /a/elevar/events /collect /server-side-gtm
ad mappings → Meta Purchase, Google Ads purchase, GA4 purchase, Klaviyo Placed Order
required fields → event_id order_id value currency email phone product_ids consent_stateInstall TrackLayer Shopify app and connect the same ad platforms
Install the TrackLayer Shopify app, choose the production store, and connect the same destinations Elevar currently feeds. Use the same Meta Pixel, Google conversion actions, GA4 property, TikTok pixel, Klaviyo account, and any additional platform accounts. Keep production routing paused until events appear in the live stream with the expected customer, product, order, consent, and browser fields.
TrackLayer Shopify setup
store → example.myshopify.com
mode → observe
destinations → Meta, Google Ads, GA4, TikTok, Klaviyo
identity fields → email phone customer_id fbp fbc gclid ttclid
order fields → order_id value currency line_items discounts shipping taxEnable side-by-side mode for 24h
Run Elevar and TrackLayer side by side for a full day. Both stacks should fire while TrackLayer records live events, destination-ready payloads, match quality, and deduplication state. Compare hourly event counts, purchase value, event IDs, product IDs, consent state, and accepted destination responses. TrackLayer should match or exceed Elevar match quality before you change production optimization signals.
24h verification
PageView → count within 3 percent
ViewContent → product_ids present
AddToCart → value and currency present
InitiateCheckout → checkout_id present
Purchase → event_id, order_id, email, phone, value, currency present
Match quality → equal or higher by platformTurn off Elevar data-layer in Shopify theme
After side-by-side verification, disable the Elevar theme integration that writes commerce events into the data layer. Depending on your setup, this may live in the Elevar app embed, theme app extensions, checkout scripts, a custom liquid snippet, or a tag loader inside the theme. Deploy during a quiet period and keep TrackLayer live events open while the first product views, add-to-carts, checkouts, and purchases come through.
Shopify theme cleanup
Online Store → Themes → Customize → App embeds
Elevar app embed → disabled
theme.liquid → remove legacy Elevar snippet if present
checkout extensibility → confirm no duplicate Elevar customer events
TrackLayer Shopify app → activeRemove Elevar tags from GTM
Once Shopify no longer emits Elevar-owned commerce events, remove the GTM tags, triggers, and variables whose only job was to receive or forward those events. Keep unrelated marketing tags intact. Publish a named GTM version that explains the migration, then monitor real purchases in TrackLayer and the destination diagnostics for at least one order cycle.
GTM removal list
tags → Elevar Meta CAPI, Elevar GA4 ecommerce, Elevar TikTok Events API
triggers → dl_purchase, dl_add_to_cart, dl_begin_checkout
variables → Elevar order id, Elevar customer email, Elevar product ids
publish note → Migrate conversion routing from Elevar to TrackLayerCancel Elevar subscription after 7 days of parallel verification
Keep Elevar available for seven days after TrackLayer owns production routing. This gives you time to review weekdays, weekend traffic, subscription renewals, delayed payment captures, refunds, cancellations, and post-purchase upsells. Export final reports, save the final GTM container version, download any documentation your team may need, then cancel the subscription.
7-day closeout
day 1 → verify paid platform diagnostics
day 3 → compare Shopify revenue, TrackLayer accepted events, GA4, and ad platforms
day 5 → review refunds, cancellations, subscriptions, and delayed captures
day 7 → export Elevar reports, archive config, cancel subscriptionEvent mapping
Map Elevar events to TrackLayer canonical events before the production switch. Names may vary by Elevar version, theme, and custom implementation, so use this table as the starting point and verify the actual dataLayer events in your store.
| Elevar event | TrackLayer canonical event |
|---|---|
| dl_page_view | PageView |
| dl_view_item | ViewContent |
| dl_view_item_list | ViewCategory |
| dl_select_item | SelectItem |
| dl_add_to_cart | AddToCart |
| dl_remove_from_cart | RemoveFromCart |
| dl_begin_checkout | InitiateCheckout |
| dl_add_shipping_info | AddShippingInfo |
| dl_add_payment_info | AddPaymentInfo |
| dl_purchase | Purchase |
| dl_refund | Refund |
| dl_sign_up | CompleteRegistration |
Preserving historical data
Export Elevar reports before cancelling the account. Save event volume, revenue reconciliation, platform diagnostics, conversion summaries, and any CSV reports your finance, lifecycle, or paid media teams use for month-end comparison. Store the exports beside the final GTM container version and a short migration note that lists the cutover date, destination IDs, and owner.
TrackLayer starts with the new live event stream, then backfills order context from Shopify order history where Shopify retains the required order data. That backfill is useful for customer, order, product, refund, and value context, but it is not a substitute for exporting Elevar reports. Keep both: Elevar for historical reporting continuity, TrackLayer for the new source-of-truth event stream and Shopify-backed order context.
What TrackLayer does that Elevar doesn't
Migration gotchas
Elevar's custom dataLayer.push events are not mapped
Custom pushes may represent quizzes, bundles, loyalty actions, or subscription events. Map them explicitly or retire them intentionally.
Klaviyo event name differences
Elevar setups often send Klaviyo names that do not match your current flows. Confirm Placed Order, Started Checkout, Added to Cart, and custom profile events before disabling the old route.
Elevar's server-side-GTM container handling is unclear
If Elevar sends into server-side GTM, identify whether the container does anything beyond forwarding events. Business logic should move intentionally, not disappear with a paused tag.
Multi-store (Plus) setups need separate validation
Each Shopify Plus store can have different themes, markets, currencies, checkout extensions, and consent behavior. Validate every store rather than assuming the flagship store covers the group.
Refund/cancellation events are easy to miss
Purchases are usually tested first, but finance and lifecycle teams depend on refunds, cancellations, partial refunds, and subscription updates. Include those in the seven-day review.
FAQ
Can we migrate in one afternoon?
Yes for a standard Shopify store with clean destination access. The installation and initial verification can happen in one afternoon. Keep the seven-day observation period for confidence before cancelling Elevar.
Will TrackLayer use the same ad accounts and pixels?
Yes. Connect the same production pixels, conversion actions, and destination accounts so platform learning continues against the same assets.
Will this reset Meta or Google learning?
It should not if event names, event IDs, order IDs, values, currency, and customer identifiers remain consistent. Side-by-side validation exists to prove that before production routing changes.
Do we still need GTM?
You can keep GTM for onsite tools, testing scripts, or non-commerce marketing tags. TrackLayer should own server-side conversion routing for the events it supports.
What happens to Elevar historical reports?
Export them before cancelling. TrackLayer starts reporting from the new event stream and can backfill order context from Shopify order history where Shopify has the required order data.
Who should be in the cutover room?
Bring marketing operations, the Shopify owner, and whoever owns paid platform diagnostics. Engineering only needs to stay close if the theme, GTM container, or server-side GTM setup is custom.