Server-side tracking for Wix
Wix hosts your site, so there is no server of yours to hook into. Server-side means an external container receiving events from Velo backend code or from a Wix automation webhook. That's genuinely possible and it's a different shape from a PHP platform — the money event comes from Wix's own APIs, not from your application code.
Free30 minutesNo obligation
Wix server-side · what breaks
What goes wrong on Wix — Wix server-side
- 01
Pixel fires on views, not on conversions
The built-in integration handles page views; the conversion event often isn't wired at all.
- 02
No server code of your own
Wix hosts everything, so PHP-style hooks don't exist.
- 03
Custom code execution is constrained
Where and when your code runs is Wix's decision, not yours.
- 04
Panel plus custom code duplication
The same pixel added twice, in two places, by two people.
Wix server-side · the fix
What changes — Wix server-side
Conversions bound to real Wix events
Velo handlers or automations, not DOM guesses.
One pixel path
Panel or custom code, not both.
Money events from Wix's APIs
Where a server container is used.
Wix server-side · architecture
What Wix exposes to a server container
The container lives outside Wix and is fed by Wix's own APIs.
- 1
Velo backend code posting events
The closest thing to a server-side hook on Wix.
- 2
Automation webhooks for orders
An alternative route that needs no code.
- 3
A first-party endpoint on your own subdomain
For cookie durability past the seven-day cap.
- 4
Order or submission ID as the deduplication key
From Wix's own record.
- 5
Consent enforced at the container
Rather than depending on Wix's panel behaviour.
Wix server-side · diagnose
Where Wix tracking breaks, in diagnostic order — Wix server-side
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Submit a form and watch what fires
Page view only is the usual finding.
- 02
Check the marketing panel and custom code
For the same pixel added twice.
- 03
Confirm Velo handlers exist
If not, conversions aren't bound to anything real.
- 04
Check click ID capture
Wix does nothing here automatically.
- 05
Reconcile against Wix records
Orders or submissions, for a closed month.
Wix server-side · prove
The QA evidence — Wix server-side
Run on Wix specifically, on a live conversion rather than in preview mode.
Source of truth
your Wix order or form submission records
- Conversion confirmed firing on a real submission or order, not a page view.
- Only one pixel path confirmed active across panel and custom code.
- Click identifiers confirmed present in the submitted data.
- Counts reconciled against Wix's own records for a closed month.
- Consent behaviour verified by capture.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Wix server-side · free audit
What we check in the free audit
- Submit a form and watch what fires
- Check the marketing panel and custom code
- Confirm Velo handlers exist
- Check click ID capture
- Reconcile against Wix records
Checked against
your Wix order or form submission records
Free30 minutesNo obligation
Wix server-side · when not to buy
When you don't need this on Wix — Wix server-side
Worth reading before you buy anything, from us or anyone.
- If your Wix conversions already fire on real submissions and reconcile, the built-in integrations are doing their job and you don't need more.
- For a small Wix site with one destination, the marketing integrations panel alone is a legitimate and free setup.
- Velo work needs someone comfortable with it. If nobody at your company is, factor that in before choosing this route.
- Server-side on Wix is external by necessity, which makes it a bigger step than on a platform you host. Be sure the gap justifies it.
Wix server-side · what we deliver
What the server-side build gives you on Wix
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from your Wix records
Velo backend code or a Wix automation webhook, both of which fire from Wix's own record rather than the browser.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
Written guarantee
95%+ tracking accuracy
Measured against your Wix order or form submission 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
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Wix server-side questions, answered
On your own subdomain, outside Wix. Wix hosts the site; it doesn't host your infrastructure.
Velo backend code posting to it, or a Wix automation webhook. Both fire from Wix's own record.
The Wix order or submission ID, available to both Velo and automations.
For cookie durability and consent control, sometimes. Fix the conversion binding first — that's usually the real problem.
WhatsApp