Home / Blog / Klaviyo Revenue Mismatch
Shopify · Tracking Troubleshooting
Klaviyo Revenue Not Matching Shopify After Elevar Setup: What to Check
If Klaviyo revenue changes after adding Elevar, do not assume Shopify, Klaviyo, or Elevar is “wrong.” Shopify reports store revenue. Klaviyo reports attributed revenue based on its attribution rules and event/profile data. Elevar can add richer server-side events, but those events must be used intentionally.
Keyword target
- Primary: Klaviyo revenue not matching Shopify Elevar
- Secondary: Klaviyo revenue not matching Shopify, Elevar Klaviyo server-side tracking, Klaviyo attribution vs Shopify revenue, Shopify Klaviyo placed order mismatch, Klaviyo flow revenue not matching Shopify
Key takeaways
- Klaviyo revenue and Shopify revenue are not the same metric.
- Elevar’s Klaviyo destination is meant to work with Klaviyo’s native Shopify app, not blindly replace every event.
- New server-side browse/cart events can change flow performance and attribution.
- Validate Placed Order, flow triggers, identity, and attribution settings before judging results.
Why the numbers differ
Shopify records orders. Klaviyo attributes revenue to marketing interactions based on its attribution settings and profile/event data. Community discussions show merchants often see Klaviyo-attributed sales that differ from Shopify-reported sales because the platforms answer different questions.
What Elevar changes
Elevar’s Klaviyo destination documentation says its server-side Klaviyo integration is built to be used in tandem with Klaviyo’s native Shopify app and that you do not need to remove pre-existing tracking when enabling Elevar. It also says you need new flows to take advantage of server-side events Elevar sends to Klaviyo.
| Change | Possible impact | Check |
|---|---|---|
| Server-side Viewed Product/Add to Cart | more identified flow triggers | flow event source |
| Native Shopify app still active | Placed Order still comes from Shopify/Klaviyo | do not duplicate order logic |
| New Elevar events | flows may not use them yet | create/update flows intentionally |
| Session enrichment | more profiles identified | attribution may rise |
| Different attribution window | revenue looks inflated/deflated | Klaviyo settings |
Competitor/tool context
Littledata also positions improved Shopify-to-Klaviyo data around richer browse/cart events and filtered purchase events. Klaviyo’s native Shopify app remains important for order/profile sync. The audit should focus on which events power flows and attribution, not just whether more events appear.
Diagnostic workflow
- Confirm Klaviyo native Shopify integration is connected.
- Confirm Elevar Klaviyo destination is connected.
- Identify which Klaviyo events are used in flows before and after Elevar.
- Check Placed Order source and whether duplicates exist.
- Compare one Shopify order to the Klaviyo profile timeline.
- Review Klaviyo attribution settings and window.
- Check whether flow revenue vs campaign revenue is being compared to total Shopify revenue.
- Check test orders, refunds, cancelled orders, and subscription renewals.
- Validate identity/session enrichment for browse/cart events.
- Document which Klaviyo events should be used going forward.
What not to do
- Do not expect Klaviyo attributed revenue to equal total Shopify sales.
- Do not remove the Klaviyo native Shopify app just because Elevar is enabled.
- Do not switch flows to new Elevar events without testing entry logic and suppression.
- Do not compare campaign revenue, flow revenue, and Shopify sales as if they are the same metric.
TrackingAudit validation checklist
- Klaviyo Shopify integration checked
- Elevar Klaviyo destination checked
- Placed Order source checked
- Duplicate orders checked
- Flow trigger events reviewed
- Attribution window reviewed
- Profile timeline tested
- Refund/test-order policy checked
- Session enrichment checked
- New flow plan documented
Need the tracking checked before scaling?
TrackingAudit can compare Shopify orders against the active event stack and show which system is missing, duplicating, or misattributing purchases.
Get your free audit →Frequently asked questions
Should Klaviyo revenue match Shopify?
No. Shopify is total order revenue; Klaviyo reports attributed revenue based on its own rules.
Does Elevar replace Klaviyo’s Shopify app?
Elevar documentation says its Klaviyo server-side integration is built to be used in tandem with Klaviyo’s native Shopify app.
Why did Klaviyo revenue increase after Elevar?
More identified browse/cart activity and session enrichment can increase flow triggering and attribution.
What should I compare?
Compare one Shopify order to the customer profile timeline, then compare event source, attribution window, and flow/campaign source.