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

2019-01-30 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 the API doc[1] and found the following fields look like related.
>
> * sourceUrl: The URL of where the original media was downloaded from (or a 
> file name).
> * name: The name of the media. The name can be used by clients to help 
> identify previously uploaded media.
>
> But I get the Video object has the empty sourceUrl and the name is 
> Video(YouTube) title, not the file name.
>
>
> {
>   name=,
>   sourceUrl=, // empty
>   // other fields
>   ...
> }
>
>
> Am I missing something?
>
> ...
>
> Code snippet is here(Scala).
>
> * "com.google.api-ads" % "ads-lib"  % 4.1.0
> * "com.google.api-ads" % "adwords-axis" % 4.1.0
>
> import com.google.api.ads.adwords.axis.factory.AdWordsServices
> import com.google.api.ads.adwords.axis.utils.v201806.SelectorBuilder
> import com.google.api.ads.adwords.axis.v201806.cm.MediaServiceInterface
> import com.google.api.ads.adwords.lib.client.AdWordsSession
> import com.google.api.ads.adwords.lib.selectorfields.v201806.cm.MediaField
>
>
> val mediaServiceSelector = new SelectorBuilder()
>   .fields(
> MediaField.MediaId,
> MediaField.YouTubeVideoIdString,
> MediaField.Name,
> MediaField.SourceUrl,
> MediaField.StreamingUrl
>   )
>   .in(MediaField.Type, "VIDEO")
>   .build()
>
>
> val session = new AdWordsSession.Builder()
>   .withOAuth2Credential()
>   .withDeveloperToken()
>   .withClientCustomerId()
>   .build()
>
>
> AdWordsServices.getInstance()
>   .get(session, classOf[MediaServiceInterface])
>   .get(mediaServiceSelector)
>
>
> [1] 
> https://developers.google.com/adwords/api/docs/reference/v201806/MediaService.Video
> [2] https://developers.google.com/youtube/v3/docs/videos#header_2
>
> ---
>
> Yoshimasa
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6a183c30-278d-4f8d-8314-71eb925026e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2019-01-14 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 UTC+1, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> 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, adsen...@bykd.com 
>> wrote:
>>>
>>> Hello,
>>>
>>> I'm trying to create new Smart Display Campaign under test account. I 
>>> set channel type to DISPLAY and channel sub-type to DISPLAY_SMART_CAMPAIGN 
>>> based on official guide
>>>
>>> https://developers.google.com/adwords/api/docs/guides/smart-display-campaigns
>>>
>>> When I call API and try to create this campaign I get following error:
>>> [OperationAccessDenied.ADD_OPERATION_NOT_PERMITTED @ 
>>> operations[0].operand.advertisingChannelSubType; 
>>> trigger:'DISPLAY_SMART_CAMPAIGN']
>>>
>>> I know that requirement for using Smart Display Campaign is to have at 
>>> least 50 conversion for last 30 days. 
>>> Does this requirement apply also to test account? How is it possible to 
>>> create such  campaign under test account?
>>>
>>> Thank you in advance.
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/6f8b4503-056c-462b-b433-c4997fa23f37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2019-01-10 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 DISPLAY and channel sub-type to DISPLAY_SMART_CAMPAIGN 
> based on official guide
>
> https://developers.google.com/adwords/api/docs/guides/smart-display-campaigns
>
> When I call API and try to create this campaign I get following error:
> [OperationAccessDenied.ADD_OPERATION_NOT_PERMITTED @ 
> operations[0].operand.advertisingChannelSubType; 
> trigger:'DISPLAY_SMART_CAMPAIGN']
>
> I know that requirement for using Smart Display Campaign is to have at 
> least 50 conversion for last 30 days. 
> Does this requirement apply also to test account? How is it possible to 
> create such  campaign under test account?
>
> Thank you in advance.
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/47137ff8-4865-4dd7-8ce3-3ce6b6a97cab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update CrmBasedUserList Name and Description

