---------------------------------------------------------------------------
NOTE: This issue tracking system is for Google Analytics developer products
only.
If you are not a developer/programmer visit:
http://www.google.com/analytics/support.html
---------------------------------------------------------------------------
Issue summary:
Hello,
I have been having recurring issues with spikes in self referrals from the main
domain across the sub domain and visa versa on multiple sites. I have
Universal running on my sites with subdomains and I have added the domain and
subdomain to the referral exclusion list and it has not helped the situation.
In some cases after adding to "Self Referral Exclusion List" I actually have
increases in self referrals. What can I do to fix this issue? The issue on
one of my sites started after adding a Facebook Like button directly from
Facebook (https://developers.facebook.com/docs/plugins/like-button) and that
coincided with the creation of these self referrals. I see many other sites
with the same set up as mine and even more widgets and 3rd party scripts.
Analytics support said that the self referrals and addition of facebook like
button do not correlate which makes no sense to me since they started the same
day. This has also caused all my ecommerce data to be funneled through this
referral since the booking engine is on the subdomain and my numbers are very
off now. I have asked analytics support for help on this many times over the
last few months and I can not get anywhere. Can anyone help me with these
issues. I have attached a screenshot of the spike in self referrals.
I have also had an issue on one site with an accuweather widget that had
tracking that somehow caused every visitor that had ever been to a website with
accuweather to be considered a returning visitor to my site. I was told by
Google support directly that the issue was with the widget. Has anyone else had
an issue with widgets and Analytics?
Original issue reported on code.google.com by ch...@rtservices.net on 19 Jan 2015 at 9:42
Original issue reported on code.google.com by
ch...@rtservices.neton 19 Jan 2015 at 9:42Attachments: