.png){kind=logo}
Understanding Row Selection in LookUp SingleRow in Clay
Hey team, when LookUp SingleRow, if there are multiple matching rows in target table, how does Clay decide which row to go for? Is it from top down?
When performing a Lookup Single Row operation in Clay, the system is designed to return a single row even if multiple matches are found. However, the exact selection criteria for choosing one row among multiple matches isn't specified in the provided sources.In most cases, a single row is expected to be returned, especially when searching by a unique identifier like an email address. This suggests that the lookup operation is typically used with conditions that should yield a unique result.To ensure you get the desired row when multiple matches are possible, it's best to use specific and unique criteria in your lookup query. For example, instead of searching by a common name, you might use a unique identifier or a combination of fields that narrow down the results to a single row.What specific use case do you have in mind for the Lookup Single Row operation? Understanding your particular scenario could help provide more targeted advice on how to structure your lookup query effectively. Sources: Lookup Single Row in Other Table with Clay Snowflake integration overview | Documentation | Clay University
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Owen C.··Hey there, yes! When using 'Lookup Single Row" in Clay this enrichment will return the first result found starting from top to bottom. If you're interested in pulling all of those data points I'd recommend using our 'Lookup Multiple Rows' enrichment which will pull all of the data points found matched in a given column. :) Hope that helps! Let me know how else I can assist here. :)
Andi D.··Thanks Owen! Just wanted to confirm, first one as it scans top-down? I’m trying to see if it’s possible to set up a master data table that acts as my own database, where I can push all the enrich leads into it and sort by updated time. And pull/match future contacts to avoid doubles enrich and also avoid double sends in Instantly
- Andi D.··
Instantly has features to prevent double sends if it’s uploaded via CSV but not if it’s from Clay. Any tips on working around that?
- Owen C.··
Hey Andi, yes you could think of this as either top-down or defaulting to returning the oldest record versus a newer record. As for preventing double sends I would recommend avoiding the situation where a lead is in multiple campaigns. This can be done by ensuring this is toggled on. Hope this helps! Let me know if you have any other questions. :) https://downloads.intercomcdn.com/i/o/w28k1kwz/1355306104/f457ebeedcae84ac976944f38771/CleanShot+2025-01-28+at+14_19_26%402x.png?expires=1738093500&signature=339f6585c88d40affe619e9405043fb240e19a30259cab01b085f19b315a53ce&req=dSMiE8p%2Bm4BfXfMW1HO4zThH8%2BsWgOT77uDlqg0hKk1JV98MTY5eZ04Mgo13%0Aj61i%0A
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.