Re: .Net Client Library location targeting not work properly on v201109
This is working for production but not the sandbox: Request: soap:HeaderSANITIZED/soap:Header soap:Body mutate xmlns=https://adwords.google.com/api/adwords/cm/v201109; operations operatorADD/operator operand campaignIdSANITIZED/campaignId criterion xsi:type=Location id2840/id /criterion /operand /operations /mutate /soap:Body /soap:Envelope Response: soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Header ResponseHeader xmlns=https://adwords.google.com/api/adwords/cm/ v201109 requestIdSANITIZED/requestId serviceNameCampaignCriterionService/serviceName methodNamemutate/methodName operations1/operations responseTime86/responseTime units1/units /ResponseHeader /soap:Header soap:Body soap:Fault faultcodesoap:Server/faultcode faultstring[CriterionError.INVALID_CRITERION_ID @ operations[0].operand.criterion; trigger:'2840']/faultstring detail ApiExceptionFault xmlns=https://adwords.google.com/api/adwords/ cm/v201109 message[CriterionError.INVALID_CRITERION_ID @ operations[0].operand.criterion; trigger:'2840']/message ApplicationException.TypeApiException/ ApplicationException.Type errors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=CriterionError fieldPathoperations[0].operand.criterion/fieldPath trigger2840/trigger errorStringCriterionError.INVALID_CRITERION_ID/errorString ApiError.TypeCriterionError/ApiError.Type reasonINVALID_CRITERION_ID/reason /errors /ApiExceptionFault /detail /soap:Fault /soap:Body /soap:Envelope -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
Hi Kevin, That might be a different issue. Here we are using location's criteriaIds listed on the documentation page and sandbox rejected them when we try to target them to a campaign. -Kevin -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
Hi Kevin, Unfortunately, they are both known issues. 1. LocationCriterionService returns fake results that do not work with CampaignCriterionService. 2. Production CriterionIds do not work in sandbox. Ideally, the two services would at least agree, and possibly we can make the production values also work. I'm working with the core engineers to try to get an answer for this. - Kevin Winter AdWords API team -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
We are having the same issue on our custom client using .Net. This is blocking our upgrade process. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
Could we get a reply from AdWords team? When should we expect to get this fix? We couldn't migrate to the latest version without doing any testing on the Sandbox. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
I'm getting a similar error as well. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
Re: .Net Client Library location targeting not work properly on v201109
I'm getting a similar error when using java client library. -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
.Net Client Library location targeting not work properly on v201109
Hi group, i am using .net client library v201109. i try to execute the AddCampaignTargetingCriteria.cs example with sandbox settings but service returned Invalid_Criterion_Id error. Response and request details are below. i tried the example with different country,province criterion id but result was the same. Can somebody help me how to add location target criteria (Country,province etc) to the campaign using v201109 version of client library? What is wrong in the example? Request --- ?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;!--POST /api/adwords/cm/ v201109/CampaignCriterionService User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.5448) VsDebuggerCausalityData: uIDPo6S0/HZ5qC5FlM/ l6mBUMBQApggbRcoVxUazd0KK8v2NvGZZ1nYsXM9Esc21ceVTjGoACQAA Content-Type: text/xml; charset=utf-8 SOAPAction: Host: adwords-sandbox.google.com Content-Length: 1421 TimeStamp: Wed, 02 Nov 2011 18:45:24 GMT --soap:HeaderRequestHeader xmlns=https://adwords.google.com/api/ adwords/cm/v201109authToken xmlns=https://adwords.google.com/api/ adwords/cm/v201109**/authTokendeveloperToken xmlns=https:// adwords.google.com/api/adwords/cm/v201109**/ developerTokenclientCustomerId xmlns=https://adwords.google.com/api/ adwords/cm/v2011099502046938/clientCustomerIduserAgent xmlns=https://adwords.google.com/api/adwords/cm/v201109;AwApi- DotNet-13.0.0|VisilabsAdManager/userAgent/RequestHeader/ soap:Headersoap:Bodymutate xmlns=https://adwords.google.com/api/ adwords/cm/v201109operationsoperatorADD/ operatoroperandcampaignId433463/campaignIdcriterion xsi:type=Locationid2840/id/criterion/operand/ operationsoperationsoperatorADD/ operatoroperandcampaignId433463/campaignIdcriterion xsi:type=Locationid2392/id/criterion/operand/operations/ mutate/soap:Body/soap:Envelope Response soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/ envelope/!--X-Content-Type-Options: nosniff X-Frame-Options: SAMEORIGIN X-XSS-Protection: 1; mode=block Transfer-Encoding: chunked Cache-Control: private, max-age=0 Content-Type: text/xml; charset=UTF-8 Date: Wed, 02 Nov 2011 16:45:27 GMT Expires: Wed, 02 Nov 2011 16:45:27 GMT Server: GSE TimeStamp: Wed, 02 Nov 2011 18:45:24 GMT --soap:HeaderResponseHeader xmlns=https://adwords.google.com/api/ adwords/cm/v201109requestId0004b0c332fa8db80a0ce912732c/ requestIdserviceNameCampaignCriterionService/ serviceNamemethodNamemutate/methodNameoperations2/ operationsresponseTime197/responseTimeunits2/units/ ResponseHeader/ soap:Headersoap:Bodysoap:Faultfaultcodesoap:Server/ faultcodefaultstring[CriterionError.INVALID_CRITERION_ID @ operations[0].operand.criterion; trigger:'2840', CriterionError.INVALID_CRITERION_ID @ operations[1].operand.criterion; trigger:'2392']/faultstringdetailApiExceptionFault xmlns=https:// adwords.google.com/api/adwords/cm/ v201109message[CriterionError.INVALID_CRITERION_ID @ operations[0].operand.criterion; trigger:'2840', CriterionError.INVALID_CRITERION_ID @ operations[1].operand.criterion; trigger:'2392']/messageApplicationException.TypeApiException/ ApplicationException.Typeerrors xmlns:xsi=http://www.w3.org/2001/ XMLSchema-instance xsi:type=CriterionErrorfieldPathoperations[0].operand.criterion/ fieldPathtrigger2840/ triggererrorStringCriterionError.INVALID_CRITERION_ID/ errorStringApiError.TypeCriterionError/ ApiError.TypereasonINVALID_CRITERION_ID/reason/errorserrors xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:type=CriterionErrorfieldPathoperations[1].operand.criterion/ fieldPathtrigger2392/ triggererrorStringCriterionError.INVALID_CRITERION_ID/ errorStringApiError.TypeCriterionError/ ApiError.TypereasonINVALID_CRITERION_ID/reason/errors/ ApiExceptionFault/detail/soap:Fault/soap:Body/soap:Envelope -END API CALL--- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups AdWords API Forum group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
