from:"peter . rietzler"

Re: Policy violations - v201710 vs 201706

2018-09-06 Thread peter . rietzler

Hi Anash

Regarding point 2. 

I am trying hard to force some PolicyFindingErrors now even in non test 
accounts. Our tests forced PolicyViolationErrors beforehands by e.g. 
creating expanded text ads containing terms like "heroin" or "rifles" (done 
in a test account), but when I try to run the same tests against a non test 
account with the updated API version (v201806), these ads are just created 
without any further notice. 

I definitely need to trigger PolicyFindingErrors for a couple of violations 
in order to check for policyTopicIds and messages (such as "Online pharmacy 
certification required" or "Inappropriate Language") just to cross check 
how I can map previous error handling (based on PolicyViolationError) to 
the information  that is now returned by the new PolicyFindingError. 

We previously used the information provided by 
PolicyViolationError.externalPolicyName
PolicyViolationError.isExemptable
PolicyViolationError.key.violatingText
PolicyViolationError.key.policyName

Can you provide a mapping to PolicyFindingError for these fields ? It would 
be really helpful if you could provide advice on how to proceed here.

Just to give you a complete picture: I am also trying to send keywords with 
the same terms test as well as non test accounts still return a proper 
PolicyViolationError even for v201806. 

Thank you for help!
Peter

On Friday, 27 July 2018 19:17:10 UTC+2, Anash P. Oommen (AdWords API Team) 
wrote:
>
> Hi Greg,
>
> Since Josh is not available, I'll answer your questions instead.
>
> 1. Yes, ETA won't produce any PolicyViolationError. Let me know if you see 
> any behaviour otherwise, and we will investigate on priority.
> 2. PolicyFindingErrors (and policies in general) are a lot dependent on 
> the account in which the ad serves, the geographies for which the ad 
> serves, the network, whether we've seen a lot of these errors (and 
> violations) in the past, etc. The test accounts are meant for minimal 
> replication of policy errors; it doesn't support all combinations of 
> PolicyViolationErrors you'd see in production accounts. My suggestion is to 
> design your application such that you can test and verify for minimal 
> PolicyViolationErrors against test accounts, and be able to specify 
> additional policies as runtime-configurable.
>
> Cheers
> Anash P. Oommen,
> AdWords API Advisor.
>
> On Friday, July 27, 2018 at 12:24:14 PM UTC-4, GregT wrote:
>>
>> Hey, Josh.
>>
>> Thanks for looking into this and for the information. I'd just like to 
>> clarify some things.  
>>
>> 1 - Are you saying that creating expanded text ads will now *never* produce 
>> a PolicyViolationError, and we should only be looking for 
>> PolicyFindingErrors? It seems pretty clear that that's what you (& the 
>> documentation you pasted) are saying, but I just want to double check, as 
>> it seems like that means for expanded text ads, there's really not 
>> exemptable vs. non-exemptable anymore, and there's just a single type of 
>> "exemptable but your request will be denied" violation.
>>
>> 2 - As I mentioned in my original July 3 post, I tried to produce (in the 
>> sandbox with v201806) policy violations by using things that are direct 
>> violations of what's given in the advertising policies page you mentioned 
>> (like "work @home", "big big SALE", "FR33 ShiPPiNG", "buy hunting rifle", 
>> various brand names that produce trademark violations in production, etc.), 
>> and these are accepted by the sandbox without issue, although production 
>> v201802 produces policy violations. As I mentioned, the only thing I can 
>> get to produce a policy violation (the new PolicyFindingError) in the 
>> sandbox for v201806 expanded text ads is multiple exclamation points in a 
>> row. Is this expected (it seems like it wouldn't be, considering you 
>> pointed to the advertising policies page for examples of ad text that 
>> should trigger errors)? I guess, in reality, if the answer to #1 above is 
>> yes, then since I can produce that error with multiple exclamation points, 
>> this question is irrelevant, although it seems odd. 
>>
>> Thanks,
>> Greg
>>
>> On Thursday, July 26, 2018 at 4:35:39 PM UTC-5, Josh Radcliff (AdWords 
>> API Team) wrote:
>>>
>>> Hi Greg,
>>>
>>> I ran some tests and spoke with my colleagues today. Starting with 
>>> v201806, some ad types will return a *PolicyFindingError* *instead of* a 
>>> *PolicyViolationError* when there are policy issues. Here's the note we 
>>> added to the Policy Exemption Requests guide 
>>>  
>>> for 
>>> the v201806 release (yellow highlights mine):
>>>
>>> *Note:* Starting in v201806, some ad types (including ExpandedTextAd 
>>> )
>>>  
>>> will fail with a PolicyFindingError 
>>>

Re: Policy violations - v201710 vs 201706

2018-09-06 Thread peter . rietzler

Hi Josh, Hi Anash

Can I find an overview of all policyTopicIds ? 

Are all policy topics listed here and do the return values of the API 
correspond with this documentation ? 
https://support.google.com/adspolicy/topic/1626336?hl=en&ref_topic=2996750,1308156,

Thanks! 
Peter

On Tuesday, 3 July 2018 12:51:44 UTC+2, Peter Lanser wrote:
>
> Hi, we are currently migrating from Adwords API v201710 to v201806 and we 
> are observing an issue regarding policy violations / excemption requests.
>
> Part of our test suite is the creation of an (expanded) text ad triggering 
> a PolicyViolationError. Everything is fine with v201710 - we are expecting 
> this error (and creating an excemption request later).
>
> [INFO] 
> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
> SOAP response:
> 
> http://schemas.xmlsoap.org/soap/envelope/";>
> ...
> 
> 
> ...
> 
> https://adwords.google.com/api/adwords/cm/v201710";>
> ...
> http://www.w3.org/2001/XMLSchema-instance"; 
> xsi:type="PolicyViolationError">
> ...
> 
> PolicyViolationError.POLICY_ERROR
> PolicyViolationError
> 
> weapons
> Rifle
> 
> Google 
> AdWords
> 
> This ad or keyword 
> requires review before it can run.
> true
> ...
> 
> 
> 
> 
> 
> 
>
> However, the error is not triggered when using v201806. The expected error 
> is not triggered:
>
> [DEBUG] 
> com.google.api.ads.adwords.lib.client.AdWordsServiceClient.soapXmlLogger 
> SOAP response:
> 
> http://schemas.xmlsoap.org/soap/envelope/";>
> ...
> 
> https://adwords.google.com/api/adwords/cm/v201806";>
> 
> 
> AdGroupAdReturnValue
> 
> ...
> http://www.w3.org/2001/XMLSchema-instance"; xsi:type="ExpandedTextAd">
> ...
> 
> PAUSED
> 
> REVIEW_IN_PROGRESS
> 
> UNDER_REVIEW
> 
> 
> 
> 
> 
> 
>
> We are aware that there are some changes concerning policy violations as 
> mentioned in 
> https://developers.google.com/adwords/api/docs/reference/release-notes/v201806#policy
>  
> and 
> https://developers.google.com/adwords/api/docs/guides/exemption-requests.
> However, we wouldn't have expected that no error is triggered at all.
>
> Are we missing something? Why isn't the policy error triggered when using 
> v201806?
>
> Thanks for your help,
> Peter
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/92436b16-0d6c-4321-beb5-31945364ae4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Keyword Criterion IDs question

