Enriching Source People Table with Signals Data: Seeking Solutions

Luke G. · 2025-11-24T18:01:02.653Z

I have a source table on People that I am trying to enrich with data from Signals. Let's say for example I have 3 separate signals set up : 1 for recent promotions, 1 for specific keywords in recent posts, and 1 for how frequently a person posts. I want to add all of this data to the Source People table into the Row that triggered the signal. Adding a row from signal->source then deduping does not seem to work because it triggers data loss. You either have to select the older or newer row in the deduping process. This means you are left with either : a.) the original row without any enrichment from the signal b.) the new row with signal enrichment without any of the original data. Does anybody have a solution to this?

Enriching Source People Table with Signals Data: Seeking Solutions | Clay

7 comments

· Sorted by Oldest

Clay Support
APP
·
·
Instead of adding rows and deduping, try using Lookup columns to pull signal data into your existing People table. [1]
You can also map child columns to existing columns - click on the signal data cell, hover over the field you want, and select "Add as column" then map it to your existing People table column. [2] This overwrites the destination column but preserves your original row structure.
Another option is extracting specific information from signal columns into new columns using AI formulas or the direct extraction method. This way you keep all original data while adding signal enrichments as separate columns.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with enriching your People table using Signals or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any challenges you’re facing?
Luke G.
·
·
It looks like the second solution you posted is not possible because "add as column" necessitates that the column being added is within the same table (signal table) which means it cannot be added to the source table. Using 'Lookup single row' worked to resolve my use case. I added a column to the Source table and looked Up to the signals table.
Clay Support
APP
·
·
You're absolutely right! The "Add as column" feature only works within the same table where the enrichment data exists. [1]
Great solution using Lookup single row - that's exactly the right approach for pulling signal data into your source People table while preserving all your original data. Lookup columns are perfect for avoiding duplicate enrichments and keeping everything organized. [2]
Glad you got it working!
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any more help with enriching your People table or have other questions, I’m here to assist. Would you like to share more about what you’re trying to resolve or understand?

Clay Support
APP
·
·
Instead of adding rows and deduping, try using Lookup columns to pull signal data into your existing People table. [1]
You can also map child columns to existing columns - click on the signal data cell, hover over the field you want, and select "Add as column" then map it to your existing People table column. [2] This overwrites the destination column but preserves your original row structure.
Another option is extracting specific information from signal columns into new columns using AI formulas or the direct extraction method. This way you keep all original data while adding signal enrichments as separate columns.
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need help with enriching your People table using Signals or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any challenges you’re facing?
Luke G.
·
·
It looks like the second solution you posted is not possible because "add as column" necessitates that the column being added is within the same table (signal table) which means it cannot be added to the source table. Using 'Lookup single row' worked to resolve my use case. I added a column to the Source table and looked Up to the signals table.
Clay Support
APP
·
·
You're absolutely right! The "Add as column" feature only works within the same table where the enrichment data exists. [1]
Great solution using Lookup single row - that's exactly the right approach for pulling signal data into your source People table while preserving all your original data. Lookup columns are perfect for avoiding duplicate enrichments and keeping everything organized. [2]
Glad you got it working!
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any more help with enriching your People table or have other questions, I’m here to assist. Would you like to share more about what you’re trying to resolve or understand?