3 ms·
In a nutshell, we fire a server-side event when a user is created. What happens is that we're using oauth to authenticate, which then screws up the referring da
by lukethomas 13y ago
In a nutshell, we fire a server-side event when a user is created. What happens is that we're using oauth to authenticate, which then screws up the referring data. It attributes all signups to LinkedIn/Facebook, which is wrong. On classic analytics, everything worked fine. Universal Analytics tracks differently, so it's been a bit of a headache.
- gk1 13y agoWithout having a full view of what's happening, my hunch would be to look into these things: 1. Channel grouping (modify how referrers are defined) 2. Attribution model (eg, change to first interaction) 3. Referrer override (specify custom URL to be credited with referral) 4. Custom page path (on page that fires event, pass custom URL path to GA instead of actual URL) 5. Referral exclusion (ignore temporary stray into oAuth domain and continue user's same session) Hope that helps. If you could use a hand in getting this fixed quickly then get in touch (contact info in profile). Same goes for anyone else with tricky Analytics situations!