2018-11-27 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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:
>
> Hi Luis,
>
> Always the same problem.
>
> *This is my code: (.Net)*
> UserList userList = new UserList()
> {
> id = long.Parse(SAudience.Social_ID),
> name = SAudience.Audience.Name,
> listType = UserListType.CRM_BASED
> };
>
> UserListOperation operation = new UserListOperation
> {
> operand = userList,
> @operator = Operator.SET
> };
>
> UserListReturnValue result = userListService.mutate(new UserListOperation[]
> {
> operation
> });
>
> *Request (I'm using a Test Account):*
> http://schemas.xmlsoap.org/soap/envelope/;>
> 
> https://adwords.google.com/api/adwords/rm/v201809;>
> https://adwords.google.com/api/adwords/cm/v201809
> ">7482331905
> https://adwords.google.com/api/adwords/cm/v201809
> ">x
> https://adwords.google.com/api/adwords/cm/v201809;>unknown 
> (AwApi-DotNet/24.1.0, Common-Dotnet/9.4.0, .NET CLR/4.0.30319.42000, 
> OAuthServiceAccountFlow, gzip)
> 
> 
> http://www.w3.org/2001/XMLSchema-instance; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema;>
> https://adwords.google.com/api/adwords/rm/v201809;>
> 
> https://adwords.google.com/api/adwords/cm/v201809;>SET
> 
> 736365788
> Audience Google 8 - Update
> CRM_BASED
> 
> 
> 
> 
> 
>
> *Response:*
> http://schemas.xmlsoap.org/soap/envelope/;>
> 
> https://adwords.google.com/api/adwords/rm/v201809; xmlns="
> https://adwords.google.com/api/adwords/cm/v201809;>
> 00057b93aa6536510a812f942709cc4f
> AdwordsUserListService
> mutate
> 1
> 190
> 
> 
> 
> 
> soap:Client
> [UserListError.USER_LIST_MUTATE_NOT_SUPPORTED @ 
> operations[0].operand]
> 
> https://adwords.google.com/api/adwords/cm/v201809; xmlns:ns2="
> https://adwords.google.com/api/adwords/rm/v201809;>
> [UserListError.USER_LIST_MUTATE_NOT_SUPPORTED 
> @ operations[0].operand]
> 
> ApiException
> http://www.w3.org/2001/XMLSchema-instance; xsi:type="ns2:UserListError">
> operations[0].operand
> 
> operations
> 0
> 
> 
> operand
> 
> 
> 
> UserListError.USER_LIST_MUTATE_NOT_SUPPORTED
> UserListError
> 
> USER_LIST_MUTATE_NOT_SUPPORTED
> 
> 
> 
> 
> 
> 
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a9a118da-542f-4600-a7cc-ed61ecbb847d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

2018-11-15 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 accounts, please contact your Google representative 
for whitelisting. 
If not, you would need to tell the owners of accounts that you want to 
create the Customer Match on to do so.

See this page  for 
whitelisting eligibility.

Best,
Thanet, AdWords API Team

On Thursday, November 15, 2018 at 5:08:33 AM UTC+9, a...@zaius.com wrote:
>
> Pinging this thread, as it's been awhile. This is continually affects a 
> large number of our user lists. Any word from engineering?
>
>
> On Friday, November 2, 2018 at 2:46:13 AM UTC-4, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> 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, al...@zaius.com wrote:
>>>
>>> Hi Thanet,
>>>
>>> Checking to see if there's been an investigation into this. Thanks!
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/422c6625-9840-4ace-a7ed-c21222f93b23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

2018-11-02 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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!
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/d9527e6f-e62c-493f-9d6f-2018be6fc602%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error message not in manual

2018-10-29 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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, you can contact your Google account representative 
to get your account whitelisted.
If the account belongs to your customers, they need to contact their Google 
representative for whitelisting.

Best,
Thanet, AdWords API Team

On Tuesday, October 30, 2018 at 8:36:32 AM UTC+9, Martin Power wrote:
>
> We are also getting this error when trying to create a CrmBasedUserList 
> via the Soap API.
>
> Any Ideas?
>
> On Wednesday, 24 October 2018 08:09:18 UTC+2, makot...@gmail.com wrote:
>>
>> Dear AdWords API Team,
>>
>> What does this error message mean?
>> 『ADVERTISER_NOT_WHITELISTED_FOR_USING_UPLOADED_DATA』
>>
>> Many Thanks,
>>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/042e3353-e944-4915-9411-631ae4522e20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2018-10-29 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 UTC-5, Dannison Yao (AdWords 
> API Team) wrote:
>>
>> Hi Greg,
>>
>> Could you provide the complete SOAP request and response logs when you 
>> encountered the error CANNOT_ADD_CLOSED_USER_LIST so I could investigate 
>> this further? I would need the logs for me to better assist you. You may 
>> send these to me via the *Reply privately to author* option. If you have 
>> not enabled logging, you may follow this guide 
>> 
>>  on 
>> how to do so.
>>
>> Regards,
>> Dannison
>> AdWords API Team
>>
>> On Wednesday, October 24, 2018 at 11:23:20 PM UTC+8, GregT wrote:
>>>
>>> Hi, Dannison.
>>>
>>> For our situation, there's not much to show in the way of SOAP logs. The 
>>> issue is that in our test account, all remarketing audiences get closed 
>>> quickly, making them unusable in tests (if you try to add them to an ad 
>>> group, you get a CriterionError.CANNOT_ADD_CLOSED_USER_LIST error). This 
>>> just started happening in the last couple weeks - these audiences in this 
>>> test account have existed, in an open membership status, for years before 
>>> then. If we look at the test account in the Google Ads UI, the UI shows 
>>> them all as closed, and if we (in the UI) change them back to Open, they 
>>> only stay open for an hour or less. If it'd be helpful to know the id of 
>>> our test account, I can email that to you.
>>>
>>> Thanks,
>>> Greg
>>>
>>> On Wednesday, October 24, 2018 at 1:24:12 AM UTC-5, Dannison Yao 
>>> (AdWords API Team) wrote:

 Hi Joana/Greg,

 The user list status should not be affected with the membershipLifeSpan 
 ,
  
 it has also nothing to do with low volume. Could you provide the complete 
 SOAP request and response logs that were generated when you were trying to 
 add a member in your user list so that I could investigate this further?

 Regards,
 Dannison
 AdWords API Team

 On Tuesday, October 23, 2018 at 7:44:49 PM UTC+8, Joana Esteves wrote:
>
> Hi Dannison,
>
> Thanks for coming back to me.
>
> I tried the code again, also in another audience that created after, 
> and it didn't work for any case.
> As we are using testing data, the audience size is < 100. Could be it 
> a reason why the audience sets to close, and also the lifespanmember 
> value 
> drops from 180 to 1?
>
> I appreciate that an OPEN status means that the list is still 
> populating members and can still be targeted, and if CLOSED, then the 
> list 
> is not being populated already and cannot be used for targeting anymore.
> So, I have a question: Why do lists automatically *Close*, without 
> our intervention, a little while after they are created? (Could it be due 
> to low volumes?)
>
> To clarify what we're trying to achieve, we need audiences to stay 
> *Open*, so we can keep adding recipients to them on a daily basis. 
> How can I grant that?
>
> Any help with this, greatly appreciated
>
> Thanks,
> Joana
>
> segunda-feira, 22 de Outubro de 2018 às 05:12:11 UTC+1, Dannison Yao 
> (AdWords API Team) escreveu:
>>
>> Hi Joana,
>>
>> Your code appears to be logically correct. If recent changes have 
>> been applied to your user list, it usually takes a while before it is 
>> reflected. Could you try running your code again and see if the changes 
>> have been reflected? If not, could you provide the complete SOAP request 
>> and response logs that were generated after setting the status to 
>> *OPEN* so I could investigate this further? You may send the 
>> requested information using the *Reply privately to author* option. 
>> If you have not enabled logging yet, you may follow this guide 
>> 
>>  on 
>> how to do so.
>>
>> According to this guide about the CrmBasedUserLIst.status 
>> ,
>>  
>> if the status is *OPEN*, the list is still populating members and 
>> can still be targeted. If it is set to *CLOSED*, then the list is 
>> not being populated already and cannot be used for targeting anymore. 
>> From 
>> your understanding, *client 1 *and *client 2* should be in the list, 
>> while *client 3* should not be in the list because it was

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

2018-10-29 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 audiences are showing up as 
> "Closed" in AdX.  We're curious if something has changed, and we can't 
> mutate them to status 'OPEN' because we're receiving this error when we try 
> to update.
>
> On Friday, October 26, 2018 at 2:54:39 AM UTC-4, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> 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, al...@zaius.com wrote:
>>>
>>> For reference, here's the SOAP request/response I sent to Peter:
>>>
>>> Request:
>>>
>>>  http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns0="
>>> https://adwords.google.com/api/adwords/cm/v201806; xmlns:wsdl="
>>> https://adwords.google.com/api/adwords/rm/v201806; xmlns:xsd="
>>> http://www.w3.org/2001/XMLSchema; xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance;>  <
>>> wsdl:RequestHeader xmlns="
>>> https://adwords.google.com/api/adwords/cm/v201806;> rails 
>>> (AwApi-Ruby/1.3.0, Common-Ruby/1.0.2, GoogleAdsSavon/1.0.3, ruby/2.2.10, 
>>> HTTPI/2.4.1, httpclient) REDACTED>> developerToken> ** >> wsdl:RequestHeader>   https://adwords.google.com/api/adwords/rm/v201806;>  <
>>> ns0:operator>ADD  **>> userListId>  ** >> membersList> >> env:Envelope>
>>>
>>>
>>> Response:
>>>
>>>  http://schemas.xmlsoap.org/soap/envelope/;>  <
>>> ns2:ResponseHeader xmlns:ns2="
>>> https://adwords.google.com/api/adwords/rm/v201806; xmlns="
>>> https://adwords.google.com/api/adwords/cm/v201806;> 
>>> 0005791104dbdce00a8112908a08ecd0 
>>> AdwordsUserListService mutateMembers>> methodName> 1 262 
>>> >> >soap:Client 
>>> >[UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST 
>>> @ operations[0].operand]  >> xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201806; xmlns="
>>> https://adwords.google.com/api/adwords/cm/v201806;> 
>>> [UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST 
>>> @ operations[0].operand] 
>>> ApiException http://www.w3.org/2001/XMLSchema-instance; xsi:type="ns2:UserListError"> 
>>> operations[0].operand  
>>> operations 0  <
>>> fieldPathElements> operand  >> /> UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST>> errorString> UserListError 
>>> CAN_NOT_MUTATE_SENSITIVE_USERLIST  >> ns2:ApiExceptionFault>>> soap:Envelope>
>>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/70ecb237-3d00-410a-a4e8-a1890d4eb94f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST due to Customer Match policy?

2018-10-26 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 to Peter:
>
> Request:
>
>  http://schemas.xmlsoap.org/soap/envelope/; xmlns:ns0="
> https://adwords.google.com/api/adwords/cm/v201806; xmlns:wsdl="
> https://adwords.google.com/api/adwords/rm/v201806; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema; xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance;>  <
> wsdl:RequestHeader xmlns="
> https://adwords.google.com/api/adwords/cm/v201806;> rails 
> (AwApi-Ruby/1.3.0, Common-Ruby/1.0.2, GoogleAdsSavon/1.0.3, ruby/2.2.10, 
> HTTPI/2.4.1, httpclient) REDACTED developerToken> **  wsdl:RequestHeader>   https://adwords.google.com/api/adwords/rm/v201806;>  <
> ns0:operator>ADD  ** userListId>  **  membersList>  env:Envelope>
>
>
> Response:
>
>  http://schemas.xmlsoap.org/soap/envelope/;>  <
> ns2:ResponseHeader xmlns:ns2="
> https://adwords.google.com/api/adwords/rm/v201806; xmlns="
> https://adwords.google.com/api/adwords/cm/v201806;> 
> 0005791104dbdce00a8112908a08ecd0 
> AdwordsUserListService mutateMembers > 1 262  ns2:ResponseHeader>
> soap:Client 
> [UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST 
> @ operations[0].operand]   xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201806; xmlns="
> https://adwords.google.com/api/adwords/cm/v201806;> 
> [UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST 
> @ operations[0].operand] ApiException
>  http://www.w3.org/2001/XMLSchema-instance; xsi:type="ns2:UserListError"> <
> fieldPath>operations[0].operand  
> operations 0  <
> fieldPathElements> operand   
> UserListError.CAN_NOT_MUTATE_SENSITIVE_USERLIST 
> UserListError 
> CAN_NOT_MUTATE_SENSITIVE_USERLIST   ns2:ApiExceptionFault> soap:Envelope>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/4a7bd2cf-fc31-4601-8d03-2bac4fa9c2c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Change of Error Types When Attaching Bidding Strategies

2018-10-24 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 for our Adwords API framework. Since July 
> 25, a couple of these tests fail because of what appears to be a change in 
> returned error codes.
>
> Specifically, we try to attach a bidding strategy to an adgroup (which was 
> possible up to v201705, but disallowed from then on), and check whether the 
> returned error is *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP* (link to 
> reference 
> ).
>  
> A second test attaches a bidding strategy to an AdGroupCriterion, which we 
> expect to similarly fail with an 
> *CANNOT_ATTACH_BIDDING_STRATEGY_TO_ADGROUP_CRITERIA* (link 
> 
> ).
>
> Both of these operations now return an 
> *OPERATION_NOT_PERMITTED_FOR_CAMPAIGN_TYPE *error, which seems a bit 
> confusing as the campaign in question is a regular search campaign.
>
> Can we expect this new error type to stay going forward, or is it an 
> oversight that will be rolled back?
>
> Thanks for any feedback and best regards,
> Dorian
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/c07349c0-75c3-4749-9204-6b16dbeb9e86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shopping Performance Report returns same product twice

2018-07-26 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 that using the current version of the API. 

Best,
Thanet, AdWords API Team

On Friday, July 27, 2018 at 2:05:00 PM UTC+9, Ad Ja wrote:
>
> Hi Thanet,
>
> Apologies if it's late, but I'm currently working on a project that would 
> make this very useful.
> Is there any updates on this?
>
> Also, do you know any other way of getting a report where it returns 
> products with the most recent information?
>
> Thanks.
>
> On Wednesday, July 12, 2017 at 8:23:44 AM UTC+1, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> Hello Marc,
>>
>> Really sorry for this long waiting.
>> It was a long conversation between many parties.
>>
>> First, it looks like this works as intended for engineering to return the 
>> CategoryL* as segment fields.
>> The documentation needs to be fixed.
>>
>> About the date range per row, I'm pushing this through but cannot tell 
>> the exact date to finish.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Tuesday, July 11, 2017 at 11:02:57 PM UTC+9, Marc P wrote:
>>>
>>> Hi Thanet,
>>>
>>> any updates on this issue?
>>>
>>> We are still having many problems due to this.
>>>
>>> At the very least, it would be helpful to get a date range per row in 
>>> the response, so we can now at what times the ID performed good and at what 
>>> times not so good.
>>>
>>> Cheers
>>> Marc
>>>
>>> On Wednesday, April 26, 2017 at 10:30:35 AM UTC+2, Thanet Knack 
>>> Praneenararat (AdWords API Team) wrote:

 Hi Marc,

 I totally understand what you said but, unfortunately, it's not 
 supported by the current version of SHOPPING_PERFORMANCE_REPORT.
 I'll give your feedback as a feature request to engineering.

 Best,
 Thanet, AdWords API Team

 On Tuesday, April 25, 2017 at 11:07:45 PM UTC+9, Firma Lemundo wrote:
>
> Hi Thanet,
>
> CategoryL5 is just one example, this seems to be happening for almost 
> all product related attributes.
>
> I guess the intended functionality is to show that a product changed 
> at some point in time, but this is very misguiding as I would not expect 
> to 
> get the same product twice (it has the same OfferId...) without the 
> information at what point it was changed or what time range we are 
> talking 
> about.
>
> This might be a case where it would be useful to have a parameter to 
> set, something like "showProductChanges = true/false".
>
> At the very least, there should be a possibility to distinguish at 
> what point in time the product changed, so for example:
>
> OfferId CategoryL2  DateRange
> 123  Clothing/Pants 03/14 - 03/18
> 123  Clothing/Shorts03/18 - 03/29
>
> In that case, I could at least detect which entry is the most recent 
> one (Clothing/Shorts) and use that one, but getting the results as is the 
> case now is like this:
>
> OfferId CategoryL2
> 123  Clothing/Pants
> 123  Clothing/Shorts  
>
> and I do not know whether the product with OfferId 123 is in 
> CategoryL2 Clothing/Pants or Clothing/Shorts RIGHT NOW.
>
> Thanks
> Marc
>
> Am Montag, 24. April 2017 19:07:03 UTC+2 schrieb Thanet Knack 
> Praneenararat (AdWords API Team):
>>
>> Hello Marc,
>>
>> Sorry for the delay. It looks like this works as intended--all data 
>> of CategoryL5 is returned in SHOPPING_PERFORMANCE_REPORT.
>> I'm still asking if there are other workarounds for this.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Monday, April 24, 2017 at 4:01:49 PM UTC+9, Marc P wrote:
>>>
>>> Hi Thanet,
>>>
>>> any update on this topic?
>>>
>>> Thanks
>>> Marc
>>>
>>> On Wednesday, April 5, 2017 at 9:27:17 AM UTC+2, Thanet Knack 
>>> Praneenararat (AdWords API Team) wrote:

 Hi Marc,

 Thanks very much for reporting.
 Your previous example then shows that *CategoryL5* really behaves 
 like a segment.
 If it's a key column, even if you don't request for it, there 
 should be two rows returned.
 I'll talk with engineering to see how we fix this.

 As for your other questions:

> 1) How do I know what are the "key fields" in a report?

 Unfortunately, it's not quite obvious from the field itself. But we 
 try to document it in the summary description in the beginning of each 
 report type page.

 2) You wrote "Have a look at OfferId and CategoryL5, you can tell 
