> For the complete documentation index, see [llms.txt](https://docs.sumble.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sumble.com/system-setup-and-configuration/data-fields.md).

# Data fields

The fields Sumble pulls from your CRM or data source to match accounts and users, and which ones are required.

Sumble matches the records you share to its own data. This page lists the fields we use for each record type and which ones you must provide. The integration pages for [Salesforce](/system-setup-and-configuration/crm/salesforce-package.md), [HubSpot](/system-setup-and-configuration/crm/hubspot.md), [Snowflake](/system-setup-and-configuration/data-destinations/snowflake-share.md) and the other sources link here.

Use whatever column or property names are natural for your system. Your Sumble account team maps them to the fields below during setup.

## Accounts

Sumble uses these fields to match your accounts to organizations in its database.

| Field                      | Required | Description                                                |
| -------------------------- | -------- | ---------------------------------------------------------- |
| Account ID                 | Yes      | Unique identifier for your account.                        |
| Account Name               | Yes      | The account's organization name.                           |
| Account URL                | Yes      | Primary URL or domain of the account.                      |
| Account LinkedIn URL       | No       | URL of the account's LinkedIn page.                        |
| Country                    | No       | Country where the account's organization is headquartered. |
| Address                    | No       | Headquarters address of the account's organization.        |
| Parent Account ID          | No       | Unique identifier of the account's parent organization.    |
| Ultimate Parent Account ID | No       | Unique identifier of the account's top-level parent.       |
| Alternate Names            | No       | Other names the account's organization is known by.        |
| Alternate URLs             | No       | Other URLs associated with the account's organization.     |

## Users

Users are the people on your team who own accounts, such as reps and account managers. Sumble uses them to map account owners to Sumble users, so each person sees signals and alerts for the accounts they own. Sumble pulls users from your CRM, so this applies to Salesforce and HubSpot.

| Field         | Required | Description                              | Typical Salesforce field |
| ------------- | -------- | ---------------------------------------- | ------------------------ |
| User ID       | Yes      | Unique identifier for the user.          | `Id`                     |
| Name          | Yes      | The user's full name.                    | `Name`                   |
| Email         | Yes      | The user's work email address.           | `Email`                  |
| Title         | No       | The user's job title.                    | `Title`                  |
| Manager ID    | No       | Unique identifier of the user's manager. | `ManagerId`              |
| Manager Name  | No       | The manager's full name.                 | `Manager.Name`           |
| Manager Email | No       | The manager's work email address.        | `Manager.Email`          |
| Manager Title | No       | The manager's job title.                 | `Manager.Title`          |

Sumble also keeps any other user fields you ask us to pull, such as a region or team. Tell us which ones during setup.