> 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/acquisition-report.md).
# Acquisition Report
#### Acquisition Report
The Acquisition Report provides data about subscriber opt-in performance across your organization. It supports two levels of reporting.
**Organization Level**
The Organization level aggregates acquisition data across all domains.
**Breakdowns:**
* **Delivery Channel**
* **Device Type**
* **Delivery Channel and Device Type**
**Measures (columns):**
* Subscriptions
* Subscription Rate
* Permissions Shown
* Permissions Denied
* Permissions Dismissed
* Prompts Shown
**Filters:**
* **Domain** — Select one or more domains by display name. You can search the list and use **Select All** to quickly choose multiple domains. Remove the filter to include all domains.
**Domain Level**
The Domain level adds an explicit domain breakdown so you can compare acquisition performance across individual domains.
**Breakdowns:**
* **Delivery Channel**
* **Device Type**
* **Delivery Channel and Device Type**
**Dimensions:**
* **Domain Name** — Selected by default
* **Domain ID** — Selected by default; can be deselected
**Measures (columns):**
* Subscriptions
* Subscription Rate
* Permissions Shown
* Permissions Denied
* Permissions Dismissed
* Prompts Shown
**Filters:**
No filters are available at the Domain level for the Acquisition 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/acquisition-report.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.
