AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

4.1K members online now
4.1K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
Guide Me

meta name="referrer" and Analytics

[ Edited ]
Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi everyone.


I have just discovered that the referrer information is not sent from HTTPS to HTTP, eg from to The easiest cure for this seems to be <meta name="referrer" content="origin">. But I don't want to leak any important information in the referrer, so a safer version would be <meta name="referrer" content="origin-when-cross-origin">.


This way, the links within the https://www subdomain will pass full referrer, whereas the links from https://www to http://blog pass only the domain.


And this is my question proper:


— Will Google Analytics still be able to see full, normal referrer for links between these subdomains, or will it be using the new, defaced referrer? In other words, will I still see "" as a referrer for internal links in Google Analytics, or will all links from the blog subdomain be stripped to "" starting at the moment when <meta name="referrer" content="origin-when-cross-origin"> is implemented?

1 Expert replyverified_user

Re: meta name="referrer" and Analytics

Top Contributor
# 2
Top Contributor
I'm not really sure I can answer your question with certainty, but GA is completely dependent on the browser for referrer information (which is why it cannot always be trusted). If your page has configured the browser to deliver only the domain, then only the domain will be available to GA.
Mike Sullivan, Google Analytics Top Contributor
Was my response helpful? If yes, please mark it as the ‘Best Answer.’ Learn how here.