Is there a way to see all of Google traffic as one row, regardless of the country domain | Community
Skip to main content
carlos_am298394
Level 2
March 8, 2016
Solved

Is there a way to see all of Google traffic as one row, regardless of the country domain

  • March 8, 2016
  • 20 replies
  • 9257 views

I have a website with lots of international website and when I look at referring sites, I have to swift through hundreds of Google domains (google.com, google.ca,  google.co.uk) instead of just seeing it as in Google Analytics, as one referrer? 

Thank you,

C.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by andrew_r-GrfLbX

It's pretty annoying I agree there, I've never been able to work out a way of rolling it all up in to one source. I disagree with hacking s-code or other types of mods to try and get round it given the amount that companies pay to use this product. I'd raise it on http://ideas.omniture.com/ and see if it gets any traction on there.

20 replies

carlos_am298394
Level 2
March 14, 2016

You are right, I like this solution but it is a big workaround for something that should be default from Site Catalyst. 

Thank you very much, @warrenSander

carlos_am298394
Level 2
March 14, 2016

You are right, I like this solution but it is a big workaround for something that should be default from Site Catalyst. 

Thank you very much, @warrenSander

Gigazelle
Adobe Employee
Adobe Employee
March 14, 2016

I have this exact same issue on sites that I manage internally. I have a bit of give/take going on, but to me it's worth it.

In DTM, I have created a page load rule where if the referrer is from any google search engine domain, I override the referrer value to https://google.com.

  • The plus side is that I have all google values in one line item, which makes things so much easier for all my traffic sources reports, marketing channels, etc. I don't have to use any custom variables or segments either.
  • The downside is that I effectively lose the ability to see which google domains people are coming from. Keyword data supposedly would be overwritten too, but since google strips keyword data already, that's not that big of an issue.

Since I personally care a lot more which overall search engines people come from (more than I care about which google domains they're using), I have opted to consolidate them using the referrer override. Google is google to me, no matter which regional search engine visitors opt to use.

Gigazelle
Adobe Employee
Adobe Employee
March 14, 2016

I have this exact same issue on sites that I manage internally. I have a bit of give/take going on, but to me it's worth it.

In DTM, I have created a page load rule where if the referrer is from any google search engine domain, I override the referrer value to https://google.com.

  • The plus side is that I have all google values in one line item, which makes things so much easier for all my traffic sources reports, marketing channels, etc. I don't have to use any custom variables or segments either.
  • The downside is that I effectively lose the ability to see which google domains people are coming from. Keyword data supposedly would be overwritten too, but since google strips keyword data already, that's not that big of an issue.

Since I personally care a lot more which overall search engines people come from (more than I care about which google domains they're using), I have opted to consolidate them using the referrer override. Google is google to me, no matter which regional search engine visitors opt to use.

warrensander
Level 6
March 14, 2016

Then you can always do my processing rule the opposite way.

continue to overwrite the referrer value but save the original value in a prop or evar called 'original referrer value' and then you have that (evar is probably better so you can breakdown the google.com by that evar to find the google country sites) (or any other rollups you use.

warrensander
Level 6
March 14, 2016

Then you can always do my processing rule the opposite way.

continue to overwrite the referrer value but save the original value in a prop or evar called 'original referrer value' and then you have that (evar is probably better so you can breakdown the google.com by that evar to find the google country sites) (or any other rollups you use.

carlos_am298394
Level 2
March 16, 2016

@Gigazelle That's exactly how I feel, Google is just google. If I really care to segment it regionally I can overlay Location. I'm always afraid of overriding data, but in this case, it may be something I won't miss... and at the end, I will have better intel.

carlos_am298394
Level 2
March 16, 2016

@Gigazelle That's exactly how I feel, Google is just google. If I really care to segment it regionally I can overlay Location. I'm always afraid of overriding data, but in this case, it may be something I won't miss... and at the end, I will have better intel.

September 6, 2017

Hi Gigazelle,

I was wondering how are you setting up through DTM as I which condition or element you are selecting and applying the criteria.

Thanks,

S

Gigazelle
Adobe Employee
Adobe Employee
September 7, 2017

Certainly!

Data element: referrer, JS object. Defined as window.document.referrer.

Page load rule condition: If the data element referrer contains google (regex enabled)

Custom page action (in editor):

s.referrer="https://google.com"