> For the complete documentation index, see [llms.txt](https://docs.corraldata.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corraldata.com/kb/explore-your-data/correlation-analysis.md).

# Correlation Analysis

Start exploring real relationships among your data with Correlation Analysis. Just AskCorral to spot the trends and connections.

{% @arcade/embed flowId="iQT7fb5gdZ1TR94hrOkh" url="<https://app.arcade.software/share/iQT7fb5gdZ1TR94hrOkh>" %}

### How it works:

**Ask a question:** Type a natural-language prompt into AskCorral. Be sure to include “correlation” in your question. Example: *“What’s the correlation between campaign spend and client rebookings last quarter?”*

**Review the results:** Get a scatterplot and correlation coefficient with one click.

**Refine on the fly:** Change your variables, adjust your date range, or ask a follow-up question.

#### Correlation is one of the most powerful tools in exploratory analysis. It helps you:

* **Spot trends** in marketing performance
* **Identify factors** that may contribute to retention or churn
* **Explore how spend** **is associated with outcomes** across channels or teams
* **Make smarter, faster decisions** without waiting on BI teams


---

# 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.corraldata.com/kb/explore-your-data/correlation-analysis.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.
