A Year of Momentum: Caregility’s Biggest Moments of 2025
Healthcare delivery continues to evolve as organizations look for new ways to support clinicians, improve operational efficiency, and deliver high-quality care across settings. Virtual care has become an essential part of that transformation—shifting from isolated use cases to enterprise-wide strategies that support teams at scale.
Throughout 2025, we continued to expand our Connected Care platform, partnerships, and capabilities to help health systems operationalize connected care. From new product launches and analytics tools to global expansion and deeper integrations, the year reflected steady progress toward more coordinated, data-driven, and scalable virtual care models.
Below are the 10 key milestones that shaped Caregility’s journey in 2025.
2. Launch of LOOP (Lens on Organizational Performance) Introduced our Lens on Organizational Performance (LOOP), a new analytics framework designed to help health systems quantify the operational, workforce, and financial impact of virtual care programs.
3. Launch of iCare Coordinator At HIMSS 2025, we launched iCare Coordinator – a centralized command hub that brings together virtual care workflows, task management, AI alerts, and bedside support requests into a single, streamlined dashboard.
5. Expanded Global Reach and International Partnerships Expanded our global footprint with new partners and deployments across Japan, Australia, the Middle East, Canada, and other international markets.
6. Epic Toolbox Designation for Inpatient Virtual Care Achieved designation in Epic’s Toolbox for Inpatient Virtual Care, reflecting deep integration with Epic workflows including CAL, ECAL, and Bedside TV.
8. Joint Research Initiative with Nagoya University Hospital Launched a research collaboration in Japan to explore AI-enabled virtual care models tailored to local healthcare needs and workforce challenges.
9. Significant Platform Enhancements Throughout 2025 Across 2025, Caregility released major platform updates, including Control Hub, interoperability upgrades, backend scalability improvements, expanded AI features (ambient listening, augmented observation), and accessibility enhancements.
10. Hosted a Successful Inaugural Customer Connect Summit Our customer community convened on Inova’s campus to share knowledge and ideas with speakers from Microsoft, Mayo, Johns Hopkins, Geisinger, and more!
Looking Ahead to 2026
As virtual care continues to evolve from isolated programs to enterprise strategies, 2025 reinforced Caregility’s role in helping health systems scale care, support clinicians, and deliver better patient experiences.
The momentum from this year sets the stage for continued innovation—and Caregility remains focused on helping connected care work in real-world clinical environments.
A Turning Point for Rural Health: How States, Systems, and Digital Health Leaders Are Shaping What Comes Next
Rural America is in the middle of a rare and powerful moment of alignment. For decades, rural hospitals have been fighting a multidimensional battle: shrinking workforces, widening access deserts, aging populations with rising acuity, and tightening financial margins that make every operational decision existential.
This year, that burden meets an unprecedented opportunity.
Through the One Big Beautiful Bill Act, Congress authorized the $50 billion Rural Health Transformation Program (RHTP), a five-year infusion designed to help states rewrite the future of rural care delivery. States submitted their proposals to CMS in early November, and final funding decisions are expected by December 31, despite federal shutdown delays that required HHS to call furloughed reviewers back to keep things moving.
What happens next will determine whether this becomes a once-in-a-generation modernization of rural healthcare or another fleeting cycle of short-term relief.
Rural Health Needs are Urgent and Growing
Rural communities face higher rates of chronic disease, behavioral health needs, maternal health risks, and care access barriers. The workforce picture is equally stark:
About 20% of the US population lives in rural areas, but only 9-11% of the nation’s physicians practice in rural communities. 1
74% of rural hospital CEOs report needing more RNs. 2
RN staffing density is substantially lower in rural areas versus metro areas, with roughly 65 RNs versus about 100 RNs per 10,000 patients, respectively. 3
Some analyses suggest that a single transferred patient may represent a lost contribution margin of roughly $10,000, a financial reality that compounds the pressure to maintain local access.
Against this backdrop, telehealth stands out as one of the most consistently emphasized modernization levers. In fact, “telehealth” appears 36 times in the RHTP framework, a signal that virtual care is essential to achieving the program’s goals.
Early Signals: How States Plan to Use Funding
Several states have already taken the lead in publicly sharing their RHTP applications, demonstrating an unusual level of transparency for a grant program of this scale. Details from early applications and announcements include:
Maine proposes $200,942,115 over five years to expand telehealth access statewide. 4
Washington plans to allocate $15–18 million annually toward a statewide Provider Technology Fund. 5
Maryland, one of the first states to publish its proposal, emphasizes broad community engagement and technology-enabled care expansion. 6
These early examples show a common thread: states are prioritizing digital infrastructure, care innovation, and workforce sustainability, even though the strategies vary. In a review of 25+ state RHTP announcements, roughly 90% of states included telehealth hub or network language to advance specialist access through programs like tele-stroke, tele-ED, and tele-behavioral health. Workforce reinforcement and mobile telehealth access were also highlighted as key initiatives by many states.
Some may centralize funding through statewide contracts. Others will distribute funds through competitive grants, regional collaboratives, or direct sub-awards to rural facilities. This variation matters and hospitals that prepare early will have the most to gain.
What Rural Leaders Should Be Doing Right Now
During our recent National Rural Health Association (NRHA) webinar, four national thought leaders – Connor Communications Grant Strategist Angela Connor, MA; Caregility CNO Susan Kristiniak, DHA, MSN, RN, NEA-BC, AHN-BC; Health Recovery Solutions CEO Jason Comer, JD; and Equum Medical Chief Marketing Officer Karsten Russell-Wood, MBA, MPH – outlined a clear path forward for rural health organizations preparing for RHTP funding.
Here are the key themes they shared.
1. Prepare: Understand Your State’s Plan and Build Your Own
With RHTP approvals coming soon, Connor underscored the importance of early readiness, encouraging hospitals to:
Review their state’s posted RHTP application to understand priorities, timelines, and distribution models.
Contact their State Office of Rural Health, which will be central to coordinating sub-grants.
Define strategic needs now, rather than waiting for a grant window to open.
Build programs “as if budget weren’t the constraint,” to respond quickly and convincingly.
The takeaway: When states begin awarding funds, hospitals with clear, shovel-ready initiatives will be far ahead of those still brainstorming.
2. Repair: Rebuild Workforce Capacity with Connected Care Tools
Kristiniak brought the inpatient lens to the conversation: rural workforce strain isn’t theoretical. It shows up in fall rates, throughput challenges, safety risks, burnout, and rising overtime.
She emphasized how hybrid care models such as virtual nursing, virtual observation, remote specialist consults, and AI-enabled monitoring relieve both cognitive and physical burden on bedside teams. She highlighted data points rural hospitals can expect when leveraging virtual care:
Faster admissions and discharges
Reduced overtime
Lower fall and hospital-acquired infection rates
Shorter length of stay
Better HCAHPS and discharge readiness scores
These are not abstract possibilities; they’re real outcomes already documented across community and rural hospitals using connected care models.
3. Care: Extend the Continuum Beyond the Hospital Walls
Comer spoke to the reality that modern rural care must extend beyond the inpatient setting. Longitudinal virtual care models such as Transitional Care Management, Remote Patient Monitoring, Chronic Care Management, and Advanced Primary Care Management are essential to the RHTP goals of keeping patients healthier, at home, and connected to their care teams.
He shared emerging success in areas like:
Maternal health: early detection of cardiac complications and reduced postpartum risk
Oncology: fever flagging, renal monitoring, and symptom tracking
Cardiology and endocrinology: continuous, data-driven chronic condition management
These models are reimbursable, scalable, and aligned with RHTP’s emphasis on high-quality care as close to home as possible.
4. Solve the Specialist Gap with Fractional Coverage and Rural Networks
Russell-Wood highlighted a critical reality: many rural hospitals lose patients because they lose specialists. Recruitment cycles stretch 12 months or more, and locums can cost 1.5 to 2X the cost of a permanent hire.
Fractional models for specialties such as neurology, cardiology, pulmonology, and beyond allow hospitals to “subscribe” to the exact specialist time they need. Combined with regional telehealth collaboratives, this creates:
Faster access to expertise
Reduced unnecessary transfers
Higher revenue retention
Stronger local clinical confidence
These models directly support RHTP goals around sustainability, care access, and innovative delivery.
The Bigger Picture: Rural Health Is Entering a New Era
If there is a single takeaway from the NRHA panel, it’s this:
Rural hospitals cannot succeed in isolation. This is a moment for connected strategy, connected technology, and connected care.
For many rural leaders, this is the first time in their careers that strategic vision, federal investment, workforce innovation, and community need have aligned so clearly. The organizations that use RHTP funding to build durable, tech-enabled care models rather than one-off pilots will define what rural care looks like for the next decade.
Ready to Build Your RHTP-Aligned Roadmap?
Caregility partners with rural hospitals and state agencies to design sustainable virtual care programs aligned to the five strategic pillars of RHTP, from regional telehealth hubs to support specialist access to inpatient virtual nursing and AI-assisted observation.
If you’d like to explore how connected care can support your rural hospital’s transformation strategy, set up a discovery call today.
Caregility Raises $25 Million to Drive the Future of Hospital-Based Virtual Care
Funding underscores confidence in Caregility’s AI and computer vision solutions that reduce staff burden and enhance patient care.
Wall, NJ – September 23, 2025 — Caregility Corporation, an enterprise telehealth leader dedicated to connecting care for patients and clinicians everywhere through innovative virtual care and AI-powered solutions today announced it has raised an additional $25.1 million through its Series A-2 Preferred Stock and Series C funding rounds. The round was led by Star Mountain Capital, with participation from a number of sources, including management, Dr. York Wang, PhD, initial founders, and high-net-worth healthcare-focused investors. This financing brings the total outside investment in Caregility to $92 million.
The new capital will accelerate Caregility’s growth initiatives, with a focus on leading in artificial intelligence solutions, computer vision, ambient listening, and sensor-based solutions that improve clinical workflows, reduce staff burden, and enhance patient care.
“Caregility is setting the standard for innovation in hospital-based virtual care, with groundbreaking capabilities such as edge-based Computer Vision AI and audio sensing room duress detection,” said Dr. David Shulkin, M.D., Independent Board Member of Caregility. “Caregility has expanded these advancements globally, and their platform is uniquely positioned to redefine how hospitals deliver safe, efficient, and high-quality care.”
Caregility has established itself as one of the world’s most widely adopted enterprise telehealth platforms, with more than 30,000 connected devices, over 6 million virtual sessions conducted annually, and deployments across 1,500 hospitals and 75+ health systems. The company’s modular platform supports a comprehensive range of solutions spanning virtual nursing, e-sitting, hospital-at-home, specialty consults, operating room telehealth, and more. Recognized for its reliability and flexibility, Caregility is the only organization in the space serving customers on a truly global scale, with successful deployments in markets including Asia-Pacific, Gulf Region, Middle East, and Canada, in addition to the U.S.
“This strategic investment strengthens our ability to accelerate innovation and scale more aggressively in the marketplace,” said Tod A. Nestor, Chief Financial Officer of Caregility. “With this capital, we can advance AI-driven solutions that meaningfully reduce clinician burden, improve patient outcomes, and deliver measurable and tangible value of the connected care programs deployed by our hospital partners.”
“Caregility is at a pivotal moment in its growth,” said Ron Gaboury, Chief Executive Officer of Caregility. “We’ve built a trusted foundation with many of the world’s leading hospitals and health systems, and this funding empowers us to accelerate the next wave of innovation that will shape the future of smart hospitals and connected care.”
About Caregility
Caregility (www.caregility.com) is a telehealth solutions company dedicated to connecting patients and clinicians everywhere. Our Caregility Connected Care™ platform powers a full suite of clinical and operational applications, enabling care delivery across the continuum, from the hospital to the home. With secure, reliable, and scalable technology, Caregility is transforming healthcare by making virtual care a seamless extension of the care team.
As telehealth’s entrenchment in healthcare delivery continues, stakeholders are exploring ways to apply the technology in specialized patient care.
Many of those initiatives seek to improve health access and equity for vulnerable populations such as adults with Intellectual and Developmental Disabilities (IDD), aging populations, and other marginalized groups. Interest in condition-specific telehealth programs is also rising as providers aim to improve care for patients navigating treatment for things like cancer, AIDS, mental health conditions, and substance use disorder.
To fund these programs, many resource-strapped, independent, and rural healthcare facilities turn to grant programs. If you fall into this camp, here are several funding opportunities you may wish to consider applying for to support your virtual care initiative.
Federal Telehealth Funding Opportunities
Federal agencies invest millions annually to support better access to quality care for rural and underserved areas.
The Federal Communications Commission (FCC) Rural Health Care Program provides support to eligible healthcare providers for “telecommunications and broadband services necessary for the provision of healthcare.” Supported in collaboration with Universal Service Administrative Company (USAC), a not-for-profit corporation charged with administering federal grant funds, the Rural Health Care Program includes two facets:
The Healthcare Connect Fund Program provides a 65% discount on eligible broadband connectivity expenses for eligible rural health providers.
The Telecommunications Program provides reduced rates to rural health providers for telecommunications and voice services for the use in telehealth.
Additional federal funding opportunities for telehealth and broadband-related programs can be found at Telehealth.HHS.gov. Built by the Health Resources and Services Administration (HRSA), an agency of the U.S. Department of Health and Human Services (HHS), the site aggregates active funding programs from various outlets including but not limited to:
National Institutes of Health (NIH)
National Institute of Mental Health (NIMH)
National Cancer Institute (NCI)
National Institute on Aging (NIA)
National Institute on Minority Health and Health Disparities (NIMHD)
National Institutes on Drug Abuse (NIDA)
Office of Disease Prevention (ODP)
Foundation Grants
Several public and private foundations offer annual grant application opportunities. Examples include:
The Legacy Foundation of Southeast Arizona is a private foundation that funds nonprofit organizations promoting population health in Cochise and eastern Santa Cruz counties.
Additional Telehealth Grant Portal Resources
The National Consortium of Telehealth Resource Centers offers a broader list of current and upcoming funding opportunities available through foundations and within specific regional offerings. Each has either a focus on or a strong potential for telehealth applications.
The Rural Health Information Hub highlights non-Federal funding opportunities for the use of telehealth in rural settings.
HRSA Office for the Advancement of Telehealth also offers numerous grants to expand and enhance healthcare services, including telehealth, particularly for underserved populations.
Grant Application Recommendations
If you are considering applying for a grant, keep in mind that you do not have to look for grants specifically targeted at telehealth. Most grants encourage the use of technology as part of the solution.
Here are a few additional tips:
Register with sites to receive notice of funding opportunity (NOFO) updates.
Carefully review eligibility criteria to ensure your organization qualifies for funds.
Have a specific plan and well-thought-out program roadmap built prior to applying.
Be aware of all submission requirements, including caveats related to fund matching or precursory Letter of Intent steps you may need to take.
Submit your proposal on time or – better still – ahead of the deadline.
Make sure you’re well-versed in post-award requirements your organization will be expected to meet should you be awarded funding.
Ensure you have cash flow available to cover up-front costs for reimbursement-oriented funding programs.
Develop a plan for program sustainability beyond grant funding.
In the event that your organization does not qualify for grant opportunities or fails to secure funding after applying for one, don’t lose hope! Fleet lease options, pay-as-you-go subscription-based pricing models, and pilot programs through your telehealth partner represent just a few of the other avenues available to bring your virtual care program to life.
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
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
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
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
_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
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
cookiePreferences
Registers cookie preferences of a user
2 years
Hotjar is a powerful analytics tool that helps you understand user behavior through heatmaps and session recordings.
Name
Description
Duration
_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
_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 cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
session
_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
_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.
-
_hjHasCachedUserAttributes
This cookie sets when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID.
365 days
_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
_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
_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
_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
_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
Vimeo is a video hosting platform for high-quality content, ideal for creators and businesses to showcase their work.
Collects analytical tracking information about videos and enables the player to function properly.
2 years
sd_identity
Collects analytical tracking information about videos and enables the player to function properly.
2 years
continuous_play_v3
Used to keep track of whether continuous play is on or not for a user
2 years
Player
This first party cookie created by Vimeo is used to remember user’s player mode preferences.
1 minute
vuid
This first party cookie created by Vimeo is used to assign a Vimeo Analytics unique id.
1 minute
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Name
Description
Duration
hubspotutk
Hubspot
1 day
__hstc
Hubspot
6 months
__hstc
Hubspot
1 day
__hssrc
Hubspot
1 day
__hssc
Hubspot
1 day
HubSpot is an all-in-one marketing, sales, and customer service platform that streamlines business growth.
Name
Description
Duration
hs-messages-hide-welcome-message
This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
1 day
hubspotapi-prefs
This is used with the hubspotapi cookie to remember whether the user checked the 'remember me' box (controls the expiration of the main cookie's authentication).
1 Year
hubspotapi
This cookie allows the user to access the app with the correct permissions.
7 days
__hs_opt_out
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
13 months
hubspotapi-csrf
This is used for CSRF prevention - preventing third party websites from accessing your data. Expires after a year.
1 year
__hs_do_not_track
This cookie can be set to prevent the tracking code from sending any information to HubSpot.
13 months
__hs_cookie_cat_pref
This cookie is used to record the categories a visitor consented to.
6 months
__hs_initial_opt_in
This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
7 days
__hs_gpc_banner_dismiss
This cookie is used when the Global Privacy Control banner is dismissed.
180 days
hs_ab_test
This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
session
__hs_notify_banner_dismiss
This cookie is used when the website uses a Notify consent banner type.
180 days
hs-messages-is-open
This cookie is used to determine and save whether the chat widget is open for future visits.
30 minutes
__hsmem
This cookie is set when visitors log in to a HubSpot-hosted site.
1 year
hs-membership-csrf
This cookie is used to ensure that content membership logins cannot be forged.
session
hs_langswitcher_choice
This cookie is used to save the visitor's selected language choice when viewing pages in multiple languages.
2 years
__hstc
The main cookie for tracking visitors.
13 months
hubspotutk
This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
13 months
__hssc
This cookie keeps track of sessions.
30 minutes
__hssrc
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
session
messagesUtk
This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser.
13 months
LinkedIn Insight is a web analytics service that tracks and reports website traffic.