> that those two rows are different" - you

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

2018-07-11 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 two weeks and I still have not gotten approval for my 
> developer token to use Google Ads API.  I would really appreciate it if you 
> could follow up on my application.
>
> Thanks
> KDJ
>
> On Thu, Jun 28, 2018 at 3:10 PM,  wrote:
>
>> Luis,
>>
>> Thank you for letting me know the time frame for my developer token 
>> getting whitelistted.
>>
>> KDJ
>>
>> On Wednesday, June 27, 2018 at 8:27:05 PM UTC-7, Luis Xander Talag 
>> (AdWords API Team) wrote:
>>>
>>> Hi,
>>>
>>> The whitelisting of your developer token for Google Ads API usually 
>>> takes up to one to two weeks for approval. You won't receive a new 
>>> developer token but rather your current developer token will be 
>>> whitelisted. You will receive an email of approval for you to get notified 
>>> regarding this. If you haven't received any approval within the time frame, 
>>> let me know so I could follow up your application.
>>>
>>> Thanks and regards,
>>> Luis
>>> AdWords API Team  
>>>
>> -- 
>> -- 
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>> Also find us on our blog:
>> https://googleadsdeveloper.blogspot.com/
>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
>>  
>> You received this message because you are subscribed to the Google
>> Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/adwords-api/2a681773-1fe4-4898-bb8a-72ce569e7053%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/0883d897-ae7a-439d-beff-dd4508c00377%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2018-07-10 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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, July 6, 2018 at 3:13:49 AM UTC+9, Jianbo zhu wrote:
>
> Soft ping :) thanks. 
>
> Thanks,
> Jianbo
> On Monday, June 25, 2018 at 1:43:14 PM UTC-7, Jianbo zhu wrote:
>>
>> Got it, thanks Thanet. 
>>
>> Thanks,
>> Jianbo
>> On Monday, June 25, 2018 at 10:23:29 AM UTC-7, Thanet Knack Praneenararat 
>> (AdWords API Team) wrote:
>>>
>>> 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 
 advance :)

 Thanks,
 Jianbo
 On Wednesday, 20 June 2018 09:47:07 UTC-7, Jianbo zhu wrote:
