In the very first edition of the Processand Newsletter, our CEO & Founder, Thomas, welcomes you to your Process Intelligence journey.
This issue brings you closer to the community with a mix of exclusive content:
Upcoming Events & Webinars: Learn how to prevent revenue leakage in order processing and discover how Process Intelligence drives smarter supply chains with Freudenberg Sealing Technologies.
Success Story: See how Knorr-Bremse improved master data quality and efficiency with Processand’s Watchdog solution.
Community Voices & Use Cases: Real-world insights on solving business challenges with Process Intelligence.
About Processand: Get to know our mission, services, and how we help companies worldwide turn data into action.
Data processing
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. By clicking “Accept All Cookies” you agree that cookies are stored on your device, which assists us to help improve your website experience and help our marketing initiative. For additional information on how the cookies function, select the ”Manage Cookie Settings” or use the link here: Data Policy
Necessary
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
Name:
Content Management System
Purpose:
We use TYPO3 as a content management system (CMS). Cookies are used to store login information, for example.
3 Cookies:
Name:
fe_typo_user
Purpose:
Standard session cookie of TYPO3. Stores the user data in case of a login.
Provider:
https://www.processand.com/
Duration:
Browser session
Name:
be_typo_user
Purpose:
Informs TYPO3 if the user is logged in to the TYPO3 backend and which backend user is active.
Provider:
https://www.processand.com/
Duration:
Browser session
Name:
be_lastLoginProvider
Purpose:
Used for TYPO3 backend login.
Provider:
https://www.processand.com/
Duration:
Browser session
Name:
Data processing management
Purpose:
We remember your data processing consent settings.
1 Cookie:
Name:
consenthandling_status
Purpose:
Cookie for saving settings regarding the consent of data processing.
Provider:
https://www.processand.com/
Duration:
Browser session
Name:
PHP
Purpose:
We use PHP to generate website content.
1 Cookie:
Name:
PHPSESSID
Purpose:
Cookie generated by PHP-based applications. It is a generic identifier used to store user session variables. Usually it is a randomly generated number; how it is used may depend on the particular website. However, a good example is to maintain a user's login status between different pages.
Provider:
https://www.processand.com/
Duration:
Browser session
Analytics
Analytics cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
Name:
Google Tag Manager
Purpose:
We use Google Tag Manager to connect Google Analytics to our website.
We use Google Analytics to register a unique ID that is used to generate statistical data on how the visitor uses the website.
5 Cookies:
Name:
ln_or
Purpose:
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
Provider:
LinkedIn
Duration:
1 day
Name:
_fbp
Purpose:
Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.
Provider:
Meta Platforms, Inc.
Duration:
90 days
Name:
_ga
Purpose:
Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
Provider:
Google
Duration:
400 days
Name:
_gid
Purpose:
Registers a unique ID that is used to generate statistical data on how the visitor uses the website.
Provider:
Google
Duration:
1 day
Name:
_gat_UA-107090104-1
Purpose:
Provider:
https://www.processand.com/
Duration:
1 minute
Name:
HubSpot
Purpose:
We use HubSpot to register a unique ID that is used to generate statistical data on how the visitor uses the website.
5 Cookies:
Name:
__hmpl and hublytics_events_53
Purpose:
This browser storage entry is used by HubSpot Product to temporarily store tracking events created by HubSpot Product until they get dispatched over the network.
It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent.
When tracking consent isn't given, this cookie stays within the current browser session and expires at the end of the session. This "cookie" will remain empty and not store anything.
It contains metadata regarding tracking events that HubSpot collects throughout the user's journey at HubSpot.
It doesn't contain personal identifiable information or information that can identify your device or hardware.
It can't be manually removed and is automatically created whenever conditions are met.
Provider:
HubSpot
Duration:
Browser session
Name:
__hstc
Purpose:
The main cookie for tracking visitors.
It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
It expires in 6 months.
Provider:
HubSpot
Duration:
6 months
Name:
hubspotutk
Purpose:
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.
It expires in 6 months.
Provider:
HubSpot
Duration:
6 months
Name:
__hssc
Purpose:
This cookie keeps track of sessions.
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.
It expires in 30 minutes.
Provider:
HubSpot
Duration:
30 minutes
Name:
__hssrc
Purpose:
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.
