Re: [1-8742000004636] ad group mobile bid modifiers in shopping campaigns not working
Hi, Anash. That worked! I'm not sure why just a Criterion object with the right id works for search and PLA campaigns but not shopping campaigns, but I'm glad we can set them now. Thanks for the help, Greg On Fri, Nov 7, 2014 at 12:13 PM, adwords-api@googlegroups.com wrote: Hi Greg, Could you try sending a Platform object instead of a criterion object in your requests? Cheers, Anash On 10/27/14 13:46:16 g...@finch.com wrote: Hi, Anash. Any news on this? Thanks, Greg On Monday, October 20, 2014 4:01:18 PM UTC-5, GregT wrote: Hi, Anash. I switched over to the new v201409 API that was just recently released, using the latest Java API library. It still doesn't work. It now gives a reasonable exception, rather than just the generic fault occurred while processing error. However, you had said on Sep 24 that the fix that should be going live was that we'd be able to set these bid modifiers on ad groups in shopping campaigns now (as can be done in the UI for shopping campaigns and could be done in the API for the old PLA campaigns)? An example request from today: ?xml version=1.0 encoding=UTF-8?soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2 001/XMLSchema xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Header ns1:RequestHeader xmlns:ns1=https://adwords.goo gle.com/api/adwords/cm/v201409 soapenv:mustUnderstand=0 ns1:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201409; operations operatorADD/operator operand adGroupId19190905510/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905390/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905270/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905150/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905030/adGroupId criterion id30001/id /criterion bidModifier1.25/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 10-20-14 15:48:08,472 [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/v201409 requestId000505e0d4e0e1500ab68045b8004eee/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime61/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[OperationAccessDenied.OPERATION_NOT_PERMITTED_ FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[4].operand.criterion; trigger:'SHOPPING']/faultstring detail ApiExceptionFault
Re: ad group mobile bid modifiers in shopping campaigns not working
For posterity's sake: Anash emailed me and asked me to try sending a Platform object with the 30001 id, rather than just a plain criterion object, and this worked. I'm not sure why just a Criterion object with the right id works for search and PLA campaigns but not shopping campaigns, but I'm glad we can set them now. Thanks again to Anash for the help, Greg On Monday, October 27, 2014 12:46:16 PM UTC-5, GregT wrote: Hi, Anash. Any news on this? Thanks, Greg On Monday, October 20, 2014 4:01:18 PM UTC-5, GregT wrote: Hi, Anash. I switched over to the new v201409 API that was just recently released, using the latest Java API library. It still doesn't work. It now gives a reasonable exception, rather than just the generic fault occurred while processing error. However, you had said on Sep 24 that the fix that should be going live was that we'd be able to set these bid modifiers on ad groups in shopping campaigns now (as can be done in the UI for shopping campaigns and could be done in the API for the old PLA campaigns)? An example request from today: ?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/v201409; soapenv:mustUnderstand=0 ns1:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201409; operations operatorADD/operator operand adGroupId19190905510/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905390/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905270/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905150/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905030/adGroupId criterion id30001/id /criterion bidModifier1.25/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 10-20-14 15:48:08,472 [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/v201409; requestId000505e0d4e0e1500ab68045b8004eee/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime61/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[4].operand.criterion; trigger:'SHOPPING']/faultstring detail ApiExceptionFault
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi, Anash. Any news on this? Thanks, Greg On Monday, October 20, 2014 4:01:18 PM UTC-5, GregT wrote: Hi, Anash. I switched over to the new v201409 API that was just recently released, using the latest Java API library. It still doesn't work. It now gives a reasonable exception, rather than just the generic fault occurred while processing error. However, you had said on Sep 24 that the fix that should be going live was that we'd be able to set these bid modifiers on ad groups in shopping campaigns now (as can be done in the UI for shopping campaigns and could be done in the API for the old PLA campaigns)? An example request from today: ?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/v201409; soapenv:mustUnderstand=0 ns1:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201409; operations operatorADD/operator operand adGroupId19190905510/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905390/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905270/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905150/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905030/adGroupId criterion id30001/id /criterion bidModifier1.25/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 10-20-14 15:48:08,472 [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/v201409; requestId000505e0d4e0e1500ab68045b8004eee/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime61/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[4].operand.criterion; trigger:'SHOPPING']/faultstring detail ApiExceptionFault xmlns= https://adwords.google.com/api/adwords/cm/v201409; message[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi, Anash. I switched over to the new v201409 API that was just recently released, using the latest Java API library. It still doesn't work. It now gives a reasonable exception, rather than just the generic fault occurred while processing error. However, you had said on Sep 24 that the fix that should be going live was that we'd be able to set these bid modifiers on ad groups in shopping campaigns now (as can be done in the UI for shopping campaigns and could be done in the API for the old PLA campaigns)? An example request from today: ?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/v201409; soapenv:mustUnderstand=0 ns1:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201409; operations operatorADD/operator operand adGroupId19190905510/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905390/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905270/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905150/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId19190905030/adGroupId criterion id30001/id /criterion bidModifier1.25/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 10-20-14 15:48:08,472 [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/v201409; requestId000505e0d4e0e1500ab68045b8004eee/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime61/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[4].operand.criterion; trigger:'SHOPPING']/faultstring detail ApiExceptionFault xmlns=https://adwords.google.com/api/adwords/cm/v201409; message[OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[0].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[1].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[2].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @ operations[3].operand.criterion; trigger:'SHOPPING', OperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE @
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi Greg, I've been told that this will work from the next API version onwards, since we had to expose new exception types for this change, and that would require us to break the wsdls already published for previous versions. Cheers, Anash On Tuesday, October 7, 2014 7:07:18 PM UTC-4, GregT wrote: Hi again, Anash. It's been another couple weeks, and still the exact same error trying to send mobile bid modifiers on ad groups in shopping campaigns. A request id from today is 000504dd2f1afa710aecde062c00771c. Any word on this? Thanks again, Greg On Wednesday, September 24, 2014 3:07:48 PM UTC-5, GregT wrote: Hi, Anash. Just tried again right now, and still failing with the exact same error. Here's the SOAP log: ?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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted (AwApi-Java, AdWords-Axis/1.30.0, Common-Java/1.30.0, Axis/1.4, Java/1.7.0_67, maven)/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406 operations operatorADD/operator operand adGroupId18951418870/adGroupId criterion id30001/id /criterion bidModifier0.24997/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951418990/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419230/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419110/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419350/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 09-24-14 15:01:25,935 [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; requestId000503d525f5ea810ac400a1c5002081/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime77/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault occurred while processing./faultstring /soap:Fault /soap:Body /soap:Envelope This is against a test AdWords account, if that makes any difference. Thanks, Greg On Wednesday, September 24, 2014 8:55:10 AM UTC-5, Anash P. Oommen (AdWords API Team) wrote: Hi Greg, The team told me that the fix is live, so you should be able to set bid modifiers on shopping adgroups now. Let me know if the request is still failing for you, and please provide a requestId from a failed request if possible. Cheers, Anash P. Oommen, AdWords API Advisor. On Tuesday, September 23, 2014 12:10:44 PM UTC-4, GregT wrote: Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have changed -- we are still getting the same error as originally. Any update on this? Thanks, Greg On Monday, September
Re: ad group mobile bid modifiers in shopping campaigns not working
Okay, thanks! Greg On Wednesday, October 8, 2014 9:55:53 AM UTC-5, Anash P. Oommen (AdWords API Team) wrote: Hi Greg, I've been told that this will work from the next API version onwards, since we had to expose new exception types for this change, and that would require us to break the wsdls already published for previous versions. Cheers, Anash On Tuesday, October 7, 2014 7:07:18 PM UTC-4, GregT wrote: Hi again, Anash. It's been another couple weeks, and still the exact same error trying to send mobile bid modifiers on ad groups in shopping campaigns. A request id from today is 000504dd2f1afa710aecde062c00771c. Any word on this? Thanks again, Greg On Wednesday, September 24, 2014 3:07:48 PM UTC-5, GregT wrote: Hi, Anash. Just tried again right now, and still failing with the exact same error. Here's the SOAP log: ?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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted (AwApi-Java, AdWords-Axis/1.30.0, Common-Java/1.30.0, Axis/1.4, Java/1.7.0_67, maven)/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406 operations operatorADD/operator operand adGroupId18951418870/adGroupId criterion id30001/id /criterion bidModifier0.24997/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951418990/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419230/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419110/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419350/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 09-24-14 15:01:25,935 [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; requestId000503d525f5ea810ac400a1c5002081/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime77/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault occurred while processing./faultstring /soap:Fault /soap:Body /soap:Envelope This is against a test AdWords account, if that makes any difference. Thanks, Greg On Wednesday, September 24, 2014 8:55:10 AM UTC-5, Anash P. Oommen (AdWords API Team) wrote: Hi Greg, The team told me that the fix is live, so you should be able to set bid modifiers on shopping adgroups now. Let me know if the request is still failing for you, and please provide a requestId from a failed request if possible. Cheers, Anash P. Oommen, AdWords API Advisor. On Tuesday, September 23, 2014 12:10:44 PM UTC-4, GregT wrote: Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi again, Anash. It's been another couple weeks, and still the exact same error trying to send mobile bid modifiers on ad groups in shopping campaigns. A request id from today is 000504dd2f1afa710aecde062c00771c. Any word on this? Thanks again, Greg On Wednesday, September 24, 2014 3:07:48 PM UTC-5, GregT wrote: Hi, Anash. Just tried again right now, and still failing with the exact same error. Here's the SOAP log: ?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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted (AwApi-Java, AdWords-Axis/1.30.0, Common-Java/1.30.0, Axis/1.4, Java/1.7.0_67, maven)/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18951418870/adGroupId criterion id30001/id /criterion bidModifier0.24997/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951418990/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419230/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419110/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419350/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 09-24-14 15:01:25,935 [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; requestId000503d525f5ea810ac400a1c5002081/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime77/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault occurred while processing./faultstring /soap:Fault /soap:Body /soap:Envelope This is against a test AdWords account, if that makes any difference. Thanks, Greg On Wednesday, September 24, 2014 8:55:10 AM UTC-5, Anash P. Oommen (AdWords API Team) wrote: Hi Greg, The team told me that the fix is live, so you should be able to set bid modifiers on shopping adgroups now. Let me know if the request is still failing for you, and please provide a requestId from a failed request if possible. Cheers, Anash P. Oommen, AdWords API Advisor. On Tuesday, September 23, 2014 12:10:44 PM UTC-4, GregT wrote: Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have changed -- we are still getting the same error as originally. Any update on this? Thanks, Greg On Monday, September 15, 2014 12:07:10 PM UTC-5, 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
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi Greg, The team told me that the fix is live, so you should be able to set bid modifiers on shopping adgroups now. Let me know if the request is still failing for you, and please provide a requestId from a failed request if possible. Cheers, Anash P. Oommen, AdWords API Advisor. On Tuesday, September 23, 2014 12:10:44 PM UTC-4, GregT wrote: Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have changed -- we are still getting the same error as originally. Any update on this? Thanks, Greg On Monday, September 15, 2014 12:07:10 PM UTC-5, 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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi, Anash. Just tried again right now, and still failing with the exact same error. Here's the SOAP log: ?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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted (AwApi-Java, AdWords-Axis/1.30.0, Common-Java/1.30.0, Axis/1.4, Java/1.7.0_67, maven)/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18951418870/adGroupId criterion id30001/id /criterion bidModifier0.24997/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951418990/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419230/adGroupId criterion id30001/id /criterion bidModifier2.5/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419110/adGroupId criterion id30001/id /criterion bidModifier0.48616/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18951419350/adGroupId criterion id30001/id /criterion bidModifier0.548885077186964/bidModifier /operand /operations /mutate /soapenv:Body /soapenv:Envelope 09-24-14 15:01:25,935 [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; requestId000503d525f5ea810ac400a1c5002081/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations5/operations responseTime77/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault occurred while processing./faultstring /soap:Fault /soap:Body /soap:Envelope This is against a test AdWords account, if that makes any difference. Thanks, Greg On Wednesday, September 24, 2014 8:55:10 AM UTC-5, Anash P. Oommen (AdWords API Team) wrote: Hi Greg, The team told me that the fix is live, so you should be able to set bid modifiers on shopping adgroups now. Let me know if the request is still failing for you, and please provide a requestId from a failed request if possible. Cheers, Anash P. Oommen, AdWords API Advisor. On Tuesday, September 23, 2014 12:10:44 PM UTC-4, GregT wrote: Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have changed -- we are still getting the same error as originally. Any update on this? Thanks, Greg On Monday, September 15, 2014 12:07:10 PM UTC-5, 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
Re: ad group mobile bid modifiers in shopping campaigns not working
Hi again, Anash. It's been another week (so, two weeks after you said to let you know if the issue still happens after a few days), and nothing appears to have changed -- we are still getting the same error as originally. Any update on this? Thanks, Greg On Monday, September 15, 2014 12:07:10 PM UTC-5, 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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion
Re: ad group mobile bid modifiers in shopping campaigns not working
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 operatorSET/operator operand xsi:type=BiddableAdGroupCriterion adGroupId13720172339/adGroupId criterion xsi:type=ProductPartition id98413046219/id /criterion userStatusACTIVE/userStatus biddingStrategyConfiguration bids xsi:type=CpcBid bid microAmount34/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; requestId000503400eff45500aece7e888004712/requestId serviceNameAdGroupCriterionService/serviceName methodNamemutate/methodName operations0/operations responseTime429/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap: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.TypeApiException/ApplicationException.Type errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=OperationAccessDenied fieldPathoperations[0].operand.userStatus/fieldPath triggerSHOPPING/trigger errorStringOperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE/errorString ApiError.TypeOperationAccessDenied/ApiError.Type reasonOPERATION_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
Re: ad group mobile bid modifiers in shopping campaigns not working
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 operatorSET/operator operand xsi:type=BiddableAdGroupCriterion adGroupId13720172339/adGroupId criterion xsi:type=ProductPartition id98413046219/id /criterion userStatusACTIVE/userStatus biddingStrategyConfiguration bids xsi:type=CpcBid bid microAmount34/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 requestId000503400eff45500aece7e888004712/requestId serviceNameAdGroupCriterionService/serviceName methodNamemutate/methodName operations0/operations responseTime429/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap: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.TypeApiException/ApplicationException.Type errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=OperationAccessDenied fieldPathoperations[0].operand.userStatus/fieldPath triggerSHOPPING/trigger errorStringOperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE/errorString ApiError.TypeOperationAccessDenied/ApiError.Type reasonOPERATION_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?
Re: ad group mobile bid modifiers in shopping campaigns not working
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 operatorSET/operator operand xsi:type=BiddableAdGroupCriterion adGroupId13720172339/adGroupId criterion xsi:type=ProductPartition id98413046219/id /criterion userStatusACTIVE/userStatus biddingStrategyConfiguration bids xsi:type=CpcBid bid microAmount34/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; requestId000503400eff45500aece7e888004712/requestId serviceNameAdGroupCriterionService/serviceName methodNamemutate/methodName operations0/operations responseTime429/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap: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.TypeApiException/ApplicationException.Type errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=OperationAccessDenied fieldPathoperations[0].operand.userStatus/fieldPath triggerSHOPPING/trigger errorStringOperationAccessDenied.OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE/errorString ApiError.TypeOperationAccessDenied/ApiError.Type reasonOPERATION_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:
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName
Re: ad group mobile bid modifiers in shopping campaigns not working
Great - thanks a lot, Anash! 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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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;
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault occurred while processing./faultstring /soap:Fault /soap:Body
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns= https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault 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/
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406 operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault 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 adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406 operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault 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 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
Re: ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault 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 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. For more options, visit https://groups.google.com/d/optout.
ad group mobile bid modifiers in shopping campaigns not working
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:clientCustomerIdredacted/ns1:clientCustomerId ns1:developerTokenredacted/ns1:developerToken ns1:userAgentredacted/ns1:userAgent ns1:validateOnlyfalse/ns1:validateOnly ns1:partialFailurefalse/ns1:partialFailure /ns1:RequestHeader /soapenv:Header soapenv:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201406; operations operatorADD/operator operand adGroupId18347850910/adGroupId criterion id30001/id /criterion bidModifier0.49994/bidModifier /operand /operations operations operatorADD/operator operand adGroupId18347851030/adGroupId criterion id30001/id /criterion bidModifier0.49994/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; requestId000500762a915dc00a8076c81c009ef5/requestId serviceNameAdGroupBidModifierService/serviceName methodNamemutate/methodName operations2/operations responseTime114/responseTime /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstringFault 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 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. For more options, visit https://groups.google.com/d/optout.
