Stape/GTM container templates

Pre-built GTM container templates for Salla

Updated Aug 29, 2025

The guide explains the process of implementing server-side tracking for your Salla website using Stape's pre-built GTM container template. This template makes it easier and speeds up the server-side tracking setup for Meta, GA4, and Google Ads.

Before starting, ensure you have:

Find out more information on how to set up server-side tagging on your Salla website in our other article.

Step 1. Download container templates

1. Download Salla templates from our GitHub.

Download template from Github
Download template from Github

2. Once you unzip the downloaded file and open the folder it contains, make sure you see the following:

Unzipped files
Unzipped files

For this article, we'll be using highlighted templates which include Meta, GA4, and Google Ads setup. 

Step 2. Import container templates into your GTM

1. You should import the templates into both your web and server containers on GTM. The process is the same across the two. You need to go AdminImport Container:

Import container templates
Import container templates

2. Select your template file (make sure the template matches the container type - web/server).

3. Pick a workspace for this import (you can create a new one for this specific purpose).

4. Select Overwrite or Merge.

"Merge" option with "Rename conflicting tags, triggers, and variables" selected
"Merge" option with "Rename conflicting tags, triggers, and variables" selected
The Overwrite option should only be used in a brand-new, empty container, or if you're completely certain you want to replace everything. For this demo, we're using the Merge option with Rename conflicting tags, triggers, and variables enabled. This ensures that if any conflicts occur, GTM will simply rename the tags instead of modifying or replacing the entities that already exist in your container.

Step 3. Configure your new setup

1. Templates are fully built, so triggers, payloads, and event names are all taken care of for you. You just need to input your specific destinations, ids, API keys etc. We've tried to make it as comfortable as possible, so in both containers (web and server), you will find a folder called [Stape] _Settings.

Web:

Web GTM container folders
Web GTM container folders

Server:

Server GTM container folders
Server GTM container folders

All these variables are already referenced in tags that use them; you just need to give them proper values, for example:

Meta API token - GTM variable
Meta API token - GTM variable

1.1. Pixel ID and API token can found in your pixel settings:

Dataset ID
Dataset ID
Generate access token
Generate access token

1.2. To find GA4 Measurement ID: go to Admin Data collection and modification Data Streams.

GA4 Measurement ID
GA4 Measurement ID

1.3. Google Ads conversion ID and conversion label can be found when creating/editing a conversions goal in Google Ads.

  • choose Use Google Tag Manager;
  • copy ID and label.
Choose “Use Google Tag Manager"
Choose “Use Google Tag Manager"
Copy "Conversion ID" and "Conversion label"
Copy "Conversion ID" and "Conversion label"

Don’t forget to save your changes!

2. Once you've changed all these variables and saved them, your last step (assuming this a new container) is to add a preview URL in your server container by going to AdminContainer Settings.

Note: if the container is not new, just skip this step.

Add a preview URL in your server container
Add a preview URL in your server container

3. From here on you can test and publish your new setup! Yes, it's that easy.

Step 4. Improve your tracking with Stape's advanced features

After implementing and testing your setup, you may want to improve tracking accuracy and reliability. Stape offers several powerful options:

Make sure your marketing cookies remain functional, even if they are deleted.

Strengthens Google Tag Manager and Google Analytics 4 scripts against ad blockers and ITPs by modifying the loading path of gtag.js and gtm.js.

Extends cookie lifetime by setting first-party cookies instead of third-party cookies.

Together, these features can significantly improve the efficiency and flexibility of your server-side tracking.

Conclusion

Pre-built container templates provide a quick and simple way to set up tracking, making them especially useful if you're just getting started or need a solid foundation for your future setup. From there, you can (and should) expand by adding custom events and adjusting the configuration to match your specific requirements. Happy tagging!

Comments

Can’t find what you are looking for?