> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/organizations/organization-insights.md).
# Organization Insights
Organization Insights provides a unified analytics view for organizations with multiple domains. Rather than reviewing performance data one domain at a time, you can aggregate and compare metrics across all of your properties from a single report.
Organization Insights is available to users with access to the organization context. To access it, navigate to the organization sidebar and click the **Insights** link, located between **Segments** and **Settings**.
**Selecting a Report**
Use the report dropdown to choose which type of report you would like to run. There are two report types available at the organization level:
* **Notification Report** — Performance data associated with notification deployment, including impressions, clicks, and clickthrough rates across your domains
* **Acquisition Report** — Data associated with the opt-in flow and subscription rates across your domains
**Configuring Date Range and Grouping**
At the top of the report, you can configure the following options:
* **Date Range** — Select an absolute or relative date range to constrain the data. Defaults to the last 7 days.
* **Date Grouping** — Choose the granularity at which dates are broken down in the report:
* **Day** (default)
* **Week**
* **Month**
* **Year**
* **None** — Completely omits the date dimension from the report
---
# 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://documentation.pushly.com/platform/organizations/organization-insights.md?ask=&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.
