Meta Conversions API setup for Wix
Wix's marketing integrations panel makes it very easy to add a Meta pixel and very easy to add a second one in custom code. Duplication here is usually panel-plus-custom-code rather than app sprawl.
Free30 minutesNo obligation
Wix + Meta CAPI · what breaks
What goes wrong on Wix — Wix + Meta CAPI
- 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 + Meta CAPI · the fix
What changes — Wix + Meta CAPI
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 + Meta CAPI · architecture
How Meta tracking behaves on Wix
Check both places a pixel can live before adding a third.
- 1
Audit panel and custom code
The two places a Wix pixel hides.
- 2
Conversion event via Velo
So Lead and Purchase actually fire.
- 3
Wix order or submission ID as event_id
Where a server event is also sent.
- 4
fbclid captured on landing
Into a form field, so fbc exists.
- 5
Customer data normalized before hashing
From the Wix record.
Wix + Meta CAPI · diagnose
Where Wix tracking breaks, in diagnostic order — Wix + Meta CAPI
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 + Meta CAPI · prove
The QA evidence — Wix + Meta CAPI
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 + Meta CAPI · 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 + Meta CAPI · when not to buy
When you don't need this on Wix — Wix + Meta CAPI
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 + Meta CAPI · what we deliver
What gets built for Meta on Wix
A shared event ID on both paths
The Wix order or submission ID, available to Velo and to any automation webhook.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
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 + Meta CAPI questions, answered
Almost always the marketing panel and custom code both have it. Two places, two additions, nobody removed the first.
A Velo submit handler. Binding to a navigation doesn't work, because Wix forms don't reliably produce one.
Capture fbclid on landing in custom code and write it into a form field. Without capture, fbc never exists.
Only if you're losing events. The webhook route makes it possible; fix the browser-side Lead event first.
Free · 30 min
Get Pixel and CAPI counting once on Wix
Free30 minutesNo obligation
