This website only uses Zoho PageSense to analyse the visitors’ behaviour. 

About our cookie policy

At Zoho PageSense, we use cookies to identify and analyze your visitors’ data when they land on your website. This cookie policy is a declaration (or consent) to users on what cookies we add to your website, what visitor metrics we track, for what purpose, and how your users may opt out of the cookies. This cookie policy is part of our privacy policy, which also includes additional details about our information collection and usage.

Why does Zoho PageSense use cookies?

PageSense uses cookies to identify individual visitors and their behavior on your website. These cookies determine whether the visitor is part of an experiment, track visitor views over a variation and let serve the same variation to the visitor consistently over multiple visits, and, finally, track completed goals. They are also used to accelerate your future activities on your website. We use different types of cookies, local storage objects, and similar technologies, each storing a different set of data. These cookies do not interfere with the loading or functioning of the web page at all. Also, they collect information that does not personally identify anyone.

GDPR with PageSense

PageSense’s activities, like tracking visitor behavior on websites and targeting specific visitors for A/B tests, generate data that’s considered private under GDPR. All of this tracked data is stored with anonymized IP addresses, so you can safely capture, process, and use it without infringing on visitors’ data privacy.

Current list of cookies

The following cookies are placed in the visitor’s browser to track and test website visitor activity.

First-party Cookies

These identify and store cookie data on a web browser within the same domain, on which the PageSense tracking code is installed and fired.

Cookie NameInformation StoredGeneration StateExpiry PeriodPurpose
zab_g_{exp_key}
(stores a random alphanumeric string of length 7 or 32)
This cookie stores details such as the experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your a/b test.Sets when the a/b test is configured with a custom or pageview goal into it.1 yearUsed to track successful custom/pageview goal conversions obtained in the same domain.
zabUserIDThis cookie stores a unique user key for every visitor reaching the website.Sets when a user visits for the first time. 1 yearUsed for identifying individual visitors along with the status of new and returning visitors. 
zabVisitIDThis cookie stores a unique visit key every time a user  returns to the web page. Sets every time a user visits.1 yearUsed for identifying every visit made by the user on the web page.
zabSplitThis cookie stores details like experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your Split URL experiments.   Sets when the experiment URL and variation URL are from the same domain. And, when a particular variation is selected for the split URL experiment. 5 secsUsed for sending the experiment and visitor information to the server upon redirection. 
zabBucketThis cookie stores details like experiment key and its corresponding variation key for you a/b or split URL experiments.   Sets when the user’s URL matches with the experiment URL. And if the target audience is satisfied. 1 yearUsed to consistently serve visitors the same variation of the test they’ve seen before. 
zabHMBucketThis cookie stores the experiment key for your heatmap experiments.Sets when the user’s URL matches with the experiment URL. 1 yearUsed for identifying the exact heatmap experiment to be tracked on the web page.
{ exp_key }
(stores a random alphanumeric string of length 7 or 32)
This cookie stores a visit key for the first-time visitor landing in a funnel analysis experiment.Sets when the user’s URL matches with the experiment URL or when the custom event of a funnel step is triggered. 1 monthUsed for deriving the  path taken by the visitor and the number of visitors that dropped off while traversing through the funnel.
{ exp_key }
(stores a random alphanumeric string of length 7 or 32)
This cookie stores details like experiment key and user data (such as browser used, user agent info, etc.) for your form analytics experiments.Sets when the experiment URL and conversion URL are from the same domain.1 hourUsed for tracking actual user conversions.
zsr { expkey }
(stores a random alphanumeric string of length 7 or 32)
This cookie stores a session key for your session recording experiments.Sets when a user’s URL matches with the experiment URL.2 hoursUsed for mapping all the user actions performed within a session.
{ sessionId }
(stores a random alphanumeric string of length 7 or 32)
This cookie stores the session’s metadata for your session recording experiments.Sets once after the user starts interacting on a web page’s session.2 hoursUsed for identifying the start time, last  interacted time, and number  of pages visited for a session.
zabmeThis cookie stores the experiment key of your a/b or split URL experiment chosen from a mutually exclusive group.Sets once a mutually exclusive group is created.1 yearUsed for serving the same experiment within a mutually exclusive group, the user has seen before.
ps_payloadSeqId: This cookie  stores the sequence key for your session recording experiments.Sets once the user starts interacting on a web page’s session.2 hoursUsed to keep track of duplicate payloads (session data).
zabPZBucketThis cookie stores the experience key for your personalization experiments.Sets when the experience is selected in  a personalization experiment and is of type redirection1 yearUsed to consistently serve visitors the same experience they have seen before. 
zPersonalizationThis cookie  stores details like  the  experiment key, experience key, and user data (such as browser used, user agent info, etc.) for your personalization experiments.Sets when the experiment URL and experience URL are from the same domain and is of type redirection.1 yearUsed for sending the experiment and visitor information to the server upon redirection. 
zia_ { projectkey }This cookie stores the identity API details of individual visitors on your website.Sets once the website owner provides the user’s information. 1 yearUsed to  avoid sending the same visitor data multiple times to the server.
zpc< projectkey>  This cookie stores the visitors’ response to the website’s privacy policy.Sets when the visitor makes a choice of privacy consent.1 yearUsed to  ensure that the banner does not reappear to the same visitor on your website.
zps_permission_statusThis cookie stores the granted and denied permission value of the visitor for your web push notification experiments.Sets when the user lands on the website with push notification enabled in it.1 yearUsed to identify and update the push notification status of the subscriber on your website.
{exp_id}+”popup”
(stores a random alphanumeric string of length 7 or 32)
This cookie stores details like the number of times a popup is displayed, the time when the cookie was created, and the popup completion status by individual visitors on your website.Sets when the user’s URL matches with the URL type configured in your popup experiment.1 yearUsed to track user impressions and whether they respond to a popup.
zps-tgr-dtsThis cookie stores the session’s metadata on your websiteSets when a user visits your site for the first time.1 yearUsed for activating your experiment based on a given trigger condition.

