> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/customer-intelligence/exploration-and-analysis/custom-charts-in-exploration-pages.md).
# Custom charts in Exploration pages
#### What's New
Previously, any changes you applied to a chart were temporary and valid only during your navigation.\
Now, you can edit chart settings and save them, so your customized chart will remain available every time you return.
{% hint style="info" %}
Saved customizations are personalized. Your changes won’t affect other users’ charts.
{% endhint %}
## Default Chart Settings
When you first open an exploration page, the chart will display:
* Chart type: Line chart
* Metric: Overall Count
* Breakdown: Aggregated at the Organization level (all data, no breakdown)
## How to Customize Your Chart
1. Click Edit chart.
2. Select your chart type.
3. Go to the setup tab.
4. In Metric, select the metric you want to track.
5. In Breakdown, choose how to segment your data.
* Use the Selection button (on the right) to narrow down the values of the chosen dimension.
* Example: You can break your chart by Customer Segments, but only include Customer Tier segments by applying a filter.
6. Optionally, limit breakdown values to the top N.
* The chart will show only the top N values, ranked by your chosen metric.
7. If using a pivot table, configure breakdowns for both rows and columns.
Once you’re happy with the setup, click Done. Your customized chart will be saved and ready for you next time.
{% hint style="warning" %}
Customizations are applied globally across all exploration pages. You can’t save different setups per page, but you can edit and change them at any moment.
{% 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://ask.birdie.ai/customer-intelligence/exploration-and-analysis/custom-charts-in-exploration-pages.md?ask=&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.
