> For the complete documentation index, see [llms.txt](https://docs.thryve.health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thryve.health/thryve-product-overview/understand.md).

# Understand

Accessing data is just the start. True value lies in effectively analyzing and interpreting it to create exceptional experiences.

In data analysis, understanding two key aspects is crucial for effective data management:

* **The context of data recording:** How was the data collected? Understanding this helps in assessing its accuracy and relevance.
* **Interpreting data for insights:** What does the data mean? Analyzing data meaningfully to gain actionable insights is vital.

Knowing the creation process enhances data accuracy assessment. Therefore, we provide standardized annotations about measurement context when available. Explore our [data annotations](https://docs.thryve.health/thryve-product-overview/understand/data-annotations.md) for further context.

[Thryve Analytics Platforms](https://docs.thryve.health/thryve-analytics-platform/overview.md) excel in turning raw data into clear interpretations. Rooted in scientific evidence, our calculations guide organizations toward informed decision-making.&#x20;


---

# 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.thryve.health/thryve-product-overview/understand.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.
