Applies to Dynamics 365 for Customer Engagement apps version 9.x
Dynamics 365 for Marketing identifies website visitors by using a technology called cookies. A cookie is a small file that's sent by a server and saved by your browser. Each time you visit a server for which a cookie is set, your browser submits that cookie value back to the server. In this way the cookie can provide a unique visitor ID, which enables the server to return information that is unique to you. This is the technology that originally made the online shopping cart possible.
Many countries/regions (including the European Union) require that you obtain consent before setting a cookie on a resident's machine. It is your organization's responsibility to be aware of, and conform to, all relevant laws and regulations in the markets where you operate, including when it comes to obtaining consent to set cookies. For example, you can read more about the EU regulations at ec.europa.eu/ipg/basics/legal/cookies/.
A cookie identifies a single device/browser/account combination. If you use two different browsers (such as Firefox and Internet Explorer) on the same computer, each will have its own cookie. Likewise, you'll have different cookies on each device that you use, and another user with their own account on your computer will have yet other cookies. If a device gets deleted and reinstalled, all cookies will also be deleted. Nevertheless, Dynamics 365 for Marketing attempts to resolve the actual marketing contact associated with each unique cookie ID.
Whenever a contact submits a marketing page, Dynamics 365 for Marketing correlates the behavior-analysis cookie ID with the incoming contact data submitted with the marketing-page form. In this way the cookie ID becomes mapped to a Dynamics 365 contact ID, so now we can determine who has been browsing the site. The system applies its configured duplicated-detection method to determine whether incoming landing-page data should be mapped to an existing contact or to a new contact.
Dynamics 365 for Marketing sets three different types of cookies:
- Long-term behavioral-analysis cookie: This cookie is set and/or read on any webpage where you have placed a Dynamics 365 for Marketing website behavioral-analysis script. It enables Dynamics 365 for Marketing to score leads based on their level of interaction with a given website. The cookie contains no personal information, but does uniquely identify a specific browser on a specific machine, and Dynamics 365 for Marketing can use it to correlate this ID with an actual contact in the Dynamics 365 for Marketing database. The cookie remains active for two years.
- Short-term, single-visit cookie: This cookie is also set and/or read on any webpage where you have placed a Dynamics 365 for Marketing website behavioral-analysis script. By default, it expires after just 30 minutes (although you can configure this). Dynamics 365 for Marketing uses it to group all page loads by a given visitor that are recorded by the same behavioral-analysis script and that occur within the configured timeframe; it will consider all of these as part of a single "visit" to the website.
- Marketing page registration cookie: This cookie is set when a contact submits a Dynamics 365 marketing page where the Remember my information check box has been selected. It enables the marketing page to show a prefilled form the next time the same contact uses it. The information stored in the cookie is a cryptographic, unique identifier and doesn't contain the data submitted or any means for an external application to uncover the submitted information.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.