Member Avatar for Dani
Dani 5,664 The Queen of DaniWeb

I am trying to get the hang of Google Analytics 4.

One of the conversions that we track is sign ups.

I'm seeing a lot of conversions attributed to the Organic Social group. However, a lot of these conversions are people who found the site some other way (e.g. organic search), and then subsequently signed up through a social OAuth flow (e.g. Log in with Facebook).

We are using the cross-channel attribution model that looks at first click, last click, etc. So I get, I suppose, that I'm wanting to look more at first click organic social conversions as opposed to last click. However, this still doesn't give me an accurate picture when someone first stumbled across my site from organic search, then subsequently from a facebook post, and then chose to sign up.

How can I exclude the portion of the conversion path that goes -> redirect to social network OAuth -> redirect back to DaniWeb from the conversion flowchart?

Hopefully this makes sense.

  • 1 Contributor
  • 0 Replies
  • 100 Views

Dani AI

Generated

For : the core issue is that the OAuth round trip can return users with the OAuth provider as the referrer, which often creates a new session in GA4 and overwrites the earlier acquisition channel. Three practical ways to prevent that redirect from skewing your conversion attribution are below.

  1. Configure unwanted referrals in GA4. In the Web data stream tagging settings add the OAuth provider domains to the “list of unwanted referrals” so the return from that domain does not start a new session. Test after changes using DebugView and Realtime to confirm the original source is preserved. Be careful with subdomains and only add domains you know should be excluded.

  2. Avoid full-page navigation for the auth flow when possible. Using a popup or native SDK/auth widget keeps the original page as the active referrer and prevents a provider-originated session. Watch for popup blockers, mobile UX limits, and provider requirements (state/csrf handling must still be correct).

  3. Persist first-touch server- or client-side and use it for attribution. Store the original source/campaign in a cookie or on the user record at first visit. When a signup happens, send the conversion with that stored source (or map it server-side) so attribution reflects first touch rather than the post-login redirect.

Start by adding unwanted-referral entries and running controlled tests. If you need guaranteed first-touch attribution, persist the first-touch server-side and use it when recording conversions.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.