Google Adwords API: Using getNewKeywordEstimate() vs. getCampaignEstimate()
It seems the Google Adwords API doesn't give you consistent results for cost and traffic data. The numbers can change radically during the same 24hr period.
How are we supposed to get reliable stats from this?
Here's the response from Adwords staff:
Does this mean that the only way to get consistent numbers is to first add a campaign, add an adgroup with keywords and then run that function?
Is this what the web interface does?
Isn't there an easier way to just get reliable numbers before you actually create the campaign? Seems like a lot of overhead just to research keywords and get cost/traffic estimates.
Look at these crazy numbers:
How are we supposed to get reliable stats from this?
Here's the response from Adwords staff:
Using getNewKeywordEstimate() function is not the best choice if you want the most accurate estimates. When you use estimateKeywordList() method, which is what being called by getNewKeywordEstimate(), the keywords are estimated as if they were partof a single new ad group in a single new campaign with global targeting.
See,http://www.google.com/apis/adwords/developer/TrafficEstimatorService.html#es.
This obviously has affect on the resulting estimates. For more accurateestimates, it is recommended to use estimateCampaignList() function, whereyou can actually set the targeting.
See,http://www.google.com/apis/adwords/developer/TrafficEstimatorService.html#es.
Does this mean that the only way to get consistent numbers is to first add a campaign, add an adgroup with keywords and then run that function?
Is this what the web interface does?
Isn't there an easier way to just get reliable numbers before you actually create the campaign? Seems like a lot of overhead just to research keywords and get cost/traffic estimates.
Look at these crazy numbers:
| keyword | datetime | lowerAveragePosition | upperAveragePosition | lowerCostPerClick | upperCostPerClick | lowerClicksPerDay | upperClicksPerDay |
| dog trainer | 5/1/2008 0:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 1:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 2:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 3:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 4:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 5:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 6:42 | 1 | 3 | 5.185826 | 6.482283 | 5.395382 | 6.83415 |
| dog trainer | 5/1/2008 7:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 8:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 9:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 10:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 11:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 12:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 13:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
| dog trainer | 5/1/2008 14:43 | 1 | 3 | 3.110532 | 3.888165 | 84.62508 | 105.8072 |
posted by GoInfo Systems at
6:58 PM
0 Comments:
Post a Comment
<< Home