In Breyta, object types refer to schemas or blueprints that define the structure of individual entities, or what we call objects. The purpose of object types is to ensure consistent and structured data for specific categories such as 'Companies' or 'People.' This consistency makes it easier to work with and interpret the data.
Object type components
An object type is made of three key components: Data fields, Title fields, and Identifiers.
1. Data fields
Data fields are containers that gather the same type of data attribute from various sources. For example, the 'GroupID' data field collects 'GroupID' data from Segment, Intercom, and Salesforce. While each of these tools may have its own 'GroupID' field, consolidating them in Breyta provides a unified and comprehensive view of 'GroupID' data across all integrated tools. Simply, you can connect like data from across your integrations into a single field.
By grouping similar types of data, data handling becomes more efficient, and it helps maintain clean and organized data within your workspace.
An example of grouped data within the Email data field:
2. Title Fields
Title fields determine which information is displayed as the title when the object appears in search results and lists. Including multiple title fields provides a fallback option when the primary Title field data value is empty.
3. Identifiers
Identifiers refer to unique keys or data attributes that distinctively define and differentiate individual data objects. Identifiers ensure the accurate correspondence of data across various sources, maintaining the precision and consistency of data within your workspace. Just as a book in a library is identified by its unique ISBN or a product in a store is identified by its unique barcode, identifiers assist in precisely locating, linking, and managing data within Breyta.
For instance, in the default 'Companies' object type, identifiers are GroupID, SalesforceID, HubspotID, and domain. These identifiers are unique to each company, enabling accurate linking and grouping of data about the same company from different sources such as Salesforce or Hubspot.
Adding identifiers
When adding identifiers in Breyta, it is important to avoid including non-relevant fields as identifiers. Doing so can result in inaccurate or misleading grouping of data objects across different data sources, potentially causing a variety of issues.
An identifier should ideally be a unique attribute that distinguishes one data object from all others. If a non-relevant or non-unique field is mistakenly used as an identifier, the following problems may arise:
Data Mismatch: The system might incorrectly link unrelated data objects from different sources based on this non-unique or irrelevant identifier, leading to inaccurate data aggregation.
Data Duplication: If the non-relevant field is not unique, the system may not be able to differentiate between different data objects correctly, resulting in duplicate entries.
Compromised Data Integrity: Over time, incorrect linking or duplications can severely compromise the integrity and reliability of the data within the system.
Impaired Analysis and Decision-making: Inaccurate data linkage or duplication can lead to flawed insights and decisions based on that data, potentially causing issues or inaccuracies in reporting, analysis, and decision-making processes.
We can't stress this enough, it is important to carefully select the fields set as identifiers, ensuring they are both unique and relevant. This ensures the accuracy and integrity of the data within the system.
🌟 Unsure about which identifiers to add to your object types? Reach out to support via your in-app chat bubble.
Default Object Types
Using default object types offers several advantages compared to creating object types from scratch. By using default object types, you can immediately benefit from preconfigured fields and identifiers that Breyta recognizes as crucial for effective data management.
Breyta provides two default object types: Companies and People. While these default object types come with preconfigured data fields and identifiers, but you also have the option to build on according to your specific needs.
Creating a default object type
From the Object Type page, click + Add
Select Enable a default object type
Select Companies, then enable
Repeat steps to enable People default object type
Companies
The default Companies object type represents the schema or blueprint for a company object. The object type defines the attributes – represented as data fields – associated with a company.
People
The default People object type represents the schema or blueprint for a person object. The People object type would define the attributes – represented as fields – associated with a person.
