Discrepancy between keyword estimate api and google web traffic estimator?

[bc109]

When I use the sample Perl script on the Google Adwords Beta API site
to return the traffic estimate for 'flowers' with a MaxCpc of 50000
micros ($0.05) I receive:

clicks = 621, position = 3.625, average cpc = $0.05

But when I use the traffic estimator provided by google at
https://adwords.google.com/select/WizardAddKeywords#a, I get, for
'flowers' with a MaxCpc of $.05:

clicks = 1100, position = 3.7, average cpc = $0.05

Can someone please explain this significant difference in the value of
clicks?

Thanks.

[inasisi]

If there has been one feature that Google never got it correct, it has
been the traffic estimator. For many of my keywords it would predict a
position of 6. When I start the advertising, I might actually end up
getting the 30 position or the 1st position. This from the very
beginning when I don't have any historical CTR. The number of clicks
and CPC estimates are also equally bad.

So the answer is I don't know what the difference is and what the hell
do I care, if both are grossly wrong anyway.

The most reliable figure I have found among these estimates, is the
number of impressions available only through the API. I have found it
to be reasonably correct as long as your actual position is within 4
namely in the first page of the search results in most of the search
engines. My experience has only been with Search Networks. Content
Network, I would guess fluctuates a lot more.

[i2pi...@gmail.com]

I have a similar problem to the original poster. When I query the web
site I get one set of numbers, yet the API returns another set. This is
a huge problem for me, as I don't know which set to trust. When you are
considering a huge spend, an error of $0.30 on a $5 CPC is important.

Any ideas as to what is going on here?