>
> Thanks, Thanet. 
> We are currently blocked by this, Appreciate if you can investigate 
> more on this topic. Looking forward to your reply, thanks in advance. 
>
> Thanks,
> Jianbo
> On Wednesday, June 20, 2018 at 12:37:20 AM UTC-7, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> 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 
>> 
>>  
>> (in Chinese).
>>
>> Once I have more info on this, I'll update this thread and our 
>> documents.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Wednesday, June 20, 2018 at 7:33:56 AM UTC+9, Jianbo zhu wrote:
>>>
>>> Hi, Adwords team,
>>> I got one question regarding PrdocutDimension in ProductScope 
>>> Campaign Criterion. 
>>>
>>> Basically, both a shooping campaign and a display campaign with GMC 
>>> feed can have product scopes. but they use different ProductDimensions: 
>>> for 
>>> example, shopping campaign use ProductType 
>>> 
>>>  
>>> dimention while display campaign with a GMC feed uses 
>>> ProductTypeFull 
>>> 
>>>  
>>> dimention. I found ProductType 
>>> 
>>>  
>>> and ProductTypeFull 
>>> is
>>>  
>>> quite different:
>>> 1. in a shopping campaign, it can have at most 5 levels of ProductType 
>>>
>>> dimension
>>>  
>>> (there are hierarchy here and they will be treated as product_type_L1 
>>> to 
>>> product_type_L5 when calling adwords API to fetch them). see below
>>>
>>>
>>> 
>>>
>>>
>>>
>>> 2. in a display campaign with a GMC feed, it can have at most 7 
>>> ProductTypeFull 
>>>
>>> dimension
>>>  
>>> (please see below) and there are no hierarchy here (all of these 7 are 
>>> treated as ProductTypeFull when calling adwords api to fetch them). 
>>> what's 
>>> the relation for these ProductTypeFull dimensions? in which scenario we 
>>> should use multiple ProductTypeFull here? the doc is unclear. 
>>>
>>>
>>> 
>>>
>>>
>>> Thanks in advance. 
>>>
>>>
>>> Thanks,
>>> Jianbo 
>>>
>>>
>>>
>>>
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this

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

