Troubleshooting

Fixes for the most common issues — no data in GA4, DNS not verifying, Tag Assistant not connecting, and cache/cookie problems.

Most issues come down to something not being published, or a DNS setting. Work through these in order.

No data in GA4 Realtime

  1. Did you publish both containers? The Server container (for the Tagging Server URL) and the Web container / Google tag (for server_container_url) must both be published. This is the #1 cause.
  2. Is the Server URL correct in both places? Compare the URL on your container page with what's in GTM — exactly, including https://. See Connect GA4.
  3. Is there a GA4 client in the server container? New server containers include one by default; if you removed it, re-add the GA4 client.
  4. Test in Preview. If events arrive in preview but not in Realtime, the issue is on the GA4/tag side, not the server.

DNS isn't verifying (own-domain mode)

  1. Proxy must be OFF. On Cloudflare, both CNAME records shown on your dashboard must be DNS only (grey cloud). An orange "proxied" cloud will block verification.
  2. Both records added? You need both CNAMEs from your dashboard, with the exact target values shown there.
  3. Give it time. Propagation can take from a few minutes to a couple of hours. Pixel Logic re-checks automatically — no need to click anything.
  4. Meanwhile, you're not down. Your Pixel Logic URL keeps working during the switch, so live tracking continues.

Tag Assistant / Preview won't connect

  1. Make sure you started Preview from the Server container in GTM (not only the web container).
  2. Use the same browser for your site and the preview pane; disable other extensions that might interfere.
  3. Confirm the Server URL is reachable (open it in a browser — you should get a valid, secure page, not a certificate warning). If you see a certificate warning right after an own-domain switch, give the certificate a few minutes to finish issuing.

I published a web GTM change but visitors see the old one

Click Purge Cache on your container page. The web container is cached for speed; purging serves the new version immediately. See Manage Your Server.

Cookies don't seem to persist (Safari)

  • Confirm you're sending data through your Server URL (not straight to Google).
  • Cookie durability is strongest on your own domain — if you're on the Pixel Logic URL and need maximum Safari longevity, switch to first-party.

Still not working?

Contact us with your container name and what you've tried — we'll dig in.