Lead and lead list
The people you are reaching, and the lists that group them.
A Person is the CRM record for a human. A Lead is that Person's enrollment in a campaign, and a lead list is the campaign's named group of enrollments.
Lead list
Every lead belongs to a lead list, and a campaign points at exactly one list. That is the mechanism by which a campaign knows who it is for.
Lists come from Lead Finder or from a CSV import. Once created, the two are indistinguishable.
Because a campaign takes one list, reaching a different audience with the same sequence means a second campaign. It also means a list is worth treating as a segment rather than a dumping ground: narrow lists produce campaigns you can actually judge.
What a lead carries
- Identity fields such as name, email address and company.
- Custom fields from your import, or produced by enrichment and AI columns. These are what personalization draws on.
- A pipeline stage, which is where the lead sits in your sales process.
- Tags, which cut across stages.
- Activity, being what was sent and what came back.
A lead can be in more than one campaign over time; its stage, tags and activity follow the lead, not the campaign.
Import identity and existing People
Imports match People by social member ID or personal social profile URL. Email is an attribute, not an automatic Person identity key. Companies are matched by social company ID, company social profile URL, or website domain; company names alone are not merged.
By default, importing a matching Person reuses that CRM record and creates a
campaign enrollment unless the Person is already enrolled there. Clients can
send skipExistingPeople: true to exclude rows matching People already in the
workspace. The older skipDuplicates input remains a compatibility alias.