2018-01-30 Thread peter . rietzler

Is it guaranteed that the criteria id will be the same within the same 
account ? 

We need to get aggregated performance data for a keyword (identified by a 
criterion id only) even if it has been "moved" to another ad group. 

Let's consider this example

Campaign 1
  Group 1
*Criterion 1*   (e.g, keyword "a")  --> Deleted and re-created in Group 
2
  Group 2
Criterion 1(e.g. keyword "a")

If Criterion 1 caused 100 clicks while it was located in Group 1 and 50 
clicks afterwards in Group 2, can we query a report in a fashion like
SELECT CriteriaId, Clicks FROM ...
and do we get 150 clicks for Criterion 1


Thanks, 
Peter


On Friday, 2 September 2011 23:06:32 UTC+2, David Torres wrote:
>
> Hi,
>
> The combination of "text + match type" in most of the circumstances is 
> unique but it is not guaranteed, what is always guaranteed is the 
> uniqueness of the combination of (text + match type + ad group id)
>
> Best,
>
> -David Torres - AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/841539ab-f9bf-4ed1-aa6c-56a8285963b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Impression values lower than zero

2017-03-30 Thread peter . rietzler

It's not just the impressions, we also see negative values in 
ConversionValue and Conversions, as well as Cost

On Thursday, 30 March 2017 15:40:27 UTC+2, sebasti...@kjobo.com wrote:
>
> Hello everyone,
>
> today, i have some rows in my SHOPPING_PERFORMANCE_REPORT with impression 
> values of "-1" and "-2". So the values are not even numbers, they are 
> strings. How do i have to interpret these values? Do they have a special 
> meaning?
>
> Thanks in advance
>
> Sebastian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/df34a3a4-93d1-4168-ad7d-52924e7da531%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error during product partition creation

2015-12-09 Thread peter . rietzler


Sorry for bothering again - still no updates on this ?

Thanks! 
Peter

Am Mittwoch, 18. November 2015 16:11:08 UTC+1 schrieb Josh Radcliff 
(AdWords API Team):
>
> Hi Peter,
>
> No updates yet, but the engineers are looking into it. I'll get back to 
> you as soon as I hear anything.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, November 17, 2015 at 11:25:13 PM UTC-5, 
> peter.r...@smarter-ecommerce.com  wrote:
>>
>> Hi Josh
>>
>> Any updates on this ?
>>
>> Thanks!
>> Peter
>>
>> Am Mittwoch, 11. November 2015 20:55:04 UTC+1 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi Peter,
>>>
>>> Using that request ID, I found some information on our side that 
>>> indicates that there may have been an unexpected duplication of this 
>>> request. I'm following up with the service owners to see what happened 
>>> here, and will let you know as soon as I hear back from them.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, November 10, 2015 at 10:09:09 AM UTC-5, peter... wrote:

 Hi 

 No, I can't see any logs in our system despite the fact that the 
 request has failed - but those logs were logged a few minutes later 
 because 
 further request were logged aggregated by our application. 

 The first example (PRODUCT_PARTITION_ALREADY_EXISTS from 30.10.2015) 
 that I've posted to this thread happened on  

 29.10.2015 21:17:20,497

 requestId (taken from response) = 00052343fe9006900a0ddbd10203b361


 I can definitely see from the SOAP logs (from the Adwords API) that a 
 new group was created and the product partition add request was only sent 
 once. Does this help ?



 Am Dienstag, 3. November 2015 17:42:00 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi,
>
> I took a look at the requests coming from your developer token, and I 
> see REMOVE mutate requests coming in for that ad group's criteria at the 
> following times:
>
> ViennaTime : 2015-10-30 06:05:40
> Successful : True
>
> ViennaTime : 2015-10-30 06:06:04
> Successful : False
>
> In the user interface, I see the product groups were removed via the 
> API at 2015-10-30 06:06:07. I realize that is after the 2nd request, 
> but I'm theorizing that the first request may have taken 27 seconds to 
> complete. Do you happen to have timestamps in your logs for those 
> requests?
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, November 3, 2015 at 8:41:56 AM UTC-5, peter... wrote:
>>
>> Hi Josh 
>>
>> These are really wild assumptions, but for me it looks like that I 
>> can see the same problem with other requests regarding shopping ad group 
>> criterions too. 
>>
>> I've got another case that looks pretty similar to me (though I 
>> cannot prove this since I do not have SOAP logs for this). But from our 
>> logs I can see that we've sent a deletion request for shopping ad group 
>> criterions (e.g.: item id = 333518-105, criterion id = 139771732115, ad 
>> group id = 23172885875, campaign id = 321117275). The product partition 
>> was 
>> successfully deleted - I can see this in the change logs in the Adwords 
>> UI (30.10.2015 
>> 06:06:07). But my application logs tell me that the API returned an 
>> error
>> Errors while removing group item bids: Group 23172885875: Item 
>> 333518-105: 
>> [EntityNotFound,CriterionId{id=139771732115},EntityNotFound.INVALID_ID;];
>>  
>>
>> For me it looks like that someone duplicates the same request. I've 
>> double checked our logs and they tell me that it's not our application 
>> (as 
>> stated above I unfortunately cannot see the SOAP request directly). 
>> When looking at the SOAP logs that I've provided earlier I assume the 
>> same could have happened here.
>>
>>
>> Am Montag, 2. November 2015 19:56:56 UTC+1 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi Peter,
>>>
>>> Are you running multiple threads that are mutating the trees in 
>>> question? I ask because I looked at two of your requests from today 
>>> that 
>>> failed with PRODUCT_PARTITION_ALREADY_EXISTS followed 
>>> by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in 
>>> question *does* already exist in the ad group.
>>>
>>> The requests I checked were for ad group IDs 21637072081 
>>> and 21637229281, both under campaign ID 345581401.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, November 2, 2015 at 12:30:38 AM UTC-5, peter... wrote:

 Hi Josh

 Could the usage of not using distinct temporary IDs cause this 
 problem ? As stated above, 99% of my requests succeed (and we've 
 actually 
 sent millions of them until now).

Re: Error during product partition creation

2015-11-17 Thread peter . rietzler

Hi Josh

Any updates on this ?

Thanks!
Peter

