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

Cookie Compliance exports Consent Logs as CSV (UTF-8): a single day downloads one CSV file, and a date range downloads a ZIP with one CSV per calendar month. Each file starts with three title lines and two blank lines, then the column header row. 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 the visitor chose: 1 (Private), 2 (Balanced) or 3 (Personalized). When the visitor gives consent by clicking a single blocked item to unblock it, the value is that item’s category number (1–4) instead.

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

iat

issued at (iat) provides a timestamp of when the consent was given; recorded as number of milliseconds since 1970-01-01 00:00:00 UTC

  • 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; values are your site’s category names, and the list always includes the essential category (by default “Basic Operations”)

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

data_event_type

event type defines what the site visitor is consenting to at a general level; field value for event type defaults to “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 stays the same when the same visitor later changes their choice, 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 app’s AppID; the site origin where the consent event was recorded (for example https://example.com) is in the iss column

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

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.

Was this article helpful?
YesNo