2018-07-08 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 25, 2018 at 1:43:14 PM UTC-7, Jianbo zhu wrote:
>>
>> Got it, thanks Thanet. 
>>
>> Thanks,
>> Jianbo
>> On Monday, June 25, 2018 at 10:23:29 AM UTC-7, Thanet Knack Praneenararat 
>> (AdWords API Team) wrote:
>>>
>>> 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 
 advance :)

 Thanks,
 Jianbo
 On Wednesday, 20 June 2018 09:47:07 UTC-7, Jianbo zhu wrote:
>
> Thanks, Thanet. 
> We are currently blocked by this, Appreciate if you can investigate 
> more on this topic. Looking forward to your reply, thanks in advance. 
>
> Thanks,
> Jianbo
> On Wednesday, June 20, 2018 at 12:37:20 AM UTC-7, Thanet Knack 
> Praneenararat (AdWords API Team) wrote:
>>
>> 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 
>> 
>>  
>> (in Chinese).
>>
>> Once I have more info on this, I'll update this thread and our 
>> documents.
>>
>> Best,
>> Thanet, AdWords API Team
>>
>> On Wednesday, June 20, 2018 at 7:33:56 AM UTC+9, Jianbo zhu wrote:
>>>
>>> Hi, Adwords team,
>>> I got one question regarding PrdocutDimension in ProductScope 
>>> Campaign Criterion. 
>>>
>>> Basically, both a shooping campaign and a display campaign with GMC 
>>> feed can have product scopes. but they use different ProductDimensions: 
>>> for 
>>> example, shopping campaign use ProductType 
>>> 
>>>  
>>> dimention while display campaign with a GMC feed uses 
>>> ProductTypeFull 
>>> 
>>>  
>>> dimention. I found ProductType 
>>> 
>>>  
>>> and ProductTypeFull 
>>> is
>>>  
>>> quite different:
>>> 1. in a shopping campaign, it can have at most 5 levels of ProductType 
>>>
>>> dimension
>>>  
>>> (there are hierarchy here and they will be treated as product_type_L1 
>>> to 
>>> product_type_L5 when calling adwords API to fetch them). see below
>>>
>>>
>>> 
>>>
>>>
>>>
>>> 2. in a display campaign with a GMC feed, it can have at most 7 
>>> ProductTypeFull 
>>>
>>> dimension
>>>  
>>> (please see below) and there are no hierarchy here (all of these 7 are 
>>> treated as ProductTypeFull when calling adwords api to fetch them). 
>>> what's 
>>> the relation for these ProductTypeFull dimensions? in which scenario we 
>>> should use multiple ProductTypeFull here? the doc is unclear. 
>>>
>>>
>>> 
>>>
>>>
>>> Thanks in advance. 
>>>
>>>
>>> Thanks,
>>> Jianbo 
>>>
>>>
>>>
>>>
>>>
>>>
>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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

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

