AdWords API Re: TrafficEstimatorService

2010-01-29 Thread AdWords API Advisor
Hi Kamil, The TrafficEstimatorService is more closely related to the Traffic Estimator Sandbox web interface: https://adwords.google.com/select/TrafficEstimatorSandbox Best, - Eric Koleda, AdWords API Team On Jan 29, 6:53 am, Kamil Kaczmarczyk <0jc...@gmail.com> wrote: > Hello > > I have rece

AdWords API Re: TrafficEstimatorService vs Keyword Tool

2010-01-22 Thread AdWords API Advisor
Hi Shane, The v200909 TargetingIdeaService encapsulates the functionalty of the v13 KeywordToolService and SiteSuggestionService. However, this service doesn't provide estimated data, including CPC, position, etc. A separate service will exist for that information, similar to the v13 TrafficEstim

AdWords API Re: TrafficEstimatorService vs Keyword Tool

2010-01-22 Thread Shane
Hi Eric, Thanks for reply. Follow up question...is there a service in either the v13 or v2009 APIs that can return similar Position and CPC results to what is found using the Keyword Tool? Shane On Jan 22, 8:18 am, AdWords API Advisor wrote: > Hi Shane, > > I think the primary reason for this

AdWords API Re: TrafficEstimatorService vs Keyword Tool

2010-01-22 Thread AdWords API Advisor
Hi Shane, I think the primary reason for this discrepancy is that you are comparing data from two different types of sources. If you are using the TrafficEstimatorService then you should use the Traffic Estimator web interface: https://adwords.google.com/select/TrafficEstimatorSandbox In my t

AdWords API Re: TrafficEstimatorService estimateCampaignList: Must specify a client in order to do traffic estimates.

2009-12-11 Thread AdWords API Advisor
Hi, While you did specify a clientCustomerId header, the ID you used was that of your MCC account. The TrafficEstimatorService requires that you specify an AdWords account as the client account in order to generate estimates. Best, - Eric On Dec 10, 10:24 am, "marc...@productengine.com" wrote:

AdWords API Re: TrafficEstimatorService estimateCampaignList: Must specify a client in order to do traffic estimates.

2009-12-10 Thread marc...@productengine.com
Thanks for quick answer. I'm still having trouble with that thing. Here is my soap request log (with my private data replaced by capitalized placeholders): http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http:// www.w3.org/2001/XMLSchema-instanc

AdWords API Re: TrafficEstimatorService estimateCampaignList: Must specify a client in order to do traffic estimates.

2009-12-09 Thread AdWords API Advisor
Hi, Please check the SOAP XML logs and ensure that the clientEmail or clientCustomerId header is being sent correctly. Thanks, - Eric Koleda, AdWords API Team On Dec 9, 10:18 am, "marc...@productengine.com" wrote: > Unable to request campaign estimates. API returns error: > > "Must specify a cl

AdWords API Re: TrafficEstimatorService

2009-03-09 Thread AdWords API Advisor
Hello, I am not exactly sure what your question is. If you're asking what the valid values are for the maxCpc parameter of the KeywordRequest object (http://code.google.com/apis/adwords/docs/ developer/KeywordRequest.html#maxCpc) then I believe it's the same as the valid maxCpc bids that you c

AdWords API Re: TrafficEstimatorService - "Must specify a client in order to do traffic estimates."

2009-03-05 Thread MyMedia
Thanks Jeff, that worked perfectly. As stated in the sandbox page, I simply had to change 'ad...@mymediainteractive.fr' for 'client_1+ad...@mymediainteractive.fr' and it did the job. Thanks again for your quick answer. Laurent On 5 mar, 17:37, AdWords API Advisor wrote: > Hello Laurent, > >  

AdWords API Re: TrafficEstimatorService - "Must specify a client in order to do traffic estimates."

2009-03-05 Thread AdWords API Advisor
Hello Laurent, The error in question is being triggered because the effective user under which your call is being made is considered an MCC user, and not a client account. In the Sandbox environment, a client account's address would look like client_x+u...@domain.com (and would be specified as t