Fields are the basic building blocks of a database. The Demandbase database provides a view into your accounts, people, opportunities, and activities.
You can use fields to identify particular rows and columns of data that are important to your business strategy. For example, maybe you want to have access to only the rows (records) of data that have Financial Services for the Industry field, so you can filter by Industry: Financial Services. Industry would be the field label or column header, and Financial Services would be the content of a cell for any row in that industry.
For example, the columns (Name, Source, Industry, etc.) in the following table are fields.
Name |
Source |
Industry |
Employees |
Billing State |
Pipeline Predict Score |
Qualification Score |
|---|---|---|---|---|---|---|
| Account A | Demandbase | Financial Services | 40 | MI | 1.0% | 3.0% |
| Account B | Demandbase | Publishing | 1 | IN | ||
| Account C | CSV | Financial Services | 18 | OR | 1.0% | 2.0% |
To manage fields that sync into the Demandbase database, see Manage Fields in the Database.
To understand how fields are used in the Demandbase database, see Understanding the Demandbase Database.
To understand how to use fields as a selector, see Working with Selectors.
Field Sources
Demandbase syncs and aggregates data for the account, opportunity, people, and activity objects.
- Account: Account data from your CRM, CSV imports, and Demandbase database.
- Opportunity: Opportunity data from your CRM and CSV imports.
- People: People data from your CRM, Marketing Automation System, and CSV imports in the platform. A Person record can be a Lead or a Contact.
- Activity: Activity data from your CRM, Marketing Automation System, CSV imports, Sales Solutions, and Demandbase database. See Understanding Activities.
Field Icons
Throughout Demandbase, we provide icons (in selectors and various Demandbase tables) to help identify a field's data source and object type.
Field Data Source Icons
The following are some examples of field data source icons:
| Data Source | Icon |
| CSV Data Import | |
| Demandbase Database | |
| Eloqua | |
| HubSpot | |
| Marketo | |
| Microsoft Dynamics | |
| Pardot (Marketing Cloud Account Engagement) | |
| Salesforce |
Field Object Type Icons
| Data Type | Icon |
| Account | |
| Person | |
| Opportunity | |
| Activity |
Merged Fields
The Merged Sources icon indicates fields with multiple sources. Hovering over a source icon shows its source.
Tip: We recommend using merged fields for accuracy and to maintain a single source of truth.
Demandbase prioritizes merged field data in the following order:
- CRM
- Marketing Automation System
- CSV Import
- Demandbase Database
The following chart shows the workflow used to determine the merged field source in Demandbase.
For example, if Salesforce determines that a Billing Country is the United Kingdom and the CSV says it's from Spain, the Merged field for Billing Country displays the United Kingdom.
Origin Field for Net New Accounts
Origin is a field populated for Net New Accounts added to the Database by Demandbase. The Origin field can be added to account tables or used as selectors to understand why an account was added to the Database.
For more information about Net New Accounts, see Demandbase Pre-Built Account Lists.
The following Origin values are available:
- Demandbase Engagement: Account visited your website in the past
- Demandbase Intent: Account showed high intent in the past
- Demandbase Qualification Score: Accounts with Qualification Score that meets a precision of greater than 90% and beats the average account.
- Demandbase Unspecified: Accounts added to the Database before the introduction of the Origin field.