Am Mittwoch, 11. November 2015 20:55:04 UTC+1 schrieb Josh Radcliff 
(AdWords API Team):
>
> Hi Peter,
>
> Using that request ID, I found some information on our side that indicates 
> that there may have been an unexpected duplication of this request. I'm 
> following up with the service owners to see what happened here, and will 
> let you know as soon as I hear back from them.
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, November 10, 2015 at 10:09:09 AM UTC-5, peter... wrote:
>>
>> Hi 
>>
>> No, I can't see any logs in our system despite the fact that the request 
>> has failed - but those logs were logged a few minutes later because further 
>> request were logged aggregated by our application. 
>>
>> The first example (PRODUCT_PARTITION_ALREADY_EXISTS from 30.10.2015) that 
>> I've posted to this thread happened on  
>>
>> 29.10.2015 21:17:20,497
>>
>> requestId (taken from response) = 00052343fe9006900a0ddbd10203b361
>>
>>
>> I can definitely see from the SOAP logs (from the Adwords API) that a new 
>> group was created and the product partition add request was only sent once. 
>> Does this help ?
>>
>>
>>
>> Am Dienstag, 3. November 2015 17:42:00 UTC+1 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi,
>>>
>>> I took a look at the requests coming from your developer token, and I 
>>> see REMOVE mutate requests coming in for that ad group's criteria at the 
>>> following times:
>>>
>>> ViennaTime : 2015-10-30 06:05:40
>>> Successful : True
>>>
>>> ViennaTime : 2015-10-30 06:06:04
>>> Successful : False
>>>
>>> In the user interface, I see the product groups were removed via the API 
>>> at 2015-10-30 06:06:07. I realize that is after the 2nd request, but 
>>> I'm theorizing that the first request may have taken 27 seconds to 
>>> complete. Do you happen to have timestamps in your logs for those requests?
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Tuesday, November 3, 2015 at 8:41:56 AM UTC-5, peter... wrote:

 Hi Josh 

 These are really wild assumptions, but for me it looks like that I can 
 see the same problem with other requests regarding shopping ad group 
 criterions too. 

 I've got another case that looks pretty similar to me (though I cannot 
 prove this since I do not have SOAP logs for this). But from our logs I 
 can 
 see that we've sent a deletion request for shopping ad group criterions 
 (e.g.: item id = 333518-105, criterion id = 139771732115, ad group id = 
 23172885875, campaign id = 321117275). The product partition was 
 successfully deleted - I can see this in the change logs in the Adwords UI 
 (30.10.2015 
 06:06:07). But my application logs tell me that the API returned an 
 error
 Errors while removing group item bids: Group 23172885875: Item 
 333518-105: 
 [EntityNotFound,CriterionId{id=139771732115},EntityNotFound.INVALID_ID;]; 

 For me it looks like that someone duplicates the same request. I've 
 double checked our logs and they tell me that it's not our application (as 
 stated above I unfortunately cannot see the SOAP request directly). 
 When looking at the SOAP logs that I've provided earlier I assume the 
 same could have happened here.


 Am Montag, 2. November 2015 19:56:56 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi Peter,
>
> Are you running multiple threads that are mutating the trees in 
> question? I ask because I looked at two of your requests from today that 
> failed with PRODUCT_PARTITION_ALREADY_EXISTS followed 
> by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in 
> question *does* already exist in the ad group.
>
> The requests I checked were for ad group IDs 21637072081 
> and 21637229281, both under campaign ID 345581401.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, November 2, 2015 at 12:30:38 AM UTC-5, peter... wrote:
>>
>> Hi Josh
>>
>> Could the usage of not using distinct temporary IDs cause this 
>> problem ? As stated above, 99% of my requests succeed (and we've 
>> actually 
>> sent millions of them until now). 
>>
>> The tree is correct for our purposes. It will be changed by other 
>> requests later on. The problem doesn't seem to be related to the actual 
>> tree anyhow. We also see this error when we are trying to add child 
>> partitions to already existing ones. This, however, is very hard to 
>> reproduce for me since I cannot just add logs for every SOAP request to 
>> our 
>> live application and wait for a few days for this to happen. Even this 
>> simple case required hammering against the API with a local test script 
>> for 
>> a few hours. 
>>
>> Thanks! 
>> Peter
>>
>> Am Freitag, 30. Oktober 2015 20:43:58 UTC+1 schrieb Josh Radcliff 
>> (

Re: Error during product partition creation

2015-11-10 Thread peter . rietzler

Hi 

No, I can't see any logs in our system despite the fact that the request 
has failed - but those logs were logged a few minutes later because further 
request were logged aggregated by our application. 

The first example (PRODUCT_PARTITION_ALREADY_EXISTS from 30.10.2015) that 
I've posted to this thread happened on  

29.10.2015 21:17:20,497

requestId (taken from response) = 00052343fe9006900a0ddbd10203b361


I can definitely see from the SOAP logs (from the Adwords API) that a new 
group was created and the product partition add request was only sent once. 
Does this help ?



Am Dienstag, 3. November 2015 17:42:00 UTC+1 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi,
>
> I took a look at the requests coming from your developer token, and I see 
> REMOVE mutate requests coming in for that ad group's criteria at the 
> following times:
>
> ViennaTime : 2015-10-30 06:05:40
> Successful : True
>
> ViennaTime : 2015-10-30 06:06:04
> Successful : False
>
> In the user interface, I see the product groups were removed via the API 
> at 2015-10-30 06:06:07. I realize that is after the 2nd request, but I'm 
> theorizing that the first request may have taken 27 seconds to complete. Do 
> you happen to have timestamps in your logs for those requests?
>
> Thanks,
> Josh, AdWords API Team
>
> On Tuesday, November 3, 2015 at 8:41:56 AM UTC-5, peter... wrote:
>>
>> Hi Josh 
>>
>> These are really wild assumptions, but for me it looks like that I can 
>> see the same problem with other requests regarding shopping ad group 
>> criterions too. 
>>
>> I've got another case that looks pretty similar to me (though I cannot 
>> prove this since I do not have SOAP logs for this). But from our logs I can 
>> see that we've sent a deletion request for shopping ad group criterions 
>> (e.g.: item id = 333518-105, criterion id = 139771732115, ad group id = 
>> 23172885875, campaign id = 321117275). The product partition was 
>> successfully deleted - I can see this in the change logs in the Adwords UI 
>> (30.10.2015 
>> 06:06:07). But my application logs tell me that the API returned an error
>> Errors while removing group item bids: Group 23172885875: Item 
>> 333518-105: 
>> [EntityNotFound,CriterionId{id=139771732115},EntityNotFound.INVALID_ID;]; 
>>
>> For me it looks like that someone duplicates the same request. I've 
>> double checked our logs and they tell me that it's not our application (as 
>> stated above I unfortunately cannot see the SOAP request directly). 
>> When looking at the SOAP logs that I've provided earlier I assume the 
>> same could have happened here.
>>
>>
>> Am Montag, 2. November 2015 19:56:56 UTC+1 schrieb Josh Radcliff (AdWords 
>> API Team):
>>>
>>> Hi Peter,
>>>
>>> Are you running multiple threads that are mutating the trees in 
>>> question? I ask because I looked at two of your requests from today that 
>>> failed with PRODUCT_PARTITION_ALREADY_EXISTS followed 
>>> by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in 
>>> question *does* already exist in the ad group.
>>>
>>> The requests I checked were for ad group IDs 21637072081 
>>> and 21637229281, both under campaign ID 345581401.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Monday, November 2, 2015 at 12:30:38 AM UTC-5, peter... wrote:

 Hi Josh

 Could the usage of not using distinct temporary IDs cause this problem 
 ? As stated above, 99% of my requests succeed (and we've actually sent 
 millions of them until now). 

 The tree is correct for our purposes. It will be changed by other 
 requests later on. The problem doesn't seem to be related to the actual 
 tree anyhow. We also see this error when we are trying to add child 
 partitions to already existing ones. This, however, is very hard to 
 reproduce for me since I cannot just add logs for every SOAP request to 
 our 
 live application and wait for a few days for this to happen. Even this 
 simple case required hammering against the API with a local test script 
 for 
 a few hours. 

 Thanks! 
 Peter

 Am Freitag, 30. Oktober 2015 20:43:58 UTC+1 schrieb Josh Radcliff 
 (AdWords API Team):
