Custom Objects Overview

Custom Objects are unique data points linked to your customers, representing various information such as revenue contracts (Deals or Opportunities), customer escalations, and more. You can create them manually in Vitally or bring them in from an external system. See Ways to create Custom Objects below for every supported route. Custom Objects on the Account level will automatically roll up to the Organization level if you have hierarchy enabled!

Manually created Custom Objects can be associated with multiple Accounts and/or Organizations.

The Owned by Field

Every Custom Object, including Opportunities, has a built-in Owned by field showing which internal user owns the record. This field is separate from the object's traits, it doesn't appear in Settings → Custom Objects → Traits, so it can't be given an editing permission level, hidden, or locked the way traits can. Only Admins, Leaders, and Team Members can be selected in the Owned by field. Observers are not selectable, even if they previously held a full seat and were reassigned to Observer. If an Observer was already set as the owner before the role change, Vitally keeps showing them as the existing owner, but that is retained data rather than a new assignment. See User Roles & Permissions for the full list of role capabilities.

You can remove the Owner column from a specific table or board view, but that only changes how that view displays the object, opening the record itself will still show the Owned by field.

Manually Create Custom Objects

Custom Objects can be created manually without relying on an integration. They'll automatically generate as a Draft until you're ready to finalize the record and create it. Additionally, some integrations support bi-directional Custom Objects so they can be manually created in Vitally and sync back to your source of truth. See Ways to create Custom Objects for more information.

How To	How To Visual
How to manually create a Custom Object Navigate to your Settings (⚙️) by selecting your Account Logo on the top left and under Custom Object select the plus sign to the right Then select Create a custom object in Vitally (or via Quick Jump Mac: `⌘ + j` Windows: `Alt + j`) Name your Custom Object and select your permissions to allow, or not allow, team members to create these custom objects If you need to edit the name or permission for your custom object: Select Edit to the right of the custom object From there, you can edit the name or change the permissions on who should be allowed to create a new opportunity.
Adding Properties to your Custom Object Once you've created the Custom Object, select Edit to the right Select Configure Fields Select Create Custom Trait Now you can create those traits (i.e Issue ID, Status, Title, etc) Now build your Zap to bring in that Custom Object!

Each object instance will include an automatically generated open text area for the description. This is not mapped to a property, and its contents are not included in table views or exports.

Configure a Custom Object layout

By default, any new Custom Objects type that is synced will have its associated traits displayed alphabetically. By using Custom Objects layouts, you can organize traits in a more useful way.

How-To

How-To Visual

To create a custom object layout:

Navigate to your Settings (⚙️) by selecting your Account Logo on the top left and under Custom Object select the Custom Object
Select the meatball menu on the top right (three dots) then select Manage layout on the custom object for which you would like to create a layout
Select Create a Layout
Configure the layout of the custom object by:
- Adding Headers to organize and group traits
- Dragging and dropping the traits to reorder
- Removing traits that you don't wish to see

All changes are auto-saved and the layout will be applied the next time the Custom Object is viewed.

In a Custom Object's field configuration, traits linked to an integration display that integration's icon next to the trait name (for example, a Salesforce or HubSpot icon). Custom traits created in Vitally appear without an icon, making it easy to tell the two apart when an object mixes both trait types.

Visualizing Custom Objects in Vitally

Once your Custom Objects are imported into Vitally, you'll be able to leverage them in practically identical ways as you can your tasks, notes, and other 'main' Vitally features.

Table View

Create a Table View to visualize Custom Objects with columns on the Custom Object, Account, or Org level. For example, you can easily save a Table View (i.e. a report) showing Opportunities with a 'Close Date' within the next 3 months (for example).

Dashboards

You can use your Custom Objects alongside Vitally's Dashboard feature. For example, you can build dashboards showcasing a breakdown of Case types, total ARR across a dynamic set of Opportunities, and much more!

Boards

Create kanban-style boards that you can use to visualize Custom Object data in a workflow structure.

Account Columns

For every Custom Object you sync into Vitally, you can leverage columns/filters on your Accounts for 1) the total Custom Objects that the Account has (e.g. number of Opportunities) and 2) the last time a Custom Object was created (e.g. last Opportunity created date).

You'll see this same interface throughout Vitally anytime you'd like to use Custom Objects - in playbook automation, health scores, etc.

Ways to create Custom Objects

Custom Objects can be created in Vitally directly or brought in from an external system. This includes standard objects as well as any custom objects you have created in your external source.

Manually in Vitally. See Manually Create Custom Objects above.
Salesforce
Hubspot
Jira
Data warehouses: BigQuery, MySQL, PostgreSQL, Redshift, and Snowflake. See Syncing Custom Objects.
Analytics API: the /customobjectinstance endpoint, which can also be called through the batch endpoint with a type of customobjectinstance. See Vitally's HTTPS Analytics API - Custom Object Instances.
REST API. See REST API: Custom Objects, and REST API: Bulk POST Requests through Postman for bulk loads.
Zapier. See Zapier.

S3 and CSV Upload do not support Custom Objects. The S3 integration imports Account, Organization, User, NPS, and Track data only, and CSV Upload cannot create or update Custom Object instances.