Google Analytics
The Google Analytics JavaScript libraries use HTTP Cookies to “remember” what a user has done on previous pages and interactions with the website. Google Analytics does not collect any personal information about your website users. Read the Google Analytics Privacy Document for more details.
Cookie Name | Expiration Time | Description |
__utma | 2 years from set/update | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmb | 30 mins from set/update | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. |
__utmc | End of browser session | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the__utmb cookie to determine whether the user was in a new session/visit. |
__utmz | 6 months from set/update | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. |
__utmv | 2 years from set/update | Used to store visitor-level custom variable data. This cookie is created when a developer uses the_setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated_setVar method. The cookie is updated every time data is sent to Google Analytics. |
WooCommerce
Cookie Name | Expiration Time | Description |
woocommerce_items_in_cart, PHPSESSID_ | End of browser session | These cookies are used by the online shop to allow it to function correctly. This information is cached in your browser and expires after your session. |
What are Cookies?
Cookies enable the website to remember your actions and preferences (such as login, language, font size and other display preferences) over a period of time, so you don’t have to keep re-entering them whenever you come back to the site or browse from one page to another.
Deleting Cookies
If you do this, however, you may have to manually adjust some preferences every time you visit a site and some services and functionalities may not work.
WordPress
On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area, /wp-admin/.
After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use.
WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface.