Strategies to Avoid Targeting Duplicate Companies Across Multiple Campaigns & Tables

when creating a new campaign, how do you ensure you don't target the same companies you targeted in a previous campaign from a different table? in other words, I ran a campaign using Table A. Now, I created Table B with new data and I don't want to target companies matching the ones in Table A. Catching and removing duplicate companies when working with multiple tables...

✅1

6 comments

David P.
·
·
old table: https://app.clay.com/workspaces/42547/tables/t_sLEBdeJ5iDHl/views/gv_AzCRwfJfxmMN new table: https://app.clay.com/workspaces/42547/tables/t_ltq60FuAkDJD/views/gv_otzHpB6OtqiD
Clay Team
APP
·
·
Hey David! Just replied to DMs :)
Joe H.
·
·
Arturo O. I would also be interested in the answer here if you can share!
Clay Team
APP
·
·
Sure thing, Joe! sorry for the delay
Clay Team
APP
·
·
There are a few concepts + logic to apply here. Either having a Do not contact (DNC) table to cross-match against new tables-> Here's an example of how to setup a lookup for DNC - https://www.loom.com/share/80d613c10d5248f6bfc662cc95c8023dAnd based on matches, you can set up conditional formulas so existing records don't get enriched or contacted.
Clay Team
APP
·
·
Or a very similar concept but creating a Master Table where all enriched companies and the data points you need/want exist, and new rows are created when a new company is enriched elsewhere...-> Start a Master company table, maybe your old table could work for this or if you'd like to keep it cleaner a fresh table would help. -> Then you can push over all companies from table 1 over to that Master table, either with CSV or Write to table. -> Then use the lookup in table 2 to determine if they exist in table 1 or the master table, -> -> If they exist then nothing happens -> -> if they are new companies (don't exist yet) then use write to table to automatically create a record in the master company tableIt's a bit of a triangulation process but would solve this for now. The team will look into how they could implement a workspace-wide lookup feature to prevent duplicates but that may take some time to build if possible