Export Format

Cookie Compliance export format is based on current work to establish a compliant consent record structure from International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC 27560). 

A date-range export of Consent Logs downloads a ZIP file holding one CSV (UTF-8) per calendar month; a single-day export downloads one CSV. Each CSV opens with a short title block, then a header row; after that, each row represents one consent event. Exports include Cookie Consent entries (banner choices) and Privacy Consent entries (policy/notice acknowledgments), depending on what your logs contain at the time of export. The export respects your anonymization setting.

File & encoding

• Format: CSV, UTF-8
• Delimiter: comma ,
• Quotes: standard CSV quoting for fields with commas or JSON
• Filename pattern: <app>_consent-logs_<YYYY.MM.DD> TO <YYYY.MM.DD>.csv

Parameters

moc

method of collection (moc) describes how the consent was collected; field value for consent collected via the banner is preset to “web form”; other values like “implicit”, “verbal” will be supported in future releases

• data type = STRING
• example output = “web form”

jurisdiction

identifies the legal jurisdiction under which the processing of personal data occurs

• data type = ISO 2-letter Country Code
• example output = “US”

consent_level

the consent level recorded with the visitor’s choice; for a banner choice, 1 = Private, 2 = Balanced, 3 = Personalized

• data type = INTEGER
• example output = “2”

iat

issued at (iat) gives the time the consent was given; recorded as the number of milliseconds since 1970-01-01 00:00:00 UTC (13 digits)

• data type = INTEGER
• example output = “1608100000000”

exp

expiration (exp) describes the length of time for which this consent receipt is valid; field value for consent expiration can be configured using the Duration parameter

• data type = INTEGER
• example output = “30”

purpose

describes the purpose categories for which the subject or site visitor has provided their consent; it lists the allowed categories by your site’s category names and always includes the essential category (default name “Basic Operations”), so it is never empty

• data type = STRING
• example output = “Basic Operations, Site Optimization”

data_event_type

event type defines what the site visitor is consenting to at a general level; field value for banner consent is “Cookie” 

• data type = STRING
• example output = “Cookie” 

Identifiers

sub

identifies the subject or site visitor; field value for consent collected via the banner will default to data_session_id; other subject identifiers like “email”, “phone” will be supported in future releases

• data type = STRING
• example output = “84a125ff-cd97-45de-b1b8-cfa05e58d43c”

jti

identifies the visitor’s consent record; it is created with the visitor’s first choice and stays the same for their later changes until the consent cookie is cleared or expires, so one jti can appear on several rows

• data type = STRING
• example output = “fc838979-3bee-432f-ad15-86aa05674a0e”

data_app_id

application id (app_id) is your domain’s App ID; the site address where the consent event was recorded is in the separate iss column

• data type = STRING
• example output = your App ID

iss

the address of the site where the consent was recorded: its origin (scheme and host, such as https://www.example.com), not the full page URL

• data type = STRING
• example output = “https://www.example.com/”

data_session_id

session id is used to identify the specific browsing session where the subject or site visitor interacted with the banner to record their consent

• data type = STRING
• example output = “84a125ff-cd97-45de-b1b8-cfa05e58d43c”

Data Controller

When your website collects data from site visitors, you are known as a data controller. The log file contains fields that identify the person responsible for privacy and compliance practices:

• If you are a business owner running your own website, then your contact information should populate these fields
• If you are running a website for a business with a dedicated privacy or compliance team, then contact information for the team lead should populate these fields. 

data_controller_on_behalf

used to identify your website or business as the party responsible for controlling the data collected from your site visitors; field value for consent captured via the banner defaults to TRUE, indicating that your website is controlling data on behalf of the site visitor

• data type = BOOLEAN
• example output = “TRUE” 

data_controller_contact

name of the individual responsible for privacy and compliance practices

data_controller_company

name of the company

data_controller_address

business address of the company

Data Controller fields can be updated on the Account page: open the 3-dot menu on the Company Information card and choose Edit.