Referral passing is indeed the task of the client software. I'm not aware of a good way for the server to prevent it from happening. What you're seeing (as am I) is most likely the result of more people than before using personal firewall software that intercepts referrers between sites.
Today, there is a multitude of customized browsers.
We experience 10-15% of our click throughs, with "no" referrer info. And this percentage has been consistent for the last several years.
What about the referer showing the same thing as the link url?
Example:
RefererURL: [example.com...]
Initial Entry Page: [example.com...]
Do other people experience this issue? Guess I am looking for answers as to why this might happen.
Thanks.
Todd
[google.com...]
This is the HTML query that the user submits to Google. We all agree here that in about 10% of the cases, this string is blank. It seems to me that the issue here is with Google, not with the users' browsers.
Are there any Google people around here? If yes, maybe they can shed some light on this.
Just stopped by for a bit, ahbal. Sorry to say that this thread is beyond my realm, as I am not highly technical.
It really seems, though, that other list members have ably stepped in with the a lot of excellent info, as usual.
AWA
[edited by: AdWordsAdvisor at 7:29 pm (utc) on Dec. 23, 2003]
In your account you can have the destination url setup something like
ht*p://www.yoursite.com/somepage.html?source=adw1
ht*p://www.yoursite.com/somepage.html?source=adw2
sometimes I want a bunch of ads pointed at the same page but, obviously, still need to know how they convert individually. Then when there is no referer I can still see the click and which ad it was from.
blank referers are just something you need to work around. As redzone said, I get about 10 - 15 % that don't show and it has absolutely nothing to do with google. It doesn't matter anyway, referer data can be faked just like most other things.
Also it's not uncommon for a users proxy server to remove the referer header, I have my proxy configured just so. There is absolutely nothing on the webserver end you can do about it.
It certainly isn't googles fault that you aren't getting the referer header.
> It certainly isn't googles fault that you aren't getting the referer header.
While it's true that some browsers block referer info, please note that an AdWords "link" links the user to the Google server, not directly to your web server. A typical AdWords link looks like this:
[google.com...]
where "ppp" is a pointer to the user's search query. When Google re-directs the user's query to yourSite.com, it adds the info relevant to the original query, including the search phrase.
Therefore, it is theoratically possible that some glitch in Google's software contributes to cases of blank referer.
I am looking forward to hear what Google's technical people say about this issue.
AdWords "link" links the user to the Google server
True. But still, it's the browser's responsibility to transmit the proper referral url.
In a case where there is redirection, like Adwords, there are two ways for the browser to handle it. It could send the original URL (the one that produces the SERP). This is what most do.
Or it could transmit the URL of the redirection script. I think I saw that once or twice from a Mac browser. In this case, you wouldn't see the keywords.
It seems to me that the sequence of events is like this:
1. The user's browser submits a search query to Google.com, with some key phrase.
2. Google.com responds with a web page that contains an AdWords ad. Embedded in the ad is a link with a URL that includes a pointer to a database record that stores info on the original query (#1 above), including the search phrase.
3. The user clicks this link, thereby submitting a new query to Google.com. The query includes a pointer to the original search query (#1).
4. Google now submits a query to yourSite.com, but somehow causes it to believe that the query came form the user's brower. The "referer" submitted to yourSite.com is the original search query (#1), retrieved from the database.
If this is a fair description of the events, aren't clickthroughs with blank referers caused by a bug in Google's software?
Ahbal
4. Google now submits a query to yourSite.com, but somehow causes it to believe that the query came form the user's brower. The "referer" submitted to yourSite.com is the original search query (#1), retrieved from the database.
Google doesn't submit a query to the site. When you click the ad, the browser submits a query to Google, Google tallies that click, then tells the browser to go to yoursite.com.
The referer doesn't come from the database, but from the url that the browser visited.
> The referer doesn't come from the database, but from the url that the browser visited.
It seems that you are right. Alas, if Google had used my "design", there will be no blank referers...
By the way, do you know if there is a way to retrieve the search phrase from the referer of "syndicated" AdWords? These look like this:
[pagead2.googlesyndication.com...]
I posted this question on another thread, but got no responses.
I looked at some googlesyndication referers. The url= variable does show the site the ad was on, but no info on the search phrase.
ahbal-
The reason you may not see a search phrase on a googlesyndication referer is because the page is not a search page and no search phrase even exists.
Your Google Ad can appear on a "normal" topic web page on a particular site therefore no "search phrase" is even used to find this page. When someone clicks on your Ad it will tell you the URL of the page the ad appeared on. A search phrase may have nothing to do with a googlesyndicated referer.
Sorry...kind of wordy!
Todd