Name	Expiry	Provider	Type	Purpose
.ASPXANONYMOUS	69 days, 10 hours, and 40 minutes	plantanapp.com	HTTP	This cookie is used by sites using the .NET technology platform from Microsoft. It enables the site to maintain an anonymous user-id to track unique users within a session without them logging in or otherwise identifying themselves.
.DOTNETNUKE	session	plantanapp.com	HTTP	Issued by DNN, necessary for site functionality, including forms authentication, created when a user logs in.
__RequestVerificationToken	session	plantanapp.com	HTTP	Anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery. It holds no information about the user and is destroyed on closing the browser.
ASP.Net_SessionId	session	plantanapp.com	HTTP	A cookie which is used to identify the users session on the server. The session being an area on the server which can be used to store data in between http requests.
language	session	plantanapp.com	HTTP	A DNN cookie is created called "language" to store the current language - in a monolingual install this is simply the browser default language, but if the site supports multiple languages then this may be different based on the language selected by clicking in the languages skin object.
_ga	2 years	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gid	session	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gat_gtag_UA_352364_3	1 minute	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
_gat_UA_352364_3	1 minute	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Data Anonimized.
cookieconsent	1 year	plantanapp.com	HTTP	Stores the user's cookie consent state for the current domain.
InfoBoxUserId	session	plantanapp.com	HTTP	In case Plant an App tutorial it is used cookie will make the tutorial continue when you change pages. This helps for reporting and track the tutorials

Name	Expiry	Provider	Type	Purpose
_ga	2 years	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
_gid	session	plantanapp.com	HTTP	Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
_gat	session	plantanapp.com	HTTP	Used by Google Analytics to throttle request rate.
_fap	3 months	plantanapp.com	HTTP	Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.
_fbp	3 months	plantanapp.com	HTTP	Used by Facebook to store and track visits across websites.
__stid	1 year	plantanapp.com	HTTP	Used by ShareThis to track link shares or similiar, and other activities.
__stidv	1 year	plantanapp.com	HTTP	Used by ShareThis to track link shares or similiar, and other activities.
__hstc	13 months	plantanapp.com	HTTP	It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
hubspotutk	13 months	plantanapp.com	HTTP	This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts. It contains an opaque GUID to represent the current visitor.
__hssc	30 minutes	plantanapp.com	HTTP	This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
__hssrc	session	plantanapp.com	HTTP	Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.

Low-Code helping Devops teams hit their KPIs

Key performance indicators (KPIs) are used by DevOps teams to measure how fast, reliable, and good their software development and deployment processes are. Here are some KPIs that DevOps teams often use:

Frequency of deployment: This KPI looks at how often new code is put into production. A more frequent deployment can mean that the process is more efficient and automated.

Change lead time: This KPI measures how long it takes for a change to be made in the code and then sent to production. A shorter lead time can mean that the process of making something is faster and more flexible.

Mean time to recovery (MTTR): is a KPI that measures how long it takes to get back to normal after an incident or service outage. A system that is more resilient and reliable may have a shorter MTTR.

Deployment success rate: This KPI measures the number of successful deployments that don't cause any problems. A codebase that has been tested and is stable can have a high rate of deployment success.

Time to find and fix problems: This KPI measures how quickly a DevOps team can find and fix problems or mistakes in its systems. A more efficient and effective incident response process can mean that it takes less time to find and fix problems.

Code coverage: This KPI looks at how much of the code is tested automatically. A more thorough testing process can be shown by a higher code coverage.

Deployment lead time: This KPI measures how long it takes for new code to go from development to production. A shorter deployment lead time can mean that the deployment process will go faster and better.

Customer satisfaction: This KPI measures how happy customers are with the software or services provided by the DevOps team. When customers are happy, it can mean that the development and deployment process went well.

A low-code platform like Plant an App can help DevOps teams reach the above KPIs in several ways:

Faster development: Low-code platforms come with pre-built components and templates that make it easy for developers to make and launch new apps quickly. This can help cut down on the time it takes to make changes and make deployments happen more often.

Automated Deployment: Low-code platforms often have deployment automation built in. This can help DevOps teams streamline their deployment processes and increase the number of successful deployments.

Simplified Testing: Low-code platforms often have automated testing features that help make sure the code is good and that more of it is tested.

Faster Response to Incidents: Automatic monitoring and alerting features in low-code platforms can help DevOps teams find and fix incidents quickly.

Improved Collaboration: Low-code platforms usually have a visual development interface that lets business users help build apps. This can help IT and business teams work together better and improve customer satisfaction.

Agile Development: Low-code platforms offer a flexible and agile development environment that lets DevOps teams respond quickly to changing requirements and improve their development and deployment processes over time.

Overall, a low-code platform like Plant an App can help DevOps teams improve their software development and deployment processes by making them more efficient, reliable, and high-quality. This can lead to better KPIs across the board.