> 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, users and people, and which ones are required.

Sumble matches the records you share to its own data. This page is the one list of the fields we use for each record type and which ones you must provide. The pages for [Salesforce](https://docs.sumble.com/system-setup-and-configuration/crm/salesforce-package.md), [HubSpot](https://docs.sumble.com/system-setup-and-configuration/crm/hubspot.md), [Snowflake](https://docs.sumble.com/system-setup-and-configuration/data-destinations/snowflake-share.md), [Databricks](https://docs.sumble.com/system-setup-and-configuration/data-destinations/databricks.md), [BigQuery](https://docs.sumble.com/system-setup-and-configuration/data-destinations/bigquery.md) and [blob stores](https://docs.sumble.com/system-setup-and-configuration/data-destinations/blob-store.md) link here.

Use whatever column or property names are natural for your system. If you connect Salesforce or HubSpot from **My Team > Integrations**, a customer admin maps the fields there. For a warehouse or file source, your Sumble account team maps them 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 Owner ID           | No       | User ID of the rep who owns the account. Needed to route signals and alerts to the owner; must match a User ID in the [users](#users) list. |
| 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, sees account status and CRM data for their own accounts in the web app, and managers see their direct reports' accounts.

Sumble pulls users from Salesforce or HubSpot. If your accounts come from Snowflake, BigQuery, Google Cloud Storage or S3 instead, send a users table alongside them with one row per user.

| Field         | Required | Description                                                                       | Typical Salesforce field |
| ------------- | -------- | --------------------------------------------------------------------------------- | ------------------------ |
| User ID       | Yes      | Unique identifier for the user. Must match the Account Owner ID on your accounts. | `Id`                     |
| Name          | Yes      | The user's full name.                                                             | `Name`                   |
| Email         | Yes      | The user's work email address. Use the address the rep signs in to Sumble with.   | `Email`                  |
| Title         | No       | The user's job title.                                                             | `Title`                  |
| Manager ID    | No       | Unique identifier of the user's manager. Must match another user's User ID.       | `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.

Each pull reads the full list. Users no longer in it are removed from the active user list. If a pull returns no users while Sumble already has some, Sumble skips the removal, so a broken source can't empty your user list.

## People

People are the contacts and leads in your CRM. Sumble uses them for champion tracking. It matches each person to a profile in its own data, and sends a [champion alert](https://docs.sumble.com/our-data/signals.md#champion-alerts) when someone you marked as a champion changes companies.

Sumble pulls people from Salesforce Contacts and Leads, or from HubSpot Contacts. If your data lives in Snowflake, BigQuery, Google Cloud Storage or S3 instead, send a people table with one row per person. Your Sumble account team maps the fields during setup.

| Field              | Required     | Description                                                                                       | Typical Salesforce field |
| ------------------ | ------------ | ------------------------------------------------------------------------------------------------- | ------------------------ |
| Person ID          | Yes          | Unique identifier for the person.                                                                 | `Id`                     |
| Name               | Yes          | The person's full name.                                                                           | `Name`                   |
| Company Account ID | One of three | Account ID of the person's employer. Must match an Account ID in your [accounts](#accounts) list. | `AccountId` on Contact   |
| Company Name       | One of three | Name of the person's employer.                                                                    | `Company` on Lead        |
| Email              | One of three | The person's work email address. Sumble reads the employer from its domain.                       | `Email`                  |
| LinkedIn URL       | No           | URL of the person's LinkedIn profile.                                                             |                          |
| Is Champion        | No           | Boolean. `true` if Sumble should track this person for job changes, `false` if not.               |                          |

Sumble matches a person on their name plus their employer, so each row needs a name and at least one of Company Account ID, Company Name and Email. A personal address, such as one at gmail.com, doesn't identify an employer. Sumble stores a person it can't match, but can't track them.

### Is Champion

Is Champion says whether Sumble tracks the person for job changes. Send a boolean, or the text `true` or `false`. An empty value counts as `false`. Sumble stores every person you send and tracks only the ones marked `true`.

If your source has no such column, who Sumble tracks depends on the source:

* Snowflake: every person in the table.
* BigQuery, Google Cloud Storage and S3: no one, so include the column.
* Salesforce: the Contacts returned by a champion query that your Sumble account team sets up with you.
* HubSpot: every Contact that matches the property filters you give us. See [champion tracking in HubSpot](https://docs.sumble.com/system-setup-and-configuration/crm/hubspot.md#champion-tracking).

Each pull reads the full list. People no longer in it stop being tracked.
