ACM data export glossary

Premium Feature: Advanced Compliance Monitoring & ACM Data Exports

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 Vendors

• 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:

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

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:

Note: ACM vendor data can be joined with ACM Tracker data using the PARTNER/VENDOR fields to get detailed tracker information for each vendor.

Field	Description
REPORT_ID	Unique report identifier
PROPERTY_ID	Website property identifier
ORGANIZATION_ID	Your organization identifier
ID	Vendor identifier (database ID if matched, or host domain if not)
REQUEST_COUNT	Number of tracker requests from this vendor
CMP	Consent scenarios where vendor was active (JSON array format)
PARTNER	Detailed vendor information and metadata (JSON format)
CREATED_AT	Report generation timestamp

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:

Field	Description
WEBSITE	Full website URL
PROPERTY_ID	Unique property identifier
CREATED_AT	Report generation timestamp
REPORTSTATUS	Overall report processing status (e.g., "Processed", "Partially Processed", "Failed")
COLLECT_CONSENT_TO_ALL	Status/errors for the "accept all" scenario collection. Click here to view available status codes
COLLECT_REFUSE_TO_ALL	Status/errors for the "refuse all" scenario collection. Click here to view available status codes
COLLECT_NO_USER_CHOICE	Status/errors for the "no user action" scenario collection. Click here to view available status codes Note: The COLLECT_NO_USER_CHOICE scenario typically has fewer error types as it does not require any button interactions.

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.

Multiple status codes can populate in a single consent scenario collection if multiple issues occurred.

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