pending API review

2011-09-08 Thread KevinC
Hi -

I've been in "pending review" status for about a month.  Can someone
unjam my application?

Thank you,
Kevin

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Error trying to set the platform target in CampaignEstimateRequest

2011-09-08 Thread jschay


I am trying to get mobile results back from the TrafficEstimatorService, but 
when I set the PlatformTarget in the CampaignEstimateRequest it comes back 
with an error: RequestError.UNSUPPORTED_TYPE_IS_USED

>From what I can tell in the documentation the platform target is listed as a 
target for CampaignEstimateRequest.

http://code.google.com/apis/adwords/docs/reference/latest/TrafficEstimatorService.CampaignEstimateRequest.html

The code that I am using:

CampaignEstimateRequest campaignEstimateRequest = new 
CampaignEstimateRequest();

LanguageTarget languageTarget = new LanguageTarget();

languageTarget.languageCode = "en";

CountryTarget countryTarget = new CountryTarget();

countryTarget.countryCode = "US";

PlatformTarget platformTarget = new PlatformTarget();

platformTarget.platformType = PlatformType.HIGH_END_MOBILE;

campaignEstimateRequest.targets = new Target[] { languageTarget, 
countryTarget, platformTarget };

Am I implementing the platform request incorrectly or is there another 
issue?

Also as a quick test I tried to set the platform type as DESKTOP and that 
failed as well.

Here is the full error:

[RequestError.UNSUPPORTED_TYPE_IS_USED @ 
selector.campaignEstimateRequests[0].targets.targets[2]; 
trigger:'com.google.ads.api.services.campaignmgmt.common.target.PlatformTarget']ApiExceptionselector.campaignEstimateRequests[0].targets.targets[2]com.google.ads.api.services.campaignmgmt.common.target.PlatformTargetRequestError.UNSUPPORTED_TYPE_IS_USEDRequestErrorINVALID_INPUT


-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: python api usage

2011-09-08 Thread Kevin Winter
Hi Saverio,
  The Python Client library is supposed to include the error text of the 
fault in the logging, so there may be a bug here.  This particular codepath 
happens when there is a SOAP fault.  Could you please turn on SOAP XML 
logging (code below) and try again?  The soap log should indicate what the 
problem is and may help me reproduce it so I can fix the error message.

client = AdWordsClient( {'userAgent': 'TEST', 
 'developerToken': 'MY_DEV_TOKEN',
 'email': "google...@gmail.com",
 'password': 'MYPASSWORD' 
},
{'debug': 'y',
 'xml_log': 'y'
})

- Kevin Winter
AdWords API Team

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Strange behavior (maybe?) in v201101 TrafficEstimatorService

2011-09-08 Thread Eric Koleda
Hi All,

First let me say that this doesn't appear to be an issue with the API 
itself, as the Traffic Estimator UI is behaving the same way.  That said, 
I'll try my best to explain the behavior, but you might want to start a 
conversation on the general AdWords forum if you want more information about 
how the product works.

Ian,

Could it just be coincidence that the estimates are the same for those 
keywords whether or not their in the same ad group estimate request?  I 
think in some cases you'll find that the estimates won't change, but for 
other sets of keywords there will be an effect.  If you have a case where 
you think the behavior is wrong please provide the sanitized SOAP XML 
request and response.

David,

The reason you are seeing different estimates depending on the surrounding 
keywords is because some of the keywords are "stealing" impressions and 
clicks from other keywords.  There may be many keywords in an ad group that 
match a given search query, but the most relevant keyword will be awarded 
the impression.  In your sample list of keywords, if you remove "movers", a 
broad keyword that would match most moving related queries, you'll see that 
some clicks are now attributed to "boise moving company" again.

Best,
- Eric

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Creative - Ad Performance v13 empty row

2011-09-08 Thread Eric Koleda
Hi Tomasz,

I haven't heard any other reports of this happening yet, and I don't know 
what the cause was int his case.  Are you seeing this behavior consistently?

Best,
- Eric Koleda, AdWords API Team

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Re: Which Service To Use to Estimate Keyword Search Volume

2011-09-08 Thread Eric Koleda
Hi,

Yes, using STATS requests you can batch together your keywords into a single 
request.  More information is available here:

http://code.google.com/apis/adwords/docs/bestpractices.html#batch_stats

Best,
- Eric Koleda, AdWords API Team

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Strange behavior (maybe?) in v201101 TrafficEstimatorService

2011-09-08 Thread Ian Knox
Eric,

I don't think it's a coincidence-- my results in testing have been 
consistent: estimating single keywords in a series of different 
adgroups yields the same result as estimating them in one adgroup _unless_ 
you place the individual adgroups in separate campaigns.

I've attached SOAP XML logs of two transactions, both contain two keywords. 
 One has one keyword per adgroup, and the other has multiple keywords per 
adgroup.  
The results are the same-- they both exhibit the "stealing" behavior you 
describe whether or not they are in an adgroup together.



-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


soap_xml.log
Description: Binary data


Re: number of concurrent API connections for pulling reports?

2011-09-08 Thread bgraves
Thanks but that link isn't specific to how many simultaneous calls to
the report download are allowed.  Do you have any information on this?

On Sep 7, 4:40 am, "Anash P. Oommen" 
wrote:
> Hi,
>
> AdWords API treats report downloads the same way as any other API calls, and
> will respond with a RateExceededError if you make too many calls in a short
> period. 
> Seehttp://adwordsapi.blogspot.com/2010/06/better-know-error-rateexceeded...for
> more details on rate exceeded errors. The only difference is that report
> downloads don't raise a soap exception, instead the contents of the
> downloaded report looks like !!!1|||REPORT_ID|||Error details???
>
> Hope this helps. Let me know if you have more questions.
>
> Cheers,
> Anash P. Oommen,
> AdWords API Advisor.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Strange behavior (maybe?) in v201101 TrafficEstimatorService

2011-09-08 Thread Eric Koleda
Hi Ian,

I did some tests and I am seeing the behavior you are describing.  However, 
this behavior is the same in the traffic estimator UI, so I don't think it 
is a bug per se.  It may be that the "stealing" behavior I described takes 
place across ad groups.  For more information about this behavior you should 
reach out to general AdWords forum.

Best,
- Eric

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en


Re: Strange behavior (maybe?) in v201101 TrafficEstimatorService

2011-09-08 Thread Ian Knox
Thanks for confirming it Eric-- I'll follow up with the general AdWords 
forum and see where that takes me.


-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en