> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/customer-hub/getting-started.md).

# Getting Started

All necessary technical operations are concentrated in the initial configuration phase, which takes less than one hour. Following this phase, non-technical users can use DinMo autonomously.

{% hint style="success" %}
Here is a step-by-step tutorial explaining how the Customer Hub should be configured:

* Import your **Profiles** and [configure your **Schema**](/customer-hub/getting-started/schema-configuration.md)
* [Build your first metric](/customer-hub/getting-started/metrics-configuration.md)
* [Build your first audience](/customer-hub/getting-started/audience-creation.md)
* When ready, **activate the** [**Profiles API**](/customer-hub/profiles-api.md) to query profiles in real‑time from your apps.
  {% endhint %}

## **Need Help?** <a href="#need-help" id="need-help"></a>

We are here to help you with any of your needs. [Send us a message](mailto:support@dinmo.io) and one of our product specialists will get back to you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/customer-hub/getting-started.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.