I am seeing quite a few conversions which have as source
accounts.google.com (almost 40%).
AFAIK, in the new Universal Analytics as soon as a user has a Referrer set a new session is started. So if a user is getting on my page, and creates an account using social auth (e.g. Google accounts) when being redirected back, will this create a new session?
I guess this would explain that there are many conversions coming from
accounts.google.com – is it safe to enter
accounts.google.com into the Referral Exclusion List? And more – what about Facebook logins, those would show up as
facebook.com, but I probably don’t want to exclude
facebook.com as referrer?
Any ideas how to deal with UA referrers and social logins?
Here is Solutions:
We have many solutions to this problem, But we recommend you to use the first solution because it is tested & true solution that will 100% work for you.
I can confirm that Google Analytics will start a new session when the user comes back from logging in with the referrer from another site. I don’t have as big a problem with it on my sites because not many of my users log in. From Google’s referral exclusion documentation:
How excluding referral traffic affects your data
By default, a referral automatically triggers a new session. When you exclude a referral source, traffic that arrives to your site from the excluded domain doesn’t trigger a new session. If you want traffic arriving from a specific site to trigger a new session, don’t include that domain in this table.
Because each referral triggers a new session, excluding referrals (or not excluding referrals) affects how sessions are calculated in your account. The same interaction can be counted as either one or two sessions, based on how you treat referrals. For example, a user on
your-site.example, and then returns to
my-site.example. If you do not exclude
your-site.exampleas a referring domain, two sessions are counted, one for each arrival at
my-site.example. If, however, you exclude referrals from
your-site.example, the second arrival to
my-site.exampledoes not trigger a new session, and only one session is counted.
accounts.google.com in the referral exclusion list would solve the problem for Google login, but as you say, you can’t do that for Facebook.
<html> <head> <meta http-equiv="refresh" content="0; url=/after-login.html"> </head> <body> </body> </html>
It strips the referrer entirely in Firefox and IE. In Chrome, Opera, and Safari, the referrer changes to the refresh URL (which would be from your site).
Note: Use and implement solution 1 because this method fully tested our system.
Thank you 🙂