# How can I access insights or analytics?

To access your Docs site's insights, navigate to your chosen Docs site and scroll down to the **Insights** in the dashboard. You can read more about how we calculate the content scores and how you can export the most searched terms in [our documentation.](https://gitbook.com/docs/published-documentation/insights)

Insights give you information on the content you've published and how it performs. It's split up between two sections — **user scores** and **search analytics**.

To access your Docs site's insights, navigate to your chosen Docs site and scroll down to the **Insights** in the dashboard. You can read more about how we calculate the content scores and how you can export the most searched terms in [our documentation.](https://gitbook.com/docs/published-documentation/insights)

{% hint style="info" %}
Site insights are available as part of the Pro plan and Enterprise plan. To find out more, [visit our pricing page](https://www.gitbook.com/pricing).
{% endhint %}

#### Integrations

You can also integrate your Docs sites with Google Analytics, Heap, Plausible, Toucan Toco, Fathom, Hotjar, Segment, or PostHog to track traffic in your tool's dashboard.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/published-documentation/site-insights/how-can-i-access-insights-or-analytics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.