2018-06-25 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 
> advance :)
>
> Thanks,
> Jianbo
> On Wednesday, 20 June 2018 09:47:07 UTC-7, Jianbo zhu wrote:
>>
>> Thanks, Thanet. 
>> We are currently blocked by this, Appreciate if you can investigate more 
>> on this topic. Looking forward to your reply, thanks in advance. 
>>
>> Thanks,
>> Jianbo
>> On Wednesday, June 20, 2018 at 12:37:20 AM UTC-7, Thanet Knack 
>> Praneenararat (AdWords API Team) wrote:
>>>
>>> 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 
>>> 
>>>  
>>> (in Chinese).
>>>
>>> Once I have more info on this, I'll update this thread and our documents.
>>>
>>> Best,
>>> Thanet, AdWords API Team
>>>
>>> On Wednesday, June 20, 2018 at 7:33:56 AM UTC+9, Jianbo zhu wrote:

 Hi, Adwords team,
 I got one question regarding PrdocutDimension in ProductScope Campaign 
 Criterion. 

 Basically, both a shooping campaign and a display campaign with GMC 
 feed can have product scopes. but they use different ProductDimensions: 
 for 
 example, shopping campaign use ProductType 
 
  
 dimention while display campaign with a GMC feed uses ProductTypeFull 
 
  
 dimention. I found ProductType 
 
  
 and ProductTypeFull 
 is
  
 quite different:
 1. in a shopping campaign, it can have at most 5 levels of ProductType 
 dimension
  
 (there are hierarchy here and they will be treated as product_type_L1 to 
 product_type_L5 when calling adwords API to fetch them). see below


 



 2. in a display campaign with a GMC feed, it can have at most 7 
 ProductTypeFull 

 dimension
  
 (please see below) and there are no hierarchy here (all of these 7 are 
 treated as ProductTypeFull when calling adwords api to fetch them). what's 
 the relation for these ProductTypeFull dimensions? in which scenario we 
 should use multiple ProductTypeFull here? the doc is unclear. 


 


 Thanks in advance. 


 Thanks,
 Jianbo 








