Cookies and Third-Party Services Used in Cool Tabs Campaigns

1. Introduction.

2. Cookies Used.

2.1. Technical Cookies.

2.2. Consent Manager Cookie.

2.3. Visit Panel Cookies.

2.4. Optional Analytics Service Cookies.

3. Third-Party Services.

3.1. Cool Tabs' Own Services.

3.2. External Libraries and Resources.

3.3. File Upload Management.

3.4. Optional Analytics Services.

4. Other Specifications.

4.1. Can External Resources Be Served Locally?

4.2. Can Storage Periods Be Reduced?

5. Related Content.

1. Introduction.

In this article, we gather all the cookies and third-party services that we use in Cool Tabs campaigns, including their purpose and duration, so you can properly document them in your campaign's privacy policy, cookie policy, and legal bases.

If what you need is to configure the consent popup in your campaign, check the tutorial How to Add a Cookie and Tracking Codes Acceptance Popup to Your Campaign.

Most cookies are associated with a specific campaign and include its ID in the name. In the examples, we will use 12345 as a reference ID, but in your campaign, it will be a 5 or 6 digit number.

2. Cookies Used.

2.1. Technical Cookies.

These are essential cookies for the campaign's operation and cannot be disabled. They are used to manage the participant's session, identify them, prevent duplicate entries, and ensure the integrity of the data they submit.

• _cp: maintains the campaign configuration. It is deleted when the browser is closed.

• an_token: stores the user's authentication token. In campaigns with social login, it is a session cookie; in campaigns with anonymous login, it lasts 1 month.

• auth_12345: internal authentication ID (varies by campaign). It is deleted when the browser is closed.

2.2. Consent Manager Cookie.

This cookie is automatically created when activating the cookie consent manager and stores the user's preferences to avoid showing the popup on each visit.

• consent_12345: stores the user's consent. Duration: 15 days.

2.3. Visit Panel Cookies.

Cookies we use to measure visits to the campaign and show you the statistics panel. They are integrated with the consent manager, so the user can reject them.

• cm12345

• cn12345

• cs12345

• uv12345

• lr12345

• lcm12345

• lcn12345

2.4. Optional Analytics Service Cookies.

These cookies are only created if you, as the campaign administrator, have activated the corresponding measurement service (Google Analytics, Google Tag Manager, or Facebook Pixel). Their duration and purpose are determined by the provider.

• _ga and _ga_XXXXXXXXXX: Google Analytics 4 cookies. Created if you configure your own GA4 in the campaign.

• Google Tag Manager Cookies: created if you activate GTM. Since it can be used to include any type of tag, you will need to document the use you give it in the legal bases.

• Facebook Pixel Cookies: created if you activate the pixel to measure the performance of your Facebook Ads campaigns.

3. Third-Party Services.

For the proper functioning of campaigns, Cool Tabs establishes connections with the following domains and providers. Below we detail the purpose of each so you can reflect them in your legal documentation.

3.1. Cool Tabs' Own Services.

• ct-assets.com: our own CDN, from which we serve the JavaScript and CSS files necessary for the campaign's execution. Purpose: delivery of essential resources.

• dctw.io: own domain that we use to register campaign visits and display statistics on the administrator panel. Purpose: campaign's own analytics.

3.2. External Libraries and Resources.

• Google Fonts (fonts.googleapis.com). Provider: Google. Used together with Google's JS for loading font types. Purpose: essential for the campaign's visual presentation.

• jQuery (jquery.com). Provider: JS Foundation. JavaScript library necessary for the campaign's functionality. Purpose: essential for execution.

• jsDelivr (jsdelivr.net). Provider: Valentio JSD Limited. CDN used to serve the jQuery library. Purpose: resource delivery.

3.3. File Upload Management.

• transloadit.com. External provider we use for managing image uploads in campaigns that include forms with file uploads. Purpose: file processing and uploading.

3.4. Optional Analytics Services.

These services are only loaded if you activate them from the campaign settings. If you use them, remember to inform users in the legal bases and privacy policy.

• Google Analytics (google-analytics.com). Provider: Google. Purpose: statistical analysis of visits and user behavior.

• Google Tag Manager (googletagmanager.com). Provider: Google. Purpose: tag manager and tracking codes configured by the campaign administrator.

• Facebook (facebook.com). Provider: Meta Platforms. Purpose: measuring the performance of Facebook Ads campaigns using the Facebook pixel.

4. Other Specifications.

4.1. Can External Resources Be Served Locally?

Currently, it is not possible to serve local resources such as Google Fonts, jQuery, or jsDelivr. These resources are loaded through their respective external providers, who are responsible for their maintenance and updates.

4.2. Can Storage Periods Be Reduced?

The indicated storage periods are the minimum necessary for the correct functioning of the campaign and cannot be reduced. In the case of optional analytics service cookies (Google Analytics, GTM, Facebook), the duration is determined by the provider.

If you have any questions about data processing at Cool Tabs, you can write to us at help@cool-tabs.com.

5. Related Content.

How to Add a Cookie and Tracking Codes Acceptance Popup to Your Campaign.

How to Configure Tracking and Conversion Tracking Codes for a Campaign.