Uliana Lesiv
AuthorIn this article, we'll explore Setup Assistant, a tool developed by Stape. You'll learn how it works, who can benefit from it, and the key advantages it provides.
Setup Assistant is a tool developed by Stape that simplifies data tracking configuration. It generates pre-made Google Tag Manager (GTM) container templates based on the tech stack and platforms you select. Once generated, these templates can be automatically imported into your web and server GTM containers.
In short, the process is as follows:
That's all it takes to start tracking right away!
The Setup Assistant is a valuable tool for anyone who wants to save time and get a customized template for their web and server GTM containers.
It is useful for marketers and business owners needing a data tracking configuration for a single website, as well as for agencies or freelancers aiming to optimize their workflow.
Whether your website is custom-built or created on a CMS platform, Setup Assistant has you covered.
Here's a list of supported CMS options:
As for the most popular advertising platforms, our Setup Assistant supports:
| Benefit | What do I get? |
| Fast launch | Skip hours of manual work — your GTM setup is ready in minutes so you can focus on growth instead of configuration. |
| Flexible tracking | Select the platforms and destinations you need and get custom GTM templates that match your business setup. |
| Expert-built configuration | Setup Assistant applies proven best practices from Stape experts. |
| User-friendly | Designed for marketers and business owners, no technical skills are required to get started. |
| Free of charge | Enjoy all these benefits at no additional cost. |
2. Ensure you have created a web container and a server container in Google Tag Manager.
3. Ensure your server container is hosted on Stape.
4. (Optional) Ensure you have configured a custom domain (although it's optional, we highly recommend it for setting first-party cookies).
5. If your website is built on Shopify, Magento 2, BigCommerce, WordPress, Wix, PrestaShop, or Salla, ensure the data layer is configured in the CMS app of the platform you're using.
The app configuration is similar for each CMS:
6. If you have a custom website, you'll need to collaborate with your developers to implement the data layer events with the specific payloads you need. To create a data layer, you can make a copy of our documentation, edit it according to your needs, and share the doc with your developers. Please check our article on data layer for helpful guidelines on data layer implementation.
Go to the "Setup Assistant" section on the menu in the Stape admin account.
Then, click on "Got it, let’s go!" to start answering the questionnaire.
Type - indicate your setup type. eCommerce setups focus on product tracking, while Lead Generation setups focus on form submissions and conversions.
Platform (if you select eCommerce as a type) - specify the CMS platform you are using (e.g., Shopify, WordPress, etc.). Setup Assistant can provide the appropriate templates and settings for your site, ensuring that everything works seamlessly with your CMS. If your platform is not on the list, select Other.
Consent settings - check the box if you have a consent provider. Then, select one from the list.
| Note: If you choose Other as your consent provider, you need to specify an additional event in the dataLayer that signals a change in consent status. You can usually find this information from your consent provider or by checking the dataLayer when the consent status changes. |
Select the advertising and analytics platforms you want to track (e.g., Google Ads, Meta, GA4, etc.).
Different platforms require specific tags and tracking settings. By selecting the platforms you want to track, the Setup Assistant customizes your GTM container with the necessary tags. This step ensures that your tracking setup aligns with the platforms you want to use.
Please note
If you selected the “Lead generation” type, enter the URLs of the “thank you” pages that users reach after completing the lead form (Lead event “Thank you” page URL) and/or after scheduling a call (Schedule event “Thank you” page URL).
Use the following format:
https://yourdomain.com/thank-you-page
To proceed, you must configure at least one field.
These URLs will be used to create tag triggers, allowing you to measure how many users submitted the form and/or scheduled a call.
If your website uses forms or call-scheduling tools but does not redirect users to a “thank-you” page after submission (for example, if it only shows an on-page confirmation pop-up), these interactions cannot be tracked. This is because viewing a thank-you page is a required trigger parameter.
Please contact your developers and request the creation of a separate thank-you page.
Enter the tracking details such as your Pixel ID, Analytics ID, or other required credentials.
This information is essential for the Setup Assistant to link your site to the respective platforms. It ensures that data is sent accurately from your website to the right destination and helps you to track conversions, user interactions, and more.
Without this step, the necessary data cannot be captured and sent to your platforms. Additionally, you can add IDs directly in your web and server containers at any time.
Regardless of the platform you need to configure, the Server Container URL field is required for any.
To find Server GTM container URL, log in to your Stape account → navigate to the sGTM section of the menu → choose your container → Domains (Tagging Server URLs) → copy domain name.
| We have prepared a quick guidance on how to find each necessary ID for destinations. |
The configuration will slightly differ based on the type you’ve chosen (eCommerce or lead generation). Here, we show how to set up both.
API Token - in Campaign Manager, → click Data on the left menu → click Sources → Select Google Tag Manager → click Generate token.
Here is an example of the fields configuration for the eCommerce type:
Here is an example of the fields configuration for lead generation type:
Here is an example of Snapchat fields configuration:
Here is an example of a field configuration for TikTok:
The configuration will differ based on the type you’ve chosen (eCommerce or lead generation). In this section, we show how to set up both, and we will start with the eCommerce fields.
Here is an example of Google Ads fields configuration for the eCommerce type:
Here is an example of Google Ads fields configuration for lead generation type:
The configuration will slightly differ based on the type you’ve chosen (eCommerce or lead generation). Here, we show how to set up both. We will start with the eCommerce fields.
Here is an example of Microsoft fields configuration for the eCommerce type:
Here is an example of Microsoft fields configuration for lead generation type:
Here is an example of Pinterest fields configuration:
Choose how you want to import templates: automatically or manually. Click on Next.
1. Authorize with a Google account that has access to the GTM account you want to import templates into.
Please note
2. Select containers and corresponding workspaces into which you want to import templates and click Import templates.
Please note
3. Make sure the templates are in your web and server GTM containers. The imported templates will be neatly organised into folders starting with “[Stape]”.
If the templates weren't imported automatically, please try importing them manually by following the instructions.
1. Click on the green buttons to download the templates.
2. Open the Web or Server GTM container, go to the Admin tab, and click Import Container.
3. Select the file you recently downloaded from Stape.
For example, the JSON file “gtm-web-template” you downloaded (make sure you upload the correct file that matches the container type - web or server).
Select the workspace for this import - new or existing.
4. 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. |
5. Click Add to workspace.
6. Do the same within the server GTM container, making sure you import the JSON file named “gtm-server-template”.
Simply open the tags to ensure they include all the necessary data, and run Preview in both web and server GTM containers.
Trigger the events on your website and check whether the tags work successfully. Once confirmed, publish the changes to activate the setup.
| For more details on debugging and monitoring your server-side tracking setup, refer to our guide. |
After publishing the changes, you can verify if everything is working correctly using our Website Tracking Checker by Stape.
Check whether you have any additional plugins or integrations that also send events to the same platforms that are currently configured in GTM. Sending duplicate events can lead to over-reporting. For example, Shopify has Google and Meta apps that may have active integrations for sending events. If any such integrations exist, disable this functionality in the apps.
Similarly, consider what you may already have in your GTM containers or site codebase, and ensure there are no conflicts or double-firing tags.
If you have any questions, please feel free to ask them in our Stape Community.
Setup Assistant is an excellent choice for anyone looking to simplify their tracking setup. It saves you time and effort by offering pre-configured templates tailored to your platform and business needs. With a user-friendly interface and expert-built configurations, you can set up your tracking in minutes without the need for technical skills.
Comments