Data export glossary
Premium Feature: Any data export premium feature (CMP, PMP, or ACM)
In the tables below, we provide glossaries for the data included in each of the data types that can be exported via data export.
ACM Trackers
The ACM Trackers data type is raw data for individual tracking events detected during 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:
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.
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:
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.
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
API events
Refer to the table below for the columns that will be included in the data export for API events.
event_type
The kind of consent event recorded (e.g. event.created)
transaction_timestamp
When the consent event actually occurred (the end-user’s action time). Use this as event time for time-series analysis.
partition_user_id
Didomi’s internal global user ID — the anchor for stitching an end-user’s events together. This value is generated by Didomi.
partition_organization_user_id
Your organization's identifier for the end-user (the ID you passed in — hashed email, CRM ID, etc.). This is the join key back to your own systems.
parameters
JSON blob of event-specific detail (choice payload, context).
datehour
Partition column (date + hour). Filter on this to scan only the days you need.
entity_id
Unique ID of the consent record/entity this event belongs to
entity_created_at
When that consent entity was first created. Distinct from transaction_timestamp (this event’s time).
CMP and PMP events
Refer to the table below for the columns that will be included in the data export for CMP events.
id
Unique ID for this single SDK event
event_type
What the SDK reported: consent.given, consent.asked, pageview, ui.action, sync.acknowledged
source_type
The SDK/platform: sdk-web, sdk-amp, sdk-mobile, sdk-ctv
source_domain
Website domain (web) or app bundle ID / package name (mobile).
source_key
Your organization’s public API key. Identifies which property fired the event.
source_session_id
Groups events from the same browsing/app session.
source_deployment_id
Which notice deployment served this event. Ties activity back to a specific published notice.
source_provider
The consent provider/config source.
source_beacon
Whether the event was sent via navigator.sendBeacon.
source_version
SDK version running when the event fired. Useful for spotting version-specific behaviour.
source_sampling
The sampling strategy applied to this event. Critical for counting — scale sampled event types up by their rate; consent.given and sync.acknowledge are never sampled.
user_country
Geo country (ISO code)
user_region
State / province where available
user_id
SDK-generated anonymous user UUID.
user_id_type
What kind of ID user_id is (e.g. uuid).
user_id_hash
Hashed form of the user ID. Pseudonymised — for privacy-safe joins/deduplication
user_organization_user_id
Your organization's end-user identifier, when the end-user was authenticated. Join key to your CRM (null for anonymous end-users).
token_user_id
User ID carried on the signed consent token.
token_user_id_hash
Hashed version of the token user ID.
token_created
When the consent token was created.
token_updated
When the token was last updated.
token_issuer
Who issued the token.
token_version
Token format version.
vendors_enabled
Vendors to which the end-user consented.
vendors_disabled
Vendors to which the end-user refused.
vendors_li_enabled
Vendors allowed under legitimate interest.
vendors_li_disabled
Vendors objected to under legitimate interest.
purposes_enabled
Purposes to which the end-user consented
purposes_disabled
Purposes to which the end-user refused
purposes_li_enabled
Purposes allowed under legitimate interest
purposes_li_disabled
Purposes objected to under legitimate interest
authentication_type
How the user was identified/authenticated for this event.
user_tcfcs
The IAB TCF consent string encoding the full choice.
user_tcfv
The TCF version to which the string conforms.
user_regs
The regulation(s) in effect for this user (e.g. gdpr, ccpa). Tells your organization which rules applied.
parameters
Event-specific JSON detail (action taken, before/after choice, interaction name). Flexible field where new data lands without schema changes.
experiment_group
Which arm the user saw (test / control).
experiment_id
Identifier of the A/B test the user was in (web only).
event_timestamp
When the event happened on the end-user’s device
datehour
Date + hour partition. For efficient file querying
Last updated