𝗟𝗮𝘂𝗻𝗰𝗵𝗲𝗱 𝗮 𝗙𝗮𝗰𝗲𝗯𝗼𝗼𝗸 𝗰𝗮𝗺𝗽𝗮𝗶𝗴𝗻 — 𝗮𝗻𝗱 𝗚𝗔𝟰 𝘀𝘂𝗱𝗱𝗲𝗻𝗹𝘆 𝘀𝗵𝗼𝘄𝘀 𝗮 𝘀𝗽𝗶𝗸𝗲 𝗶𝗻 𝗱𝗶𝗿𝗲𝗰𝘁 𝘁𝗿𝗮𝗳𝗳𝗶𝗰? 𝗪𝗲𝗶𝗿𝗱, 𝗿𝗶𝗴𝗵𝘁?

𝗟𝗮𝘂𝗻𝗰𝗵𝗲𝗱 𝗮 𝗙𝗮𝗰𝗲𝗯𝗼𝗼𝗸 𝗰𝗮𝗺𝗽𝗮𝗶𝗴𝗻 — 𝗮𝗻𝗱 𝗚𝗔𝟰 𝘀𝘂𝗱𝗱𝗲𝗻𝗹𝘆 𝘀𝗵𝗼𝘄𝘀 𝗮 𝘀𝗽𝗶𝗸𝗲 𝗶𝗻 𝗱𝗶𝗿𝗲𝗰𝘁 𝘁𝗿𝗮𝗳𝗳𝗶𝗰? 𝗪𝗲𝗶𝗿𝗱, 𝗿𝗶𝗴𝗵𝘁?

You launch Meta ads. Clicks are cheap, engagement looks great, conversions are rolling in.Then you open GA4… and see this mess:

1. Half of your purchases have no source
2. facebook / cpc? Nowhere. But (direct) / (none) is having a party

What’s going on?

It’s the infamous in-app browser from Meta. Facebook and Instagram don’t open links in Chrome or Safari — they trap users inside their own little browser. And that’s where the attribution train crashes.

Here’s how it breaks:

1. User clicks the ad → site opens inside Meta’s in-app browser.
2. Referrer is stripped (because it’s an app), fbclid or UTM parameters get lost in redirects or dynamic loads.
3. The user comes back later via Safari or Chrome — either typing the URL manually or from a saved tab. GA4 thinks it’s a brand-new (direct) session.

The result? Meta drives sales. GA4 sees… nothing.

Here’s how I fix this in my own projects:

1. I capture fbclid from landing page URLs and store it in BigQuery. Then I link it with Meta Ads API exports. This is what we call the Matching Loop: click → session → event → export → match.
2. I run GA4 through server-side GTM and pipe everything into BigQuery. That helps bypass ad blockers and keep the context.
3. I stitch sessions manually when needed — using IPs, user-agent, fingerprints. If there’s a login, I connect client_id to user_id and deduplicate the mess.

Bottom line:

Not every “direct” is direct. Sometimes it’s just broken paid social that never got proper credit. If you’re not tracking fbclid, syncing with Meta’s API, and building your own attribution — you’re flying blind.

Want to fix that? Drop bigquery in the comments or DM me — I’ll send you a free lesson from my BigQuery Attribution course.

This post was originally shared by on Linkedin.