Third-party Cookies

These identify recurring visitors on a web browser across different domains and store cookie data under the domain called “cdn.pagesense.io”.

Cookie NameInformation StoredGeneration StateExpiry PeriodPurpose
zab_g_{exp_key}
(stores a random alphanumeric string of length 7 or 32)
This cookie stores details such as the experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your a/b tests. Sets when the a/b test is configured with a custom or pageview goal into it.1 yearUsed to  track successful custom/pageview goal conversions obtained across different domains. 
{ exp_key }  This cookie stores details such as the experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your a/b tests.Sets when the a/b test is configured with a revenue goal into it.1 yearUsed to keep track of successful revenue goal conversions obtained across different domains.
{ variation_url }This cookie stores experiment details like experiment key, variation key, and additional user data (such as browser used, user agent info, etc.) for your Split URL tests. Sets when the variations are from different domains. And,   when a particular variation is selected in the split URL experiment.1 yearUsed for identifying the exact split experiment and its corresponding variation URL for returning visitor.
zab_ { expkey }This cookie  stores details like the experiment key  and user data (such as browser used, user agent info, etc.) for your form analytics experiments.Sets when the experiment URL and confirmation URL are from different domains. And, if the  user submits the form.1 hourUsed for tracking actual form conversions.   
{ exp_key }
(stores a random alphanumeric string of length 7 or 32)
This cookie stores a visit key for the  first-time visitor landing in  a  funnel analysis experiment.Sets when the user’s URL matches with the experiment URL or when the custom event of a funnel step is triggered. 1 monthUsed for deriving the  path taken by the visitor and number of visitors who dropped off while traversing through the funnel.
{ zps_push }This cookie stores text content like bannerpopup, sidepopup, and nopopup when push notifications are enabled in PageSense’s project.Sets when the user lands on the website with the push notification. Used for deciding whether to show or hide the notification box and maintain its position on a website.
{ exp_id } +”polls”This cookie stores details like the number of times a poll was shown, whether the  poll was completed, and the time it was created for your  polls experiment.Sets when user’s URL matches with the poll URL.1 yearUsed for
tracking user actions such as impressions, answered/unanswered polls, and other poll parameters. 
zPersonalizationThis cookie  stores details like  the  experiment key, experience key, and user data (such as browser used, user agent info, etc.) for your personalization experiment.Sets when the experience URL and experience URL are from different domains. And, if  the audience parameter matches with the respective personalization experience. 1 yearUsed for identifying and redirecting users  to consistently show the same experience.

localStorage

These store visitor data locally within the visitor’s browser.

Cookie NameInformation StoredGeneration StateExpiry PeriodPurpose
payloadQueueThis cookie  stores the session’s data on a local storage system for your session recording experiments.Sets when the user starts interacting on a web page.No expiryUsed to resend canceled or failed requests and prevent data loss during session recording.
{ expId }
(stores a random alphanumeric string of length 7 or 32)
This cookie  stores  experiment key and additional user data (such as browser used, user agent info, etc.) on a local storage system for your session recording experiments.Sets once the user starts interacting on a web page. No expiryUsed for identifying and keeping track of  a  visitor’s data during a session. 

sessionStorage

These store visitor data for a session as long as a web browser is open or the web page is refreshed.

Cookie NameInformation StoredGeneration StateExpiry PeriodPurpose
tabUidThis cookie stores the tab ID for your session recording experiments.Sets when  a  user visits for the first time. Cleared once after the browser tab is closed. Used for mapping all the user actions performed within the respective tabs for a session.