Send GA4 from web GTM through your server container

Skip this section if you already have a GA4 property. You only need its Measurement ID.

1. 1 Open analytics.google.com, go to Admin and click Create, then Property.
2. 2 Enter a property name, your reporting time zone and currency, then finish the business details.
3. 3 When asked to start collecting data, choose Web, enter your website URL and a stream name, and click Create stream.
4. 4 Copy the Measurement ID from the stream details. It looks like G-XXXXXXXXXX.

The Google tag loads GA4 on the page and sends the page_view. One setting, server_container_url, changes where its hits go.

gtag('config', 'G-XXXXXXXXXX', {
  server_container_url: 'https://k7q2x.example.com'
});

Use exactly the URL of your server container: https://, no path and no trailing slash.

Page views and enhanced measurement events (scrolls, outbound clicks, site search, file downloads) come from the Google tag automatically. Your own events, such as sign-ups and purchases, need a Google Analytics: GA4 Event tag. Reuse the sign_up trigger from lesson 1:

1. 1 Create a tag of type Google Analytics: GA4 Event.
2. 2 Set Measurement ID to G-XXXXXXXXXX (your ID). The event goes through the Google tag with the same ID, including its server URL.
3. 3 Set Event Name to sign_up. Under Event Parameters add method with the Data Layer Variable you created earlier.
4. 4 Select the Custom Event trigger sign_up and save.

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({ ecommerce: null });
window.dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'T-10293',
    value: 129.90,
    currency: 'EUR',
    items: [{ item_id: 'SKU-1', item_name: 'Shoes', price: 129.90, quantity: 1 }]
  }
});

Without a server URL, GA4 sends hits to Google hosts such as region1.google-analytics.com or analytics.google.com. With it, the same hits go to your subdomain on the /g/collect path:

https://k7q2x.example.com/g/collect?v=2&tid=G-XXXXXXXXXX&en=page_view&...

• The request stays on your own domain, so it is first-party for the browser.
• Fewer blockers match it, because it no longer goes to a known analytics domain. Blockers that match the /g/collect path can still catch it: Request Proxy in lesson 8 covers that.
• The server container sees every GA4 hit before GA4 does, which is where you can filter or enrich data later.

1. 1 Click Preview in the web container and connect to your site. The Google tag should fire on Initialization and the GA4 Event tags on their events.
2. 2 In the site window open DevTools, go to the Network tab and filter by collect.
3. 3 Reload the page. You should see requests to https://k7q2x.example.com/g/collect with status 200 or 204, and none to google-analytics.com or analytics.google.com.
4. 4 When everything looks right, click Submit and publish the web container.

• No hard-coded gtag.js snippet for the same ID is left on the site.
• The Google tag has server_container_url set to your subdomain.
• /g/collect requests go to k7q2x.example.com.
• The server container Preview shows incoming requests (the debugging lesson explains how to read it).