>
> Hi,
>
> I noticed that your request is operating on two ad groups but you are 
> reusing the same temporary ID for both. I would recommend using distinct 
> temporary IDs for distinct *Biddable/NegativeAdGroupCriterion* within 
> a single request.
>
> Also, in each case you are constructing what looks like an invalid 
> product partition tree 
> ,
>  
> consisting of:
>
>  ROOT (-1 biddable SUBDIVISION)
> /
>   ProductOfferId (negative UNIT)
>
> It looks like you are trying to create a 2nd level of the tree that 
> excludes *everything*, since you don't have other UNIT nodes at that 
> level and th

Re: Error during product partition creation

2015-11-03 Thread peter . rietzler

Hi Josh 

These are really wild assumptions, but for me it looks like that I can see 
the same problem with other requests regarding shopping ad group criterions 
too. 

I've got another case that looks pretty similar to me (though I cannot 
prove this since I do not have SOAP logs for this). But from our logs I can 
see that we've sent a deletion request for shopping ad group criterions 
(e.g.: item id = 333518-105, criterion id = 139771732115, ad group id = 
23172885875, campaign id = 321117275). The product partition was 
successfully deleted - I can see this in the change logs in the Adwords UI 
(30.10.2015 
06:06:07). But my application logs tell me that the API returned an error
Errors while removing group item bids: Group 23172885875: Item 333518-105: 
[EntityNotFound,CriterionId{id=139771732115},EntityNotFound.INVALID_ID;]; 

For me it looks like that someone duplicates the same request. I've double 
checked our logs and they tell me that it's not our application (as stated 
above I unfortunately cannot see the SOAP request directly). 
When looking at the SOAP logs that I've provided earlier I assume the same 
could have happened here.


Am Montag, 2. November 2015 19:56:56 UTC+1 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi Peter,
>
> Are you running multiple threads that are mutating the trees in question? 
> I ask because I looked at two of your requests from today that failed 
> with PRODUCT_PARTITION_ALREADY_EXISTS followed 
> by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in 
> question *does* already exist in the ad group.
>
> The requests I checked were for ad group IDs 21637072081 and 21637229281, 
> both under campaign ID 345581401.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, November 2, 2015 at 12:30:38 AM UTC-5, peter... wrote:
>>
>> Hi Josh
>>
>> Could the usage of not using distinct temporary IDs cause this problem ? 
>> As stated above, 99% of my requests succeed (and we've actually sent 
>> millions of them until now). 
>>
>> The tree is correct for our purposes. It will be changed by other 
>> requests later on. The problem doesn't seem to be related to the actual 
>> tree anyhow. We also see this error when we are trying to add child 
>> partitions to already existing ones. This, however, is very hard to 
>> reproduce for me since I cannot just add logs for every SOAP request to our 
>> live application and wait for a few days for this to happen. Even this 
>> simple case required hammering against the API with a local test script for 
>> a few hours. 
>>
>> Thanks! 
>> Peter
>>
>> Am Freitag, 30. Oktober 2015 20:43:58 UTC+1 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi,
>>>
>>> I noticed that your request is operating on two ad groups but you are 
>>> reusing the same temporary ID for both. I would recommend using distinct 
>>> temporary IDs for distinct *Biddable/NegativeAdGroupCriterion* within a 
>>> single request.
>>>
>>> Also, in each case you are constructing what looks like an invalid 
>>> product partition tree 
>>> ,
>>>  
>>> consisting of:
>>>
>>>  ROOT (-1 biddable SUBDIVISION)
>>> /
>>>   ProductOfferId (negative UNIT)
>>>
>>> It looks like you are trying to create a 2nd level of the tree that 
>>> excludes *everything*, since you don't have other UNIT nodes at that 
>>> level and the object is a *NegativeAdGroupCriterion*. If you subdivide 
>>> the tree by a dimension (offer ID in this case), you must have at least 
>>> *two* UNIT nodes: one for "Everything else" (*ProductOfferId* with a 
>>> null value) and at least one for a specific *ProductOfferId* with a 
>>> non-null value. Otherwise, the subdivision does not serve any purpose.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, October 30, 2015 at 6:35:58 AM UTC-4, peter... wrote:

 It looks like that we have the same problem. 

 We create a brand new AdGroup, then send the following request:

 
https://adwords.google.com/api/adwords/cm/v201506
 ">
 
ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns2:BiddableAdGroupCriterion">
22340202143

-1
   
  SUBDIVISION

  
 
 
ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns3:NegativeAdGroupCriterion">
22340202143

UNIT
-1


 
 
 
ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns4:BiddableAdGroupCriteri

Re: Error during product partition creation

2015-11-03 Thread peter . rietzler

i Josh 

Our app definitely mutates trees in parallel - but it never mutates trees 
in parallel belonging to the same campaigns. The requests that I sent 
before were reproduced in a single-threaded sandbox. The requests you 
mention are requests that our app tries to send once a day exactly because 
of this issue (it’s a follow up error on our side). The first occurrence 
(the one that should be this issue) must have been somewhere around 
2015-10-30 16:35:32 (+/- a few minutes) - maybe this helps. We currently 
resolve this on our side by reacting to the error - we will just query the 
external id of the existing partition. This is released on our system 
tomorrow - so it will definitely get harder for me to find the underlying 
requests since no special logging is done on our side due to the fact that 
this case gets business as usual … sorry.

Here is some additional info from our side: We've got other code that 
creates many product partitions - and we’ve never seen this before. The 
difference is that this code (the one working w/o any problems) never 
creates product partitions for more than one ad group at a time. The code 
where the issues arises sends stuff in batches to the API and mutates a 
maximum of 2 ad groups at a time (since this is the maximum allowed by the 
API).

Thanks!

Peter

