Re: UserList bug from AdwordsUserListService

Thanks for the quick response! On Friday, February 15, 2019 at 3:58:17 PM UTC-5, googleadsapi-forumadvisor wrote: > > Hi Han, > > I got a quick response from the API team. It turns out this is expected > behavior for the AdWords API. > > The good news is that this behavior is specific to *Simila

RE: UserList bug from AdwordsUserListService

Hi Han, I got a quick response from the API team. It turns out this is expected behavior for the AdWords API. The good news is that this behavior is specific to *SimilarUserLists*. Therefore, if you use the predicate I shared in my previous post, you won't get back multiple records when using a

Re: UserList bug from AdwordsUserListService

Awesome, thanks for the update! On Fri, Feb 15, 2019 at 3:14 PM wrote: > Hi, > > I was able to reproduce the issue you described and I've reported it to > the user list team. I'll reply back here as I receive updates from them. > > As a workaround, you could either select lists by *Id* instead,

RE: UserList bug from AdwordsUserListService

Hi, I was able to reproduce the issue you described and I've reported it to the user list team. I'll reply back here as I receive updates from them. As a workaround, you could either select lists by *Id* instead, or add additional filters to exclude the unwanted records. For example, if Similar

RE: UserList bug from AdwordsUserListService

Hi Peter, Thanks for response. If you take a look at my SOAP request, i was asking the API for the UserList with the exact name. The API was returning the additional object with a similiar name which is unexpected from the API consumer perspective. So you confirm this is an expected behavior? Th

RE: UserList bug from AdwordsUserListService

Hi Han, It appears that the userlist you are referring to is a SimilarUserList type of audience. It is automatically created by Google and you can refer here