Why in-app browsers (Instagram, Facebook, TikTok) break your tracking
When someone taps your link inside Instagram, Facebook or TikTok, it does not open their normal browser. It opens a stripped-down in-app browser with its own rules, and those rules quietly break a lot of tracking, especially for social ad traffic.
What makes in-app browsers different
In-app browsers are isolated: cookies set in them often do not persist, they can block or limit third-party scripts, and they do not share state with the user's real browser. So a visitor who taps your Instagram ad, browses, then returns later in Safari looks like two different people, and conversions that depend on a surviving cookie go missing.
Why it hits social ads hardest
Almost all your paid social traffic arrives through these in-app browsers, so if they break tracking, they break it precisely on the traffic you are paying for. That is a common reason Meta and GA4 never agree and why social campaigns look worse in GA4 than in the ad platform.
How to recover the data
- Rely on the ad platform's own measurement (pixel plus CAPI) for social performance, since it is better placed to match in-app sessions.
- Add server-side tracking so conversions report from your server regardless of the browser's limits.
- Do not judge social campaigns on GA4 last-click alone; it structurally undercounts them.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Tracking works on desktop but not mobile