Am Montag, 2. November 2015 19:56:56 UTC+1 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi Peter,
>
> Are you running multiple threads that are mutating the trees in question? 
> I ask because I looked at two of your requests from today that failed 
> with PRODUCT_PARTITION_ALREADY_EXISTS followed 
> by PRODUCT_PARTITION_DOES_NOT_EXIST, and in both cases the partition in 
> question *does* already exist in the ad group.
>
> The requests I checked were for ad group IDs 21637072081 and 21637229281, 
> both under campaign ID 345581401.
>
> Thanks,
> Josh, AdWords API Team
>
> On Monday, November 2, 2015 at 12:30:38 AM UTC-5, peter... wrote:
>>
>> Hi Josh
>>
>> Could the usage of not using distinct temporary IDs cause this problem ? 
>> As stated above, 99% of my requests succeed (and we've actually sent 
>> millions of them until now). 
>>
>> The tree is correct for our purposes. It will be changed by other 
>> requests later on. The problem doesn't seem to be related to the actual 
>> tree anyhow. We also see this error when we are trying to add child 
>> partitions to already existing ones. This, however, is very hard to 
>> reproduce for me since I cannot just add logs for every SOAP request to our 
>> live application and wait for a few days for this to happen. Even this 
>> simple case required hammering against the API with a local test script for 
>> a few hours. 
>>
>> Thanks! 
>> Peter
>>
>> Am Freitag, 30. Oktober 2015 20:43:58 UTC+1 schrieb Josh Radcliff 
>> (AdWords API Team):
>>>
>>> Hi,
>>>
>>> I noticed that your request is operating on two ad groups but you are 
>>> reusing the same temporary ID for both. I would recommend using distinct 
>>> temporary IDs for distinct *Biddable/NegativeAdGroupCriterion* within a 
>>> single request.
>>>
>>> Also, in each case you are constructing what looks like an invalid 
>>> product partition tree 
>>> ,
>>>  
>>> consisting of:
>>>
>>>  ROOT (-1 biddable SUBDIVISION)
>>> /
>>>   ProductOfferId (negative UNIT)
>>>
>>> It looks like you are trying to create a 2nd level of the tree that 
>>> excludes *everything*, since you don't have other UNIT nodes at that 
>>> level and the object is a *NegativeAdGroupCriterion*. If you subdivide 
>>> the tree by a dimension (offer ID in this case), you must have at least 
>>> *two* UNIT nodes: one for "Everything else" (*ProductOfferId* with a 
>>> null value) and at least one for a specific *ProductOfferId* with a 
>>> non-null value. Otherwise, the subdivision does not serve any purpose.
>>>
>>> Thanks,
>>> Josh, AdWords API Team
>>>
>>> On Friday, October 30, 2015 at 6:35:58 AM UTC-4, peter... wrote:

 It looks like that we have the same problem. 

 We create a brand new AdGroup, then send the following request:

https://adwords.google.com/api/adwords/cm/v201506
 ">

ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns2:BiddableAdGroupCriterion">
22340202143

-1

  SUBDIVISION

ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns3:NegativeAdGroupCriterion">
22340202143

UNIT
-1

Re: Error during product partition creation

2015-11-01 Thread peter . rietzler

Hi Josh

Could the usage of not using distinct temporary IDs cause this problem ? As 
stated above, 99% of my requests succeed (and we've actually sent millions 
of them until now). 

The tree is correct for our purposes. It will be changed by other requests 
later on. The problem doesn't seem to be related to the actual tree anyhow. 
We also see this error when we are trying to add child partitions to 
already existing ones. This, however, is very hard to reproduce for me 
since I cannot just add logs for every SOAP request to our live application 
and wait for a few days for this to happen. Even this simple case required 
hammering against the API with a local test script for a few hours. 

Thanks! 
Peter

Am Freitag, 30. Oktober 2015 20:43:58 UTC+1 schrieb Josh Radcliff (AdWords 
API Team):
>
> Hi,
>
> I noticed that your request is operating on two ad groups but you are 
> reusing the same temporary ID for both. I would recommend using distinct 
> temporary IDs for distinct *Biddable/NegativeAdGroupCriterion* within a 
> single request.
>
> Also, in each case you are constructing what looks like an invalid 
> product partition tree 
> ,
>  
> consisting of:
>
>  ROOT (-1 biddable SUBDIVISION)
> /
>   ProductOfferId (negative UNIT)
>
> It looks like you are trying to create a 2nd level of the tree that 
> excludes *everything*, since you don't have other UNIT nodes at that 
> level and the object is a *NegativeAdGroupCriterion*. If you subdivide 
> the tree by a dimension (offer ID in this case), you must have at least 
> *two* UNIT nodes: one for "Everything else" (*ProductOfferId* with a null 
> value) and at least one for a specific *ProductOfferId* with a non-null 
> value. Otherwise, the subdivision does not serve any purpose.
>
> Thanks,
> Josh, AdWords API Team
>
> On Friday, October 30, 2015 at 6:35:58 AM UTC-4, peter... wrote:
>>
>> It looks like that we have the same problem. 
>>
>> We create a brand new AdGroup, then send the following request:
>>
>> 
>>https://adwords.google.com/api/adwords/cm/v201506";>
>> 
>>ADD
>> https://adwords.google.com/api/adwords/cm/v201506"; 
>> xsi:type="ns2:BiddableAdGroupCriterion">
>>22340202143
>>
>>-1
>>SUBDIVISION
>>
>>  
>> 
>> 
>>ADD
>> https://adwords.google.com/api/adwords/cm/v201506"; 
>> xsi:type="ns3:NegativeAdGroupCriterion">
>>22340202143
>>
>>UNIT
>>-1
>>
>>
>> 
>> 
>> 
>>ADD
>> https://adwords.google.com/api/adwords/cm/v201506"; 
>> xsi:type="ns4:BiddableAdGroupCriterion">
>>22340202263
>>
>>-1
>>SUBDIVISION
>>
>> 
>> 
>> 
>>ADD
>> https://adwords.google.com/api/adwords/cm/v201506"; 
>> xsi:type="ns5:NegativeAdGroupCriterion">
>>22340202263
>>
>>UNIT
>>-1
>>
>>
>> 
>> 
>> 
>> 
>>
>> and *sporadically* get back
>>
>> 
>> 
>>soap:Server
>> 
>> [AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS @ 
>> operations[2].operand.criterion, 
>> AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST @ 
>> operations[3].operand.criterion.parentCriterionId; 
>> trigger:'TempCriterionId{id=1}']
>> 
>>https://adwords.google.com/api/adwords/cm/v201506";>
>> 
>> [AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS @ 
>> operations[2].operand.criterion, 
>> AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST @ 
>> operations[3].operand.criterion.parentCriterionId; 
>> trigger:'TempCriterionId{id=1}']
>>   
>>  ApiException
>>http://www.w3.org/2001/XMLSchema-instance"; 
>> xsi:type="AdGroupCriterionError">
>>operations[2].operand.criterion
>>
>>   
>>  
>> AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS
>>AdGroupCriterionError
>>PRODUCT_PARTITION_ALREADY_EXISTS
>> 
>>http://www.w3.org/2001/XMLSchema-instance"; 
>> xsi:type="AdGroupCriterionError">
>>   
>>  operations[3].operand.criterion.parentCriterionId
>>TempCriterionId{id=1}
>>   
>>  
>> AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST
>>AdGroupCrit

