> 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/adsecure-documentation/quick-start-guide.md). # Quick Start Guide First time using AdSecure? Start here! ## Getting started With AdSecure, you can scan ads and URLs in real-time to detect security, compliance, and quality issues hidden inside the digital ad supply chain - and this guide will show you how. It will walk you through the setup process and help you get up and running quickly. For more specific information, please consult our [detailed guides](/adsecure-documentation/how-to-guides/introduction.md) or contact us directly. ### Create a Quick Analysis With a Quick Analysis you can run a **one-off check** of an ad or URL. We recommend creating a Quick Analysis to understand the setup of scanning with AdSecure. In the Analyses menu, you can run a Quick Analysis via the button in the right upper corner. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FPjx8umzjvkhg0GLARbmp%2F19ff80f80f5f.png?alt=media\&token=77701e62-18b8-446b-b455-c2bfa769fead) Continue through the stepper and fill in the required fields. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2F7MKEtreeDm1Ol2rgOncE%2F4939bef7440e.png?alt=media\&token=3e75de58-1256-436e-b47c-d8dc496c0b15) ### View the results Once the analysis is complete, you can click on the corresponding line to view its analysis report. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FbAK8PhKwv1gx4Y0ojRih%2F15b7e336a733.png?alt=media\&token=a53ce33c-058c-4d5c-92e0-95b6e73ff851) #### Analysis report: ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FQBOCeKTLzHtacbIdNill%2Fcb7f50a0647e.png?alt=media\&token=45c4d6ac-7135-477b-94e5-2fb317ac3c6b) ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FHu8JcJ4XOjRfGmYYnrf3%2F17dd901f4a63.png?alt=media\&token=9595d8d6-f607-4191-9040-e1b2745e44a4) ### Create an Alert Rule By default, each [detection](/docs/detections.md) will get flagged as a violation. [Alert Rules](/adsecure-documentation/how-to-guides/alert-rules.md) allow you to define which detections should be displayed as highlighted alerts in the analysis reports. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2Fc34sNJXCLix6wqVPUWyq%2F1a9e2417dbc2.png?alt=media\&token=ada4ab82-c973-4410-8ec3-785d45b6ea19) ### Create Notifications Settings Creating a [notification setting](/adsecure-documentation/how-to-guides/manage-notifications.md) will allow you to receive information about analyses through **email** and **HTTP callback**. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2F2B3GkvWXl8I0CXtdcgsW%2F1b9baa472af4.png?alt=media\&token=cf380c62-84e6-489d-9d4f-4116930b2aca) ### Create Projects In order to scan your ad campaigns or site pages frequently, we recommend setting up a [Project](/adsecure-documentation/how-to-guides/manage-projects.md) in order to automatically let scans run on the frequency of your choice. The Project stepper contains a Frequency step which allows you to set the interval and number of iterations of your choice. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FwzIQSbnTQ6DUqWz3mNHv%2Fc952dc62b360.png?alt=media\&token=25f992fd-a5f2-4c0e-b6dc-4e50a99ae24f) ## Best practices ### Benefits of frequent scanning Since ads are likely to show different behaviour from one moment to another, it’s important to scan frequently to increase your chances to catch any malicious or non-compliant activity when it’s present. This approach will keep the detection rate as high as possible. ### When to use residential proxies? We recommend using residential proxies when you are suspecting ad cloaking or IP blacklisting. Want to learn more about this? You might find [this article](https://www.adsecure.com/blog/inside-adsecure-optimising-threat-protection-with-residential-proxies/) an interesting read. ### Reviewing scan results When reviewing scan results in the **Analyses menu**, analyses will be marked as viewed after opening them. You can also select multiple analyses and mark them as viewed manually. Use these options to keep things organized! Scan results that contain [alerts](/adsecure-documentation/how-to-guides/alert-rules.md) can also be reviewed in the **Notifications Hub**. The alerts are aggregated per scan iteration, allowing you to review these alerts quickly and easily. Each alert notification in the Notifications Hub can be marked as viewed to keep things organized. ![](https://405863316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsuRaI0FQmgJwzlmWKw5f%2Fuploads%2FkK3GtCl1YdmVImPmSkjB%2F9aaadebbc175.png?alt=media\&token=c5efb32e-c860-440d-9b48-0b8cb3896f1c) ## More AdSecure ### Get in touch The best ways to get in touch with us: * in-app chat * * website chat via [www.adsecure.com](https://www.adsecure.com/) ### Share your feedback We love feedback! We encourage you to share your opinions and ideas with us via . ### Blog For more tips, tricks, and industry information, check out our [blog](https://www.adsecure.com/blog). --- # 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/adsecure-documentation/quick-start-guide.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.