Workflow Issue: Suppressing Duplicate Companies in Ocean Integration

Good morning all! I'm building a workflow for a client and running into an issue. We're using the Ocean lookalike finder but running into a problem suppressing previous results from future requests. We keep buying the same companies over and over again. Since the Ocean integration doesn't let you reference another table to exclude results, I'm stuck. The payload we receive includes 5-10 companies, but I can't figure out how to extract the domains and add each one to a new row in the same spreadsheet. We're pushing the results (company name and domain name) to another table, but it looks like I can't reference that table and column in the original table. Any suggestions?

7 comments

Channeled
APP
·
·
Here's how you can manage your Ocean.io lookalike results effectively: 1. For suppressing previous results: • Use the "Domains to Exclude" field in the Ocean.io integration • Add your previously found domains as comma-separated values in this field 2. To organize the lookalike results: • Use Clay's "Write to Table" feature • Create a new table if you don't have one already • Select the fields you want to include (company name, domain, etc.) • Use this new table to track all your lookalike results 3. To maintain clean data: • Rename columns for clarity • Deduplicate the list to remove redundant entries • Add a lookup to ensure lookalikes aren't in your original list Sources: Find Company Lookalikes [Clay 101] - Clay University Find Lookalike Companies with Ocean.io with Ocean.io
Bruno R.
·
·
Hey there, thanks for reaching out. Taking a look at this now! You can exclude specific domains from your ocean.io company lookalike search, but you will need to input the exclusion parameters manually at setup: https://downloads.intercomcdn.com/i/o/w28k1kwz/1358124078/7e3be51609e29d9dbdd6e2322691/CleanShot+2025-01-30+at+09_33_47%402x.png?expires=1738249200&signature=db2fbe4ccef6617173194163c94172207a95caaee303838717d9c45cf341c9c6&req=dSMiHsh8mYFYUfMW1HO4zZsGrZsuK9Fa5Jolc7aBIRgKZhuDkyFgw3DaQzo6%0Azfnq%0A I can relay your feedback on running more complex exclusion logics on this integration to our product team.
Taft L.
·
·
Thanks Bruno. Yes I'm using that field. To make sure I understand, my choices are:
1.
Reference a column in the table where the operation is being run (not another table)
2.
Manually update the exclusion list by pasting in specific domains
Meaning that there is not a way to reference a column in another sheet (like with the Clay lookalike search)?
Bruno R.
·
·
That is correct - you can use our lookup action which allows you to retrieve records from another table based on a specific identifier, but this will involve importing the lookalikes first to then exclude them from the subsequent enrichment process.
Taft L.
·
·
I tried to leverage the Lookup Multiple Rows in Another Table enrichment, but it's not clear how to make it work. I need those values to show up in the same column that I'm using for exclusion. If I understand correctly, the lookup action won't create new rows, which is critical to this working.
Bruno R.
·
·
The lookup single rows will be the best action here. It functions like an xls lookup- here's a video explaining how to set this up: https://www.loom.com/share/ad767e3be9914d19a2f6647efe4dfa85?sid=b392b189-1b2a-4fba-a8dc-edb8032f79b1. You can read more about this feature in this docs page.
Channeled
APP
·
·
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.