What type of cookies do you create on the devices of recipients and visitors?

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.

Feature Name of cookie Type of cookies Purpose Expires Essential?
All contact-facing services
__cfduid
First-party; persistent Enables our infras tructure provider, Cloudflare, to manage security and load balancing. Defined by a third party, but usually a period of around six months. Yes
Web Behaviour Tracking (inc. abandoned cart)
dm_i
recordID
sessionID
First-party; persistent Tracks and identifies a visitor as an Engagement Cloud 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
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 and forms / Pages and forms - responder
Survey-X

where X is a reference to the survey number being taken

First-party if a survey is accessed via a direct link (that is r1.dotmailer-surveys.com/…) 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.  Yes
Surveys and forms / Pages and forms - date started
Survey-Started-X

where X is a reference to the individual taking the survey

First-party if a survey is accessed via a direct link (that is r1.dotmailer-surveys.com/…) 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 and forms / Pages and forms - pop-over
X-Dismissed
X-Completed

where X is a reference to the ID of the survey that is being hosted in the popover

First-party if a survey is accessed via a direct link (that is r1.dotmailer-surveys.com/…) 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
Pages and forms (form component)
lpformX

where X is a reference to the ID of the landing page hosting 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
Landing pages
LP-X

where X is a reference to the dotdigital customer who created the landing page

First-party, persistent Identifies the contact to enable personalisation when they visit any landing page from that particular account. 30 days after last view No
Abandoned cart functionality of the Shopify connector
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
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
*Note: the abandoned cart module also makes use of Web Behaviour Tracking cookies in order to track and identify a contact, in order to then automatically send an abandoned cart email.
Have more questions? Submit a request

Comments