Resolving Lookalike Account Errors in Data Tables: Seeking Guidance

I'll start by saying thus channel has become my go to for all challenges which is amazing - 🙂 I encountered a 'newby' problem today. Table A = list of 70 accounts. Ran a lookalike and posted to table B. Wanted to write the lookalike accounts in table B back to table A. Kept getting an error. I realised if the new accounts were posted to table A it would create a circle look-up as the lookalike enrichment was still active on table A. I turned off auto-update, however the problem continued. It was only when I deleted the lookalike column that I could write to table A. This is probably not the correct process. What should I have done?

4 comments

Channeled
APP
·
·
Instead of writing lookalike results back to the same table (Table A), here's the recommended process: 1. Create a new separate table for your lookalike results using the "Write to Table" function: • Select "New Table" as your destination • Choose the fields you want to include (company name, domain, similarity score, etc.) 2. When setting up the write operation: • Turn off auto-update in the run settings to prevent automatic enrichment loops • Map your desired columns from the source to the destination tableThis approach prevents circular lookups and keeps your data organized. You can then use lookups between tables if you need to reference the data across tables. Sources: Find Company Lookalikes [Clay 101] - Clay University Write to table integration overview | Documentation | Clay University
👍1
Channeled
APP
·
·
Hi Charles T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
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.
Channeled
APP
·
·
Thank you so much for sharing your feedback Charles T.!