Assistance Needed with Clay's Find Lookalikes Enrichment Feature

Christopher O. · 2025-11-06T14:46:52.847Z

Hey @Clay S., Good day to you! Just wanted to ask for help, Im using a column value to actually push into an enrichment [Clay's native Find Lookalikes] (https://app.clay.com/workspaces/427203/workbooks/wb_0t55uw0G3Ge5XVF4gN4/tables/t_0t55uwjjvFEF2f8AHbh/views/gv_0t55uwjYhSvtJDjowHy) im trying to push a data into a the input "Size" which is a drop down, previously this works, but now its not working. I have 2 screenshots below, the one with a square bracket in "red" is working, means it comes from the native drop down selection. The all black font color is from a manually written text. Can you help me and look at this? here is the clay table (https://app.clay.com/workspaces/427203/workbooks/wb_0t55uw0G3Ge5XVF4gN4/tables/t_0t55uwjjvFEF2f8AHbh/views/gv_0t55uwjYhSvtJDjowHy)

Assistance Needed with Clay's Find Lookalikes Enrichment Feature | Clay

Clay Support
APP
·
·
The issue appears to be with list formatting when pushing data to dropdown inputs. When a value isn't formatted as a list, it may cause errors.
To troubleshoot this, could you copy and paste the exact JSON or data format you're using in the Size field? This will help identify any formatting issues that might be preventing the dropdown from accepting the value properly.
The red bracketed format ["1"] suggests it's being recognized as a proper list, while the black text might indicate incorrect formatting. [1]
Christopher O.
·
·
I need to talk to a person ❤️
Clay Support
APP
·
·
I understand, and I’m connecting you to a human agent who can assist you further. Thank you for your patience. ❤️
Intercom
APP
·
·
Clay Support is sharing a file with you.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Loading attachments
Quentin R.
·
·
Hi Christopher, I just checked the native lookalike column in your table and it looks like you solved the problem by using the property. Is it correct? 😌
Loading attachments
Christopher O.
·
·
Hi Quentin R. Unfortunately, no not yet, We still need to add the company Country and Revenue into the search. That's when the problem arises.
Loading attachments
Christopher O.
·
·
Maybe our formula for that is wrong? Is there any way we could make it work?
Quentin R.
·
·
Got it. Let’s start with countries.
If you’re unsure what format the menu expects, check one of the dropdown options – that’ll show you how it’s written. In this case, the countries are spelled out in full (not initials).
Since your import only includes country codes, I’d suggest adding an AI column that converts the two-letter codes into full names (e.g. CH → Switzerland). You can use the cheapest model for this – it’s a simple text transformation 😊
When it comes to revenue, the process is similar – just a bit trickier. The values need to fall within the range accepted by the dropdown. For this, I’d recommend using a formula. You don’t need any special formatting; a plain number within the range (as shown below) will work perfectly 😌
Loading attachments
Quentin R.
·
·
Hope this helps!
Christopher O.
·
·
Hi Quentin R., we already got that correct as we are using this feature before. Its just right now its not working, You can check our clay table and columns to match (image below). we got some sample data here, and its working before 🙂 Just wanted to make sure there's a way to make it work. ❤️ I already sent the image and my concern on my first message in this thread ❤️ Thank you Quentin R., I know its kinda hard to explain on my side.
Loading attachments
Bo (.
·
·
Hey,
Do you have a table where it’s currently working? From what I remember, that setup shouldn’t work since those dropdown inputs are fixed in the backend. But if you’ve got an example showing it used to work, please share it and I’ll check it with the team to confirm what changed.
Let me know if you can send that link or screenshot.
Christopher O.
·
·
Hi Bo (. there were data points in this table that should have a column that work perfectly https://clayrunhq.slack.com/archives/C025KSBLPGX/p1762440412847189
Bo (.
·
·
Hey, I get that this table isn’t working right now. What I meant earlier is that you mentioned it worked before — could you share which previous table that was?
The “Property Size” and “Revenue” columns are fixed setups, so they don’t usually accept dynamic values from a lookup like this. Knowing where it worked before will help us check what’s changed.
Let me know once you’ve got that link.
Christopher O.
·
·
That's from a previous client and we can't share their tables right now as we don't work with them now. Thank you for this ❤️ We will try to think of some other way to get moving with this. If you have an idea, please let us know ❤️
Bo (.
·
·
Okay, I see. No worries. Unfortunately, it’s not possible to use lookups on those properties since they’re fixed in our database and mapped internally. This has come up before as feedback, though, so it’s definitely on our radar.
Thanks for flagging it.

17 comments