Re: Error during product partition creation

2015-10-30 Thread peter . rietzler

It looks like that we have the same problem. 

We create a brand new AdGroup, then send the following request:


   https://adwords.google.com/api/adwords/cm/v201506";>

   ADD
https://adwords.google.com/api/adwords/cm/v201506"; 
xsi:type="ns2:BiddableAdGroupCriterion">
   22340202143
   
   -1
   SUBDIVISION
   
 


   ADD
https://adwords.google.com/api/adwords/cm/v201506"; 
xsi:type="ns3:NegativeAdGroupCriterion">
   22340202143
   
   UNIT
   -1
   
   



   ADD
https://adwords.google.com/api/adwords/cm/v201506"; 
xsi:type="ns4:BiddableAdGroupCriterion">
   22340202263
   
   -1
   SUBDIVISION
   



   ADD
https://adwords.google.com/api/adwords/cm/v201506"; 
xsi:type="ns5:NegativeAdGroupCriterion">
   22340202263
   
   UNIT
   -1
   
   





and *sporadically* get back



   soap:Server

[AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS @ 
operations[2].operand.criterion, 
AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST @ 
operations[3].operand.criterion.parentCriterionId; 
trigger:'TempCriterionId{id=1}']

   https://adwords.google.com/api/adwords/cm/v201506";>

[AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS @ 
operations[2].operand.criterion, 
AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST @ 
operations[3].operand.criterion.parentCriterionId; 
trigger:'TempCriterionId{id=1}']
  
 ApiException
   http://www.w3.org/2001/XMLSchema-instance"; 
xsi:type="AdGroupCriterionError">
   operations[2].operand.criterion
   
  
 
AdGroupCriterionError.PRODUCT_PARTITION_ALREADY_EXISTS
   AdGroupCriterionError
   PRODUCT_PARTITION_ALREADY_EXISTS

   http://www.w3.org/2001/XMLSchema-instance"; 
xsi:type="AdGroupCriterionError">
  
 operations[3].operand.criterion.parentCriterionId
   TempCriterionId{id=1}
  
 
AdGroupCriterionError.PRODUCT_PARTITION_DOES_NOT_EXIST
   AdGroupCriterionError
   PRODUCT_PARTITION_DOES_NOT_EXIST

   




(request id of this particular response was 00052343fe9006900a0ddbd10203b361 
- if this helps).

We also see this error when creating concrete product partitions with case 
values. It succeeds in 99% of all cases, but we sporadically get back this 
error. We've seen this only for product partitions so far. Our code is 
single-threaded.

Am Dienstag, 6. Oktober 2015 16:06:53 UTC+2 schrieb Anthony Madrigal:
>
> Hi, 
>
> Since you are using the AdGroupCriterionService, do you mean AdGroup 
> instead of campaign? Could you please send me both your SOAP request and 
> response for the successful and failed operations through *Reply 
> privately to author*? This will help me see why it is working for one and 
> not the other.
>
> Thanks,
> Anthony
> AdWords API Team
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/8b6b7634-583e-4708-ab92-6892f77c46f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BiddingErrors.INVALID_BID occurring sporadically since 25.07.2015

2015-07-29 Thread peter . rietzler

Here is some more information for all of you reading this thread

-) Adwords does not accept bids for subdivisions anymore (see above). At 
least for us, the sporadical nature of this is gone since today - requests 
are now always rejected. 
-) When you send no bid, then Google applies a default bid (1, or 0.01) 
for the subdivision (as documented 
here: 
https://developers.google.com/adwords/api/docs/reference/v201506/AdGroupCriterionService.BiddingStrategyConfiguration)
-) When you fetch the partition from the API again, then the partition is 
returned with the default bid (1, or 0.01)


