This article is for developers who use server-side tagging and want to serve Google scripts from their own servers.
Server-side tagging allows you to load Google scripts, such as gtm.js or gtag.js, directly from your tagging server instead of from Google's servers. This allows you to serve data within a first-party context.
Before you begin
This guide assumes that you have done the following:
To get started, pick your implementation option.
Step 1: Configure the client
To establish a first-party context between your web container and your tagging server, Google scripts need to be loaded through your server.
To load Google scripts through your server container:
Pick an implementation option to see instructions.Step 2: Update the script source domain
By default, Tag Manager or gtag.js loads their dependencies from Google-owned servers, such as www.googletagmanager.com.
You need to update the script URL on your website to load dependencies through your own server.
Step 3: Verify the source of your scripts
The following instructions show how to test using Google Chrome. You can use any browser of your choice, but the steps might differ.
To test if your server container is loading the dependencies:
- Open your website in a new browser tab.
- Open the browser's developer tools. In Google Chrome, you can right-click anywhere on the page and select Inspect.
In the developer tools, open the Sources tab. This window displays all dependencies that were loaded when you opened the website.
- ✅ Your implementation is correct if
gtm.jsis loaded from the source you specified.
- ❌ If the Sources tab displays
www.googletagmanager.comas the source forgtm.js, the dependencies are still loaded from Google servers.
- Check if you've modified the source URL in your code, see step 2.
- Check if the code is live.
- ✅ Your implementation is correct if
Next steps
If you are using consent mode, you can set up region-specific tag behavior for even more control.