Difference in API and KeywordTool

33 views
Skip to first unread message

Dave

unread,
Nov 19, 2009, 2:37:26 PM11/19/09
to AdWords API Forum
Hi

Am using v13 instead of v2009 because I need the estimated CPC values.
I gave :

keyword = {
'text': 'mesothelioma',
'maxCpc': SOAPpy.Types.untypedType('30000000'), # $30
'type': SOAPpy.Types.untypedType('Exact')
}

Output I got was

$ python estimate_keyword.py
Estimates for keyword with text "mesothelioma":
Lower average position is "7.0".
Upper average position is "10.0".
Lower clicks per day is "17.23188".
Upper clicks per day is "21.584587".
Lower cpc is "14543535".
Upper cpc is "21815302".

For a $30 max bid, I get position 7.0 - 10.0 with lowerCPC as $14.54,
upperCPC as $21.82 and hence avg CPC as $18.18.

But when I checked the KeywordTool (https://adwords.google.com/select/
KeywordToolExternal) for the same input I got
position 4 - 6, Estimated avgCPC = $15.70

How come the difference ?

AdWords API Advisor

unread,
Nov 19, 2009, 5:52:25 PM11/19/09
to AdWords API Forum
Hi,

The likely cause is a mismatch in the language and location targeting
between the two methods. The TrafficEstimatorService makes certain
assumptions about language and location, which are explained in this
blog post:

http://adwordsapi.blogspot.com/2008/07/traffic-estimator-service-explained.html

Best,
- Eric Koleda, AdWords API Team

emergejuice

unread,
Nov 20, 2009, 12:20:44 AM11/20/09
to AdWords API Forum
Yes, I am aware of the fact that the API uses the settings English and
All Countries and Google Search network only.

I set it to English and All Countries in https://adwords.google.com/select/KeywordToolExternal
and I got position 4-6, avgCPC as $15.42 which is still far different
from the API results (7-10 position, lowerCPC as $14.54, upperCPC as
$21.82 and hence avg CPC as $18.18).

On Nov 20, 3:52 am, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> Hi,
>
> The likely cause is a mismatch in the language and location targeting
> between the two methods.  The TrafficEstimatorService makes certain
> assumptions about language and location, which are explained in this
> blog post:
>
>  http://adwordsapi.blogspot.com/2008/07/traffic-estimator-service-expl...

emergejuice

unread,
Nov 20, 2009, 1:05:35 AM11/20/09
to AdWords API Forum
Keyword : "car insurance"
MaxCPC : $10
Type : Exact

Via API :
Estimates for keyword with text "car insurance":
Lower average position is "4.0".
Upper average position is "6.0".
Lower clicks per day is "415.84586".
Upper clicks per day is "623.76886".
Lower cpc is "4390587" = $4.39
Upper cpc is "6585882" = $6.58
Avg CPC = $5.48

Via Web Interface (English, All Countries) :
Position : 1 - 3
Estimated Avg CPC : $8.23

I have a $1000 monthly budget for API usage. But theres no use when
there is such a huge difference in data.

AdWords API Advisor

unread,
Nov 20, 2009, 9:38:17 AM11/20/09
to AdWords API Forum
Hi,

I think the problem here lies in the Keyword Tool's web interface.
You'll notice that changing the match type drop down from Broad to
Phrase or Exact does not change the estimated position or average
CPC. It is unlikely that the match type has no effect on these
parameters, and in the API changing the match type does change the
returned position and CPC values. My guess is that the web tool is
always using the Broad match type for getting estimates, and that the
numbers returned by the API are accurate.

Best,
- Eric
Reply all
Reply to author
Forward
0 new messages