In this article, I will describe how to set up a custom subdomain within your Google Tag Manager server container. The main advantage of a custom subdomain inside the Google Tag Manager Server container is that it helps to bypass Intelligent Tracking Preventions, AdBlockers and increases cookie lifetime for users browsing in Safari. Pixels will be loaded from your subdomain and run as the first-party.
Google Tag Manager Server-side tagging allows moving out third-party tracking pixels off the website or app to the server-side environment.
Server-side tagging offers a few advantages over client-side tags:
You have two option for tagging server URL:
We recommend setting up a custom subdomain since with the custom subdomain you’ll enjoy the following benefits:
Tracking prevention doesn’t affect requests from your own domain. Your website will bypass AdBlockers and ITPs, giving the full data about your website visitors and conversions.
First of all, you need to create and set up the Google Tag Manager server container. If you don’t have a server container follow this instruction.
1. Log in to your stape account, choose a container, scroll down and click Add domain.
2.Navigate to your DNS provider; for instance:
3. The below example will show how to add DNS setting in Cloudflare. Login to your account -> click on your site’s domain -> Click DNS -> Add record
4. Add these setting:
Name: ss (or any other subdomain you prefer)
IPv4 address: IP address depends on the location of the servers. You can find the custom domain IP address in your stape.io account.
Proxy status: disable
Your settings should look like this:
Do not forget to add CNAME record if you enabled CDN for your container. You will find required CNAME records in the stape.io container settings.
5. Once you have done, click Save.
6. Go to your app.stape.io account and add a custom domain. It should consist of the name that you added to Cloudflare and your domain. Click Save. After adding the domain, it passes through the verification process. It can take up to 72 hours. Once the domain is verified, the status will be changed to “Verified”
You can force stape to verify domain by clicking "revalidate domain" button near in sGTM container setting
7. Once your GTM subdomain is added and verified, you should see the status Running.
8. Go to your Server Google Tag Manager Server container -> Admin -> Container Settings -> Change Tagging server URL to your subdomain.
9. Modified Google Tag Manager code on your website with a new Tagging server URL to your subdomain. It should look like this:
10. Update tagging URL inside Google Analytics Tags or Google Analytics Variable inside your GTM web container. Open Google Analytics Tag -> More Settings -> Advanced Configuration -> Past your GTM subdomain inside Transport URL.
That’s it! Now your GTM server container runs from your subdomain.
1. It's been more than 72 hours, but my domain still not verified.
First of all we recommend using one of free online DNS checkers to verify if DNS settings are correct. Stape team uses this tool by Google. All you need to do is add your custom domain and verify that A and CNAME records (in case you've enabled Global CDN)
You must have only one A record and one CNAME record (if you've enabled Global CDN). If there are multiple records please remove non-stop records and use another custom domain for stape.
2. I've checked my DNS settings, it's correct but domains is still not verified.
If you've previously used the same subdomains for GCP ensure that you removed AAAA record. Also log in to your stape account, open sGTM container settings and click Revalidate Domain.
In case all these did not help, contact stape.io support.
All it takes is a few simple questions. Click Get help, fill up the form, and we will guide you.
By the end of 2024, Chrome and Chrome-based browsers will be done with third-party cookies. Safari and Firefox already implemented Intelligent Tracking Algorithms that can block trackers. That leads to the next point: digital advertising methods that rely on third-party cookies to target consumers might become ineffective or even stop working altogether. This change in how advertisers track users will hurt many publishers and ad networks that rely on these third-party companies to display ads and collect data from site visitors to understand their audience. In this blog post, I will explain what a third-party cookie is, why it matters, and how server-side tracking can help businesses transit to the world without third-party cookies.Oct 8, 2021
What cost can you expect for server Google Tag Manager hosted on Google Cloud? Is it a good idea to use a test environment on the productions site. Why stape’s hosting for server GTM is cheaper and how we secure our user’s data.Feb 28, 2021
Server-side tagging has been one of the main trends in web analytics for the last couple of years. Ad blockers, Intelligent Tracking Protection, 3rd party cookie restrictions, regulations like GDPR made analytics and advertising companies start worrying about how and what information they collect about site visitors. Server-side tagging allows moving third-party tags off your site and into a cloud server. In this case, third-party pixels are loaded directly from the could server rather than your site. In this article, I will explain and demonstrate the basics of setting up Google Tag Manager server container, server Universal Analytics, GA4, and Facebook Conversion API.