The Noticeable Widget creates first-party cookies when you embed it on your pages. These cookies are necessary for technical and service purposes: restoring the widget states when browsing between your website pages and/or coming back on your pages later.

Widget Version 2

First-party cookies created by the Noticeable SDK are all starting with the prefix noticeable_:

noticeable_lpr_{PROJECT_ID}: Noticeable cookie that is set once a visitor interacts with publications on a Noticeable widget. It is used to restore the state of publications that have been read. This cookie makes use of browser local storage and remains until the user clears its browsing history or manually deletes the local storage entry.

noticeable_lps_{PROJECT_ID}: Noticeable cookie that is set once a visitor interacts with a Noticeable widget. It is used to restore the state of publications that have been seen. This cookie makes use of browser local storage and remains until the user clears its browsing history or manually deletes the local storage entry.

noticeable_vid_{PROJECT_ID}: Noticeable cookie that is set when a Noticeable widget is loaded. It is used to restore Noticeable widget states. This cookie has a default duration of 365 days.

noticeable_uid_{PROJECT_ID}: When you pass user traits with the Noticeable SDK this cookie is set. It is used to enable cross-device synchronization and restore widget states. This cookie has a default duration of 365 days.

noticeable_traits_{PROJECT_ID}: When you pass user traits with the Noticeable SDK this cookie is set in Session storage (as opposed to legacy cookies). It is used to enrich reactions or comments made by a user. This session cookie gets cleared when the browser / browser tab is closed.

Some cookies (noticeable_lpr_{PROJECT_ID} and noticeable_lps_{PROJECT_ID}) are using browser local storage. The advantage of using local storage cookies compared to legacy cookies (i.e. cookies with an expiration date) is that local storage cookies remain until the user deletes them or the browser free up some space to reclaim storage. Besides, local storage cookies are not sent with every request, in contrary to legacy cookies.

If you are required to set an expiration time to all cookies that are created on your pages, then you can use the Noticeable SDK to disable local storage usage. In that case, legacy cookies are used instead. Such cookies have a default expiration time of 12 months and renew when a user comes back to your page and loads or interact with a Noticeable Widget.

Widget Version 1 (deprecated as of 2021/02/01)

When the Noticeable Widget is embedded on your pages, the following cookies are created:

noticeable:project:{PROJECT_ID}:widget:posts:seen: This cookie appears in the browser local storage to store what posts a user has seen. It is used to know whether new posts should be highlighted between page reloads. This cookie remains until the user clears its browsing history or manually deletes the local storage entry.

noticeable:project:{PROJECT_ID}:widget:posts:read: This cookie appears in the browser local storage to store what posts a user has read. It is used to know whether a post must be marked as read in the widget or not. This cookie remains until the user clears its browsing history or manually deletes the local storage entry.

__cfduid: This browser cookie is a third-party cookie set by Cloudflare when Noticeable Widget resources are loaded. We make use of Cloudflare as a CDN to improve static resource loading. The cookie expires after 30 days. You can learn more about this cookie on the next page: https://support.cloudflare.com/hc/en-us/articles/200170156-Understanding-the-Cloudflare-Cookies#12345682

Additionally, the following cookies may be set depending of the Noticeable features used:

noticeable:project:{PROJECT_ID}:widget:posts:reaction:{POST_ID}: This cookie appears in the browser local storage to store what reaction a user has selected when the emoji reaction feature is enabled on a post. The cookie is used to restore the user choice when a user come back on a post where he has already reacted. This cookie remains until the user clears its browsing history or manually deletes the local storage entry.

noticeable:project:{PROJECT_ID}:widget:posts:feedback:{POST_ID}: This cookie appears in the browser local storage to store when the last feedback was made for a given post when the user feedback feature is enabled . This cookie is used to hide the feedback form when a feedback was already sent recently, thus preventing spam. This cookie remains until the user clears its browsing history or manually deletes the local storage entry.

noticeable:session: This browser session cookie stores user data for the duration of the session when the cross-device synchronization feature is configured: https://help.noticeable.io/en-us/article/widget-cross-device-synchronization-1m7jpkm/. This session cookie is used to pass identity information when a user submits feedback on a post, thus allowing you to know who submitted what feedback and have a means to contact the user back if needed. This session cookie gets cleared when the browser / browser tab is closed.
Was this article helpful?
Cancel
Thank you!