Skip to main content

What is the data model?

The data model defines the types of data your workspace tracks. Each type of data is called an object — for example, Accounts, Users, Subscriptions, and Companies are all objects. Each object contains records (individual entries) and properties (fields that describe each record). You can customize your data model to match how your business works.

High-level data model

At a high level, Bigdelta organizes your data around core objects and the relationships between them. The diagram below shows how Accounts, Users, Subscriptions, and other objects connect to form a unified view of your customers and their activity.
High-level diagram showing how core Bigdelta objects such as Accounts, Users, Subscriptions, and Events relate to each other

Online status

Companies, Accounts, and Users all have an online status. This signal is collected by the Bigdelta SDK, which tracks activity from the users who are actively using your product. The status rolls up from users to the accounts and companies they belong to, so you can quickly see who is currently engaged at every level of your customer hierarchy.

Revenue and Payments

Revenue and Payments data comes from your Payments integrations — for example, Stripe, PayPal, Solidgate, or PayMe. Once connected, Bigdelta syncs payment events and revenue records and attaches them to the matching Companies and Accounts. Revenue and Payments are tracked separately for Companies and for Accounts. They are not shared between the two levels because the calculations and logic for revenue metrics differ depending on whether you look at them per company or per account. For example, a company can still be paying overall even when one of its accounts has already churned. Keeping revenue data separate at each level ensures that metrics like MRR, churn, and expansion reflect reality at the level you are analyzing — and that an event on one account does not distort the financial picture of the parent company.

Account subscriptions

Subscriptions belong to Accounts. An account can have one or more subscriptions, each representing a plan the customer is currently on or was on in the past. Subscription records carry details like the plan, billing period, status (trialing, active, paused, canceled), and start and renewal dates. Subscription data is synced from your Payments integrations and is what Bigdelta uses to assign a Revenue Stage — for example, Paying, Trialing, Non-Paying, or Churned — to each account. Because subscriptions live at the account level, a single company can have accounts on different plans, trialing alongside paying, or churned alongside active — and each account’s subscription history is preserved independently.

Viewing and configuring objects

  1. Go to SettingsData.
  2. You will see a list of all objects in your workspace (Accounts, Users, Subscriptions, etc.).
  3. Click any object to open its configuration.

Object settings

When you open an object, you can configure the following:
SettingDescription
Display namesSet the singular and plural names for the object (e.g., “Account” and “Accounts”)
Label propertiesChoose which fields display as the record name throughout Bigdelta
Icon propertySelect a property to use as the visual icon for records

Adding custom properties

Properties are the fields that make up each record. To add a new property to an object:
  1. Open the object from SettingsData.
  2. Click Add Property.
  3. Choose a name and select the property type.
  4. Configure any additional options for the property.

Creating custom objects

If the built-in objects do not cover your needs, you can create your own:
  1. Go to SettingsData.
  2. Click Add Object.
  3. Set the object name and configure its properties.
Custom objects work just like built-in objects — you can create views, build reports, and set up automations with them.

Property types

The following property types are available when adding fields to an object:
Property typeDescription
TextFree-form text field
NumberNumeric value
CheckboxTrue/false toggle
SelectDropdown with a single choice
Multi-SelectDropdown with multiple choices
StageUsed for board views to organize records into columns
DateDate picker
Date and TimeDate and time picker
CurrencyMonetary value with currency symbol
EmailEmail address
Phone NumberPhone number
Full NameFirst and last name
LocationGeographic location
DomainWebsite domain
Link HandleURL or link reference
Image/ThumbnailImage upload or thumbnail
Time ZoneTimezone selector
MemberReference to a workspace team member
RelationLink to a record in another object
The Stage property type is required if you want to use board views for an object. Make sure to add one before switching to a board layout.