# Overview

{% hint style="info" %}
The Customer Hub is an additional module and only available on the Enterprise Plans.
{% endhint %}

The **Customer Hub** is DinMo’s marketer‑first interface that turns warehouse data into actionable customer insights. It gives marketing teams a 360° view of their customers, lets them build and analyse audiences, and measures the real impact of every activation.

> **Prerequisites**\
> • Customer Hub module enabled by your account manager
>
> • A connected and active data source
>
> • A **parent model** of type *Users* selected as the source for Profiles

***

### Why the Customer Hub matters?

Traditionally DinMo focused on data movement for data teams. Customer Hub shifts the centre of gravity to **marketers**, letting them:

1. **Understand** customers and key metrics without SQL.
2. **Act** through segmentation, orchestration, and sync.
3. **Measure** outcomes over time—including true uplift via A/B tests.

Less back‑and‑forth with data teams, faster iteration, clearer ROI.

***

### Key Concepts

| Concept                 | What it is                                                                                                                                                                                                          | Why it matters                                                                         |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| **Profile**             | A record derived from a *Users* parent model. Includes identifiers (email, user\_id, anonymous\_id), native attributes, plus **computed** attributes such as audience membership flags and latest metric snapshots. | Single source of truth for each person; fuels the Profiles API and Customer Hub views. |
| **Metric**              | An aggregate measure computed on an *Events* / *Transactions* model (e.g. revenue, number of orders, AOV). Metrics can be calculated **per profile** *and* rolled‑up **per audience**.                              | Lets you benchmark audiences and quantify campaign impact.                             |
| **Audience**            | A cohort—subset of Profiles—built either by importing an existing segment from the parent model or by using DinMo’s Audience Builder.                                                                               | Targeting unit for activations, experiments, and reporting.                            |
| **Membership Tracking** | Option on an audience to store entry/exit timestamps.                                                                                                                                                               | Enables churn windows, win‑back logic, and trend charts.                               |
| **Control Group**       | A percentage of an audience excluded from treatment.                                                                                                                                                                | Unlocks A/B testing and uplift measurement on chosen metrics.                          |
| **Profiles API**        | Low‑latency REST API that surfaces profile data (identifiers, attributes, audience flags, metrics) once Customer Hub is configured.                                                                                 | Power onsite personalisation and decisioning with <30 ms p99 latency.                  |

***

### What you can do in the Customer Hub

#### 🔍 Profiles Explorer

* Search by any identifier
* Inspect attributes & computed fields
* View activity timeline (events, audience entry/exit)

#### 📊 Audience Metrics Dashboard

* Out‑of‑the‑box metrics: Revenue, Orders, AOV
* Custom metrics built with your formulas
* Compare audiences side‑by‑side

#### ✂️ Audience Builder

* Visual and natural‑language filters on Profiles
* Import existing segments from the parent model
* Toggle **membership tracking** and pick **metrics to monitor**

#### 🧪 Experiments

* Split an audience into **Treatment** and **Control**
* Track uplift on any selected metric
* Export results or sync winning segments

***

### Who is the Customer Hub for?

| Persona                          | Benefits                                             |
| -------------------------------- | ---------------------------------------------------- |
| **CMO / VP Marketing**           | Always‑on view of marketing KPIs and audience trends |
| **Growth / Lifecycle Marketers** | Self‑serve segmentation, activation, and testing     |
| **Performance Marketers**        | Measure true incremental uplift without SQL          |

Data teams remain owners of data models but no longer need to:

* Write ad‑hoc analysis SQL
* Set up experiments manually
* Interpret campaign results for marketing

***

## Ready to get started?

Book a demo and we will walk through the best way to launch your first DinMo use case.

[Book a demo](https://www.dinmo.com/contact/)

## Need help?

Our team is here to help with setup, modeling, activation, and troubleshooting.

[Contact us](mailto:hello@dinmo.com?subject=Docs%20help)

## Feature requests?

Tell us which connector, workflow, or improvement would make DinMo more useful for your team.

[Request a feature](mailto:hello@dinmo.com?subject=Feature%20request)

[Privacy Policy](https://www.dinmo.com/legals/privacy/) | [Terms of Service](https://www.dinmo.com/terms-of-service/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dinmo.io/customer-hub/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.