First suspect
A redirect, shortener, app, or platform layer removed the query string before GA4 received the page view.
Troubleshooting guide
If you clicked an ad landing page URL but GA4 does not show the source, medium, or campaign you expected, start with this simple debugging path before changing every setting at once.
A redirect, shortener, app, or platform layer removed the query string before GA4 received the page view.
GA4 is installed twice, installed late, blocked by consent, or not firing on the actual landing page you clicked.
Click the exact final URL, inspect the address bar after every redirect, then check GA4 Realtime right away.
utm_source, utm_medium, and utm_campaign are still visible in the browser address bar.| Symptom | Likely cause | What to check |
|---|---|---|
| UTMs vanish after click | Redirect strips query parameters | Shortener, redirect app, platform redirect, old landing page rule. |
| Visit appears, campaign is wrong | Duplicate or conflicting UTM fields | Look for repeated utm_source or mixed static and dynamic values. |
| No visit in Realtime | GA4 tag not firing | Tag install, consent banner, GTM trigger, page template, blockers. |
| First page works, purchase attribution fails | Checkout or domain handoff issue | Checkout domain, cross-domain settings, duplicate tags, ecommerce event setup. |
Use a very plain URL first. Add macros or encoded nested values only after the basic click path is visible in GA4.
Most GA4 campaign issues get clearer when you separate URL problems from tag and checkout problems.