Data Model Overview

The data model defines how information is structured inside Adtaria. It determines what you can track, how records relate to each other, and how data flows across pipelines, contacts, tasks, notes, and more.

We built Adtaria with the Data Model first, and then built everything else on top. That’s why things seem to just link together effortlessly.

Core Concepts

Objects

Objects are the main types of data in Adtaria. Each object represents a category of information you track.

Here are the core “Objects” of Adtaria:

• Contacts

• Pipeline

• Pipeline Stage

• Deals

• Tasks

• Notes

• Conversations/Call recordings

• Files & Links

• KPIs

• Conversations (Inbox)

Each object is designed to work together through linking and activity tracking.

Custom objects may be available depending on your plan and permissions.

Object Details

To better understand the structure, below is the details of each object and it’s purpose, this will give you a better understand of how things intertwine.

Contacts

Details:

A person or organization you’d like to be connected with or are connected with.

Can be linked with:

Deals, Conversations, Comments, Activity

Uses:

Contacts are the foundation of a deal, you can create a deal without a contact, but it’s best to have a contact linked to a deal, so you can store the information neatly. Contacts are also built off your conversations on LinkedIn. You can’t message with a deal, you message a contact and create a deal off that contact.

Fields

Fields are the attributes that describe an object. Fields store the actual data.

Examples:

• A Contact has fields like name, email, company, tags

• A Deal has fields like value, stage, pipeline, close date

• A Task has fields like due date, priority, status

Field types may include text, number, date, select, multi-select, and relations.

Fields can be shown or hidden in views without changing the data.

Records

Records are the individual entries inside an object.

Examples:

• A specific person is a contact record

• A single opportunity is a deal record

• A follow-up is a task record

Records are what you work with day to day. Objects and fields define the structure; records fill it with data.

Simple Analogy

• Objects are tables

• Fields are columns

• Records are rows

How Objects Connect

Adtaria is built around relationships.

• Contacts can be linked to deals

• Tasks, notes, conversations, and files can be linked to contacts and deals

• Activity stays connected to the records it belongs to

This keeps context centralized and avoids duplicate data.

When to Use Fields vs Objects

Use a field when:

• It’s just a property of something else

• It only describes a record

• It has a fixed set of values

Examples:

• Priority on a deal

• Status on a task

• Type on a contact

Use an object when:

• It has its own lifecycle

• It can exist multiple times per record

• It connects to multiple other objects

Examples:

• Tasks instead of multiple follow-up fields

• Notes instead of long text fields

• Conversations instead of call summary fields

Keep the Model Simple

Start with fields first.

Only introduce new objects when:

• You are repeating the same data pattern

• A concept needs its own relationships

• You need unlimited instances instead of fixed slots

Avoid creating complexity before you need it.

Special Note on Contacts and Deals

Contacts and deals are the core relationship in Adtaria.

• Most activity should link to one or both

• Filtering, views, and reporting are strongest when data stays connected here

Best practices:

• Use fields and tags to segment contacts instead of creating separate objects

• Use saved views to separate workflows

• Hide fields that don’t apply to every record instead of duplicating objects

Accessing the Data Model

• Go to Settings

• Open Data Model

• View available objects

• Select an object to manage its fields

If you don’t see Data Model in Settings, access may be restricted to administrators.

Next Steps

Once your data model is defined:

• Create or adjust fields

• Customize views around your structure

• Build filters and pinned views on top of clean data