Am Dienstag, 28. Juli 2015 19:12:22 UTC+2 schrieb Michael Cloonan (AdWords 
API Team):
>
> Hello,
>
> This change was intentional in v201506 of the API. Bids on subdivisions in 
> product partitions are meaningless, and even setting them in the past had 
> no effect on actual bidding. This is simply new validation that prevents 
> you from even setting such bids.
>
> Regards,
> Mike, AdWords API Team
>
> On Tuesday, July 28, 2015 at 11:35:58 AM UTC-4, Józef Janik wrote:
>>
>> I'm only seeing this error on ADD operations.  SET operations seem to be 
>> fine...
>>
>> On Tuesday, July 28, 2015 at 10:49:33 AM UTC-4, Michael Cloonan (AdWords 
>> API Team) wrote:
>>>
>>> Hello,
>>>
>>> I've filed a bug with the engineering team, and I will keep this post 
>>> updated as I find out more information. Thanks for the reports and the 
>>> detailed information, everyone.
>>>
>>> Regards,
>>> Mike, AdWords API Team
>>>
>>> On Monday, July 27, 2015 at 9:23:27 AM UTC-4, 
>>> peter.r...@smarter-ecommerce.com wrote:

 Hi 

 We experience sporadically occurring BiddingErrors.INVALID_BID errors 
 when we send product partitions. First sight: 
 2015-07-25T02:31:05.650+02:00
 Seen 23 times since then. Seen across multiple accounts.

 It looks like, that *sometimes* the API does not accept a bid for 
 partitions (see examples below). The error is not reproducible. It's not 
 related to threading problems. We've got a simple single-threaded unit 
 test 
 that sporadically fails with this error (~1 out of 10-15 runs).
 Adwords Api version is v201506. Java API version is 2.2.0.

 Thanks! 
 Peter

 2015-07-27 12:41:07,521 1.1.1.RELEASE  WARN task-scheduler-16 
 AdWordsServiceClient.soapXmlLogger - SOAP Request:
 http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="
 http://www.w3.org/2001/XMLSchema"; xmlns:xsi="
 http://www.w3.org/2001/XMLSchema-instance";>
 
 https://adwords.google.com/api/adwords/cm/v201506"; 
 soapenv:mustUnderstand="0">
 false
 false
 
 
 
 
 https://adwords.google.com/api/adwords/cm/v201506";>
 
 ADD
 https://adwords.google.com/api/adwords/cm/v201506"; 
 xsi:type="ns2:BiddableAdGroupCriterion">
 X
 
 -2
 SUBDIVISION
 
 
 uco
 
 
 
 
 
 80
 
 
 
 
 

 

 https://adwords.google.com/api/adwords/cm/v201506";>
 00051bd8fdb71fa00ac4006bca04b828
 AdGroupCriterionService
 mutate
 0
 248
 

 [*BiddingErrors.INVALID_BID @ 
 operations[0].operand.biddingStrategyConfiguration.bids; 
 trigger:'CpcBid{bid=0.80, contentBid=null, cpcBidSource=null}',*
  ..

>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0e77730d-3669-4ad7

BiddingErrors.INVALID_BID occurring sporadically since 25.07.2015

2015-07-27 Thread peter . rietzler

Hi 

We experience sporadically occurring BiddingErrors.INVALID_BID errors when 
we send product partitions. First sight: 2015-07-25T02:31:05.650+02:00
Seen 23 times since then. Seen across multiple accounts.

It looks like, that *sometimes* the API does not accept a bid for 
partitions (see examples below). The error is not reproducible. It's not 
related to threading problems. We've got a simple single-threaded unit test 
that sporadically fails with this error (~1 out of 10-15 runs).
Adwords Api version is v201506. Java API version is 2.2.0.

Thanks! 
Peter

2015-07-27 12:41:07,521 1.1.1.RELEASE  WARN task-scheduler-16 
AdWordsServiceClient.soapXmlLogger - SOAP Request:
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

https://adwords.google.com/api/adwords/cm/v201506"; 
soapenv:mustUnderstand="0">
false
false




https://adwords.google.com/api/adwords/cm/v201506";>

ADD
https://adwords.google.com/api/adwords/cm/v201506"; 
xsi:type="ns2:BiddableAdGroupCriterion">
X

-2
SUBDIVISION


uco





80








https://adwords.google.com/api/adwords/cm/v201506";>
00051bd8fdb71fa00ac4006bca04b828
AdGroupCriterionService
mutate
0
248


[*BiddingErrors.INVALID_BID @ 
operations[0].operand.biddingStrategyConfiguration.bids; 
trigger:'CpcBid{bid=0.80, contentBid=null, cpcBidSource=null}',* ..

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ee7d22ff-bf2b-4cf4-8523-4fd06ae3f967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error: "Processing instructions are not allowed within SOAP messages"

2015-07-02 Thread peter . rietzler

Hi Josh

We do follow the threading guidelines.

I've just checked that we had 44 occurrences of this error within the last 
7 days. 
The error is not account specific.
If the error occurs, then a retry typically succeeds (there is some time 
between retries on our side - usually up to 20 minutes).

Am Montag, 29. Juni 2015 15:11:50 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):

> Hi,
>
> Are you following the guidelines mentioned in the Thread safety page for 
> the Java client library? 
>  In 
> particular, please make sure that you are not reusing instances of 
> *AdWordsSession* across threads.
>
> Thanks,
> Josh, AdWords API Team
>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/23711409-45c2-48ef-a33d-6b24eb961f1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Error: "Processing instructions are not allowed within SOAP messages"

2015-06-28 Thread peter . rietzler

We hit this issue occasionally, it's, however, getting worse now: 48 
occurrences within the last 7 days. It seems that it cannot be boiled down 
to a single service. I've added two example stacktraces. 

Caused by: org.xml.sax.SAXException: Processing instructions are not 
allowed within SOAP messages at 
org.apache.axis.AxisFault.makeFault(AxisFault.java:101) at 
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) at 
org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at 
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
 
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at 
org.apache.axis.client.Call.invokeEngine(Call.java:2784) at 
org.apache.axis.client.Call.invoke(Call.java:2767) at 
org.apache.axis.client.Call.invoke(Call.java:2443) at 
org.apache.axis.client.Call.invoke(Call.java:2366) at 
org.apache.axis.client.Call.invoke(Call.java:1812) at 
com.google.api.ads.adwords.axis.v201409.cm.CampaignServiceSoapBindingStub.get(CampaignServiceSoapBindingStub.java:1350)

Caused by: org.xml.sax.SAXException: Processing instructions are not 
allowed within SOAP messages at 
org.apache.axis.AxisFault.makeFault(AxisFault.java:101) at 
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) at 
org.apache.axis.Message.getSOAPEnvelope(Message.java:435) at 
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
 
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at 
org.apache.axis.client.Call.invokeEngine(Call.java:2784) at 
org.apache.axis.client.Call.invoke(Call.java:2767) at 
org.apache.axis.client.Call.invoke(Call.java:2443) at 
org.apache.axis.client.Call.invoke(Call.java:2366) at 
org.apache.axis.client.Call.invoke(Call.java:1812) at 
com.google.api.ads.adwords.axis.v201409.ch.CustomerSyncServiceSoapBindingStub.get(CustomerSyncServiceSoapBindingStub.java:521)

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/34f45175-699b-4074-a21a-407ea84ec2e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BUG] Geo Performance Report: {Error: AuthenticationError.AUTHENTICATION_FAILED, Trigger: , FieldPath: }

2015-04-26 Thread peter . rietzler

We've got the same problem! And it happens for other reports too (e.g. 
SHOPPING_PERFORMANCE_REPORT). Looks like GEO_PERFORMANCE_REPORT is always 
affected and other are affected in an unpredictable manner - they sometimes 
succeed and sometimes fail ...

Am Freitag, 24. April 2015 19:52:34 UTC+2 schrieb AdWordsApiUser:
>
> Started getting this error if city, or region is selected (if you select 
> only country, it works OK) in the GEO_PERFORMANCE_REPORT. API v201409.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/3c9556bb-a376-4982-87a5-a08c21e69b7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AuthenicationError.NOT_ADS_USER - but only for single report type.

2015-03-09 Thread peter . rietzler

We experience the same problems since a few days. It is unpredictable if 
the error occurs or not. The same request sometimes fails (with the 
NOT_ADS_USER error) and sometimes succeeds. Test requests were issued right 
after each other (first succeeded, second failed, third succeeded, ...)

Am Samstag, 7. März 2015 18:24:03 UTC+1 schrieb Alex Jones:
>
> We are experiencing issues with requesting a Geography Report from the 
> API. Strangely, we use the same code to process all of our other reports, 
> which completed successfully both before and after the failing Geography 
> Report. We've waited several hours and then requested the report again, to 
> no avail. I'm hoping you have some insight into this issue. This is the 
> same production code we've been executing for some time now with no issues, 
> and configurations have not been altered recently either. We rely on this 
> data, and not having it available is very inconvenient for us. We'd 
> appreciate any help you can provide. 
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/85048955-9a82-4af7-b8ec-e0024b67ccf6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Feed Item Mapping Validation Information via API ?

2014-11-11 Thread peter . rietzler

I am wondering how I can get validation information for feed items via the 
API. 

I am currently using the FeedItemService. Here is what I experience at the 
moment when using the selector "ValidationDetails":

If an item awaits approval, then the validationDetails property is not set 
at all.
If an item is either approved or disapproved, then the validationDetails 
property is set, but no validationErrors are delivered.

In the Adwords UI I can see, disapproval reasons, e.g. "Guns & parts". I 
hoped, that I can access this information via the validationErrors 
property. 

Is there any other way to get the information or am I doing something wrong 
?

Thanks! 
Peter

// --- here is  Groovy code snippet that should conceptually show what I am 
doing ---

adwordsDataService.getFeedItems(account, feedId).eachWithIndex { item, i ->

println "$item.feedItemId ($i)"
if(item.validationDetails) {
item.validationDetails.each {
println "  $it.approvalStatus / $it.validationStatus"
if(it.validationErrors) {
it.validationErrors.each {
println "$it.feedAttributeIds / 
$it.validationErrorCode / $it.errorInformation"
}
} else {
println "no validation errors"
}

}
} else {
println "  no validation details"
}
println "="
}

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/ca34025b-e66c-4a2d-88a3-7b7b2b104653%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Placeholder Feed Item Report: Problems with Zero Impression Rows

