> For the complete documentation index, see [llms.txt](https://docs.adsecure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adsecure.com/faqs/notifications.md). # Notifications Find here frequently asked questions about notifications ## How to get automatically notified on the outcome of analyses? [AdSecure’s notification system](/adsecure-documentation/how-to-guides/manage-notifications.md) allows you to receive information in real-time about the outcome and status of analyses via email, in-app notifications and callback URL. ## What information is displayed in the reports? At AdSecure we provide our clients with Forensic-level reporting. Each analysis report contains the complete redirection path from submitted content to the landing page, with every redirection in between. We provide these detailed reports for all analyses, whether they come back with a detection or are clean. This allows our clients to have full control and transparency. ## Can I share a report with a third party? If you need to share digital evidence of the violation(s) detected during the scan of a creative, you have the possibility to share the public version of a report with the third party of your choice. Simply click on the share icon to copy the public URL of a given report before sharing it with the third party of your choice. --- # 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.adsecure.com/faqs/notifications.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.