Install GA4 tags in the server container

Prerequisites

• a GTM server container
• a web container already configured to send GA4 events to your server container endpoint

  (using the server_container_url parameter)

• a GA4 Measurement ID and property ready

Set up the GA4 client in the server container

The GA4 client is responsible for intercepting incoming GA4 HTTP requests and parsing them into event data objects for further processing.

1. Open your GTM server container.
2. Go to Clients in the left menu.
3. If the GA4 client does not exist, click New and select Google Analytics: GA4 as the client type.
4. Configure the client settings:
   Default GA4 paths

   Keep enabled to capture standard GA4 event requests, such as /collect or /g/collect.
   Default gtag.js paths for specific IDs

   Enable if you want your server container to serve the GA4 JavaScript library through your domain. List your Measurement IDs as needed.
   Automatically serve all dependent Google scripts

   Recommended to keep enabled for seamless script loading.
   Compress HTTP response

   Enable for optimized network usage.
   Enable region-specific settings

   Optional, for advanced consent and privacy controls.
   Cookies and Client Identification

   Use "JavaScript Managed" by default, or configure server-managed cookies if you have set up a custom domain.
   
5. Save the client configuration.

Create a GA4 tag in the server container

The GA4 tag will receive event data from the GA4 client and forward it to your GA4 property.

1. In your GTM server container, go to Tags and click New.
2. Click Tag Configuration and select Google Analytics: GA4.
3. Leave fields at their default values unless you need to customize event forwarding (the tag inherits Measurement ID and parameters from the client).
4. Optionally, add custom mappings or parameter modifications as needed for your analytics strategy.

Set the trigger for the GA4 Tag

1. In the tag settings, click Triggering.
2. Click the + icon to create a new trigger.
3. Choose Custom as the trigger type.
4. Set the trigger to fire on events generated by the GA4 client:
   • Under conditions, select Client Name equals GA4.
   • This ensures the tag only fires for events parsed by the GA4 client.
5. Save the trigger and tag configuration.

Test your server-side GA4 setup

1. Use the Preview mode in your GTM server container to simulate incoming events.
2. In your browser, trigger events on your website (e.g., page views, purchases).
3. In the server container preview, verify that:
   • The GA4 client claims the incoming requests.
   • The GA4 tag fires as expected.
   • Events are dispatched to your GA4 property (check GA4 DebugView or Realtime reports).
4. For additional validation, append /healthy to your server container URL in a browser to check server health (should return ok).

Best practices

Troubleshooting

Useful resources

Where to find your Google Tag