This page provides comprehensive information about how we use cookies on our website to enhance your browsing experience, improve website performance, and deliver personalized content. Cookies are small text files that are stored on your device when you visit our site. They help us understand how visitors interact with our website, allowing us to offer a smoother and more efficient user experience. In the table below, you will find detailed information about each type of cookie we use, their purpose, and how long they remain on your device. We are committed to respecting your privacy and providing transparency about the data we collect through cookies. For more information on how we handle your personal data, please see our Privacy Policy.
Essential
Essential cookies enable basic functions and are necessary for the proper function of the website.
| Name | Description | Duration |
|---|---|---|
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
CloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Learn more| Name | Description | Duration |
|---|---|---|
| cf_use_ob | The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds. | session |
| __cfwaitingroom | The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active. | session |
| cf_chl_rc_i | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_ni | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| cf_chl_rc_m | These cookies are for internal use which allows Cloudflare to identify production issues on clients. | session |
| __cfruid | Used by the content network, Cloudflare, to identify trusted web traffic. | session |
| __cf_bm | Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions. | session |
| __cflb | When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool. | session |
| _cfuvid | The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address. | session |
| cf_clearance | Whether a CAPTCHA or Javascript challenge has been solved. | session |
| __cfseq | Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies. | session |
| cf_ob_info | The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic | session |
Comments
These cookies are needed for adding comments on this website.
| Name | Description | Duration |
|---|---|---|
| comment_author | Used to track the user across multiple sessions. | Session |
| comment_author_email | Used to track the user across multiple sessions. | Session |
| comment_author_url | Used to track the user across multiple sessions. | Session |
Statistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Learn more| Name | Description | Duration |
|---|---|---|
| _gali | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds |
| _ga_ | ID used to identify users | 2 years |
| _gid | ID used to identify users for 24 hours after last activity | 24 hours |
| _gat | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute |
| _gac_ | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days |
| __utma | ID used to identify users and sessions | 2 years after last activity |
| __utmt | Used to monitor number of Google Analytics server requests | 10 minutes |
| __utmb | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity |
| __utmc | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | End of session (browser) |
| __utmz | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity |
| __utmv | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity |
| __utmx | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months |
| _ga | ID used to identify users | 2 years |
Hotjar
Hotjar is a behavior analytics tool that helps site owners understand how visitors use their site through heatmaps, session recordings, surveys, and feedback widgets.
Learn more| Name | Description | Duration |
|---|---|---|
| _hjShownFeedbackMessage | This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show. | 365 days |
| _hjptid | This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site. | session |
| _hjAbsoluteSessionInProgress | The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. | 30 minutes |
| _hjFirstSeen | The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information. | 30 minutes |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's page view limit. | 30 minutes |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit | 30 minutes |
| _hjSession_ | A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session. | 30 minutes |
| _hjSessionUser_ | Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar 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 |
| _hjSessionTooLarge | Causes Hotjar 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 |
| _hjSessionRejected | If present, this cookie will be set to 1 for the duration of a user’s session, if Hotjar 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 |
| _hjSessionResumed | A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection. | session |
| hjViewportId | This cookie stores user viewport details such as size and dimensions. | Session |
| _hjSessionStorageTest | This cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set. | Session |
| _hjTLDTest | When the Hotjar 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 |
| _hjCookieTest | This cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set. | Session |
| _hjUserAttributesHash | User Attributes sent through the Hotjar Identify API are hashed and cached in this cookie so Hotjar knows when an attribute has changed and needs to be updated. The cookie is refreshed while the visitor stays active. | 2 minutes |
| _hjCachedUserAttributes | This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool. | session |
| _hjLocalStorageTest | This cookie is used to check if the Hotjar 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 immediately after creating it so the expected storage time is under 100ms. | under 100ms |
| _hjHasCachedUserAttributes | This cookie lets Hotjar know whether the User Attributes cached in the _hjUserAttributes local storage item are up to date. | session |
| _hjid | Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random 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 |
| hj_visitor | hotjar uses cookies to enhance the user’s experience on our website, for example to complete forms, navigating the site, and identify returning users and offer related content. Users can control the use of cookies at the individual browser level. | Session |
| _hjIncludedInSample | Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels. | 365 days |
| _hjClosedSurveyInvites | Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown. | 365 days |
| _hjDonePolls | Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in. | 365 days |
| _hjMinimizedPolls | Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. | 365 days |
| _hjDoneTestersWidgets | Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in. | 365 days |
| _hjMinimizedTestersWidgets | Hotjar cookie. This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site. | 365 days |
Marketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Facebook Pixel
Facebook Pixel is a web analytics service that tracks and reports website traffic.
Learn more| Name | Description | Duration |
|---|---|---|
| _fbc | Used to track the last session visit. | 12 months |
| _fbp | Used to track the user across multiple sessions. | 3 months |
| fr | Used to track the user across multiple sessions. | 3 months |
Google Maps
Google Maps is a web mapping service providing satellite imagery, real-time navigation, and location-based information.
Learn more| Name | Description | Duration |
|---|---|---|
| OGPC | These cookies are used by Google to store user preferences and information while viewing Google mapped pages. | 1 month |
| OGP | This cookie is used by Google to activate and track the Google Maps functionality. | 2 months |
LeadConnector
LeadConnector is the CRM and marketing automation platform behind HighLevel, embedding chat widgets, forms, calendars and call tracking on websites. Its call-tracking and attribution scripts record the traffic source that led to each visit.
Learn more| Name | Description | Duration |
|---|---|---|
| session_id_* | Stores the visitor session id that LeadConnector call tracking uses to tie a phone call back to the visit and the traffic source it came from. One cookie per connected LeadConnector location. | 1 year |
| pool_id_* | Stores the id of the LeadConnector phone number pool used for this visit, so the same tracking number keeps being shown to the visitor. | 1 year |
| poolId_* | Stores the phone number pool id returned by LeadConnector when a tracking number is assigned to the visitor. | 1 year |
| count_* | Records how many tracking numbers the LeadConnector pool holds, so a single number pool can be served from the cached assignment instead of being requested again. | 1 year |
| is_active_* | Records that phone number swapping is switched off for this LeadConnector location, so no further number requests are made for the visitor. | 1 year |
| type_* | Records whether the tracking number for this visit comes from a LeadConnector number pool or a number group. | 1 year |
| in_progress_pool_id_* | Marks that a tracking number request for this number pool is already running, so the same visit does not request a number twice. | Session |
| v2_contact_session_*_session_id | Identifies the visitor session for LeadConnector attribution reporting, which records the referrer, campaign and ad click ids that brought the visitor to the site. Stored in browser local storage when that is available and written as a cookie when it is not. | 30 minutes, or 1 year when the session id is passed in the page URL |
| i18n_redirected | Remembers the language detected for the visitor on an embedded LeadConnector form, survey, quiz or calendar page. | 1 year |
TikTok Pixel
TikTok Pixel is a tracking tool that measures user interactions and optimizes ad campaigns on the TikTok platform.
Learn more| Name | Description | Duration |
|---|---|---|
| ttclid | Used for advertising and conversion tracking. | 13 months |