yes, right, I figured this out, I missed the userStatus while checking the error,
was just about to write it here... sorry, thanks a lot, Albert On Wednesday, September 17, 2014 5:11:16 PM UTC+3, GregT wrote: > > Hi, Albert. > > You actually have a different error than what I'm talking about. This > thread is about setting mobile bid modifiers on ad groups in shopping > campaigns, as opposed to setting bids on shopping partitions. If you look > at the fault that was returned, you'll see that the fieldPath is > operations[0].operand.userStatus that it's complaining about. The reason > is that you are not allowed to set the status on partitions, unlike other > BiddableAdGroupCriterion. If you stop sending the userStatus in your > request, you should stop getting that error. > > FYI, > Greg > > On Wednesday, September 17, 2014 5:16:28 AM UTC-5, Albert wrote: >> >> >> hi, >> >> we've been getting this error as well, while trying to change bids on >> shopping items (offer ids) >> >> 10. is it a bug or intended behavior? >> >> 20. does it have something to do with using api version v201402, not >> latest? >> >> enclosed is the soap trace: >> >> ~~~soap_request hacked~~~ at local time: 17/09/2014 07:08:47 >> <?xml version="1.0" encoding="utf-8"?> >> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd=" >> http://www.w3.org/2001/XMLSchema";> >> <soap:Header> >> <RequestHeader xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402";> >> <developerToken xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402 >> ">**************</developerToken> >> <clientCustomerId xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402 >> ">*************</clientCustomerId> >> <userAgent xmlns="https://adwords.google.com/api/adwords/cm/v201402 >> ">***********</userAgent> >> <validateOnly xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402";>false</validateOnly> >> </RequestHeader> >> </soap:Header> >> <soap:Body> >> <mutate xmlns="https://adwords.google.com/api/adwords/cm/v201402";> >> <operations> >> <operator>SET</operator> >> <operand xsi:type="BiddableAdGroupCriterion"> >> <adGroupId>13720172339</adGroupId> >> <criterion xsi:type="ProductPartition"> >> <id>98413046219</id> >> </criterion> >> <userStatus>ACTIVE</userStatus> >> <biddingStrategyConfiguration> >> <bids xsi:type="CpcBid"> >> <bid> >> <microAmount>340000</microAmount> >> </bid> >> </bids> >> </biddingStrategyConfiguration> >> </operand> >> </operations> >> </mutate> >> </soap:Body> >> </soap:Envelope> >> >> -----SoapResponse at 17/09/2014 07:08:48 >> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> >> <soap:Header> >> <ResponseHeader xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402";> >> <requestId>000503400eff45500aece7e888004712</requestId> >> <serviceName>AdGroupCriterionService</serviceName> >> <methodName>mutate</methodName> >> <operations>0</operations> >> <responseTime>429</responseTime> >> </ResponseHeader> >> </soap:Header> >> <soap:Body> >> <soap:Fault> >> <faultcode>soap:Server</faultcode> >> >> <faultstring>[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE >> >> @ operations[0].operand.userStatus; trigger:'SHOPPING']</faultstring> >> <detail> >> <ApiExceptionFault xmlns=" >> https://adwords.google.com/api/adwords/cm/v201402";> >> >> <message>[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ >> operations[0].operand.userStatus; trigger:'SHOPPING']</message> >> >> <ApplicationException.Type>ApiException</ApplicationException.Type> >> <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:type="OperationAccessDenied"> >> <fieldPath>operations[0].operand.userStatus</fieldPath> >> <trigger>SHOPPING</trigger> >> >> <errorString>OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE</errorString> >> <ApiError.Type>OperationAccessDenied</ApiError.Type> >> <reason>OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE</reason> >> </errors> >> </ApiExceptionFault> >> </detail> >> </soap:Fault> >> </soap:Body> >> </soap:Envelope> >> >> >> >> On Monday, September 15, 2014 8:07:10 PM UTC+3, GregT wrote: >>> >>> Hi, Anash. >>> >>> It's been a week since your post, and we are still getting the same >>> error as we originally did. Has it just not gone live yet, or is it >>> possible that the intended fix did not actually fix it? >>> >>> Thanks, >>> Greg >>> >>> On Monday, September 8, 2014 8:31:00 AM UTC-5, Anash P. Oommen (AdWords >>> API Team) wrote: >>>> >>>> Hi Greg, >>>> >>>> We have added a fix, and this should go live during the next server >>>> push. If the issues persist after a few days, let me know. >>>> >>>> Cheers, >>>> Anash P. Oommen, >>>> AdWords API Advisor. >>>> >>>> On Thursday, September 4, 2014 12:56:29 PM UTC-4, Anash P. Oommen >>>> (AdWords API Team) wrote: >>>>> >>>>> Hi Greg, >>>>> >>>>> Not yet, I have pinged them again today for updates. I'll keep you >>>>> posted. Apologies for the delay in getting this resolved. >>>>> >>>>> Cheers, >>>>> Anash >>>>> >>>>> On Tuesday, September 2, 2014 2:13:34 PM UTC-4, GregT wrote: >>>>>> >>>>>> Hi, Anash. >>>>>> >>>>>> Just wondering if you got any update from the API team last week >>>>>> regarding why the ad group mobile bid modifiers for shopping campaigns >>>>>> are >>>>>> not permitted through the API, even though you can do it in the UI? >>>>>> >>>>>> Thanks, >>>>>> Greg >>>>>> >>>>>> On Monday, August 25, 2014 10:07:14 AM UTC-5, Anash P. Oommen >>>>>> (AdWords API Team) wrote: >>>>>>> >>>>>>> Hi Greg, >>>>>>> >>>>>>> No updates, I'll ping the team again for updates today. >>>>>>> >>>>>>> Cheers, >>>>>>> Anash P. Oommen, >>>>>>> AdWords API Advisor. >>>>>>> >>>>>>> On Thursday, August 21, 2014 2:17:33 PM UTC-4, GregT wrote: >>>>>>>> >>>>>>>> Hi, Anash. >>>>>>>> >>>>>>>> Any word on this -- particularly as to why adding ad group mobile >>>>>>>> bid modifiers on shopping campaigns would not be permitted through the >>>>>>>> API >>>>>>>> when it works fine through the AdWords UI? We'd really like to be >>>>>>>> able to >>>>>>>> set these, as we previously were on our PLA campaigns. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Greg >>>>>>>> >>>>>>>> On Thursday, August 14, 2014 10:23:14 AM UTC-5, Anash P. Oommen >>>>>>>> (AdWords API Team) wrote: >>>>>>>>> >>>>>>>>> Hi Greg, >>>>>>>>> >>>>>>>>> I checked the logs, this is >>>>>>>>> a OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE error that is not getting >>>>>>>>> rethrown correctly. I've filed a request to ensure that the error is >>>>>>>>> handled and rethrown correctly instead of the generic "Fault occurred >>>>>>>>> while >>>>>>>>> processing." message. I'll also find out why the operation is not >>>>>>>>> allowed >>>>>>>>> by the API if it is allowed by the UI. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> Anash P. Oommen >>>>>>>>> AdWords API Advisor. >>>>>>>>> >>>>>>>>> On Wednesday, August 13, 2014 10:57:14 AM UTC-4, GregT wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> I'm doing final testing of our code to start handling the >>>>>>>>>> upcoming migration to shopping campaigns. One common thing we do on >>>>>>>>>> all >>>>>>>>>> our campaign types (including PLA, and will need to do on shopping >>>>>>>>>> campaigns) is adjust mobile bid modifiers at the ad group and >>>>>>>>>> campaign >>>>>>>>>> level. However, every attempt at doing this at the ad group level >>>>>>>>>> in our >>>>>>>>>> test account is failing (campaign level is working fine). The exact >>>>>>>>>> same >>>>>>>>>> code is used to manage this for every type of campaign we manage, >>>>>>>>>> and has >>>>>>>>>> been working (and still does work) on all of them (PLA, search, and >>>>>>>>>> display), except for shopping. We get a very generic error back >>>>>>>>>> from the >>>>>>>>>> API whenever we do it for a shopping campaign, saying "Fault >>>>>>>>>> occurred while >>>>>>>>>> processing.". An example request/response is below. We can >>>>>>>>>> add/modify >>>>>>>>>> these bid modifiers in the AdWords UI, so it's not that shopping >>>>>>>>>> campaigns >>>>>>>>>> don't support mobile bid modifiers -- the API just appears to have a >>>>>>>>>> bug >>>>>>>>>> adding them. >>>>>>>>>> >>>>>>>>>> Could someone please look into this? We are using v201406 via >>>>>>>>>> the latest version of the Java client API, if that matters. >>>>>>>>>> >>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope >>>>>>>>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >>>>>>>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" >>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance";> >>>>>>>>>> <soapenv:Header> >>>>>>>>>> <ns1:RequestHeader xmlns:ns1=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201406"; >>>>>>>>>> soapenv:mustUnderstand="0"> >>>>>>>>>> <ns1:clientCustomerId>redacted</ns1:clientCustomerId> >>>>>>>>>> <ns1:developerToken>redacted</ns1:developerToken> >>>>>>>>>> <ns1:userAgent>redacted</ns1:userAgent> >>>>>>>>>> <ns1:validateOnly>false</ns1:validateOnly> >>>>>>>>>> <ns1:partialFailure>false</ns1:partialFailure> >>>>>>>>>> </ns1:RequestHeader> >>>>>>>>>> </soapenv:Header> >>>>>>>>>> <soapenv:Body> >>>>>>>>>> <mutate xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201406";> >>>>>>>>>> <operations> >>>>>>>>>> <operator>ADD</operator> >>>>>>>>>> <operand> >>>>>>>>>> <adGroupId>18347850910</adGroupId> >>>>>>>>>> <criterion> >>>>>>>>>> <id>30001</id> >>>>>>>>>> </criterion> >>>>>>>>>> <bidModifier>0.49999999999999994</bidModifier> >>>>>>>>>> </operand> >>>>>>>>>> </operations> >>>>>>>>>> <operations> >>>>>>>>>> <operator>ADD</operator> >>>>>>>>>> <operand> >>>>>>>>>> <adGroupId>18347851030</adGroupId> >>>>>>>>>> <criterion> >>>>>>>>>> <id>30001</id> >>>>>>>>>> </criterion> >>>>>>>>>> <bidModifier>0.49999999999999994</bidModifier> >>>>>>>>>> </operand> >>>>>>>>>> </operations> >>>>>>>>>> </mutate> >>>>>>>>>> </soapenv:Body> >>>>>>>>>> </soapenv:Envelope> >>>>>>>>>> 08-12-14 17:26:54,409 [main] WARN soapXmlLogger - SOAP Response: >>>>>>>>>> <?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap=" >>>>>>>>>> http://schemas.xmlsoap.org/soap/envelope/";> >>>>>>>>>> <soap:Header> >>>>>>>>>> <ResponseHeader xmlns=" >>>>>>>>>> https://adwords.google.com/api/adwords/cm/v201406";> >>>>>>>>>> >>>>>>>>>> <requestId>000500762a915dc00a8076c81c009ef5</requestId> >>>>>>>>>> <serviceName>AdGroupBidModifierService</serviceName> >>>>>>>>>> <methodName>mutate</methodName> >>>>>>>>>> <operations>2</operations> >>>>>>>>>> <responseTime>114</responseTime> >>>>>>>>>> </ResponseHeader> >>>>>>>>>> </soap:Header> >>>>>>>>>> <soap:Body> >>>>>>>>>> <soap:Fault> >>>>>>>>>> <faultcode>soap:Server</faultcode> >>>>>>>>>> <faultstring>Fault occurred while >>>>>>>>>> processing.</faultstring> >>>>>>>>>> </soap:Fault> >>>>>>>>>> </soap:Body> >>>>>>>>>> </soap:Envelope> >>>>>>>>>> >>>>>>>>>> Thanks in advance, >>>>>>>>>> Greg >>>>>>>>>> >>>>>>>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. 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/71cd1d91-27d5-4f21-81ee-c9d6b210f532%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
