On Wix there are two clean routes: connect Meta through the Wix dashboard, which also gives the site a server-side route to the Conversions API, or paste the base code in the custom code area set to load in the head. Choose one, remove the other, and make sure the Lead fires once per saved form submission rather than on the click.
Route 1: the Wix connection
Meta lists Wix among the commerce platforms that work as partner integrations for the Conversions API, at no extra cost. That is the practical advantage of this route: the platform that renders the site also knows when a form was submitted, so a server event can be sent even when the visitor’s browser blocked the Pixel.
- In the Wix dashboard, open the marketing or integrations area and find the Meta connection.
- Connect the Facebook account that has access to the right business portfolio, then pick the Pixel.
- Choose which form submissions count as a lead. One event, one form, so the mapping stays readable later.
- Publish the site. The connection only applies to the live version, not to the editor preview.
- Submit a test form on the live site and check that the event arrives in Events Manager.
Dashboard labels change between versions, so look for the Meta or Facebook item rather than a specific menu path. What matters is which events the platform sends on its own, as the platform integrations row in Meta Pixel setup warns: a connection that already reports a Lead makes any coded Lead the second copy.
Route 2: the base code by hand
Custom code is the route for a Wix site whose forms submit somewhere else, or for a landing page built in Wix next to a CRM that owns the conversion.
- Copy the base code from Events Manager, under Data sources, for the Pixel you intend to use.
- In the site dashboard, open the custom code area, add a snippet and paste the code unchanged.
- Set it to load in the head, on all pages. A code added at the end of the body fires the PageView late, and a visitor who leaves quickly is never counted.
- Publish, then load the live site with the browser console open and confirm the Pixel initialised with the ID you expect.
- Check the site’s cookie banner: if it holds back custom code until consent, nothing is sent until someone accepts.
Keep the snippet in one place. Two snippets, or a snippet next to the platform connection, produce duplicate PageViews and, worse, duplicate Leads.
Which events to send
| Event | When it fires | Sent by |
|---|---|---|
| PageView | the landing page or form page loads | the base code, automatically |
| Lead | a form submission has been saved | the platform connection, or your own call after the success state |
| A custom event such as FormStart | the visitor begins filling the form | the browser only, and only if you code it |
A Wix form that shows a confirmation screen has a natural success state, and that is where the Lead belongs. A refresh of the confirmation, or a back button visit, must not create a second Lead: tie the event to the submission, not to the page load.
If the platform connection sends the Lead, leave it alone. If you code your own, pass an event ID that matches the server side, so Meta pairs the two copies instead of counting one form twice. Meta pairs them when the IDs and the event names match inside 48 hours, keeps the first copy, and favours the browser copy when the two arrive within five minutes of each other. The mechanics are in Pixel and CAPI deduplication.
Building a server route on Wix
If the platform connection is not available for the plan or the template, the server-side options are the same as on any site: a partner that already posts from the server, a Conversions API Gateway relaying the browser events through a server you host, or a direct integration from a backend that saw the submission. Meta’s four setup options never change, and the Conversions API setup covers what each one needs.
The part that does not move is the payload: a hashed email and phone, the fbc and fbp values from the visit, the IP address and the user agent in clear, and one event ID shared with the browser. On a Wix site the fbc value depends on the fbclid reaching the page, so check that the ad’s destination URL has no redirect chain in front of it that rebuilds the query string.
What breaks on a Wix site
- The platform connection plus a hard-coded base code, so every event fires twice.
- A Lead on the submit click, which counts failed validations and double taps.
- A form inside a lightbox or an embedded widget whose success state the snippet never observes.
- A consent banner that holds back custom code, so a share of visitors is invisible in Events Manager and still submits the form.
- A site published to a staging address tested instead of the live domain, which sends events from a URL that is not the one the ads point at.
Check it the way Meta checks it
Open Events Manager, choose the Pixel, then Test events. Submit the form on the live site with your own details and look for the Lead with the parameters you expect: name, event ID, and the fbc value when you arrived from an ad click. Then submit again and refresh the confirmation, and confirm the count does not move. Event Match Quality is worth a look at the same time, and the Event Match Quality guide explains which fields move the score.
One habit makes all of this cheaper: keep the count of leads in your own system as the reference, and use Meta’s number to steer delivery. They will differ, and Meta Pixel, Conversions API and attribution covers the reasons. DropCPL takes the landing page off the site builder entirely: the page is served from your own domain, the click is logged there first-party, and each lead leaves for Meta server-side with the ad, the creative and the landing page attached.