Home / Blog / Validate Elevar Server-Side Tracking
Elevar · Server-Side Tracking · Validation
How to Validate Elevar Server-Side Tracking on Shopify
If Elevar is installed and dashboards show events, that does not automatically mean server-side tracking is correct. A real validation has to prove the Shopify order was captured, the server event was sent, the destination received it, duplicates were deduplicated, and value, currency, consent, and attribution context were usable.
Key takeaways
- A browser tag firing is not proof that Elevar server-side tracking works.
- Validate by Shopify order ID, not dashboard totals.
- GA4, Meta, and Google Ads all need separate validation.
- Deduplication, consent, value, currency, and customer data are part of validation.
What validated actually means
| Layer | What you are proving | Tool to check |
|---|---|---|
| Shopify source | Order exists with stable ID, value, currency, data | Shopify order admin/export |
| Elevar source | Elevar captured the order/event | Elevar Real-Time Activity |
| Destination send | Elevar sent the event | Elevar destination status/activity |
| Destination receive | Platform received event | GA4, Meta, Google Ads tools |
| Deduplication | Browser/server copies are not double-counted | Meta dedup, Google transaction ID, GA4 transaction ID |
| Data quality | Value, currency, identifiers, consent, attribution usable | Event payload/details |
| Reporting | Reports reconcile after latency | Destination reports |
Step 1: Create a controlled test order plan
Use at least three test paths: normal online checkout, accelerated payment such as Shop Pay or PayPal, and consent-path tests. Record order ID, timestamp, value, tax, shipping, discount, currency, payment method, device, market, UTM/click ID, and consent state.
Step 2: Check Elevar Real-Time Activity first
Elevar’s Real-Time Activity Report shows recent purchase events including order ID, products purchased, revenue, last-touch UTM parameters, and source such as web, draft order, or POS. Elevar Real-Time Activity
If the order is missing in Elevar, do not start debugging GA4 or Meta yet. The source layer failed.
Step 3: Validate GA4
Elevar says GA4 server-side validation can be done in the GA4 real-time report and notes that server-side purchases may not appear in the browser. Elevar server-side testing
Google’s DebugView displays events and user properties in real time. Google’s ecommerce validation docs say DebugView can show ecommerce event and item parameters. GA4 DebugView GA4 ecommerce validation
- Confirm
purchasereceived. - Confirm
transaction_id,value,currency, anditems. - Confirm no duplicate transaction IDs.
- Validate reports after processing latency.
Step 4: Validate Meta CAPI and deduplication
Elevar’s Meta testing guide uses Meta Events Manager Test Events and a server test code. Elevar Meta CAPI testing
Meta’s CAPI docs say the Test Events tool generates a test ID and sending it as test_event_code lets events appear in the Test Events window. Meta CAPI Test Events
- Confirm browser Pixel event appears where expected.
- Confirm server CAPI event appears.
- Confirm browser
eventIDand serverevent_idmatch. - Confirm value, currency, and customer parameters.
- Confirm deduplication in Events Manager.
Step 5: Validate Google Ads
Google Ads Tag Assistant can troubleshoot unverified or inactive conversion actions, and Google Ads troubleshooting docs say to verify implementation, check status, and review primary/secondary and enhanced conversion settings. Google Ads Tag Assistant Google Ads troubleshooting
- Confirm correct Google Ads account and conversion action.
- Confirm conversion ID/label or server-side action mapping.
- Confirm Primary/Secondary status by design.
- Confirm transaction ID, value, and currency.
- Respect reporting latency before calling it failed.
Step 6: Validate consent behavior
Test consent accepted, denied, and no-choice states. Also test regional behavior for EU, UK, California, or any market using different privacy settings. Validation is not just “did the event arrive?” It is also “was it allowed to be sent, and was it sent with the correct fields for that consent state?”
Step 7: Reconcile real orders
Use 20–50 orders from a completed date range and compare Shopify order ID, Elevar log, GA4 transaction ID, Meta event/order details, Google Ads transaction ID, value, currency, source, consent, and duplicate status.
Destination validation table
| Destination | Where to validate | What must match |
|---|---|---|
| Elevar | Real-Time Activity | Order ID, revenue, products, UTMs, source |
| GA4 | Realtime, DebugView, Explore/BigQuery | purchase, transaction_id, value, currency, items |
| Meta | Events Manager Test Events, server details | Pixel/CAPI receipt, event ID, value, currency, customer parameters, dedup |
| Google Ads | Tag Assistant, conversion diagnostics | Conversion action, transaction ID, value, currency, enhanced conversions |
| Shopify | Orders/export | Order ID, value, currency, tags, order type |
Common validation failures
| Failure | What it usually means | Fix direction |
|---|---|---|
| Event visible in browser but not Elevar | Browser-only tag firing, server source unconfirmed | Check Shopify Source and Elevar setup |
| Order in Elevar but not GA4 | GA4 destination/send issue | Check GA4 destination and Realtime |
| Meta counts Pixel and CAPI | Deduplication failed | Match event name and event ID |
| Google Ads tag verified but no conversions | Wrong action, label, status, attribution, or latency | Validate conversion action and wait |
| Value mismatch | Tax/shipping/discount/currency differs | Standardize value definition |
| Currency warning | Shopify Markets/presentment mismatch | Match value and currency path |
| Only desktop tests pass | Mobile/Shop Pay/PayPal not validated | Test real checkout paths |
| Recurring orders missing | Subscription flow not configured | Validate server-side renewal logic |
What not to do
- Do not validate Elevar only with browser developer tools.
- Do not validate Meta only by event count; check deduplication and customer parameters.
- Do not validate GA4 only with standard reports immediately after testing.
- Do not validate Google Ads only from campaign conversions right away.
- Do not ignore order ID reconciliation.
TrackingAudit validation checklist
- Shopify test orders created for normal checkout, accelerated payment, and consent paths.
- Order IDs, values, currencies, payment methods, UTMs, and consent states recorded.
- Elevar Real-Time Activity shows the order.
- GA4 receives purchase with transaction ID, value, currency, and items.
- Meta receives browser and server events where expected.
- Meta Pixel/CAPI deduplication is confirmed.
- Google Ads conversion action is verified and correct.
- Duplicate native app/GTM/pixel/CAPI sources are removed or controlled.
- Mobile, Safari, Shop Pay/PayPal, and subscription paths are tested when relevant.
- A real order sample reconciles across Shopify, Elevar, GA4, Meta, and Google Ads.
Need proof your Elevar setup is really working?
TrackingAudit can run a source-to-destination audit, compare order IDs and payloads, check deduplication, identify duplicate sources, and document exactly which paths pass or fail.
Get your free audit →Frequently asked questions
How do I validate Elevar server-side tracking?
Create controlled Shopify test orders, check Elevar Real-Time Activity, then verify the same order in GA4, Meta Events Manager, and Google Ads using each platform’s validation tools.
Why can’t I see server-side purchases in the browser?
Server-side purchases may be created from Shopify order data or webhooks, not from a browser request. Browser tools alone are not enough.
What should I check first?
Start with Shopify order ID and Elevar Real-Time Activity. If Elevar did not capture the order, destination debugging will waste time.
How do I validate GA4?
Use GA4 Realtime or DebugView, then check transaction ID, value, currency, and items. Validate final reports after processing latency.
How do I validate Meta CAPI?
Use Meta Events Manager Test Events and server event details. Confirm CAPI receipt, Pixel/CAPI event ID matching, event name matching, value/currency, and customer parameters.
Is one test order enough?
No. Test normal checkout, accelerated payment, consent paths, and high-volume subscription or third-party checkout paths.
Sources
- Elevar: How to Test Tracking for Server-Side and GTM Web Containers
- Elevar: Real-Time Activity Report
- Elevar: What is Server-Side Tracking?
- Elevar: Getting Started with Server-Side Tracking
- Elevar: Set up GA4 as a server-side destination
- Elevar: Set up Google Ads as a server-side destination
- Elevar: Set up Meta as a server-side destination
- Elevar: Test Meta CAPI integration for Shopify
- Elevar: Disable Meta CAPI Gateway integration
- Elevar: Disable native Meta Pixel in Shopify
- Google Analytics Help: Monitor events in DebugView
- Google Developers: Validate ecommerce setup
- Google Developers: Verify Measurement Protocol implementation
- Google Ads Help: Use Tag Assistant to troubleshoot conversion actions
- Google Ads Help: Troubleshoot conversion tracking status
- Meta Developers: Verify events and Test Events tool
- Meta Business Help: Test server events
- Meta Developers: Deduplicate Pixel and CAPI events
- Stape: Server-side tagging for Shopify
- Littledata: How Shopify to GA4 works
- Analyzify: Server-side conversion tracking for GA4 purchase