The introduction of server-side tagging in Google Tag Manager has expanded the possibilities for your server-side proxy. One of them is eliminating third-party downloads in the browser by routing them through the server-side container.
At Stape, we have a power-up that serves this goal: File Proxy. In this article, we discover its use cases, how it works, and how to set it up.
Serve files through server-side GTM using own subdomain. By proxying files through your own subdomain (the subdomain you created when setting up server-side tracking), you get higher control over file hosting than when using a third-party domain. The higher the control, the higher the security of the files.
Besides, the power-up has the feature to cache the files you need to proxy, so they won’t load whenever required.
In Stape’s admin, you can connect the File Proxy power-up and define the file's URL as well as the desired path for proxying.
For instance, if your tagging server's URL is ss.example.com and the path is /load.js, the file will be loaded from ss.example.com/load.js. Once set up, the server-side GTM container will process requests for specific files and deliver them as if they were coming from your own domain.
1. Go to Stape admin → Power-ups → click “Use” next to File Proxy.
2. Add the required settings:
See the example of the configuration below:
Proxying files through subdomain on the server side provides higher control over files as you don’t use third-party domains for proxying.
Stape has a File Proxy power-up that serves this purpose and is extremely easy to configure. If you have any problems with the power-up, feel free to contact our support team.
Stape has lots of tags for server GTM! Click on Try for free to register and check them all.
