> For the complete documentation index, see [llms.txt](https://docs.quanti.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quanti.io/key-concepts/concepts/connected-account.md).

# Connected Account

In QUANTI:, a **Connected Account** refers to a user account within a data source. Each platform uses its own terminology. Facebook Ads calls them *ad accounts*, Google Analytics 4 calls them *properties*, Instagram Insights calls them *profiles*. In QUANTI:, all of them are called Connected Accounts.

When a connector does not have an account concept of its own, the connector instance itself counts as a single Connected Account.

A Connected Account always belongs to a single [Data Source](/key-concepts/concepts/data-source.md). You can create multiple Connected Accounts from the same Data Source. For instance, two different Meta Ads ad accounts for two different markets.

Connected Accounts are the **unit of billing** in QUANTI:. The number you can activate depends on your plan:

| Plan       | Connected Accounts |
| ---------- | ------------------ |
| Free       | 1                  |
| Pro        | 5                  |
| Growth     | 15                 |
| Expert     | 50                 |
| Enterprise | Unlimited          |


---

# 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 dynamically by asking a question.

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

```
GET https://docs.quanti.io/key-concepts/concepts/connected-account.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.