1. Accounts and billing
  2. Contacts
  4. Pages and forms
  5. SMS
  6. Transactional email
  7. Ecommerce
  8. Chat
  9. Analytics
  10. Integrations
  1. Dotdigital Help Centre
  2. Accounts and billing
  3. Compliance

Cookies that might be placed on contacts' devices

Learn about the cookies and similar technologies used by Dotdigital to provide our services, and how these cookies might affect your contacts.

Overview

We sometimes place cookies (small text files) on your contacts' devices. 

The table below provides an overview of the features that place cookies, the type of cookies that get placed, the purpose they serve and when they expire.

Essential cookies

Some cookies are essential for the operation of our website. For example, some cookies allow us to identify subscribers and ensure they can access the subscription only pages. If a subscriber opts to disable these cookies, the user will not be able to access all of the content that a subscription entitles them to.

Web Behaviour Tracking (inc. abandoned cart)

Name of cookie Type of cookie Purpose Expires Essential 
dm_i
recordID
sessionID
 First-party; persistent Tracks and identifies a visitor as a Dotdigital contact whilst they browse a site’s pages. This data can then be used for better segmenting and targeting of contacts. Ranges from a cookie that expires after 20 minutes (collecting session information on pages visited) to cookies that expire after 365 days. No

Site and ROI tracking

Name of cookie Type of cookie Purpose Expires Essential 
dm_i

First-party; persistent

 Tracks contacts whilst they browse a site’s pages and records any ROI data, should they make a purchase. This data is then available in reporting, and for ROI split testing. One hour No

Surveys built with Surveys and forms and Pages and forms: Responder

Name of cookie Type of cookie Purpose Expires Essential 
Survey-X

where X is a reference to the survey number being taken

 First-party if a survey is accessed using a direct link or third-party if the form is a pop-over or embedded; persistent Tracks and identifies a respondent as they answer the survey and records when the survey is complete. 365 days after first view of the survey.  Yes 
respondentidX

where X is a reference to the survey number being taken

 First-party if a form is accessed using a direct link or third-party if the form is a pop-over or embedded; persistent Tracks and identifies a respondent as they answer the survey and records when the survey is complete. 30 days after the first view of the survey. Yes 
respondent-X

where X is a reference to the survey number being taken

 First-party if a form is accessed using a direct link or third-party if the form is a pop-over or embedded; persistent Tracks and identifies a respondent as they answer the survey and records when the survey is complete. N/A - is a session cookie Yes 
respondentidXcount

where X is a reference to the survey number being taken

 First-party if a form is accessed using a direct link or third-party if the form is a pop-over or embedded; persistent A counter to stop users filling in the same form in a second time and overwriting any previous submissions. N/A - is a session cookie Yes

Surveys built with Surveys and forms and Pages and forms: Date started

Name of cookie Type of cookie Purpose Expires Essential 
Survey-Started-X

where X is a reference to the individual taking the survey

 First-party if a survey is accessed using a direct link or third-party if the survey is a pop-over or embedded; persistent Tracks and identifies a respondent as they answer the survey and records when the survey is complete. 365 days after first view of the survey No

Surveys built with Surveys and forms and Pages and forms: Pop-over

Name of cookie Type of cookie Purpose Expires Essential 
X-Completed

where X is a reference to the survey number being taken

 First-party if a form is accessed using a direct link or if the form is a pop-over or embedded; persistent Used to track if a user has completed a pop-up form. 365 days after the first view of the form. Yes 
X-Dismissed

where X is a reference to the survey number being taken

 First-party if a form is accessed using a direct link or if the form is a pop-over or embedded; persistent Used to track if a user has dismissed a pop-up form. 7 days after the first view of the form. Yes

Forms built with Pages and forms

Name of cookie Type of cookie Purpose Expires Essential 
lpformX

where X is a reference to the ID of the landing page containing the form

 First party, persistent, HTML5 local storage-based Enables someone filling in a form to save their progress so they can return to complete the form at later date. HTML5 prevents application developers from specifying expiration; individual web browsers can define expiration policies Yes

Pages built with Pages and Forms and Landing pages

Name of cookie Type of cookie Purpose Expires Essential 
LP-X

where X is a reference to the Dotdigital user who created the landing page

 First-party, persistent Identifies the contact to ensure that  personalised content is  shown only to the intended viewer. 30 days after last view Yes

Abandoned cart functionality of the Shopify connector

Name of cookie Type of cookie Purpose Expires Essential 
dm-subscriber

Holds the email address of the visitor, supplied by Shopify

 N/A Identifies the visitor abandoning a cart and facilitates follow-up messaging. N/A No

Chat

Name of cookie Type of cookie Purpose Expires Essential 
comapi.hub.currentState
comapi.hub.lastClicked
comapi.hub.session
comapi.hub.deviceId
comapi.hub.welcomeMessage.sentOn
comapi.hub.profileId
comapi.hub.orphanedEvents
comapi.hub.config
comapi.hub.comapiMessengerState
comapi.hub.comapiConfig

 

 

 First party, persistent, HTML5 local storage-based Local storage is used to save the visitor's current chat status, when they last clicked (so it's possible to tell if they're returning to a conversation or not), IDs that enable us to identify the user with a conversation, orphaned conversation message events that enable us to apply them to historic messages, and configuration settings. HTML5 prevents application developers from specifying expiration; individual web browsers can define expiration policies  Yes

Information

The abandoned cart module also uses Web Behaviour Tracking cookies to track and identify a contact before sending an abandoned cart email.
Did you find this article helpful?

Can we help?

Thanks for using Dotdigital. If you need more help or support, then contact our support team.