2014-11-11 Thread peter . rietzler

When I post the AWQL query 
SELECT FeedId, FeedItemId, Status, ValidationDetails FROM 
PLACEHOLDER_FEED_ITEM
I get back a the following error
HTTP Response Code: 400, Type: QueryError.DATE_COLUMN_REQUIRES_DURING_CLAUSE

In contrast, when using a ReportDefinition with includeZeroImpressions set 
to true, I do get back that data as expected. It seems that the Date column 
is included automatically, which in turn leads to the fact that we cannot 
get zero impression rows via AWQL because a segment is included. 

Is there any other way to get this data via AWQL ?

Thanks! 
Peter


-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

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
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/057f0e6f-4976-4a5d-98e3-958cb03700a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Integer Id fields in GEO_PERFORMANCE_REPORT

2014-10-24 Thread peter . rietzler

Hi 

It would help us if you fix the data type in the report reference as well 
as in the report reference CSV files to download. We use this information 
to generate some stuff and have to change the datatype each time we update 
our Adwords API versions. 

Thanks! 
Peter


Am Dienstag, 20. Mai 2014 23:11:44 UTC+2 schrieb Josh Radcliff (AdWords API 
Team):
>
> Hi Devesh,
>
> I've submitted a separate enhancement request to add fields for the Long 
> IDs to the report. We may not switch the meaning of the existing fields 
> since that could cause problems for developers who are expecting a 
> combination of Long and String values in those fields. I'll post here when 
> I have updates on either issue.
>
> Cheers,
> Josh, AdWords API Team
>
> On Monday, May 19, 2014 8:25:37 PM UTC-4, Devesh Parekh wrote:
>>
>> Hi Takeshi,
>>
>> This bug is causing the reporting endpoint to return data that I cannot 
>> automatically map to an ID. For example, when I run "SELECT CityCriteriaId, 
>> MetroCriteriaId, RegionCriteriaId, CountryCriteriaId, 
>> MostSpecificCriteriaId, Impressions,Clicks FROM GEO_PERFORMANCE_REPORT 
>> WHERE AdGroupId=8385025797 DURING 20140501,20140515", I get the following 
>> two rows, which are referring to two different Zacatecas, but I can't tell 
>> which Zacatecas by reading the report:
>>
>> Unspecified,,Zacatecas,Mexico,Zacatecas,---,---
>> Unspecified,,Zacatecas,Mexico,Zacatecas,---,---
>>
>> If the report returned integer IDs like the documentation says (
>> https://developers.google.com/adwords/api/docs/appendix/reports#geo), I 
>> would know which Zacatecas each line is referring to.
>>
>> -- 
>> Devesh
>>
>> On Monday, July 29, 2013 11:18:03 AM UTC-7, Devesh Parekh wrote:
>>>
>>> Thanks, Takeshi. Can you also request that they add integer id fields to 
>>> the report?
>>>
>>> -- 
>>> Devesh
>>>
>>> On Sunday, July 28, 2013 11:45:08 PM UTC-7, Takeshi Hagikura (AdWords 
>>> API Team) wrote:

 Hi Devesh,

 Thanks. Confirmed the situation. 
 Escalated a request to fix the fieldType to String. 

 Best,
 - Takeshi, AdWords API Team

 On Saturday, July 27, 2013 3:10:21 AM UTC+9, Devesh Parekh wrote:
>
> Hi Takeshi,
>
> Yes, all the values for these ID fields are non-numerical (like 
> "Ireland" and "Cork"), and you can verify it by running the example query 
> I 
> provided. According to the documentation, these should be Integers, and I 
> would much prefer to have the report behave as documented instead of as 
> the 
> way it currently behaves.
>
> -- 
> Devesh
>
>
> On Thu, Jul 25, 2013 at 10:49 PM, Takeshi Hagikura (AdWords API Team) 
>  wrote:
>
>> Hi, 
>>
>> Was there a non numerical value for Id field?
>> If not, you can map it to Integers in a programing language. 
>> Basically the result is returned as CSV or XML as you specified when 
>> you download a report.
>>
>> Best,
>> - Takeshi, 
>>
>> On Wednesday, July 24, 2013 9:19:34 AM UTC+9, Devesh Parekh wrote:
>>>
>>> According to https://developers.google.
>>> com/adwords/api/docs/appendix/reports#geo, CountryCriteriaId and 
>>> RegionCriteriaId should be Integers, but the when I send an AWQL query 
>>> to 
>>> the reportdownload endpoint (https://adwords.google.com/
>>> api/adwords/reportdownload/v201306) to return those fields, I get 
>>> Strings. Example query: SELECT CountryCriteriaId, RegionCriteriaId, 
>>> Impressions FROM GEO_PERFORMANCE_REPORT DURING 20130101,20130723
>>>
>>> Can you make them Integers?
>>>
>>> -- 
>>> Devesh
>>>
>>  -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> 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 adwor...@googlegroups.com
>> To unsubscribe from this group, send email to
>> adwords-api...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/adwords-api?hl=en
>>  
>> --- 
>> You received this message because you are subscribed to a topic in 
>> the Google Groups "AdWords API Forum" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/adwords-api/EiGdtzXY30s/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> adwords-api...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
h

Quality Score History

2011-10-14 Thread Peter Rietzler

I want to see a history of the quality score for a single keyword. When I 
fetch a keyword performance report for the last 30 days, the quality score 
is the same for each keyword for every day. Is the quality score recorded 
and delivered on a daily basis or do I just see the current value - in which 
case I have to fetch the report every day to get a history ?

Thanks!
Peter

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
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: Policy violations - v201710 vs 201706

Re: Policy violations - v201710 vs 201706

Re: Keyword Criterion IDs question

Re: Impression values lower than zero

Re: Error during product partition creation

Re: Error during product partition creation

Re: Error during product partition creation

Re: Error during product partition creation

Re: Error during product partition creation

Re: Error during product partition creation

Re: Error during product partition creation

Re: BiddingErrors.INVALID_BID occurring sporadically since 25.07.2015

BiddingErrors.INVALID_BID occurring sporadically since 25.07.2015

Re: Error: "Processing instructions are not allowed within SOAP messages"

Error: "Processing instructions are not allowed within SOAP messages"

Re: [BUG] Geo Performance Report: {Error: AuthenticationError.AUTHENTICATION_FAILED, Trigger: , FieldPath: }

Re: AuthenicationError.NOT_ADS_USER - but only for single report type.

Feed Item Mapping Validation Information via API ?

Placeholder Feed Item Report: Problems with Zero Impression Rows

Re: Integer Id fields in GEO_PERFORMANCE_REPORT

Quality Score History

21 matches

Site Navigation

Mail list logo

Footer information