Get your Wix tracking to 95%+ accuracy guaranteed in writing.
Wix's marketplace pixel apps don't pass email, phone, or full purchase data. EMQ stays low, custom audiences stay small, and your CPM keeps creeping up. We extend your Wix store with Velo backend functions and a real server-side CAPI gateway so Meta and Google finally see who's actually buying.
Free30 minutesNo obligation
Wix · what breaks
Wix tracking gotchas — Wix
- 01
Native pixels are minimal
Email and phone don't pass through. EMQ stays low.
- 02
Wix Stores events miss order detail
Default purchase event lacks line items and full value breakdown.
- 03
Custom code blocks fire too late
Direct script blocks load after Wix's render cycle, missing fast bounces.
- 04
Wix's GTM integration is a black box
Limited debug, hard to tell what's actually firing on the live site.
Wix · the fix
What we build — Wix
Velo backend CAPI
Server-side Meta CAPI fired from a Velo backend webhook on order_paid.
Enhanced Conversions
Hashed customer data passed to Google Ads.
GA4 measurement protocol
Server-side GA4 events for purchases.
Consent banner integration
Wix Cookie Consent or third-party banner wired to events.
Wix · architecture
How a Wix order should reach the ad platforms — Wix
Wix restricts what can run on the page more than most platforms, and its checkout is fully hosted. Working within those limits, rather than fighting them, is what makes a Wix setup reliable.
- 1
Click identifiers captured at first touch
Click IDs are captured with Velo code at landing and stored in a first-party cookie, because the Wix checkout does not carry your URL parameters through to the confirmation page.
- 2
The browser sends the fast, fragile copy
Wix's own Custom Element and Velo APIs fire the browsing and cart events. Wix's tag manager integration is limited, and events that work on the site frequently do not run inside checkout at all.
- 3
The order itself is the source of truth
The Wix Stores order, delivered by the onOrderPaid backend event, is the truth. The thank-you page is unreliable on Wix specifically because the hosted checkout controls the redirect.
- 4
A server container sends the authoritative event
A Velo backend event handler posts the paid order to a GTM server container on your own subdomain, keyed on the Wix order number.
- 5
Customer identity raises match quality
The order carries buyer email, phone and shipping address. Hashed in the backend handler, these give a Wix store the identity signal its front end cannot supply.
Wix · events
The event set we build on Wix, and where each one comes from — Wix
On Wix the useful distinction is not browser versus server but page versus backend — the backend events are the only ones the hosted checkout cannot break.
| Event | Fires when, on Wix | Key parameters | Sent from |
|---|---|---|---|
| view_item | A product page renders | item_id, value, currency, event_id | Browser + server, deduped |
| add_to_cart | The Wix Stores cart API confirms the add | item_id, quantity, value, currency, event_id | Browser + server, deduped |
| begin_checkout | The hosted checkout is entered | value, currency, num_items, event_id | Browser + server, deduped |
| purchase | The onOrderPaid backend event fires | order_id, value, currency, items[], hashed email/phone/name/address, event_id | Server authoritative |
| generate_lead | A Wix Form submits successfully | hashed email/phone, click IDs, event_id | Server preferred |
Wix · normal or broken
Wix limits that look like faults — Wix
A lot of Wix tracking advice assumes access the platform does not grant. Knowing the boundary saves a great deal of wasted effort.
Normal, not a fault
Custom scripts not running inside checkout
Wix's hosted checkout does not execute arbitrary site scripts. This is the platform boundary, and the backend event exists precisely because of it.
Wix Analytics disagreeing with GA4
Different session definitions and attribution models. Expected.
Ad platforms report more conversions than you have orders
Meta credits a 7-day click and 1-day view; Google credits on click date. Two platforms can each claim the same sale. Compare each one to your order records separately and never add them together.
Recent days always look worse than they finish
Conversions are credited back to the date of the click, so yesterday's return on ad spend is understated and will keep improving for several days. This is attribution working, not data arriving late.
Actually broken
Purchase tracked only from the thank-you page
Wix's redirect behavior means a share of paid orders never render it. Those conversions are simply never reported.
Wix's native pixel integration running alongside a manual one
Both fire, conversions double, and the native one is easy to forget because it is configured in a different part of the dashboard.
Velo code disabled on a site republish
Republishing can revert backend code if it was not saved correctly. Tracking stops with no error anywhere.
Wix · prove
How we prove the Wix build is correct — Wix
The tag firing proves the tag fires. These prove the numbers are right.
Source of truth
Wix Stores order records
- onOrderPaid confirmed firing and delivering for a real paid order.
- The native Wix pixel integration audited and either removed or deliberately kept as the only path.
- Backend code confirmed surviving a republish.
- Purchase count within a few percent of wix stores order records for a fully closed week, matched on order ID rather than on totals.
- No order ID appearing twice in any platform's event log.
- Deduplication confirmed at every destination that supports it.
- Test and staff orders excluded, with the exclusion confirmed active rather than merely configured.
- The same reconciliation repeated 30 days later, because a setup that works once and then drifts is the harder failure to catch.
Wix · free audit
What we check in the free audit
- Native pixels are minimal
- Wix Stores events miss order detail
- Custom code blocks fire too late
- Wix's GTM integration is a black box
Checked against
Wix Stores order records
Free30 minutesNo obligation
Wix · when not to buy
When a Wix rebuild is not what you need — Wix
We would rather say this now than three weeks into an engagement.
- You use Wix for a brochure site with no store. There is no order to reconcile against and the standard tags will do.
- You spend under about $1,500 a month on ads. Wix's native integrations will cover most of it.
- You are moving to another platform this quarter. Rebuild there.
Wix · what we deliver
Deliverables — Wix
Velo backend module
Installable .jsw + docs
Meta CAPI + Google EC
Live-fired and verified
GA4 measurement protocol
Server-side events
QA report
Test orders + EMQ screenshots
Written guarantee
95%+ tracking accuracy
Measured against Wix Stores order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Foundation pixel install for your Wix store. Honest disclosure: this is a starting point only. If you spend $1K+/month on paid media you should be on the 1st-party server-side tier — rather than quote you a recovery percentage, we'll show you how to measure your own gap: compare what the platforms reported against the orders in your backend for the same week. That ratio is the entire argument, and it's yours to check — see trackingconsulting.com/measurement-accuracy-methodology.
- One-time fee · zero monthly · zero SaaS lock-in
- Wix dataLayer (clean spec)
- GA4 e-commerce events
- Meta Pixel · Google Ads tag
- TikTok Pixel · Microsoft UET
- Consent Mode v2 banner integration
- QA test orders + 7-day support
- No CAPI · no iOS recovery
1st-party server-side
Recommended$800One-time fee · most popular
The done-for-you package every Wix store running paid ads should start with. We build the entire 1st-party server-side stack on your subdomain — Meta, Google, TikTok, Microsoft, LinkedIn all fed from the server. Recovers the conversions iOS, Safari ITP, ad blockers and cookie deprecation hide today. You don't lift a finger. Built in 2–4 days · accurate data in 7 days.
- One-time fee · save vs SaaS subscriptions over 5 years
- Fully recovered + built in 2–4 days · accurate data in 7 days
- Everything in browser-side starter
- 1st-party server-side GTM (your subdomain)
- Meta CAPI · full advanced matching · 8+ EMQ
- Google Enhanced Conversions (Web + Leads)
- TikTok Events API · Microsoft UET server
- Deterministic browser ↔ server deduplication
- Live EMQ verification + screenshots
- Notion runbook + 30-day support · zero recurring
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid-media channel running 1st-party server-side, end-to-end. For Wix brands spending $30K+/month who can no longer afford attribution leaks. Pay once. Own everything. Includes Pinterest + Snap + Reddit + LinkedIn CAPI, Klaviyo identity stitching, BigQuery + Looker Studio.
- One-time fee · save 6-figure SaaS subscriptions over 5 years
- Everything in 1st-party server-side tier
- Pinterest · Snapchat · Reddit · LinkedIn · X CAPIs
- Klaviyo identity stitching (if used)
- BigQuery export (server logs + GA4)
- Looker Studio attribution dashboard (branded)
- Multi-region / multi-currency / EU residency
- GDPR-audit-ready Consent Mode v2 wiring
- 60-day support · optional retainer · no lock-in
FAQ
Wix questions, answered
Yes — works on any Wix Stores plan with Velo enabled.
We usually disable the redundant ones and consolidate on the cleaner stack.
WhatsApp