Google Tag Manager on Wix

Google Tag Manager (GTM) works on Wix, and you connect it without touching code: go to Marketing Integrations in your site's dashboard, click Connect under Google Tag Manager, click Add Google Tag Manager, enter your GTM ID and click Save. You need a Premium site and a connected domain. Wix is direct on one point: "Do not use custom code to connect Google Tag Manager."

The part that surprises people who have used GTM elsewhere is the triggers. Wix is a single-page application, so GTM's built-in "All Pages" trigger doesn't behave as it does on a traditional website. Wix tells you never to use it for page views and to fire tags on a Custom Event trigger named Pageview instead.

Do you need GTM on Wix?

GTM is a container: one script on your site that loads other tracking tags according to rules you set in Google's interface. It is useful when you have several tags and want to control them in one place. It adds work when you only need Google Analytics.

Wix offers three routes for adding tracking, and they suit different situations.

If all you need is GA4 with Wix's standard events, the simpler route is in our guide on how to add Google Analytics 4 to Wix. Choose GTM when you need something that route can't do and someone will maintain the container.

The choice is either-or for Google tags. Wix states: "Avoid installing Google Tag and Google Tag Manager together, as they may conflict with each other."

How to connect GTM to Wix

First create a GTM account and a web container at Google, and note the container ID. Then, following Wix's article on connecting your Google Tag Manager account to your Wix site:

1. Go to Marketing Integrations in your site's dashboard.
2. Under Google Tag Manager, click Connect.
3. Click Add Google Tag Manager.
4. Enter your GTM ID.
5. Click Save.

Before you add tags in the container, remove overlaps on the Wix side. If Google Tag is connected in Marketing Integrations and you intend to run GA4 through GTM, remove the Google Tag connection. If you plan to run the Meta Pixel inside GTM, Wix says the same code must be disabled in your Wix account, or it "may cause the code to misreport or malfunction".

Why Wix needs different triggers

On a traditional website, every click to a new page loads a fresh document. A single-page application loads once and then swaps content as the visitor moves around, so a trigger that waits for a full page load can miss the later pages.

Wix handles this for you in the data layer, which is the list of events and values a site hands to GTM. In Wix's words: "Wix ensures a pageview event is sent to the Google Tag Manager data layer every time a user visits a new page on your site." Your job is to listen for that event. Wix's instruction is to never use the built-in "All Pages" trigger "since it is not compatible with Single Page Applications", and to create a Custom Event trigger with the event name Pageview.

Setting up GA4 inside GTM, the way Wix recommends

Wix's guide to setting up Google Tag Manager with Wix describes a two-tag setup:

1. Create the Google Tag configuration tag. Enter your GA4 Measurement ID. Add a configuration parameter named send_page_view with the value false. Set its trigger to "Initialization - All Pages". The send_page_view setting stops this tag from sending its own page view.
2. Create the Pageview trigger. Add a new trigger of type Custom Event, with the event name Pageview.
3. Create a GA4 Event tag. Give it the event name page_view and attach the Pageview trigger from step 2.
4. Preview, then publish the container. Use GTM's preview mode to confirm one page_view fires on each page you open.

The result is that page views come from Wix's Pageview event only, one per page.

When you create the GA4 web stream, Wix's Google Analytics setup also asks you to deselect "Page changes based on browser history events" in the stream's advanced page view settings.

The data layer events Wix documents

Beyond page views, Wix describes events and variables you can use for conversions. These come from its article on tracking Google Ads conversions, as of October 2026. The user_data variable is from its enhanced conversions article.

One inconsistency to know about. Wix's conversions article uses a Custom Event trigger named lead for form submissions. Its enhanced conversions article uses generate_lead. Don't assume either. Open GTM's preview mode, submit a test form on your live site, and read the event name that appears. Build your trigger on what you see.

Wix also says the events it supplies to GTM are "compatible with the Google Analytics format", and its events list for GTM includes view_item, add_to_cart, begin_checkout, purchase and generate_lead.

Tracking conversions with GTM on Wix

Form leads

Wix recommends capturing the lead event as the trigger. The alternative is a thank-you page method: a Pageview Custom Event trigger filtered to the thank-you page's URL. Use the event_label variable if you want to count a quote form separately from a newsletter signup.

