Re: How can I get YouTube video's file name?

Hello Tanabe, I'll check with Engineering and get back to you soon. Best, Thanet, AdWords API Team On Tuesday, January 29, 2019 at 9:41:59 PM UTC+9, Yoshimasa Tanabe wrote: > > Hi, > > Is there any way to get YouTube video's original file name(like foo.mp4) > the user uploaded? > > I referred

Re: Creating new Smart Display Campaign under test account is not possible.

Hello, Unfortunately, no updates yet. I'm following this issue. Best, Thanet, AdWords API Team On Tuesday, January 15, 2019 at 10:45:52 AM UTC+9, adsense...@bykd.com wrote: > > Hello, > > do you have any update regarding this case? > > Thank you. > > On Friday, January 11, 2019 at 5:13:38 AM UT

Re: Creating new Smart Display Campaign under test account is not possible.

Hello, Let me confirm this requirement with Engineering and get back to you. Best, Thanet, AdWords API Team On Thursday, January 10, 2019 at 3:28:38 AM UTC+9, adsense...@bykd.com wrote: > > Hello, > > I'm trying to create new Smart Display Campaign under test account. I set > channel type to D

Re: Update CrmBasedUserList Name and Description

Hello Zied, I'm confirming this with Engineering. With recent changes in user list policy, it might affect the user list in the test accounts too. I'll update this thread once I have more info. Best, Thanet, AdWords API Team On Tuesday, November 27, 2018 at 1:23:28 AM UTC+9, Zied Chaari wrote:

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

Hello Alex, Sorry for the late reply. I've confirmed that, by the Customer Match policy update , all accounts need to get whitelisted first before using the customer match ( *CrmBasedUserList*). So, in case you own the ac

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

Hello Alex, I'm in the middle of conversation with Engineering. Please hang in there. :) Best, Thanet, AdWords API Team On Friday, November 2, 2018 at 5:19:33 AM UTC+9, a...@zaius.com wrote: > > Hi Thanet, > > Checking to see if there's been an investigation into this. Thanks! > -- -- =~=~=~=

Re: Error message not in manual

Hello everyone, Due to the recent update of policy of Customer Match, your request for mutating CrmBasedUserList will fail if the advertiser account hasn't been whitelisted for using the feature. If you own the account

Re: Update the status of a CrmBasedUserList from Closed to Open

Hello Greg, We're investigating this and will get back to you soon when I hear any news. Best, Thanet, AdWords API Team On Saturday, October 27, 2018 at 7:11:13 AM UTC+9, GregT wrote: > > I've replied privately to you, Dannison. > > FYI, > Greg > > On Thursday, October 25, 2018 at 11:27:44 AM UT

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

Hello, I'm not 100% sure if that is related to this issue or not. Could you please open a new thread with your details so our team can help separately? Thanks. Best, Thanet On Saturday, October 27, 2018 at 8:17:46 AM UTC+9, a...@audigent.com wrote: > > We're having the same issue. Many of our a

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

Hello Alex, Thanks for reporting this. I'm passing this information to engineering and we'll update this thread as soon as possible. Best, Thanet, AdWords API Team On Friday, October 26, 2018 at 2:45:24 AM UTC+9, a...@zaius.com wrote: > > For reference, here's the SOAP request/response I sent t

Re: Change of Error Types When Attaching Bidding Strategies

Hello Dorian, I've got confirmation that, going forward, the error message for such a scenario is now *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE* instead. Best, Thanet, AdWords API Team On Monday, July 30, 2018 at 5:48:00 PM UTC+9, Dorian Kind wrote: > > Hi, > > we run daily integration test fo

Re: Shopping Performance Report returns same product twice

Hello Ad Ja, Unfortunately, this doesn't look like very high priority for engineering at this moment. So, there is no progress on this right now. Also, do you know any other way of getting a report where it returns > products with the most recent information? As far as I know, we cannot get th

Re: Google Ads API beta { "authorizationError": "DEVELOPER_TOKEN_NOT_WHITELISTED" }

Hello KDJ, Sorry for the delay. I'm chasing this matter for you. Could you please tell us your client customer ID you've filled in by *Replying privately to author*? Best, Thanet, AdWords API Team On Wednesday, July 11, 2018 at 4:54:07 AM UTC+9, rentcafe dev wrote: > > Luis, > > It's been over

Re: ProductType dimension difference between a shooping campaign and a display campaign with GMC feed

Hi Jianbo, Engineering has confirmed that it's a legacy product dimension, that are not designed to be used right now. It exists for backward support of some old types of campaigns. So, I'd suggest using other product dimensions instead of this one. Best, Thanet, AdWords API Team On Friday, Jul

Re: ProductType dimension difference between a shooping campaign and a display campaign with GMC feed

Hello Jianbo, Unfortunately, I haven't heard from the engineering yet. I'm following this up and will inform you once I have more info. Best, Thanet, AdWords API Team On Friday, July 6, 2018 at 3:13:49 AM UTC+9, Jianbo zhu wrote: > > Soft ping :) thanks. > > Thanks, > Jianbo > On Monday, June 2

Re: ProductType dimension difference between a shooping campaign and a display campaign with GMC feed

Hello Jianbo, I'm still waiting for the confirmation from engineering. Will update this thread when I have more information. Best, Thanet, AdWords API Team On Tuesday, June 26, 2018 at 2:13:27 AM UTC+9, Jianbo zhu wrote: > > Gentle ping, please let us know if there are any findings. thanks in >

Re: ProductType dimension difference between a shooping campaign and a display campaign with GMC feed

Hi Jianbo, I'll check for more detail on that. As far as I can find info on my side, the *ProductTypeFull *seems to be the legacy product dimension that existed before the roll-out of shopping campaigns. You can find some info here

Re: Some campaigns not retrieved by API

Hello Arthur, It turned out that your campaigns in question belong to the sub-type that are supported through the UI only. That's why you cannot retrieve them via AdWords API SOAP services and reporting. Best, Thanet, AdWords API Team On Tuesday, May 8, 2018 at 5:13:36 AM UTC+9, Arthur Balduin

Re: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 16383: unexpected end of data

Hi Christos, We can't reproduce your issue on our end, using both Python 2 and 3, so it doesn't look like this is an issue on AdWords API server. I'll ask the Python library owner to continue following up on GitHub. Best, Thanet, AdWords API Team On Friday, May 4, 2018 at 7:20:43 PM UTC+9, chri