-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/12b5b585-4fb7-4b97-83f2-5469e566ec63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2018-06-20 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 

 
(in Chinese).

Once I have more info on this, I'll update this thread and our documents.

Best,
Thanet, AdWords API Team

On Wednesday, June 20, 2018 at 7:33:56 AM UTC+9, Jianbo zhu wrote:
>
> Hi, Adwords team,
> I got one question regarding PrdocutDimension in ProductScope Campaign 
> Criterion. 
>
> Basically, both a shooping campaign and a display campaign with GMC feed 
> can have product scopes. but they use different ProductDimensions: for 
> example, shopping campaign use ProductType 
> 
>  
> dimention while display campaign with a GMC feed uses ProductTypeFull 
> 
>  
> dimention. I found ProductType 
> 
>  
> and ProductTypeFull 
> is
>  
> quite different:
> 1. in a shopping campaign, it can have at most 5 levels of ProductType 
> dimension
>  
> (there are hierarchy here and they will be treated as product_type_L1 to 
> product_type_L5 when calling adwords API to fetch them). see below
>
>
> 
>
>
>
> 2. in a display campaign with a GMC feed, it can have at most 7 
> ProductTypeFull 
>
> dimension
>  
> (please see below) and there are no hierarchy here (all of these 7 are 
> treated as ProductTypeFull when calling adwords api to fetch them). what's 
> the relation for these ProductTypeFull dimensions? in which scenario we 
> should use multiple ProductTypeFull here? the doc is unclear. 
>
>
> 
>
>
> Thanks in advance. 
>
>
> Thanks,
> Jianbo 
>
>
>
>
>
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/a470a533-d165-48c1-a5bc-b048e703def5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Some campaigns not retrieved by API