Purchases

For stores, Wix says: "Do not use the Thank You page capturing method to track eCommerce-based conversions". Use the purchase event, with the transaction ID and revenue variables passing the order details. Wix notes other ecommerce conversions can be set up the same way, such as "View product page", "Add to cart" and "Begin checkout".

Phone, email and WhatsApp clicks

This is where GTM adds something the native integrations don't. Wix documents a "Click - Just links" trigger filtered on the link address containing Tel:, mailto or wa.me. That lets you record clicks on phone numbers, email addresses and WhatsApp links anywhere on the site. We go further into this in tracking leads and calls from a Wix site.

Turning these into ad conversions is covered in Google Ads conversion tracking on Wix.

A shortcut: export from Wix Event Manager

Wix has a tool called Event Manager, in Marketing Integrations, that scans your site for trackable events and lets you define Google Ads conversions without code. When you apply the setup with Update Tracking, one of the two options is Google Tag Manager (Advanced), which exports a JSON file of tags, triggers and variables that you import into your GTM container.

Wix adds a warning in its Event Manager guide: "Tracking the same conversion in Wix and Google Tag Manager at the same time can cause duplicates, so you must choose one path."

Consent and GTM on Wix

If your site shows a cookie banner, Wix says "Google Tag Manager will only gather data after a visitor provides consent and approves using the relevant cookies." Expect lower numbers than on a site with no banner.

Inside the container, Wix asks GTM users to switch on consent settings. Its article on enabling consent mode in Google Tag Manager gives these steps:

1. In GTM, go to Admin → Container Settings → Additional Settings and select Enable consent overview.
2. Open Tags and click the shield icon to see consent settings for every tag.
3. Set Google tags to "No additional consent required".
4. Set non-Google tags to "Require additional consent for tag to fire" and choose the category that fits.

Wix says it supports the consent types ad_storage and analytics_storage, and what it calls "functionality storage". If your setup depends on other Google consent signals, test what your banner actually sends before relying on it.

Consent law varies by country and state, and this is not legal advice. Wix's tools apply the visitor's choice; deciding what your site must ask for is a question for an attorney. Our guide to cookie consent and privacy on Wix explains how the banner works.

Limits and common mistakes

• Business app pages. Wix's GTM setup article says: "It is not possible to track events for business solutions pages (e.g. Wix Restaurants, Wix Bookings, etc.)". Its separate events list, however, shows Bookings and Restaurants events for GTM. Wix's pages don't agree, so if you depend on tracking inside a booking or ordering flow, test it thoroughly in preview mode first.
• The "All Pages" trigger on tags that should fire per page. Wix says it isn't compatible with single-page applications. Use the Pageview Custom Event.
• Running a tool in two places. GA4 in both Google Tag and GTM, or the Meta Pixel in both GTM and Marketing Integrations, leads to double counting or broken reporting. For Meta, the native route also provides the Conversions API, described in Meta Pixel and Conversions API on Wix.
• Installing GTM through an HTML embed or Custom Code. Use the integration.
• Expecting Wix to debug your tags. Wix does not support technical problems with third-party code snippets and directs you to the provider.
• Loading too much. Every tag is more script for visitors to download. Wix says its own Marketing Integrations "have less of an impact on your site's performance" than pasted marketing code. See Wix site speed and Core Web Vitals.

How to test before you publish

1. In GTM, start preview mode for your live site.
2. If you have a cookie banner, accept all cookies.
3. Open three or four pages and check for one Pageview event per page.
4. Submit a test form and note the event name and the event_label value.
5. On a store, place a test order and check the purchase event and its variables.
6. Repeat the visit without accepting cookies and note what fires, so you know how consent changes your data.
7. Publish the container only when each step behaves as expected.

Conclusion

GTM on Wix is a sound choice when you have several tags to manage and someone with the skills to maintain them. Connect it through Marketing Integrations, base page tracking on the Pageview custom event, build conversions on the lead and purchase events, switch on consent settings, and keep each tool in one place only. If your needs stop at GA4, the native Google Tag integration is less work. If you'd like a container built and tested for your site, or tied into ad campaigns, our Wix website services and search engine marketing teams can help. More guides are in our Wix hub.

Frequently asked questions