When To Use The Same LeadTable Vs. A Separate One?

You’ll typically want to use just one LeadTable to house all the leads for a single business.

Sometimes it can be worth creating a second LeadTable as a “throwaway testing ground” for enrichment ideas prior to merging them into your main table.

But as a rule, I’d advise against multiple tables for different ICPs etc., and instead would recommend that you use just one table with tags and saved filter views for managing your different sub-lists.

The reason I advise against separate LeadTables within the context of one business is…

• Duplicate data; deduping happens per table, so you could have one lead in multiple tables without knowing
• Not knowing where a given lead lives, and losing track of them
• Challenges adding to campaigns, given that a given campaign can only hold leads from one table
• Managing & tracking lead interactions — if the same contact lives in two tables and you mark one as having positively replied to a cold email or as requesting a lead magnet, that info wouldn’t carry over to the version of them in the other table

Tags in LeadTables are very very powerful, and I’d almost always recommend a good tagging strategy over using separate LeadTables if it’s for the same business.

(And if you’re managing leads for different businesses, it’s usually best to separate those businesses into separate teamspaces)