2018-05-10 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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 Balduini wrote:
>
> Hello, I'm not an expert in Adwords, It's been 4 days since I started to 
> learn and use it, so my question may be a little trivial, but I would 
> really aprecciate some help!
>
> I have two specific campaigns that are not being retrieved by the API when 
> I try to generate a report using getSheetData. Although I can access the 
> data from the UI, the reports generated by the UI  are missing this 
> campaigns. The other campaigns are being retrieved as expected by the API, 
> so I imagine it may not be a coding error.
>
> Any suggestions and ideas would help me a lot! :)
>
> Thanks in advance
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and Google Ads 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 https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/b304e05b-b653-466c-945a-8d0ca4e704c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2018-05-08 Thread 'Thanet Knack Praneenararat (AdWords API Team)' via AdWords API and Google Ads API Forum 
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, christos.alexa...@fromatob.com 
wrote:
>
> HI,
>
> I have already created an issue 
> 
>  
> in github and was advised to ask here for help.
>
> I am getting the error:
> Traceback (most recent call last):
>   File "test.py", line 267, in 
> client_list.append(tostring(adwords_client, report_name, id))
>   File "test.py", line 243, in tostring
> skip_report_summary=True, include_zero_impressions=True)
>   File ".../anaconda3/lib/python3.6/site-packages/googleads/common.py", 
> line 531, in Wrapper
> return utility_method(*args, **kwargs)
>   File ".../anaconda3/lib/python3.6/site-packages/googleads/adwords.py", 
> line 1292, in DownloadReport
> output, **kwargs)
>   File ".../anaconda3/lib/python3.6/site-packages/googleads/adwords.py", 
> line 1569, in _DownloadReport
> and not isinstance(output, io.BytesIO))
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc3 in position 
> 16383: unexpected end of data
>
>
>
> while trying to download an Ad Perfromance report as string in memory with 
> the DownloadReport function or as stream with DownloadReportAsStream 
> function.
>
> The problem comes from the AdGroupName field that contains german 
> characters like ä, ü, ö.
>
> I am not receiving any error though when I use the DownloadReportAsStream 
> function to write the report in a .csv file or when I force the decoding to 
> be 'latin-1' with 
>
> report_data.write(chunk.decode('latin-1') if sys.version_info[0] == 3
>   and getattr(report_data, 'mode', 'w') == 'w' 
> else chunk)
>
> I am using Python 3, API v201802  and the locale in the container is set 
> to be C.UTF-8.
>
> Below are the functions which are mostly copied from AdWords API 
> documentation.
>
> write in csv (working):
> def write_csv(client, report, customer_id):
> client.SetClientCustomerId(customer_id)
> report_downloader = client.GetReportDownloader(version='v201802')
>
>
> filename = str(customer_id) + '_' + report + '_' + min_date
>
>
> report_data = io.open(filename, 'wb')
>
>
> stream_data = report_downloader.DownloadReportAsStream(
> reports[report], skip_report_header=True, skip_column_header=False
> ,
> skip_report_summary=True, include_zero_impressions=True)
>
>
> try:
> while True:
> chunk = stream_data.read(CHUNK_SIZE)
> if not chunk:
> break
> report_data.write(chunk.decode() if sys.version_info[0] == 3
>   and getattr(report_data, 'mode', 'w') == 'w' 
> else chunk)
> finally:
> report_data.close()
> stream_data.close()
>
> stream with latin-1 (working):
> def stream(client, report, customer_id):
> client.SetClientCustomerId(customer_id)
> report_downloader = client.GetReportDownloader(version='v201802')
>
>
> report_data = io.StringIO()
> stream_data = report_downloader.DownloadReportAsStream(
> reports[report], skip_report_header=False, skip_column_header=
> False,
> skip_report_summary=False, include_zero_impressions=True)
>
>
> try:
> while True:
> chunk = stream_data.read(CHUNK_SIZE)
> if not chunk:
> break
> report_data.write(chunk.decode('latin-1') if sys.version_info[
> 0] == 3
>   and getattr(report_data, 'mode', 'w') == 'w' 
> else chunk)
> return report_data
> finally:
>report_data.close()
>stream_data.close() 
>
> write to string (not working):
> def tostring(client, report, customer_id):
> client.SetClientCustomerId(customer_id)
> report_downloader = client.GetReportDownloader(version='v201802')
> 
> report_data = io.StringIO()
> report_downloader.DownloadReport(
> reports[report], report_data, skip_report_header=True, 
> skip_column_header=False,
> skip_report_summary=True, include_zero_impressions=True)
>
>  return report_data
>
>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads 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 and