Cookies Policy

Cookie Name	What it does	Explaination	How long it lasts for
GA	Analytics	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center. See here to enable or disable these Google Analytics Cookies:Enabling Google Analytics for your Help Center	1 minute
Google Analytics	Analytics	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	1 day
Zendesk Google Analytics	Analytics	Google Analytics (when enabled in Guide Settings) allows subscribers to gain insights into the use of their help center.	2 years
Zendesk Help Center	Analytics and/or Essential	[LOCAL STORAGE] To help subscribers understand the resources an end-user has attempted in seeking support, this object tracks recently-viewed articles within the help center. This Cookie allows Zendesk customers to identify an end-user's recently-viewed articles. If used exclusively by Subscriber for providing customer support purposes, this could be deemed Essential.	Forever (Local Storage)
Help Center Functionality	Essential	This is only dropped when anonymous end-users actually vote on articles. It is used to track the fact that an anonymous user has voted on an article, so that they are not repeatedly prompted to vote on an article that they have already voted on nor are they able to submit multiple votes relating to one article.	Forever (Local Storage)/Session (cookie)
Help Center Functionality	Essential	Stores unique session key for Help Center product.	Session
Help Center Functionality	Functionality	This cookie is only used in the Request List App. This cookie saves the settings that end-users choose when they configure their own view in the Request List App. It saves which of the available custom values end-users want to filter by and which columns they want to see.	Local storage duration is decided by the browser policy.
Help Center Functionality	Analytics	Stores the text string of an end-user’s search term in the Help Center Functionality. It stores this so that it can check whether a ticket was created after that term was searched. A user identifier is not stored so it is not possible to specify which user completed the search at the time of reporting.