Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

Thank you for the concise reply. On Monday, May 22, 2017 at 8:00:24 PM UTC-7, Peter Oliquino wrote: > > Hi Jean-Guy, > > The CriterionUse > > field > is currently read only a

Re: How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

biddable" to "excluded" not "negative" > > On Friday, May 19, 2017 at 10:33:43 PM UTC+1, Jean-Guy Speton wrote: >> >> We're using the PHP SDK 25.4.0, lib v201609. >> >> We have an odd use case for one of our clients. We want to structure &g

How to change a ProductOfferId ProductPartition BIDDABLE to NEGATIVE and vice-versa?

We're using the PHP SDK 25.4.0, lib v201609. We have an odd use case for one of our clients. We want to structure product campaigns based on product margins which is a function of the price of the product. However as prices change we wish to "move" products out of the current campaign into a d

Re: Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

Hi... any update on this issue? We are still getting this error 100% of the time. Thanks. On Friday, March 3, 2017 at 11:03:22 AM UTC-8, Shwetha Vastrad (AdWords API Team) wrote: > > Hi Jean-Guy, > > Could you send over the SOAP request log as well so I can take a look? > Could you also tell

Consistent InternalApiError.UNEXPECTED_INTERNAL_API_ERROR when setting Location criterion on non-US shopping campaign.

For the last week or so when publishing changes to non-US shopping campaigns location criteria are causing the request to fail with the InternalApiError.UNEXPECTED_INTERNAL_API_ERROR exception. This call works for US location, but fails for UK, CH, CA and AU. When I remove the location criter

Re: Fatal Error: invalid_request

New endpoint gives the following 400 response: Error 400 (Not Found)!!1*{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px;}* > body{background:url(//www.google.c

Re: Fatal Error: invalid_request

Same problem here, have been getting "error":"invalid_request" responses on RefreshAccessToken requests starting early yesterday. They happen frequently, but usually one or more retries succeeds in getting an access token. We're on v201607 using the same OAuth2 credentials we've been using for