To function properly, WebMaxy stores first-party cookies on your user’s browser. Cookies are either set by the Webmaxy script, or by visiting WebMaxy’s website.
When you use the WebMaxy script on your website, WebMaxy cookies are responsible for displaying the correct content to your users without personally identifying anyone. When you visit WebMaxy’s website, it is important to note that the WebMaxy script is enabled on this website.
If you do not wish to be tracked by WebMaxy you may do so by following the steps on our Do Not Track page. This will apply to all sites WebMaxy is installed on.
I use the WebMaxy script on my website. Should my users be aware of these cookies? If so, how should I classify them? #
Given the complexities around jurisdictions, privacy laws/regulations, and how you and your team intend to use WebMaxy, it’s best that you seek guidance from your own legal counsel when determining which cookies need to be listed on your site and whether or not a cookie manager should be utilized.
Similarly, your legal counsel will be able to help you determine how to classify cookies. WebMaxy support cannot assist with any questions that might have legal implications.
Cookies set by the WebMaxy script #
| Name | Description | Duration | Data type |
| _hjSessionUser{site_id} | WebMaxy cookie that is set when a user first lands on a page with the WebMaxy script. It is used to persist the WebMaxy User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | 365 days | JSON |
| _hjSession{site_id} | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same WebMaxy session. | 30 minutes | JSON |
| _hjClosedSurveyInvites | WebMaxy cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. | 365 days | Boolean true/false |
| _hjDonePolls | WebMaxy cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. | 365 days | Boolean true/false |
| _hjMinimizedPolls | WebMaxy cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. | 365 days | Boolean true/false |
| _hjShownFeedbackMessage | WebMaxy cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. | 365 days | Boolean true/false |
| _hjSessionTooLarge | Causes WebMaxy to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit. | Session | Boolean true/false |
| _hjSessionRejected | If present, this cookie will be set to ‘1’ for the duration of a user’s session, if WebMaxy rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues. | Session | Boolean true/false |
| _hjSessionResumed | A cookie that is set when a session/recording is reconnected to WebMaxy servers after a break in connection. | Session | Boolean true/false |
| _hjid | WebMaxy cookie that is set when the customer first lands on a page with the WebMaxy script. It is used to persist the WebMaxy User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. | 365 days | UUID |
| _hjRecordingLastActivity | This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that WebMaxy records). | Session | Numerical Value (Timestamp) |
| _hjTLDTest | When the WebMaxy script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. | Session | Boolean true/false |
| _hjUserAttributesHash | User Attributes sent through the WebMaxy Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. | Session | Hash |
| _hjCachedUserAttributes | This cookie stores User Attributes which are sent through the WebMaxy Identify API, whenever the user is not in the sample. Collected attributes will only be saved to WebMaxy servers if the user interacts with a WebMaxy Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present. | Session | JSON |
| _hjLocalStorageTest | This cookie is used to check if the WebMaxy Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | Under 100ms | Boolean true/false |
| _hjIncludedInPageviewSample | This cookie is set to let WebMaxy know whether that user is included in the data sampling defined by your site’s pageview limit. | 30 minutes | Boolean true/false |
| _hjIncludedInSessionSample | This cookie is set to let WebMaxy know whether that user is included in the data sampling defined by your site’s daily session limit. | 30 minutes | Boolean true/false |
| _hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 Minutes | Boolean true/false |
| _hjFirstSeen | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time WebMaxy saw this user. It is used by Recording filters to identify new user sessions. | Session | Boolean true/false |
| _hjViewportId | This stores information about the user viewport such as size and dimensions. | Session | UUID |
| _hjRecordingEnabled | This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. | Session | Boolean true/false |
Users with Disabled Cookies #
WebMaxy does not track or record users who have cookies disabled. In fact, the WebMaxy script doesn’t properly load its different components if it detects that cookies are disabled. Learn more
Cookies set by visiting the WebMaxy website #
Cookies set when you visit the WebMaxy website can be categorized into essential and non-essential cookies.
Essential Cookies #
Essential cookies are set when you visit WebMaxy’s website. They serve to operate the WebMaxy Website and its features in a workable fashion.
To the extent personal data is processed via these cookies, the respective legal basis is Article 6(1)(f) GDPR as operating the WebMaxy website is in our legitimate interest.
| Name | Description | Duration |
| _hjptid | This cookie is set for logged in users of WebMaxy who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site. | Session |
| hjSiteLang | This cookie is set when a page that supports multiple languages on webmaxy.com is visited. This allows us to always load the content in the preferred language when available. | 365 days |
| _hjOptOut | WebMaxy Opt-Out setting. More information can be found on our Do Not Track Page | 4 months |
| X-Access-Key | This cookie keeps your website session alive. | Session |
Non-essential Cookies #
With your consent, non-essential cookies are set when you visit the WebMaxy website. They serve to optimize the user experience, provide us with insights about how users use the WebMaxy website, or are used for marketing purposes.
To the extent personal data is processed via these cookies, the respective legal basis is your consent in accordance with Article 6(1)(a) GDPR. You may withdraw your consent at any time with future effect by adjusting your cookie settings.
| Name | Description | Duration |
| JSESSIONID | New Relic cookie which is used to monitor session counts for an application. Read more | Session |
| optimizely* | This cookie is set by Optimizely to run tests on webmaxy.com Read more | Decided by Optimizley |
| mp_* | This cookie is set by Mixpanel to run track usage on webmaxy.com | Decided by Mixpanel |
| MUID (Microsoft User ID) | This cookie is set by Microsoft as a unique user ID. The cookie enables user tracking by synchronising the ID across many Microsoft domains. | 1 year |
| UserMatchHistory | This cookie is set by LinkedIn Ads for ID syncing. Read more | 30 days |
| bcookie | This cookie is set by LinkedIn to keep track of the browser ID. Read more | 2 years |
| bscookie | A secure browser cookie set by LinkedIn. Read more. | 2 years |
| lidc | This cookie is set by LinkedIn used for routing. Read more. | 1 day |
| lissc | Used by LinkedIn for tracking the use of embedded services. Read more. | 1 year |
| lang | This cookie is set by LinkedIn to set default locale/language. Read more. | Session |
| lang | This cookie is set by ads.likedin.com. Read more. | Decided by Linkedin |
| test_cookie | This cookie is set by Google used to check if the user’s browser supports cookies. | 1 day |
| _gid | This cookie is set by Google Analytics used to distinguish users. Read more. | 1 day |
| _ga | This cookie is set by Google Analytics used to distinguish users. Read more. | 2 years |
| _gaexp | This cookie is set by Google Analytics used to determine a user’s inclusion in an experiment and the expiry of experiments a user has been included in. Read more. | 90 days (typically, depends on experiment length) |
| _gcl_au | This cookie is set by Google Analytics to take information in advert clicks and store it in a 1st party cookie so that conversions can be attributed outside of the landing page. Read more. | 3 months |
| ajs_anonymous_id | This cookie is set by Segment as a randomly generated ID for anonymous users. | 365 days |
| ajs_group_id | This cookie is set by Segment used to group visits by different website users if logged in. | 365 days |
| ajs_user_id | This cookie is set by Segment used for usage analytics if logged in. | 365 days |
| ajs_user_traits | This cookie is set by Segment to identify call is made on webmaxy.com | 365 days |
| _BEAMER_FIRST_VISIT_{product ID} | This cookie is set by Beamer to store the date of this user’s first interaction with insights. | 3000 days |
| _BEAMER_USER_ID_{product ID} | This cookie is set by Beamer to store an internal ID for a user. | 300 days |
| _BEAMER_FILTER_BY_URL_{product ID} | This cookie is set by Beamer stores whether to apply URL filtering on the feed. | 20 minutes |
| _BEAMER_DATE_{product ID} | This cookie is set by Beamer stores Stores the latest date in which the feed was opened. | 300 days |
Adam Wilson #
Adam Wilson comes with an experience of 12+ years in the IT industry. As a Customer Success Manager, he has been researching and trying to understand the customers’ behavior in different scenarios. He has also studied human psychology to relate it to the purchase journey of the customers. His published books on customer psychology and behavior have received many honors and awards from various enterprises.
