A Targetable People column stores the people associated with each list row. It supports manual people, contact enrichment, people-specific views, and outreach targeting. You can also prefill it from a JSON column or a CRM data column configured to list contacts.
#Add a Targetable People column
- Open the list and select Manage columns.
- Select Add.
- Choose Targetable People as the column type and give the column a name.
- Optionally select a source under Prefill people.
- Create the column, then run the relevant cell, row, or column to merge source people into it.
#Supported prefill sources
- JSON column: Select any JSON column that contains an array of people or one of the supported envelopes below.
- CRM List contacts column: Select a CRM data column configured with Resolve > List contacts.
- CRM contact association: A custom-object association that resolves Contact records is also supported.
#Recommended JSON structure
The simplest source is an array of person objects. Each person must have a first name or full name. All other fields are optional.
[
{
"first_name": "Jordan",
"last_name": "Lee",
"email": "jordan.lee@example.com",
"phone_number": "+31 6 1234 5678",
"linkedin_profile_url": "https://www.linkedin.com/in/jordan-lee-example",
"title": "Revenue Operations Lead",
"bio": "Leads revenue operations and go-to-market systems.",
"avatar_url": "https://example.com/jordan-lee.jpg",
"target": true
}
]#Supported JSON envelopes
Bigmind accepts the direct array above and these common wrapper shapes:
{
"people": [
{ "first_name": "Jordan", "email": "jordan.lee@example.com" }
]
}{
"records": [
{ "FirstName": "Jordan", "Email": "jordan.lee@example.com" }
]
}{
"record": {
"firstName": "Jordan",
"email": "jordan.lee@example.com"
}
}#Recognized person fields
Field matching ignores capitalization and separators, so first_name, FirstName, firstName, and firstname are treated as the same field. Bigmind also recognizes common CRM aliases:
| Targetable People field | Accepted examples |
|---|---|
| First name | first_name, firstName, givenName, forename |
| Full name | full_name, fullName, name, displayName |
| Last name | last_name, lastName, surname, familyName |
email, emailAddress, primaryEmail, workEmail, emailAddress1 | |
| Phone | phone_number, phoneNumber, phone, mobilePhone, businessPhone, workPhone, telephone1 |
| LinkedIn URL | linkedin_profile_url, linkedinProfileUrl, linkedinUrl, linkedin, hs_linkedin_url |
| Title | title, job_title, jobTitle, position, role |
| Bio | bio, description, biography, about |
| Avatar | avatar_url, avatarUrl, photo_url, photoUrl, profileImageUrl |
Person fields may be at the top level of each record or nested inside a properties or fields object. This supports the different record shapes returned by CRM providers.
#How merging works
- Bigmind matches people by email, LinkedIn URL, phone number, or full name.
- Source people are added to the Targetable People column.
- Manual edits and values already stored in Targetable People take precedence over the source.
- Existing enriched values and their enrichment metadata are preserved when you rerun the cell, row, or column.
- People that exist only in Targetable People are kept; rerunning does not delete manually added people.
#Missing contact details
Your source does not need to contain every Targetable People field. For example, CRM contacts may have a name and email but no LinkedIn URL. After the people are merged, configure enrichment for the missing email, phone, or LinkedIn fields and run it from the people view.
If a source person has none of those targetable contact channels, Bigmind keeps the person with targeting disabled until you add or enrich a channel.
#Troubleshooting
- The source column is not available: Confirm it is a JSON column, a CRM List contacts column, or a CRM association that resolves Contact records.
- A record was skipped: Include a first-name field or a full-name field in that record.
- Two entries did not merge: Ensure they share an email address, LinkedIn URL, phone number, or the same full name.
- A CRM custom field is missing: Import that field into Bigmind, then add it under Fields in the CRM data column.
- A contact detail is missing: Configure and run enrichment for that Targetable People field.