> For the complete documentation index, see [llms.txt](https://help.meetmadison.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meetmadison.ai/reports/overview.md).

# Reports

See how your reviews, listings, and social media are performing.

The **Reports** section turns your data into clear, easy-to-read insights. Use it to see how your reputation is improving, how customers are finding you on Google, and how your social media is performing. There's nothing to set up. Your reports are always ready to view.

## Using a report

Most reports let you:

* **Choose a date range** (the default is the last 30 days, compared with the period before it).
* **Filter by location**: reports show one location at a time.

Charts and figures update to match what you've selected. Numbers refresh automatically, so very recent activity may take a short while to appear.

Some reports also let you **Export CSV** to download the figures for the date range you're viewing.

## Reports available

<details>

<summary>Review performance</summary>

* **Reviews overview**: a summary of your reviews across all platforms, including how many you've received and your average rating, with a breakdown by star rating.
* **Review ratings**: how each month's reviews are affecting your overall rating.
* **Net Promoter Score**: a measure of how likely your customers are to recommend you.
* **Direct review requests**: how the requests your team sends by hand are converting, broken down by who sent them. See [Direct review requests report](/reports/direct-review-requests.md).
* **Review request links**: which of your shareable links and QR codes are bringing in responses. See [Review request links report](/reports/review-request-links.md).

</details>

<details>

<summary>Google performance</summary>

* **Google performance**: how your Google Business Profile is doing, including how often people see it.
* **Google actions**: what people do after finding you on Google, such as calling you, visiting your website, or asking for directions.
* **Google organic traffic**: the search terms bringing people to your listing, split into searches for your name and searches that discovered you.
* **Rank tracking**: where your business ranks in Google search for the terms Madison tracks, over time.

</details>

<details>

<summary>Social performance</summary>

* **Social actions**: how people are interacting with your social profiles each month: engagement (likes, comments, and shares) on Facebook and Instagram, and check-ins at your location on Facebook.

</details>

{% hint style="success" %}
Check your reports monthly to spot trends, like a rise in reviews after sending [review requests](/reputation/review-requests.md).
{% 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://help.meetmadison.ai/reports/overview.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.
