How to Copy Missing Industry Data Based on Shared Domain

Hello Clay crew, I have a ‘company name’, ‘domain’ and ‘industry’ column in a table. For the same domain, in one row I have industry data, while in the other row this data is missing. How do I replicate the industry from one row to another because both rows share the same domain? [please see the picture attached] Link to table: https://app.clay.com/workspaces/522602/workbooks/wb_0swnzb7kausXp6kDotR/tables/t_0swo1n3uK5r8qoBAXii/views/gv_0swo1n46VnnDpfAGtrn Thanks a bunch 🙏

2 comments

Channeled
APP
·
·
You can use the "write to table" feature to copy industry data between rows with the same domain. Here's how: 1. Create a new table or select an existing one as your destination 2. Add the "write to table" enrichment to your source table 3. Select your Clay account 4. Choose the destination table 5. Map your columns, making sure to include: • Domain (to match records) • Industry (to fill missing values) • Company name (and any other data you want to preserve) 6. In the configuration, set a condition to only run for rows where the industry data exists This will populate your destination table with complete records, effectively copying industry values between rows that share the same domain.
Sources: Write to Other Table | Documentation | Clay University Table columns | Documentation | Clay University
Owen C.
·
·
Hey Igor, thanks for reaching out! The scalable solution in this case is to actually create a separate table dedicated to companies. In this other table you'd have all ~98 companies in their own row with all of their own data associated on the company level. Then, when we are handling contacts within those companies, we can simply reference this company table for all company related data points to avoid duplicate enrichments and trying to workaround this. The reason why we can't do this directly is because rows in Clay tables don't talk to each other as of right now, meaning we can reference another row in a current row. Let me know if that helps clear things up and how I can best help here! :)
(317 kB)