Does Elevar actually guarantee accurate purchase data, and what does its accuracy claim mean in practice?
Short answer
Elevar does not guarantee accurate purchase data, because its terms make no warranty that results will be accurate (Audiense's terms, October 2026). Its marketing promise of "nearly 100% of ad and website conversion data" (Audiense, October 2026) describes delivery, not attribution. Elevar's Channel Accuracy report counts orders sent or deliberately skipped against Shopify orders (Elevar's documentation, October 2026).
- Accuracy warranty in Elevar's terms
- NoneThe terms, updated 1 September 2026, provide the product as is and make no warranty that it will be accurate, complete or error-free (Audiense, October 2026).Source: Audiense (Audiense Online Terms & Conditions)
- Elevar's accuracy claim
- Nearly 100% of conversion dataAudiense's product page says Elevar "captures nearly 100% of ad and website conversion data" (October 2026).Source: Audiense (Audiense Online: E-commerce Conversion Tracking Platform)
- What Channel Accuracy measures
- Orders sent or skipped, over Shopify ordersElevar's example: 95 transactions sent to Facebook plus 5 ignored, over 100 Shopify orders, equals 100% (Elevar documentation, October 2026).Source: Elevar (Why Doesn't Channel Accuracy Equal 100%)
- Elevar's troubleshooting line
- A Facebook match below 95%Elevar lists four setup causes, from a webhook integration older than its 26 October 2022 update to a second checkout without the integration (Elevar documentation, October 2026).Source: Elevar (Why Doesn't Channel Accuracy Equal 100%)
Deploi’s call
Elevar does not guarantee accurate purchase data, and its terms disclaim it. It ships a delivery reconciliation and a candid documentation page explaining why that reconciliation lands below 100%. Treat "nearly 100%" as a description of delivery completeness under a correct install, and treat attribution as permanently unresolved.
BuyBuy Elevar for delivery you can audit when
- You will reconcile Channel Accuracy against Shopify orders every month and after each checkout change.
- Every checkout, a subscription app's included, sends purchases through Elevar's webhook integration (Elevar's documentation, October 2026).
- Paid media runs past roughly $20,000 a month, where Deploi's Elevar vs. built data layer record scores Elevar BUY, as the record's illustrative estimate (October 2026).
WaitDon't buy it as a guarantee when
- Accuracy has to be contractual and no order form expressly overrides the terms, because the terms disclaim accuracy and govern any conflict (Audiense's terms, October 2026).
- Your dispute is which channel gets credit, which no delivery report settles.
- Nobody will own the reconciliation after each checkout or app change.
Basis: Elevar vs. a Built Data Layer: Buy Tracking or Own the Pipes?, our Build vs. Buy decision record, scored BUY.
What does Elevar promise about accuracy?
Elevar promises near-complete capture in its marketing and no accuracy in its contract. Audiense, which now sells Elevar, says Elevar "captures nearly 100% of ad and website conversion data". It adds that marketing leaders use Elevar's server-side tracking "to capture conversion data with near 100% accuracy" (Audiense, October 2026). Elevar's terms, updated 1 September 2026, provide the product as is and make no warranty that it will be accurate, complete or error-free (Audiense's terms, October 2026). The same terms let an agreement include a service level agreement (SLA) beside them, so any accuracy commitment is one you negotiate. Whether Elevar's entry plan works below Shopify Plus is the question this one follows.
What does Elevar's Channel Accuracy number measure?
Elevar's Channel Accuracy number measures delivery: whether each Shopify order reached a destination or was deliberately left out. Elevar's documentation sets out the calculation (Elevar's documentation, October 2026):
- "We log Shopify orders (i.e. source of truth)".
- Elevar logs each server-side destination's "success or failure responses".
- "We also log the number of orders you have specifically chosen not to send to your destination".
- Elevar divides orders sent plus orders skipped by Shopify's order count. Its own example is 95 sent to Facebook plus 5 ignored, over 100 Shopify orders, which equals 100%.
So the number answers one question: did every order either reach the destination or get excluded on purpose? It doesn't say whether the ad platform credited the right channel, whether the order value was right, or whether the platform's total matches your finance system.
Which kind of accuracy does Channel Accuracy cover?
Channel Accuracy covers delivery, the first of three things buyers mean by accuracy, and neither of the other two.
| Meaning of accuracy | Who owns it | Covered by Channel Accuracy? |
|---|---|---|
| An event reached the destination for every order | The tracking vendor | Yes: this is the calculation |
| The value and customer details on the event are right | Your setup and the vendor's pipeline | No: the calculation counts orders, not values or customer details |
| The ad platform credited the right channel | The ad platform's model | No, and no tracking vendor can |
In our judgment, most disputes about tracking accuracy are about the third row. No pipeline product resolves it, because it is a modelling disagreement between platforms, not a data-delivery failure. The limits server-side tracking leaves in place cover attribution in more depth.
Why does Channel Accuracy fall below 100%?
Channel Accuracy falls below 100% because of setup states that Elevar documents itself. Its troubleshooting page lists four conditions behind a Facebook match below 95% (Elevar's documentation, October 2026):
- A Shopify webhook integration for purchases that predates Elevar's 26 October 2022 update for Facebook click IDs.
- A Conversions API (application programming interface) running client side only, without Elevar's webhook integration.
- A purchase event that fires only on the final thank-you page of an upsell funnel.
- More than one checkout, such as Shopify and Recharge, without the webhook integration, or with client-side tracking set up on only one.
The same page shows all zeros when a Google Tag Manager (GTM) server-side container runs without Elevar's Shopify logging, which Elevar lists as "coming soon for all Elevar plans". Elevar says moving to its Fully Managed Server setup "will solve the vast majority of channel accuracy issues". So the four Facebook-match causes are install states, not product defects, and the accuracy you get depends mostly on how the tracking was installed.
How do you check Elevar's accuracy claim yourself?
You check Elevar's accuracy claim by reconciling three numbers for one channel and one month.
- Pick one channel and one month. Start with Meta, because Elevar's troubleshooting page sets its 95% match line there (Elevar's documentation, October 2026).
- Pull three numbers. Take Shopify orders in the window, orders Elevar reports as delivered or deliberately excluded, and the platform's own reported conversions.
- Expect the first two to reconcile. If they don't, that is a delivery problem and Elevar's to explain.
- Expect the platform's number to differ from both. That gap is attribution, and it is not a bug.
- Set an alert and re-run after every checkout or app change. Elevar can alert you "when tracking accuracy drops below your target threshold" (Audiense, October 2026), so a silent outage doesn't pass for a bad month.
When should you not rely on Elevar for accuracy?
Don't rely on Elevar for accuracy you need in writing, for attribution, or for a reconciliation nobody runs.
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- The category sells accuracy as a product attribute. It is an operating state. A correct install drifts out of accuracy on its own the first time a theme changes, an app is added or a checkout path forks, which is why the reconciliation report matters more than the headline percentage.
- Where we look first
- In our judgment, a low match rate more often traces to a second checkout path nobody mentioned during scoping than to the vendor: usually a subscription platform, sometimes a headless landing page, occasionally a post-purchase upsell with its own thank-you page.
- What this page adds
- The parent asks whether Elevar's entry plan works below Plus. This answer reads Elevar's accuracy promise against its terms, which disclaim accuracy, gives the formula behind its Channel Accuracy number, and lists the reasons Elevar itself gives for that number landing below 100%.
Decision records behind this answer
What we’ve built
When this answer changes
- Audiense changes its terms to warrant accuracy, or publishes a service level agreement for event delivery.
- Elevar changes the Channel Accuracy calculation or its 95% troubleshooting line for Meta.
- Audiense publishes a method or a third-party audit behind its nearly 100% claim.
- Elevar adds a report that checks event values or attribution, not just delivery.
Related questions
This follows from Does Elevar's basic Data Layer plan work fine for a non-Plus Shopify merchant who isn't using Checkout Extensibility?
- What does server-side tracking NOT fix, even after a full and correct implementation?
Server-side tracking, even correctly implemented, does not fix declined consent, 48-hour deduplication windows or ad platforms' attribution models.
- Does Elevar's data-layer accuracy focus actually reduce Meta/Google ad-spend waste, or is that just a marketing claim?
Elevar publishes no controlled evidence that its tracking cuts Meta or Google ad-spend waste.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.