> 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/integrations/data-export/data-export-glossary.md).

# Data export glossary

{% hint style="success" %}
**Premium Feature**: Any data export premium feature (CMP, PMP, or ACM)
{% endhint %}

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](#acm-trackers)
* [ACM Vendors](#acm-vendors)
* [ACM Properties](#acm-properties)
* [API events](#api-events)
* [CMP and PMP events](#cmp-and-pmp-events)

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

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

### API events

Refer to the table below for the columns that will be included in the data export for API events.&#x20;

<table><thead><tr><th width="304">Column</th><th>Description</th></tr></thead><tbody><tr><td><code>event_type</code></td><td>The kind of consent event recorded (<em>e.g. event.created)</em></td></tr><tr><td><code>transaction_timestamp</code></td><td>When the consent event actually occurred (the end-user’s action time). Use this as event time for time-series analysis.</td></tr><tr><td><code>partition_user_id</code></td><td>Didomi’s internal global user ID — the anchor for stitching an end-user’s events together. This value is generated by Didomi.</td></tr><tr><td><code>partition_organization_user_id</code></td><td>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.</td></tr><tr><td><code>parameters</code></td><td>JSON blob of event-specific detail (choice payload, context).</td></tr><tr><td><code>datehour</code></td><td>Partition column (date + hour). Filter on this to scan only the days you need.</td></tr><tr><td><code>entity_id</code></td><td>Unique ID of the consent record/entity this event belongs to</td></tr><tr><td><code>entity_created_at</code></td><td>When that consent entity was first created. Distinct from <code>transaction_timestamp</code> (this event’s time).</td></tr></tbody></table>

### CMP and PMP events

Refer to the table below for the columns that will be included in the data export for CMP events.&#x20;

<table><thead><tr><th width="251">Column</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>Unique ID for this single SDK event</td></tr><tr><td><code>event_type</code></td><td>What the SDK reported: <code>consent.given</code>, <code>consent.asked</code>, <code>pageview</code>, <code>ui.action</code>, <code>sync.acknowledged</code></td></tr><tr><td><code>source_type</code></td><td>The SDK/platform: <code>sdk-web</code>, <code>sdk-amp</code>, <code>sdk-mobile</code>, <code>sdk-ctv</code></td></tr><tr><td><code>source_domain</code></td><td>Website domain (web) or app bundle ID / package name (mobile).</td></tr><tr><td><code>source_key</code></td><td>Your organization’s public API key. Identifies which property fired the event.</td></tr><tr><td><code>source_session_id</code></td><td>Groups events from the same browsing/app session.</td></tr><tr><td><code>source_deployment_id</code></td><td>Which notice deployment served this event. Ties activity back to a specific published notice.</td></tr><tr><td><code>source_provider</code></td><td>The consent provider/config source.</td></tr><tr><td><code>source_beacon</code></td><td>Whether the event was sent via <code>navigator.sendBeacon</code>.</td></tr><tr><td><code>source_version</code></td><td>SDK version running when the event fired. Useful for spotting version-specific behaviour.</td></tr><tr><td><code>source_sampling</code></td><td>The sampling strategy applied to this event. Critical for counting — scale sampled event types up by their rate; <code>consent.given</code> and <code>sync.acknowledge</code> are never sampled.</td></tr><tr><td><code>user_country</code></td><td>Geo country (ISO code)</td></tr><tr><td><code>user_region</code></td><td>State / province where available</td></tr><tr><td><code>user_id</code></td><td>SDK-generated anonymous user UUID.</td></tr><tr><td><code>user_id_type</code></td><td>What kind of ID <code>user_id</code> is (e.g. <code>uuid</code>).</td></tr><tr><td><code>user_id_hash</code></td><td>Hashed form of the user ID. Pseudonymised — for privacy-safe joins/deduplication</td></tr><tr><td><code>user_organization_user_id</code></td><td>Your organization's end-user identifier, when the end-user was authenticated. Join key to your CRM (null for anonymous end-users).</td></tr><tr><td><code>token_user_id</code></td><td>User ID carried on the signed consent token.</td></tr><tr><td><code>token_user_id_hash</code></td><td>Hashed version of the token user ID.</td></tr><tr><td><code>token_created</code></td><td>When the consent token was created.</td></tr><tr><td><code>token_updated</code></td><td>When the token was last updated.</td></tr><tr><td><code>token_issuer</code></td><td>Who issued the token.</td></tr><tr><td><code>token_version</code></td><td>Token format version.</td></tr><tr><td><code>vendors_enabled</code></td><td>Vendors to which the end-user consented.</td></tr><tr><td><code>vendors_disabled</code></td><td>Vendors to which the end-user refused.</td></tr><tr><td><code>vendors_li_enabled</code></td><td>Vendors allowed under legitimate interest.</td></tr><tr><td><code>vendors_li_disabled</code></td><td>Vendors objected to under legitimate interest.</td></tr><tr><td><code>purposes_enabled</code></td><td>Purposes to which the end-user consented</td></tr><tr><td><code>purposes_disabled</code></td><td>Purposes to which the end-user refused</td></tr><tr><td><code>purposes_li_enabled</code></td><td>Purposes allowed under legitimate interest</td></tr><tr><td><code>purposes_li_disabled</code></td><td>Purposes objected to under legitimate interest</td></tr><tr><td><code>authentication_type</code></td><td>How the user was identified/authenticated for this event.</td></tr><tr><td><code>user_tcfcs</code></td><td>The IAB TCF consent string encoding the full choice.</td></tr><tr><td><code>user_tcfv</code></td><td>The TCF version to which the string conforms.</td></tr><tr><td><code>user_regs</code></td><td>The regulation(s) in effect for this user (e.g. gdpr, ccpa). Tells your organization which rules applied.</td></tr><tr><td><code>parameters</code></td><td>Event-specific JSON detail (action taken, before/after choice, interaction name). Flexible field where new data lands without schema changes.</td></tr><tr><td><code>experiment_group</code></td><td>Which arm the user saw (test / control).</td></tr><tr><td><code>experiment_id</code></td><td>Identifier of the A/B test the user was in (web only).</td></tr><tr><td><code>event_timestamp</code></td><td>When the event happened on the end-user’s device</td></tr><tr><td><code>datehour</code></td><td>Date + hour partition. For efficient file querying</td></tr></tbody></table>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.didomi.io/integrations/data-export/data-export-glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.