Traffic Estimator Glitch

[sem4u]

If I am in an Ad Group and try to use the traffic estimator, it won't let me go onto pages other than the first one, or won't let me change the number of rows per page.

I get this error: "You attempted to reach a non-existent page. Please check the URL and try again."

I contacted support a few days ago and have not had a reply yet.

[dave741]

I can confirm this bug too.

[sem4u]

Still not working for me...

[AdWordsAdvisor]

I'm not seeing this as an issue at this end, sem4u, as I scan advertiser emails and so forth - which suggests that it may be something to do with the interaction of your machine, your browser, and the AdWords interface.

Have you tried another browser, or tried updating your current browser if it's a few revisions old?

Also, another common fix that seem to help in many cases is simply rebooting your machine, and logging in from a fresh page (adwords.google.com) rather than a bookmarked page.

Clearing your cache and cookies may help as well.

And of course, writing AdWords support with this sort of issue is a pretty good idea, especially in you've been having the same problem for a number of days.

I hope one of these ideas takes care of it.

AWA

[sem4u]

It works fine in Firefox and on IE I only needed to clear out the temporary internet files. All working OK now - thank's for answering AWA :)

[irish_john]

This kind of problem seems to be an aspect alot, where google will do a major update, and some things will stop working.

I think its invariably because you will have some javascript file cached on your local machine. Google then does an update, but reuses the same javasciript file names. As a result your cached javascript file no longer is the proper working one that you need. As a result you see this kind of behaviour, and are told to clean your cache.

If google, applied some kind of versioning system to their javascripts, ( or at least change the names) they could avoid this kind ofproblem.

1 way could be to maintain a directory of version number, then script name.
e.g.
/v22/somescript.js

so when you do an update the new script would be referenced by

/v23/somescript.js

[gamb]

the traffic estimator has had a glitch for a while now, it simply doesn't work ;)....

[grigoroo]

I agree that the estimator is inaccurate at best. Yesterday I put in a few new ad groups at the insistance of my client. I doubted that they would generate any significant traffic so when the estimator suggested a bid of $.05, predicting 0 clicks and number one positioning I went along with it. Last night I looked at the traffic and saw that although I'd seen a couple impressions, it was running in 80th position! I raised the bid to $.40 and now I've gotten a few more impressions and they are running on the second page.

[PyrettaBlaze]

The Traffic Estimator has not been working for me for quite a while now. I found a way around it, rather than sorting right away, I clicked the first keyword, then sorted...but today when I tried it, it sent me to a nonexistant page. It gets kind of frustrating after a while...