> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/web-app/analytics-campaigns-and-reports.md). # Analytics, campaigns & reports Analytics, Campaigns, Reports, Ad Library, and Meta Audit ## Analytics Track the KPIs that matter across your connected channels. Use it together with the [Analytics & ROI tools](/analytics-roi-and-attribution.md) for deeper AI-driven analysis. ## Campaigns Manage campaigns across platforms from one place — create, review, and optimize without hopping between ad managers. ## Reports Every report you generate is stored here, ready to review or share with clients. ## Ad Library All the ad creatives you've generated, browsable in one place — reuse and iterate instead of starting from scratch. ## Meta Audit A dedicated audit workspace for Meta ad accounts: run the audit, review the findings, act on them with the matching [Facebook & Meta tools](/facebook-and-meta-ads.md). ## Command Centre The power view: everything running in your account — jobs, automations, and recent results — on one screen. --- # 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.marketingtool.pro/web-app/analytics-campaigns-and-reports.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.