Pre-configured Google Tag Manager container templates for Wix provide a powerful solution that simplifies the server-side tracking setup. These templates make it quicker and easier to configure server-side tracking for Meta, GA4, and Google Ads.
In this article, we’ll walk you through the steps needed to configure and complete the server-side tracking setup for your Wix website.
To set up the pre-built template, make sure you have:
1.1 Download GTM Templates for Wix from GitHub. Click on “Code” → “Download ZIP”.
1.2 Unzip the file you downloaded. We will use the first two highlighted templates, which include Meta, GA4, and Google Ads setup.
2.1 To import the templates, go to Admin → Import Container.
Please note you should import the templates in both - web and server GTM containers. The process is the same for both containers.
2.2 Select the template file from the unzipped folder (ensure you upload the correct file that matches the container type - web or server).
Select the workspace for this import - new or existing.
Select Overwrite or Merge.
| The "Overwrite" option should only be used with a new or empty container. For this demo, we are using the Merge option with the "Rename conflicting tags, triggers, and variables" setting enabled. This ensures that GTM will simply rename the tags without altering existing entities in your container if any conflicts arise. |
Click “Add to workspace”.
3.1 Templates come fully prepared, with configured triggers, payloads, and event names. You only need to enter your specific destinations, IDs, API keys, and other details. For your convenience, see the “Folder” section of web and server GTM containers, here, you can find the folders that start with “[Stape]”; they store all the pre-built tags and variables.
Web
Server
All the variables are already referenced in tags that use them; you only need to change the values.
Here is the example with added value for the Meta API token variable:
To customize the tags and variables for Meta, GA4, and Google Ads you will need the following data:
a. For Meta settings, you will need Pixel ID and API token.
You can find the Pixel ID and API token in Pixel Settings:
b. For Google Analytics 4 settings, find the GA4 Measurement ID by going to Admin → Data collection and modification → Data Streams.
c. Google Ads conversion ID and conversion label you can find when creating/editing a conversion goal in Google Ads.
Save changes.
3.2 If your GTM container is new, add a preview URL in your server container by going to Admin → Container Settings. If the container is not new, skip this step.
3.3 Test and publish the setup. The test process is the same as when making changes in the GTM container. Run Google Tag Manager preview, trigger events on the website, and see them in GTM.
| Check the detailed post on debugging and monitoring server-side tracking configuration. |
Having completed the configuration, you may want to improve tracking accuracy with the help of Stape power-ups and features:
This feature enhances the resilience of Google Tag Manager and Google Analytics 4 scripts against ad blockers and ITPs by adjusting the loading paths of gtag.js and gtm.js.
Using a custom domain allows you to extend cookie lifespan by setting first-party cookies instead of third-party ones.
| See the detailed instructions on how to add a custom domain to the Google Tag Manager server container in our blog post. |
Pre-built container templates for Wix offer a fast and easy solution for implementing server-side tracking. They provide a strong foundation for those looking to build out their setup further.
And if you need help with our Stape Server GTM app for Wix or Stape admin, don’t hesitate to contact us.
Stape has lots of tags for server GTM! Click on Try for free to register and check them all.
