Cookies and Local Storage
Dynamic Yield stores personal data in cookies and local storage to create personalized
experiences on your website. In this article, you can see our classification of these cookies to support you with your own classification requirements under applicable data privacy regulations.
Most of these cookies are created by the Dynamic Yield script embedded on
your site. These cookies are stored on the dynamicyield.com cookie domain, or on your
second-level domain (SLD). Your SLD is a part of your site's URL address.
When working with the Experience OS Landing Pages app without setting up a custom domain,
the content is served by a Dynamic Yield domain (adserve.io). This domain then also hosts
cookies designated to your SLD.
Note
In accordance with applicable privacy laws, we limit the storage time of all cookies to a maximum of 365 days.
Performance, analytics, and personalization cookies
The following cookies are used to detect browser-specific behavior, to conduct experimentation
and analytics, and for personalization purposes.
| Name | Description | TTL | Cookie Domain |
|---|---|---|---|
| DYID | A Dynamic Yield unique identifier that operates as a key for personalization (tailoring the content users see on your website). | 1 year | dynamicyield.com |
| _dyid | A Dynamic Yield unique identifier that operates as a key for personalization (tailoring the content users see on your website). | 30 days | Customer’s SLD |
| _dyid_server | A Dynamic Yield unique identifier that operates as a key for personalization. | 1 year | Customer’s SLD |
| DYSES | A Dynamic Yield unique identifier that operates as a key for personalization. It tracks user sessions to monitor performance and learn about user activities to optimize the personalization of content users see on your website. | browser session | dynamicyield.com |
| _dyjsession | A Dynamic Yield unique identifier that operates as a key for personalization. It tracks user sessions to monitor performance and learn about user activities to optimize the personalization of content users see on your website. | browser session | Customer's SLD |
| _dy_csc_ses | Tracks when a user closes their browser. Is necessary for the Dynamic Yield script to function properly. | browser session | Customer’s SLD |
| _dycmc | Identifies users who regularly delete cookies ("cookie deleters"). Is necessary for the Dynamic Yield script to function properly. | 30 days | Customer’s SLD |
| _dycnst | Used to remember user cookie consent preferences. Is necessary for the Dynamic Yield script to function properly. | 30 days | Customer’s SLD |
| _dy_lu_ses | Determines the first page URL a user comes from, and its validity. | browser session | Customer's SLD |
| _dy_df_geo | Used for audience creation purposes to store geographical location data (country, state, city). | 30 days | Customer's SLD |
| _dy_geo | Used for audience creation purposes to store geographical location data (country, continent, area, city). | 30 days | Customer's SLD |
| _dycst | Used for audience creation purposes to collect data about the user-agent and associated window size. | 30 days | Customer's SLD |
| _dy_ses_load_seq | Used for experimentation and A/B testing purposes, to detect browser sessions. | 30 days | Customer's SLD |
| _dy_soct | Controls the frequency of periodically-activated campaigns. Without this cookie, periodically-activated campaigns would be either disabled or executed upon every page load. | 1 year | Customer's SLD |
| _dy_toffset | Validates the user's clock drift (for computers that don't sync their clock with the internet). | 30 days | Customer’s SLD |
| dy_fs_page | Indicates the URL of the first page a user visits when they start a session on a website, and targets a user by the first page of their session. | browser session | Customer's SLD |
| _dy_cs_storage_items | Used for proprietary custom implementation on your website, for Dynamic Yield campaigns to operate correctly. | ✔ / 30 days | Customer's SLD |
| _dy_cs_cookie_items | Used for proprietary custom implementation on your website, for Dynamic Yield campaigns to operate correctly. | ✔ / 30 days | Customer's SLD |
Data stored in local storage
| Name | Description |
|---|---|
| _dyuss_ | Used for audience creation purposes to provide the user state in a real-time audience segmentation system (session-oriented). |
| dyaud_sess | Used for audience creation purposes to provide the user state in a real-time audience segmentation system (session-oriented). |
| _dy_weather_ | Used for audience creation purposes to display local weather forecasts to the user immediately upon returning to the website or offer suggestions based on their past interactions with weather data. |
| _dy_cweather_ | Used for audience creation purposes to display local weather forecasts to the user immediately upon returning to the website or offer suggestions based on their past interactions with weather data. |
| _dy_tsrc | Used for audience creation purposes to track and analyze the cached source of traffic that brings a visitor to a website. |
| _dyaud_nchc | Used for audience creation purposes to track and manage real-time audience users and deliver more relevant content to different segments of users. |
| _dyaud_page | Used for audience creation purposes to track and manage real-time audience visitors and deliver more relevant content to different segments of visitors. |
| _dy_device | Used for audience creation purposes to cache coarse device data (for example, brand, or tablet vs. smartphone). |
| _dy_csc | Used for experimentation and A/B testing purposes to keep track of events for the "elapsed time" condition. |
| _dyexps, _dy_att_exps | Used for experimentation and A/B testing purposes to keep the state of experiment selections and attribution. It helps track which variant of the experiment a user is assigned to and records their interactions with the website accordingly. |
| _dyrc | Tracks user engagement actions that were not successfully sent to the server during the previous pageview. It typically includes information indicating whether another attempt to send the data should be made. |
| _dybatch | Tracks user engagement actions that were not successfully sent to the server during the previous pageview. It typically includes information indicating whether another attempt to send the data should be made. |
| _dy_cs_session_items | Used for proprietary custom implementation on your website, for Dynamic Yield campaigns to operate correctly. |
| _dy_cs_local_items | Used for proprietary custom implementation on your website, for Dynamic Yield campaigns to operate correctly. |
Updated 5 months ago