> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/reports/campaign-analysis.md).
# Campaign Analysis
You can get an insight into which of your campaigns are performing best, what might be the best time and days to reach your customers, and which subject lines yield more opens by checking the Campaign Analysis Report.
To view this report, navigate to the **Reports** tab from the menu and click on the 'Campaign Analysis' report.
You should be able to see all types of important information regarding your ongoing campaigns. This includes average open & click rate, top performing campaigns, best days and hours for engagement, etc. You can also filter these by date and specific campaigns.
This should allow you to optimize your campaigns with a data-driven approach!
---
# 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.gleantap.com/reports/campaign-analysis.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.
