> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/common-chart-configuration.md).

# Common Chart Configuration

When setting up a visualization, you can select how your data should be aggregated. These aggregations define how raw values are summarized and displayed in the chart. The available options include:

* **Sum** – Adds all numeric values in the column.
* **Average** – Calculates the arithmetic mean of the values.
* **First** – Returns the first value in the column based on the dataset order.
* **Last** – Returns the last value in the column based on the dataset order.
* **Maximum** – Returns the highest numeric value in the column.
* **Minimum** – Returns the lowest numeric value in the column.
* **Count** – Counts the total number of rows.
* **Count Distinct** – Counts the number of unique values in the column.
* **No Aggregation** – Displays the raw data without summarizing. Secondary values cannot be aggregated in this mode.

All aggregations are applied **per group of dimensions** defined in the chart configuration—most commonly labels or x-axis values, but they can also include other groupings like segments or packs.

{% hint style="info" %}
**Hint**

Dimensional columns support only the *Count* and *Count Distinct* aggregation methods, as other types of summarization are not applicable.
{% endhint %}


---

# 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-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/common-chart-configuration.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.