Forum Moderators: buckworks & skibum

Message Too Old, No Replies

Google Analytics - Tracking Referral Data for Yahoo

         

PPC_Chris

7:00 pm on Apr 24, 2008 (gmt 0)

10+ Year Member



I have had Google Analytics tracking set up for a while now. Recently, I have updated the landing urls at Yahoo and other non-Google outlets to include "utm_source=Yahoo", "utm_medium=CPC", etc. Everything seems to be tracking properly now in Google Analytics.

However, I used to be able to see stats for the actual referral site. In other words, I could see all the traffic that Yahoo's partners were sending by referral domain. Now that I have entered the proper tracking code, all traffic from Yahoo (whether it be directly from Yahoo or from one of its partner networks) is grouped together as "Yahoo" in Google Analytics reporting. This is obviously a huge problem because to optimize my Yahoo account, I need to be able to see where poor performing traffic is coming from and exclude these domains.

My question is this... is this how Google Analytics is supposed to work? If it is, is there anyway around this other than deleting the GA specific tracking code from my destination urls?

GAnalyticsAdvisor

12:10 am on Apr 25, 2008 (gmt 0)

10+ Year Member




I have had Google Analytics tracking set up for a while now. Recently, I have updated the landing urls at Yahoo and other non-Google outlets to include "utm_source=Yahoo", "utm_medium=CPC", etc. Everything seems to be tracking properly now in Google Analytics.

However, I used to be able to see stats for the actual referral site. In other words, I could see all the traffic that Yahoo's partners were sending by referral domain. Now that I have entered the proper tracking code, all traffic from Yahoo (whether it be directly from Yahoo or from one of its partner networks) is grouped together as "Yahoo" in Google Analytics reporting. This is obviously a huge problem because to optimize my Yahoo account, I need to be able to see where poor performing traffic is coming from and exclude these domains.

My question is this... is this how Google Analytics is supposed to work? If it is, is there anyway around this other than deleting the GA specific tracking code from my destination urls?

Hi PPC_Chris,

I believe I know why this happens, but would like to confirm with other members of our team before confirming. I will get back to this thread soon!

GAA

PPC_Chris

6:52 pm on Apr 25, 2008 (gmt 0)

10+ Year Member



Great. Thanks!

GAnalyticsAdvisor

6:43 pm on May 5, 2008 (gmt 0)

10+ Year Member



Hi PPC_Chris,

Apologies for the delay. If you are using the new ga.js tracking code, this shouldn't be an issue. If you have a moment, please PM me a sample tracking URL that you're using, so I can use that to test with.

Thanks,

GAA

netmeg

7:06 pm on May 5, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



So that only works with the new code? We're not using that yet, because we were losing transactions with it. On the other hand, we're losing transactions with the old code too, so I guess there's no reason not to switch over.