Hey!! I replied to the other web chat thread but in case you see this one first: "Okay, it seems it's because the query is taking several inputs but if you do a specific keyword or phrase per search it does collect more results. I ran a test in your table with just "handmade" in the US, that uses Shopify in the Apparel category and limited to 3 results. These 3 were generated here https://app.clay.com/workspaces/136950/tables/t_v9oe9CfbPoM0/views/gv_z76d8cZqp51XLet me know if running separate queries does increase options!"
Arturo O. yes i did this test too but isn’t this a bug from Clay side? technially, the reason why you want to use queries because yoou want to add multiple “values” and “logics/filters” to get results, otherwise it’s time consuming and less effective. For my use case, Location is a must have, Categories are must have too, and ideally i can add more than just 1 keyword.
Just replied to the other thread but in case this comes up first: "
Got it! Not sure if it's a limitation of the query field but I was able to apply all other filters without issues.Keethu R., could you help us with some insights when you're available, if this would be possible?
"
Can you keep me posted with the fix timeline Keethu R.? just bc it definitely more helpful if i can use multiple keywords vs running each of them separately 😄 CC: Arturo O.
Hey Brigitta R., putting up the fix right now and it should be live by EOD! Was looking at your Store Leads tables though and was wondering why you're using backslashes in your queries? Was testing and seems like the quality of results returned is always higher without them
Brigitta R., thanks for the clarification! I think I've seen that happen too. Keethu R., looks like that's happening on our end after the search is queued up, we add the backslashes for some reason.
.png){kind=logo}
