ASP.NET_SessionId
Module: Functional
Expires: When you leave the site, the cookie is deleted.
Extends: Automatically
Type: First-party cookie
About: This cookie stores data during your visit. The cookie remembers, for example a selection you have made or which or which page you have you have seen before. Without the cookie, the site will only function limited
ppms_privacy_<appID>
Module: Consent Manager
Expires after: 365 days (can be changed), 30 minutes (for anonymous tracking)
Type: First-party cookie
About: Stores visitor’s consent to data collection and usage.
Lang_elected_culture_code
Module: Functional
Expires after: 365 days
Type: First-party cookie
About: Stores visitor’s language selection
Expires after: 30 minutes (can be changed)
Type: First-party cookie
About: Shows an active session of the visitor. If the cookie isn’t present, the session has finished over 30 minutes ago and it was counted in a pk_id cookie.
_pk_id.<appID>.<domainHash>
Module: Analytics
Expires after: 13 months (can be changed)
Type: First-party cookie
About: Used to recognize visitors and hold their various properties.
Visitor_id<accountid>
Module: Marketing automation
Expires after: 1 year
Type: First-party cookie
About: The visitor cookie includes a unique visitor ID and the unique identifier for your business unit. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct business unit. The visitor value is the visitor_id in your business unit. This cookie is set for visitors by the Account Engagement tracking code.
pi_opt_in<accountid>
Module: Marketing automation
Expires after: 1 year
Type: First-party cookie
About: If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a true or false value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to true, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to false. The visitor cookie is disabled, and the visitor isn’t tracked.
visitor_id<accountid>-hash
Module: Marketing automation
Expires after: 1 year
Type: First-party cookie
About: The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor and access corresponding prospect information.
lpv<accountid>
Module: Marketing automation
Expires after: 1 year
Type: First-party cookie
About:This LPV cookie is set to keep us from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot
Module: Marketing automation
Expires after: 1 year
Type: First-party cookie
About:A session cookie named pardot is set in your browser while you’re logged in as a user or when a visitor accesses a form, landing page, or page with Account Engagement tracking code. The cookie denotes an active session and isn’t used for tracking.
In addition to cookies, Makino uses local storage in the visitor’s browser to stack some information. Here’s what is kept in that storage.
ppms_webstorage
Module: Tag Manager, Consent Manager and Analytics
About: Prevents visitor’s data loss that may happen because of some mechanisms used by browsers, for example, Safari’s ITP.
Value: A stringified object that contains information about created cookies for each module. It stores data about each created cookie, such as a key, value, expiry date, path, domain, and more. This is the same data that was used to create a cookie.
Removed if: A ppms_webstorage item isn’t removed automatically. But a visitor can delete it manually. Single entries in the object are removed after a corresponding cookie expires.