> For the complete documentation index, see [llms.txt](https://academy.synap.ac/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.synap.ac/doc/analytics.md).

# Analytics

- [Fractal](https://academy.synap.ac/doc/analytics/fractal.md): Fractal is Synap's approach to question analytics with Tags & Facets, learn about the best practices and how to start setting up your own Facet structure for your use case
- [Tags & facets](https://academy.synap.ac/doc/analytics/tags-and-facets.md): Setting up tags and facets on questions is key to unlocking all of the analytics on platform
- [Facet best practice](https://academy.synap.ac/doc/analytics/tags-and-facets/facet-best-practice.md): Deeper dive into what each facet type does and how to set up your content to make best use of the results pages
- [Student Insights](https://academy.synap.ac/doc/analytics/student-insights.md): A look into Student and Educator insights on Synap
- [Exam statistics](https://academy.synap.ac/doc/analytics/exam-statistics.md): Learn how to use the Question statistics page to make more data driven decisions and gain a new level of insights into your questions.


---

# 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://academy.synap.ac/doc/analytics.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.
