Connect GA4

Connecting GA4 to Pixel Logic Server is two settings — one on the server side and one on the web side. Both point at the Server URL shown on your container page (either your Pixel Logic URL or your own-domain URL like https://metrics.yourdomain.com).

  ┌──────────────────────────┐
  │  Web GTM / GA4 tag        │
  │  server_container_url     │
  │   = your Server URL       │  ← web side: where the
  └────────────┬─────────────┘    browser sends data
               │  events
               ▼
  ┌──────────────────────────┐
  │  Pixel Logic Server       │
  │  your Server URL          │  ← server side: where the
  │  (server GTM)             │    container thinks it lives
  └────────────┬─────────────┘
               │  via GA4 tag
               ▼
  ┌──────────────────────────┐
  │  GA4                      │
  └──────────────────────────┘

1. Server side — Tagging Server URL

This tells your GTM Server container its own public address.

1. In Google Tag Manager, open your Server container.
2. Admin → Container Settings.
3. Set Tagging Server URL to your Server URL.
4. Save, then Submit/Publish the server container.

Inside the server container you should have a GA4 client (the default "GA4" or "Google Analytics: GA4" client) enabled — this is what receives and processes incoming events. New server containers include it by default.

2. Web side — server_container_url

This tells the browser to send data to your server instead of straight to Google.

If you use the Google tag (gtag) via GTM Web or directly:

1. Open your Google tag / GA4 Configuration tag.
2. Add a configuration field:
   • Field name: server_container_url
   • Value: your Server URL (e.g. https://metrics.yourdomain.com)
3. Publish the web container.

If you configure GA4 in the GA4 Admin (Google tag settings): you can also set the server container URL there under your Google tag's Configure your domains / server settings. Either approach works; do it in one place.

3. Publish everything

Make sure you publish both containers after editing:

• the Server container (so the Tagging Server URL takes effect), and
• the Web container / Google tag (so the browser starts sending to your server).

4. Verify it's working

1. Browse your site in a normal tab and trigger a few events (page views, a button click).
2. GA4 → Reports → Realtime should show the activity.
3. For request-level confirmation, use Preview & Debug — you'll see each event arrive at the server and the GA4 tag fire.

Sending to Meta, TikTok, and others

Once GA4 is flowing, you add more destinations entirely inside your server container in GTM — add the relevant tag (e.g. Meta Conversions API, TikTok Events API), map your event data, and publish. Nothing changes on the Pixel Logic side; your server already forwards whatever your container is configured to send. The More Destinations & Enrichment guide in the Learn track covers the patterns.