First-party cookies are defined as cookies that are directly used for communication between a website and a user. For example, if you purchase goods in a web shop, the shop uses first-party cookies to identify you and keep track of your shopping cart; you have a direct business relationship with the web shop. The shop needs to know who you are, otherwise you can't pay and the shop can't deliver your purchase to you.
In contrast, third-party cookies are cookies that communicate with other websites, for example advertising services or analytics engines. If a website asked to share your address data with another company, you might not agree to the transaction. Regulations therefore rely on the opt-in concept, in which a user has to explicitly authorize the sharing of their data with a third-party.
AppMon uses only first-party cookies. Real-user metrics are returned securely to their originating URL (the web server behind the URL) and not to a different server in the Cloud that is not under the vendor's control. The visit identification using the first-party cookie is standard technical and business practice.
The following table provides an overview of cookie usage in AppMon. These are all first-party cookies.
|dtCookie||<randomValue> | <encoded application info>||visit||100B||Technical visit ID for PurePath correlation|
|dtLatC||<numeric value>||visit||5B||Measures server latency for performance monitoring|
|dtPC||<serverID>$<randomValue>_<currentMillis>v<randomValue>||visit||54B||Required to identify proper endpoints for beacon transmission; includes visit ID for correlation|
|dtSa1||<URL-encoded action name>||visit||max URL length||Intermediate store for page-spanning actions|
dtSa cookie is used to save user action names, such as
sessionStorage to store a backup of
dtCookie because certain browsers delete random cookies when too many cookies are used. AppMon sets the
localStorage. The following table gives an overview of the key/value pairs that AppMon writes to local storage.