CSV format reference

The CSV export of a compliance report provides detailed information about the compliance status of a given website. The CSV export can be generated in the Didomi console. The CSV file will include all information for the report period.

Download the results of your report

After running the compliance report there are 2 CSV files that the user can download: trackers and vendors. To do so follow the next steps:

  1. Click on the Compliance Report section on the left menu.

  2. Click on the 3 dots button that appear next to the report that you want to export. This will open a dropdown where the user has 2 export options: Download Vendors CSV and Download Trackers CSV

  3. Click on the item you would like to download

  4. Your report is automatically exported in an CSV file.

If you desire to do the same thing for a previous report, navigate to the details of the report. From the "Pick a report" dropdown select the report you would like to export. After the report has loaded, click on the 3 dots button in the header and select the export type you wish to download.

Available exports

Vendors

The vendors export provides more information on the vendors found on the website during a scanning session.

Column
Type
Description
Example

Date

Date

The date and time when the page was browsed

1/9/2018 2:41:43 AM

Vendor

String

Vendor name as known in our database, vendor domain if unknown

Didomi

Page url

URL

Page url where the vendor was discovered on your website

Request url

URL

URL that triggered the vendor

Is Tag

String

yes/no depending if the vendor is considered a tag

yes

Tag type*

String

Type of the file that was requested

  • if the request was mate to a javascript file it is considered a tag

  • otherwise the file type that was requested by the vendor is displayed

text/javascript

Initiator url

URL

URL of the initiator of the vendor

Initiator vendor

String

Initiator vendor name as known in our database, initiator vendor domain if unknown

Didomi

Trackers

This export lists all the cookies set on the original domain (the one that is being browsed by our bot). These are called "first-party" cookies and include both the cookies set by the website itself as well as cookies set by third-parties embedded on the website via JavaScript.

Column
Type
Description
Example

Vendor

String

Name of the vendor that dropped the cookie as known in our database, vendor domain if unknown

Didomi

Page url

URL

Page on which the cookie was dropped

Vendor URL

URL

URL of the vendor that dropped the tracker

Cookie Domain

String

The domain that was used when setting the cookie

didomi.io

Cookie Name

String

The name of the cookie

uuid

Lifetime

Integer

The lifetime in seconds of the cookie dropped, usually negative if it's a session cookie

3600

Sample

String

A sample of content extracted from the cookie

a8fbf13f-419b-498e-919c-e60071501cea

Party

String

1st/3rd party depending who dropped the cookie

1st party

*What is a tracking tag?

What we call a tracking tag is an HTTP request that is used by a vendor for tracking/targeting purposes. For instance, we try to identify all the requests that adblockers would block. There is no exact definition of what constitutes a tag and there is surely no perfect way to identify them.

We do our best to classify requests as tags when possible to get an estimate of how many tags are embedded on webpages. We use rules like: the format of the HTTP response (image, JavaScript), the size of the response, the query-string parameters, the domain, etc.

Last updated