File Proxy power-up

The File Proxy power-up lets you serve external files through your own subdomain via sGTM, reducing reliance on third-party domains. This helps improve script reliability, reduce ad-blocking interference, and keep asset delivery under your control.

File Proxy is available on the Business subscription plan and higher. To check your current plan or upgrade, go to your sGTM container settings.

1. Log in to your Stape account and select your sGTM container from the dashboard.

2. Go to the Power-ups tab.

3. Scroll down to the Utilities and infrastructure section, and click on the File Proxy panel.

4. Toggle the File Proxy switch to enable it.

5. Fill in the required settings:

• Original file URL - the URL of the file you want to proxy.
• sGTM path - the path used to serve the file through your tagging server. For example, if your tagging server is sgtm.example.com and you set the path to /file.js, the file will be served from sgtm.example.com/file.js.
• Cache max age - the maximum time the file should be cached.

6. Click Save changes.

After saving, verify the setup by loading the file from your configured sGTM path. For example, if your original file is hosted at ss.example.com and your sGTM path is /load.js, confirm the file loads correctly from sgtm.example.com/file.js.

A sample scenario is a marketing team that notices their third-party tracking scripts are being blocked at an unusually high rate, causing gaps in conversion data. Their ad platform reports show strong click-through numbers, but attributed conversions in the dashboard are consistently lower than expected, and they can't tell whether the discrepancy is due to ad fraud, user drop-off, or script blocking.

You can identify this problem and fix it this way:

1. 1.
   In your ad platform, compare click volume against the number of conversion events recorded in your sGTM container over the same period. If clicks are high but server-side events are significantly lower, script blocking on the client side is likely the cause rather than a tracking configuration issue.
2. 2.
   Enable the File Proxy power-up and configure it to serve your tracking script from your sGTM subdomain instead of the original third-party domain. Set an appropriate cache max age. For example, 86400 seconds for a script that updates infrequently, to ensure fast load times without stale content.
3. 3.
   Monitor conversion event volume before and after the change over 1-2 weeks to establish a reliable comparison baseline.

If script blocking was the root cause, you will see a measurable increase in conversion events recorded server-side.