Home / Blog / Wrong Purchase Value in Elevar
Elevar · Shopify · Purchase Value
Wrong Purchase Value in Elevar: What to Check
If Elevar is firing purchase events but GA4, Meta, or Google Ads shows the wrong revenue, do not assume the whole tracking setup is broken. First define what “wrong” means: gross revenue, net revenue, subtotal, total paid, value without tax, value without shipping, discounted value, presentment currency, or duplicated purchase value.
Most wrong-value issues are not event-delivery problems. They are definition problems.
Key takeaways
- Define “correct value” before debugging.
- GA4, Google Ads, and Meta use purchase value differently.
- Tax, shipping, discounts, currency, and duplicate purchases are the most common causes.
- Elevar has server-side purchase value customization options, so check destination settings before hard-coding fixes.
First decide what value should mean
| Value definition | Usually means | When it makes sense |
|---|---|---|
| Gross order total | Products + tax + shipping after discounts | Finance reconciliation |
| Product subtotal | Product revenue after discounts, excluding shipping/tax | Marketing ROAS and ecommerce analytics |
| Net sales | Revenue after refunds/returns/adjustments | Post-purchase reporting |
| Margin/profit value | Revenue minus COGS or margin logic | Profit-based bidding |
| Presentment currency total | Customer-paid currency/value | Multi-currency reporting |
Platform-specific value rules
GA4
Google’s GA4 ecommerce documentation says purchases are measured by sending a purchase event with items and relevant fields. The purchase event should include parameters such as transaction_id, value, currency, and items. Google: Measure ecommerce
Wrong GA4 value usually comes from tax/shipping inclusion, missing discounts, currency mismatch, duplicate purchase events, or comparing adjusted Shopify net sales against original purchase events.
Google Ads
Google Ads uses conversion value for bidding and ROAS. Google’s web conversion docs say dynamic values can capture purchase value, transaction ID, or currency when available where the tag fires. Google Ads dynamic values
Google Ads also recommends transaction IDs to minimize duplicate conversions. Google Ads transaction IDs
Meta
Meta’s CAPI docs say currency is required for purchase events when value is specified. Meta says value and currency help measure ROAS and optimize for value. Meta CAPI custom data Meta value and currency
Elevar-specific value checks
Elevar has documentation for customizing purchase value sent via server-side destinations. Elevar purchase value customization
- Which destinations receive purchases?
- Is purchase value customized per destination?
- Is Shopify total, subtotal, tax, shipping, discount, or presentment value used?
- Are browser and server purchase events deduplicated?
- Are transaction IDs consistent across GA4, Google Ads, Meta, and Shopify?
- Are Shopify Markets/local currencies enabled?
- Are post-purchase upsells or recurring subscription orders handled separately?
- Are test, sample, or $0 orders filtered with tags?
Elevar order tags can be used to exclude sample orders, $0 transactions, or test purchases that can skew attribution models. Elevar order tags
Common causes
- Tax and shipping: included in one platform, excluded in another.
- Discounts: applied twice, not applied, or item-level discounts do not match event value.
- Currency: value and currency code do not match, especially with Shopify Markets.
- Browser vs server: Pixel/browser calculates one value while server uses final Shopify order.
- Duplicates: multiple integrations send the same purchase.
- Refunds and edits: adjusted Shopify net sales are compared to original purchase events.
- Post-purchase upsells: event fires before or after upsell value is added.
- Subscriptions: first orders, renewals, and prepaid subscriptions use different logic.
Diagnostic table
| Symptom | Likely cause | Where to check | Fix direction |
|---|---|---|---|
| GA4 revenue higher than Shopify | Duplicate purchase or tax/shipping included | GA4 transaction IDs, Tag Assistant, Elevar logs | Deduplicate and standardize value |
| GA4 revenue lower than Shopify | Missing orders or value excludes tax/shipping | Order export vs GA4 transaction IDs | Separate missing orders from value logic |
| Meta value higher than Shopify | Pixel and CAPI both counted | Meta deduplication | Match event ID and value source |
| Google Ads value too high | Multiple primary actions or duplicate conversion | Google Ads conversion actions | Use one primary action and transaction ID |
| Value correct but currency wrong | Markets/presentment mismatch | Payload currency/value pair | Send matching value and currency |
| Product revenue differs from order revenue | Item discount mapping issue | GA4 items array and Shopify line items | Align item discounts and event value |
| Recent report changed later | Refunds/order edits/cancellations | Shopify order timeline | Compare original vs adjusted sales |
| Subscription value strange | Renewal/prepaid/tag logic | Subscription provider + Elevar | Define first vs recurring value rules |
Reconciliation workflow
- Export 20–50 Shopify orders from a completed date range.
- Include total, subtotal, tax, shipping, discounts, currency, presentment currency, refunds, tags, source, and order type.
- Pull matching GA4, Google Ads, and Meta events by order ID/transaction ID.
- Record value and currency in every destination.
- Mark whether each destination includes tax, shipping, and discounts.
- Check duplicate transaction IDs or events.
- Segment mismatches by currency, discount, country, upsell, subscription tag, and order source.
- Choose the value definition you want.
- Update Elevar destination settings or mapping.
- Retest with controlled orders.
What not to do
- Do not “fix” value with random GTM math before checking Elevar server-side value settings.
- Do not compare Shopify gross sales to GA4 purchase revenue and expect exact equality.
- Do not send one value in Meta Pixel and another value in Meta CAPI for the same Purchase.
- Do not optimize Google Ads against multiple primary purchase actions with different value definitions.
- Do not ignore currency.
Validation checklist
- Value definition chosen for GA4, Google Ads, and Meta.
- Tax inclusion/exclusion documented.
- Shipping inclusion/exclusion documented.
- Discount logic documented.
- Currency and value pair validated for Shopify Markets.
- Transaction ID/order ID is consistent.
- Meta Pixel and CAPI deduplicate with same event ID.
- Google Ads uses transaction ID and one primary purchase action.
- GA4 transaction IDs are not duplicated.
- Elevar server-side value customization checked.
- Test/sample/$0 orders excluded or segmented.
Purchase value still looks wrong?
TrackingAudit can compare Shopify order totals against GA4, Meta, and Google Ads event payloads, then define the correct value rule per destination.
Get your free audit →Frequently asked questions
Why is purchase value wrong in Elevar?
Usually because Shopify order totals are mapped inconsistently, tax/shipping/discount logic is unclear, currency is mismatched, browser and server events use different value sources, duplicates inflate revenue, or order edits/refunds are compared against original purchase values.
Should purchase value include tax and shipping?
It depends on your reporting and optimization goal. Many marketing teams prefer product revenue after discounts, excluding tax and sometimes shipping. The key is to define the rule and apply it consistently.
Why does Meta show higher purchase value than Shopify?
Meta can show higher value if Pixel and CAPI are both counted, attribution windows differ, or Meta receives value including tax/shipping while Shopify comparison excludes them.
Can Elevar customize purchase value by destination?
Elevar has documentation for customizing purchase value sent via server-side. Check destination settings before editing theme code or GTM variables.
What should I check first?
Start with one Shopify order ID. Compare Shopify total, subtotal, tax, shipping, discount, currency, GA4 value, Meta value, Google Ads value, and duplicate events.
Sources
- Elevar: Customize purchase value sent via server-side
- Elevar: Configuring Google Ads conversion actions with Elevar
- Elevar: Google Ads knowledge base
- Elevar: GA4 knowledge base
- Elevar: Multi-currency conversion tracking for Shopify
- Elevar: Understanding Order Tags
- Google Developers: Measure ecommerce
- Google Developers: Set up a purchase event
- Google Developers: Apply discount to ecommerce event
- Google Ads Help: Set up web conversions with dynamic values
- Google Ads Help: Use transaction ID to minimize duplicate conversions
- Meta Developers: CAPI custom data parameters
- Meta Business Help: Set value and currency for standard events
- Meta Developers: Pixel reference
- Shopify Help: Setting up currencies for markets
- Shopify Community: tax and shipping conversion value
- Shopify Community: GA4 order numbers not matching Shopify
- Analyzify: GA4 purchase event on Shopify