Re: Issue creating custom combination remarketing list using LogicalUserList

Hello Mike, Thanks for the update, had my head cracking on this, will file for an issue now. Regards, Kaushik Vinay On Wednesday, 18 November 2015 13:37:41 UTC-5, Michael Cloonan (AdWords API Team) wrote: > > Hello, > > Looking at the WSDL, I believe that hash is supposed to work. We only

Re: Issue creating custom combination remarketing list using LogicalUserList

Hello, Looking at the WSDL, I believe that hash is supposed to work. We only recently added choice support for requests to the ruby library, but only tested it for a different use case, not LogicalUserLists. I believe this to be a bug with the ruby library itself. Can you please file an issue

Re: Issue creating custom combination remarketing list using LogicalUserList

Hi, I was only able to pass :xsi_type as "UserList", anything other than that throws an error user_list_srv = adwords.service(:AdwordsUserListService, :v201509) operation = { :operator => 'ADD', :operand => { :xsi_type => 'LogicalUserList', :name =>

Re: Issue creating custom combination remarketing list using LogicalUserList

Hello, In your initial email, you mentioned that the library validation worked and that you got a response from the API. Try that same syntax, but using the specific :xsi_type (ExpressionRuleUserList) rather than the generic "UserList". If that's already what you've tried, please provide the ex

Re: Issue creating custom combination remarketing list using LogicalUserList

Hello Mike, I tried that before and gave it a try again now, this is what i got as response AdsCommon::Errors::TypeMismatchError: AdsCommon::Errors::TypeMismatchError: expected: 'choice subtype', provided: 'ExpressionRuleUserList' for field '{:id=>185402532}' On Wednesday, 18 Nove

Re: Issue creating custom combination remarketing list using LogicalUserList

Hello, You shouldn't need to define :user_list => within the array of :rule_operands. Instead, just define the user list directly. This is what "choice" type means; you can populate the data with one of many possible classes. This is why an explicit :xsi_type is required, as well. So, for exam

Re: Issue creating custom combination remarketing list using LogicalUserList

Hi Nadine, I tried to send the parameters as u mentioned, but Im unable to create it using ruby client library, please let me know if im passing the right syntax user_list_srv = adwords.service(:AdwordsUserListService, :v201509) operation = { :operator => 'ADD', :op

Re: Issue creating custom combination remarketing list using LogicalUserList

Hello, I gave this a try myself using the example, while keeping in mind what you wanted to do. This is the request and response in SOAP XML (minus the header): [17 Nov 2015 16:26:44,075 - INFO ] Outgoing Request: https://adwords.google.com/api/adwords/rm/v201509";>https://adwords.google.com/ap

Re: Issue creating custom combination remarketing list using LogicalUserList

Hi Nadine, Yes, the example shown for "Combining multiple user lists" on that page. Thanks. On Monday, 16 November 2015 18:10:38 UTC-5, Nadine Sundquist (AdWords API Team) wrote: > > Hi, > > In order to make sure I reproduce this correctly, is this example >

Re: Issue creating custom combination remarketing list using LogicalUserList

Hi, In order to make sure I reproduce this correctly, is this example the one that you were following when creating your request? Best, Nadine, AdWords API Team On Monday, November 16, 2015 at 8:

Issue creating custom combination remarketing list using LogicalUserList

Hello, We are using Ruby client library for the AdWords API, currently having issues creating custom combination of existing remarketing list using LogicalUserList. Passing multiple Userlist as an array inside rule_operands seems to set only one of Userlist in the result. My problem i