# ACM data export glossary

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

In the tables below, we provide glossaries for the data included in each of the data types that can be exported via ACM data export.

* [ACM Trackers](#acm-trackers)
* [ACM Vendors](#acm-vendors)
* [ACM Properties](#acm-properties)

#### ACM Trackers

The ACM Trackers data type is raw data for individual tracking events detected during compliance monitoring scans. Each row represents a single tracker (cookie, script, etc.) found on your websites during different consent scenarios. This data can be leveraged by your organization to analyze:

* Detailed tracker behavior analysis across consent scenarios
* Technical debugging of tracking implementations
* Understanding when specific trackers fire relative to consent actions
* Vendor compliance auditing at the individual tracker level

Fields included in the ACM Trackers data type include:

<table><thead><tr><th width="256">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>ID</code></td><td>Unique identifier for this tracker instance within the scan</td></tr><tr><td><code>EVENT_TIME</code></td><td>Timestamp when the crawler registered the event during scanning</td></tr><tr><td><code>CREATED_AT</code></td><td>Timestamp when tracker data was processed at end of page scan (for data ingestion)</td></tr><tr><td><code>COLLECT_ID</code></td><td>Unique identifier for the collect (scan scenario: accept/refuse/no action)</td></tr><tr><td><code>COLLECT_PAGE_ID</code></td><td>Unique identifier for the specific page scanned within a collect</td></tr><tr><td><code>HOST</code></td><td>Domain hosting the tracker</td></tr><tr><td><code>TYPE</code></td><td>Type of tracker (e.g., "cookie", "script")</td></tr><tr><td><code>PAGE_URL</code></td><td>Full URL where tracker was detected</td></tr><tr><td><code>PAGE_URL_HOST</code></td><td>Host domain of the page being scanned</td></tr><tr><td><code>PAGE_URL_SLD</code></td><td>Second-level domain of the page</td></tr><tr><td><code>PROPERTY_ID</code></td><td>Your website property identifier</td></tr><tr><td><code>REPORT_ID</code></td><td>Unique report identifier</td></tr><tr><td><code>ORGANIZATION_ID</code></td><td>Your organization identifier</td></tr><tr><td><code>IS_TC_STRING_IDENTICAL</code></td><td>Whether the TCF API <code>tc_string</code> matches the <code>gdpr_consent</code> query parameter</td></tr><tr><td><code>INITIATOR</code></td><td>The vendor actually dropping/creating the tracker</td></tr><tr><td><code>INITIAL_NAME</code></td><td>Original tracker name before processing</td></tr><tr><td><code>NAME</code></td><td>Processed tracker name (after regex pattern matching)</td></tr><tr><td><code>NAME_PATTERN</code></td><td>Regex pattern used to process the initial name</td></tr><tr><td><code>VENDOR</code></td><td>Vendor that owns the tracker (if successfully matched in database)</td></tr><tr><td><code>VALUE</code></td><td>Tracker value/content</td></tr><tr><td><code>LIFETIME_SECONDS</code></td><td>How long the tracker persists</td></tr><tr><td><code>IS_THIRD_PARTY</code></td><td>Whether tracker is from a third-party domain</td></tr><tr><td><code>IS_HTTP_ONLY</code></td><td>Security and persistence flags</td></tr><tr><td><code>IS_SECURE_ONLY</code></td><td>Security and persistence flags</td></tr><tr><td><code>IS_PERSISTENT</code></td><td>Security and persistence flags</td></tr><tr><td><code>SOURCE</code></td><td>How tracker was created ("javascript" or "http request")</td></tr><tr><td><code>CMP</code></td><td>Consent scenario context (JSON format showing when tracker was detected)</td></tr><tr><td><code>HASH_NAME_HOST_TYPE</code></td><td>Hash for aggregating trackers (processed name + host + type)</td></tr><tr><td><code>HASH_INITIAL_NAME_HOST_TYPE</code></td><td>Hash for aggregating trackers (initial name + host + type)</td></tr></tbody></table>

#### ACM Vendors

The ACM Trackers data type is consolidated information about vendors detected across your properties, aggregated by consent scenarios. Each row represents a vendor's activity summary within a specific report. This data can be leveraged by your organization to analyze:

* Vendor performance reporting across consent scenarios
* Third-party risk assessment and vendor inventory
* Compliance dashboard creation showing vendor-level metrics
* Understanding which vendors are active in different consent contexts

Fields included in the ACM Vendors data type include:

{% hint style="warning" %}
**Note**: ACM vendor data can be joined with ACM Tracker data using the `PARTNER`/`VENDOR` fields to get detailed tracker information for each vendor.
{% endhint %}

<table><thead><tr><th width="195">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>REPORT_ID</code></td><td>Unique report identifier</td></tr><tr><td><code>PROPERTY_ID</code></td><td>Website property identifier</td></tr><tr><td><code>ORGANIZATION_ID</code></td><td>Your organization identifier</td></tr><tr><td><code>ID</code></td><td>Vendor identifier (database ID if matched, or host domain if not)</td></tr><tr><td><code>REQUEST_COUNT</code></td><td>Number of tracker requests from this vendor</td></tr><tr><td><code>CMP</code></td><td>Consent scenarios where vendor was active (JSON array format)</td></tr><tr><td><code>PARTNER</code></td><td>Detailed vendor information and metadata (JSON format)</td></tr><tr><td><code>CREATED_AT</code></td><td>Report generation timestamp</td></tr></tbody></table>

### ACM Properties

The ACM Trackers data type is consolidated information that aggregates property-level compliance status and collection results. Each row represents the overall compliance status for a website property. This data can be leveraged by your organization to analyze:

* High-level compliance monitoring across your website portfolio
* Identifying properties with collection issues or errors
* Monitoring scan success rates and troubleshooting failed collections
* Executive reporting on overall compliance monitoring health

Fields included in the ACM Properties data type include:

<table><thead><tr><th width="228">Field</th><th>Description</th></tr></thead><tbody><tr><td><code>WEBSITE</code></td><td>Full website URL</td></tr><tr><td><code>PROPERTY_ID</code></td><td>Unique property identifier</td></tr><tr><td><code>CREATED_AT</code></td><td>Report generation timestamp</td></tr><tr><td><code>REPORTSTATUS</code></td><td>Overall report processing status (e.g., "Processed", "Partially Processed", "Failed")</td></tr><tr><td><code>COLLECT_CONSENT_TO_ALL</code></td><td>Status/errors for the "accept all" scenario collection. <a href="#status-codes">Click here</a> to view available status codes</td></tr><tr><td><code>COLLECT_REFUSE_TO_ALL</code></td><td>Status/errors for the "refuse all" scenario collection. <a href="#status-codes">Click here</a> to view available status codes</td></tr><tr><td><code>COLLECT_NO_USER_CHOICE</code></td><td>Status/errors for the "no user action" scenario collection. <a href="#status-codes">Click here</a> to view available status codes<br><br><mark style="background-color:$warning;"><strong>Note</strong>: The <code>COLLECT_NO_USER_CHOICE</code> scenario typically has fewer error types as it does not require any button interactions.</mark></td></tr></tbody></table>

#### Status codes

The following status codes are human-readable status messages that indicate the outcome of each consent scenario collection (e.g. `COLLECT_CONSENT_TO_ALL`) and can be used to help identify specific areas for website optimization or troubleshooting.

{% hint style="info" %}
Multiple status codes can populate in a single consent scenario collection if multiple issues occurred.&#x20;
{% endhint %}

<table><thead><tr><th width="233">Status Code</th><th>Description</th></tr></thead><tbody><tr><td><code>SUCCESS</code></td><td>Collection completed successfully for that scenario</td></tr><tr><td><code>Website not reachable</code></td><td>Network issues, website down, or crawler cannot access the site</td></tr><tr><td><code>Anti-bot system</code></td><td>Bot protection or anti-automation measures detected and blocking crawler</td></tr><tr><td><code>No existing or clear CMP on the page</code></td><td>No CMP found or CMP not clearly identifiable</td></tr><tr><td><code>No refuse options found</code></td><td>CMP detected but no refuse/reject consent options available</td></tr><tr><td><code>No accept button found</code></td><td>CMP detected but no accept consent button found</td></tr><tr><td><code>Not able to click on the button in the page</code></td><td>UI interaction failed - button exists but cannot be clicked</td></tr><tr><td><code>General Error</code></td><td>Other unspecified errors not covered by above categories</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.didomi.io/advanced-compliance-monitoring-acm/advanced-compliance-monitoring-acm-data-export/acm-data-export-glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.