This is for Wix site and Wix Stores owners who run Google or Meta ads and can't trust the numbers they see. Wix's built-in marketing integrations are easy to switch on, but they are hard to customise and easy to duplicate with manual code. I decide what Wix should handle natively, what GTM should handle, and add server-side events where they make the data more complete.
Proper Wix tracking means choosing one sender per event: Wix's built-in Marketing Integrations or GTM, not both. GTM connects through the Wix dashboard and reads the events Wix pushes for Stores, Bookings and forms. Purchases go to GA4, Google Ads and Meta with value and order ID, and server-side GTM adds a Conversions API copy with deduplication.
The events I set up on Wix, and where each one is sent.
Wix lets you connect GA4, Google Ads, the Meta Pixel and GTM from Marketing Integrations, and also paste code in Settings > Custom Code. Sites often end up with the same pixel installed both ways, so every purchase and lead is counted twice.
Wix pushes its own store events to the dataLayer when GTM is connected, but the names and structure don't match GA4's recommended ecommerce schema. Without remapping, GA4 gets purchases with missing items or no value.
You can't freely edit the Wix checkout or drop scripts into it. Tracking checkout steps and the thank-you page has to rely on the events Wix exposes rather than your own page code.
Wix Forms usually show a success message instead of loading a new page, and Wix Bookings runs its own flow. A thank-you page trigger never fires, and button clicks count failed attempts as leads.
Even when the built-in Meta integration is working, ad blockers, Safari limits and declined consent mean a share of conversions never reach Meta or Google from the browser.
| Event | When it fires | Sent to |
|---|---|---|
view_item / ViewContent | Wix Stores product page viewed | GA4, Meta Pixel + CAPI |
add_to_cart / AddToCart | Product added to cart | GA4, Meta Pixel + CAPI |
begin_checkout / InitiateCheckout | Checkout started from the cart | GA4, Meta Pixel + CAPI |
purchase / Purchase | Wix reports the order as completed (thank-you page) | GA4, Google Ads, Meta Pixel + CAPI |
generate_lead / Lead | Wix Form shows its success message | GA4, Google Ads, Meta Pixel + CAPI |
book_appointment / Schedule | Wix Bookings appointment confirmed | GA4, Google Ads, Meta |
contact_click | Click on a tel:, mailto: or WhatsApp link | GA4, Google Ads |
I check every place tracking can live on Wix: Marketing Integrations, Custom Code, embeds and apps. Then I compare platform conversions with your Wix orders and form submissions.
We agree which events stay with Wix's native integrations and which move to GTM, so each event has exactly one sender per platform.
I connect GTM, remap Wix store and form events to GA4 and ad platform events, and add server-side GTM for Meta CAPI.
I place test orders and submit real forms on your published domain, and confirm each one is counted once in every platform.
You get an event map and notes on what to check when you add apps or change your store setup.
Wix's built-in integrations for Google and Meta are fine for a simple setup and need no code. Their limits show up when you need control: custom event names, extra parameters, conversion values for leads, or a single server-side pipeline for several platforms.
My usual approach is to connect GTM through the dashboard, which is how Wix recommends adding it rather than pasting the snippet into Custom Code. GTM then listens to the events Wix pushes and sends them on in the format each platform expects. Where a native integration is already doing a job well, such as catalogue sync, I keep it and switch off only the overlapping events.
Wix doesn't let you run your own server code next to the site, so server-side tracking runs in a separate server GTM container on Stape or Google Cloud, on a subdomain of your own domain. Browser events are forwarded there and sent to Meta CAPI with the same event ID as the Pixel, so Meta keeps one copy of each.
For developers using Velo, Wix's backend order events can also send a server copy of each order, which helps when the thank-you page doesn't load in the browser.
A server-side Meta tracking build for a Wix store, sending every funnel event through the Conversions API on a custom tracking subdomain and deduplicating it against Wix's browser Pixel.
Read case studyConnect it from Marketing Integrations in the Wix dashboard by entering your GTM container ID. Wix recommends this over pasting the snippet into Custom Code. Custom Code and connected integrations generally need a premium plan with a connected domain.
Usually because the same pixel or conversion tag is installed twice, once through Wix's built-in integration and once through GTM or Custom Code. Pick one sender per event and remove the other, then test a new order.
Wix's Meta integration can send some server events, but with limited control over parameters and matching. For full control I run server-side GTM on a custom subdomain and send CAPI events with a shared event ID, so they deduplicate against the browser Pixel.
Yes. Either use Wix's GA4 integration, or connect GTM and remap Wix's store events to GA4's purchase event with order ID, value and items. Using both at once creates duplicate purchases.
Track the successful submission, not the button click. When GTM is connected I use the form event Wix exposes or the success message state, then send it to GA4, Google Ads and Meta as a lead.
Meta merges Pixel and server events only when the event name and event ID match. Here is how to set that up correctly and prove it works.
What server-side tracking really is, how server-side GTM works, what it fixes and what it does not, and a checklist to decide if your business needs it.
The step-by-step checklist I use to set up GA4 ecommerce tracking: events, data layer, GTM tags and testing, so product and revenue reports are accurate.
Get a free audit of your tracking and ad account. Usually replies within 1–2 hours.
