As a native Salesforce app, Dash includes many custom objects that are used for reporting as well as configuration settings.

Below is a list of off of the custom objects that Dash includes and a brief description.

Primary Custom Objects

These custom objects in Dash are used to store most of the data, as well as what's used in most reports and dashboards.

Custom ObjectMaster ObjectDescription
Used to capture and report on Journey Stage transitions.
AttributionJourneyUsed for attribution modeling and reporting.
Journey Summary
Used for summarizing Journey data for funnel metrics.
Engagio Activity
Used to bring in Engagio Activities into Salesforce.

Custom Objects for Configuration and Settings

These Dash custom objects are used for settings and configurations and require very little data storage.

Custom ObjectMaster ObjectDescription
Global Settings
Settings for controlling the main triggers that create Journey records.
Business configuration settings for Journey records and attribution criteria.
Journey Stage SettingsConfiguration
Defines all of the stages of the Journey.
Account Status SettingsConfiguration
Maps the accounts statuses to Journey Stages.
Opportunity Stage SettingsConfiguration
Maps the Opportunity Stages to Journey Stages.
Lead Status Settings
Maps the Lead Statuses to Journey Stages.
Custom Activity FieldsConfiguration
Optional mapping of fields between Engagio Activity Attributes/Segments and the Engagio Activity table in Salesforce.

Salesforce Custom Object Limits

You should review the Salesforce Limits guide to understand the impact of adding any app or custom code to your org.

In the Salesforce Limits guide, you'll see that the custom objects that are contained in a managed package that’s publicly posted on the AppExchange don’t count against the limits for your Salesforce edition.

Therefore, the custom objects included in Dash described above do not count towards your org's custom object limit because Dash is a managed package that's publicly posted on the AppExchange.