Hi, Any updates or ETA?
Thanks Ashley On Thursday, October 1, 2015 at 4:25:43 PM UTC-7, Ashley Xu wrote: > > Ok, thank you! Please keep me updated > > On Thursday, October 1, 2015 at 9:58:09 AM UTC-7, Nadine Sundquist > (AdWords API Team) wrote: >> >> Hi Ashley, >> >> Thanks for the update about you upgrading to a newer version. This one >> seems to be a tricky one to resolve. We're still working on trying to find >> the root cause. >> >> Regards, >> Nadine, AdWords API Team >> >> On Thursday, October 1, 2015 at 12:31:30 PM UTC-4, Ashley Xu wrote: >>> >>> We have upgraded to the recommended SDK. Still it does not help. We have >>> reported to you about this issue a month ago, provided you with the full >>> soap request\response and tried out what you recommended, but to no avail. >>> Please treat this as a high priority. And let us know what is the root >>> cause and what we can try next asap. >>> >>> Thanks >>> Ashley >>> On Friday, September 18, 2015 at 5:05:31 PM UTC-7, Nadine Sundquist >>> (AdWords API Team) wrote: >>>> >>>> Hi Ashley, >>>> >>>> I just checked on the thread that Thanet started about this issue. They >>>> haven't been able to figure it out, yet. >>>> >>>> Regards, >>>> Nadine, AdWords API Team >>>> >>>> On Friday, September 18, 2015 at 4:20:38 PM UTC-4, Ashley Xu wrote: >>>>> >>>>> Hi Thanet, >>>>> >>>>> Any update? The issue is still happening. We are in the progress of >>>>> uploading the v201506. But still it'll be good to know the root cause. >>>>> >>>>> Thanks >>>>> Ashley >>>>> >>>>> On Thursday, September 10, 2015 at 11:39:42 PM UTC-7, Thanet Knack >>>>> Praneenararat (AdWords API Team) wrote: >>>>>> >>>>>> Hi Ashley, >>>>>> >>>>>> I'm investigating this issue and will let you know once I have any >>>>>> update. >>>>>> Have you also tried v201506 and add your client customer ID in your >>>>>> header? >>>>>> >>>>>> Cheers, >>>>>> Thanet, AdWords API Team >>>>>> >>>>>> On Friday, September 11, 2015 at 7:48:54 AM UTC+9, Ashley Xu wrote: >>>>>>> >>>>>>> I've replied to your email with the information. Could you please >>>>>>> take a look? >>>>>>> >>>>>>> Thanks >>>>>>> Ashley >>>>>>> >>>>>>> On Wednesday, September 9, 2015 at 8:14:30 PM UTC-7, Thanet Knack >>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>> >>>>>>>> Hi Ashley, >>>>>>>> >>>>>>>> I've replied to your email yesterday. Could you please check your >>>>>>>> inbox again? >>>>>>>> >>>>>>>> What I've said in the email is that it seems your log a bit too old >>>>>>>> so we can't track back to see what happened. >>>>>>>> >>>>>>>> Could you please: >>>>>>>> >>>>>>>> 1. Send a recent one ? >>>>>>>> 2. Try v201506? >>>>>>>> 3. Add your client customer ID? (I know that it's written that >>>>>>>> the client customer ID is not needed but to investigate the >>>>>>>> problem, this >>>>>>>> may help us.) >>>>>>>> >>>>>>>> By the way, I still don't get your use case much about using this >>>>>>>> service to get client customer ID. >>>>>>>> If possible, could you please also give your code snippets and >>>>>>>> explain more? >>>>>>>> >>>>>>>> Best, >>>>>>>> Thanet, AdWords API Team >>>>>>>> >>>>>>>> On Thursday, September 10, 2015 at 10:36:41 AM UTC+9, Ashley Xu >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hi Thanet, >>>>>>>>> >>>>>>>>> Did you get my private reply? Please help investigate on your >>>>>>>>> earliest convenience. Our availability has been impacted for a long >>>>>>>>> time >>>>>>>>> now. This is one example request id 00051e629b8f3bc80a4c992354005dfb. >>>>>>>>> The >>>>>>>>> full soap request/response is already attached. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Ashley >>>>>>>>> >>>>>>>>> On Tuesday, September 8, 2015 at 5:15:05 PM UTC-7, Ashley Xu wrote: >>>>>>>>>> >>>>>>>>>> I've included the soap request/response and the class/method from >>>>>>>>>> adwords api client we use in private mode. >>>>>>>>>> >>>>>>>>>> On Tuesday, September 8, 2015 at 10:44:01 AM UTC-7, Thanet Knack >>>>>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> Could you please provide more information how you use the >>>>>>>>>>> service? >>>>>>>>>>> Any SOAP logs or code snippets would help much. >>>>>>>>>>> Please reply by clicking *Reply privately to author* on the top >>>>>>>>>>> right button of my comment. >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Thanet, AdWords API Team >>>>>>>>>>> >>>>>>>>>>> On Tuesday, September 8, 2015 at 9:17:59 PM UTC+9, >>>>>>>>>>> jxx...@hotmail.com wrote: >>>>>>>>>>>> >>>>>>>>>>>> Thanks Thanet for looking into it. I'm working with Ashley. And >>>>>>>>>>>> we've been use this way to get customer id for a long time and >>>>>>>>>>>> just >>>>>>>>>>>> recently that we noticed that we got UnKnownException from Adwards >>>>>>>>>>>> for this >>>>>>>>>>>> call. Nothing was changed on our end. So can you please help check >>>>>>>>>>>> why we >>>>>>>>>>>> are getting UnknownException. BTW, not all the request failed. >>>>>>>>>>>> Actually >>>>>>>>>>>> only 2% of the requests got UnknownException error. Thanks a lot >>>>>>>>>>>> for your >>>>>>>>>>>> help! >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Tuesday, September 1, 2015 at 1:35:38 AM UTC-7, Thanet Knack >>>>>>>>>>>> Praneenararat (AdWords API Team) wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Ashley, >>>>>>>>>>>>> >>>>>>>>>>>>> Could you please tell me more about your use case? >>>>>>>>>>>>> It's true that you don't need to pass arguments to use >>>>>>>>>>>>> CustomerService, but that's because the default, which is the ID >>>>>>>>>>>>> of >>>>>>>>>>>>> authenticated account, is always returned. >>>>>>>>>>>>> If you want to get information of your child accounts, you >>>>>>>>>>>>> need to specify a *clientCustomerId* when authenticating as >>>>>>>>>>>>> an MCC to obtain such information. >>>>>>>>>>>>> >>>>>>>>>>>>> In other words, CustomerService is designed to give you >>>>>>>>>>>>> customer information, e.g., currency code, date time zone, >>>>>>>>>>>>> *not* the *clientCustomerId* itself (though the ID is also >>>>>>>>>>>>> returned with other information). >>>>>>>>>>>>> If you don't know the clientCustomerId at first and that >>>>>>>>>>>>> account is not managed under your MCC account, I don't think you >>>>>>>>>>>>> can get >>>>>>>>>>>>> information using CustomerService. >>>>>>>>>>>>> >>>>>>>>>>>>> Best, >>>>>>>>>>>>> Thanet, AdWords API Team >>>>>>>>>>>>> >>>>>>>>>>>>> On Saturday, August 29, 2015 at 8:31:45 AM UTC+9, Ashley Xu >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> We are calling CustomerService to get the customer Id, we >>>>>>>>>>>>>> don't have that on our side. Also according to your >>>>>>>>>>>>>> documentation about >>>>>>>>>>>>>> Customer Service-'It has a get method that *takes no >>>>>>>>>>>>>> arguments* and returns a Customer record containing fields >>>>>>>>>>>>>> such as customerI' It suggests that when calling Customer >>>>>>>>>>>>>> Service, we don't need to pass you any argument. >>>>>>>>>>>>>> >>>>>>>>>>>>>> clientCustomerID is used to obtain info for a specific >>>>>>>>>>>>>> account. We failed before we even reach that step. >>>>>>>>>>>>>> >>>>>>>>>>>>>> For us, it's first call CustomerService to get customer id. >>>>>>>>>>>>>> Then call ManagedCustomerService to get account info. We failed >>>>>>>>>>>>>> at the >>>>>>>>>>>>>> first step. So I don't think it's because we didn't pass in >>>>>>>>>>>>>> clientCustomerId. Just in case, we tried importing from a MCC >>>>>>>>>>>>>> user in our >>>>>>>>>>>>>> production environment, it succeeded. >>>>>>>>>>>>>> >>>>>>>>>>>>>> From the SOAP response, there's a request ID, can we use it >>>>>>>>>>>>>> to nail down to the exact error? That'll help a lot. Thank you! >>>>>>>>>>>>>> >>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>> Ashley >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, August 28, 2015 at 2:09:25 PM UTC-7, Anthony >>>>>>>>>>>>>> Madrigal wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> HI Ashley, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Are you using your MCC account to make this request or a >>>>>>>>>>>>>>> client account? If it is an MCC account, you will need to >>>>>>>>>>>>>>> specify the *clientCustomerId. >>>>>>>>>>>>>>> *Here are more details on the CustomerService >>>>>>>>>>>>>>> <https://developers.google.com/adwords/api/docs/guides/managing-accounts#customerservice> >>>>>>>>>>>>>>> . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I also noticed you are using v201502. I suggest updating >>>>>>>>>>>>>>> your client library to v201506 >>>>>>>>>>>>>>> <https://developers.google.com/adwords/api/docs/clientlibraries> >>>>>>>>>>>>>>> . >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>> Anthony >>>>>>>>>>>>>>> AdWords API Team >>>>>>>>>>>>>>> >>>>>>>>>>>>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/5c9844bb-c0bc-44d9-96b8-ad34534ff894%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
