> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/labs/workflow-tools/generative-analytics-dashboards.md).

# Generative Analytics Dashboards

AI-generated custom components that render subscription analytics — usage data, order history, payment trends — directly inside the Limio Page Builder. Instead of static reports or exporting to a BI tool, describe the dashboard you need and have it generated as a live component.

<figure><img src="https://2795969304-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq9wdhXZqegnxpmXpYfIT%2Fuploads%2Fgit-blob-12bb8a217af15cdb7ddeedc307d6d550f2b3c742%2FScreenshot%202026-03-24%20at%2013.29.31.png?alt=media" alt=""><figcaption></figcaption></figure>

## How it works

This builds on Limio's [MCP Server](https://docs.limio.com/product/mcp-server/mcp-server) (which can query order and subscription data). Ask for a report, and the system fetches the data via MCP and generates a visual component to render it.

For example, you could ask for a breakdown of orders by offer over the last 30 days, and receive a chart component that renders directly in your Limio pages. The component is a real custom component - configurable, deployable, and reusable.

## Why it matters

You can show much richer subscription data without a full development cycle. This is an early exploration of what that looks like: AI-powered, on-demand analytics built on the same component architecture that powers the rest of your Limio pages.

***

{% hint style="info" %}
**This is a Labs feature.** We're experimenting with this and it's not yet part of the core platform. Interested in early access or want to help shape it?

[Request access →](mailto:hello@limio.com?subject=Labs%20—%20Generative%20Analytics)
{% 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://docs.limio.com/labs/workflow-tools/generative-analytics-dashboards.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.
