> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/advanced-compliance-monitoring-acm/introduction.md).

# Introduction

{% hint style="success" %}
**Premium Feature**: Advanced Compliance Monitoring
{% endhint %}

Advanced Compliance Monitoring (ACM) is an advanced feature set offered by Didomi that augments the capabilities of the tracker and vendor discovery. When configured, your organization will generate an ACM report customized to your organization's needs and have access to dedicated analytics based on the results&#x20;

In this article, we provide a brief overview of the methodology Didomi utilizes to generate an Advanced Compliance Monitoring report for any given domain.

{% hint style="info" %}
While the methodology in producing an Advanced Compliance Monitoring (ACM) report is the same as that of a tracker and vendor discovery. The ACM report includes more robust features and a higher default page scan limit compared to that of the tracker and vendor discovery.&#x20;
{% endhint %}

* [Bot navigation](#bot-navigation)
* [Data analysis](#data-analysis)
* [Generate Advanced Compliance Monitoring report](#generate-advanced-compliance-monitoring-report)

{% hint style="warning" %}
When Advanced Compliance Monitoring (ACM) is enabled for your organization, the left-hand tab to view and generate your tracker and vendor discovery is renamed to **Advanced Compliance Monitoring**.
{% endhint %}

### Bot navigation

The Didomi bot will visit the configured domains to perform a *scraping session* in accordance with the configured parameters for each domain. During the scraping session, the Didomi bot will collect information about the trackers dropped and vendors triggered on the specific domain.

{% hint style="info" %}
[Click here](https://docs.didomi.io/advanced-compliance-monitoring-acm/acm-report-domains/request-acm-report.md) for more information on how to reinitiate a scraping session and generate a new ACM report by the Didomi bot for a given domain.
{% endhint %}

### Data analysis

Once the Didomi bot has finished scrapping a domain, Didomi will analyze the collected data and convert the information into a human-readable format. By analyzing the dropped trackers and triggered vendors, Didomi will calculate any potential compliance issues in regards to the configured behavior for the scan that may be present on the domain.&#x20;

<table data-header-hidden><thead><tr><th width="214.7000732421875"></th><th></th></tr></thead><tbody><tr><td>Trackers</td><td>In addition to tracker information recorded, Didomi will also categorize the trackers into three distinct groups (cookies, pixels or local storage) and parse first-party trackers from third-party trackers. </td></tr><tr><td>Vendors</td><td>Didomi evaluates each vendor triggered on the domain.</td></tr></tbody></table>

### Generate Advanced Compliance Monitoring report

The analyzed data will be used to generate an ACM report for the domain after Didomi performs the following steps:

* Data aggregation
* Mapping of trackers to initiators
* Calculation of number of requests to/from each vendor
* Computation of recommendations
* Calculation of Didomi rating

[Click here](https://docs.didomi.io/advanced-compliance-monitoring-acm/acm-report-results.md) for an in-depth review on the data included in an ACM report for a domain.


---

# 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.didomi.io/advanced-compliance-monitoring-acm/introduction.md?ask=<question>&goal=<user_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.
