Cookies
mediarithmics tracking capabilities rely on first-party cookies, third-party cookies, and local storage variables to identify browsers and capture their activity.
Cookies installed on the third-party domain .mediarithmics.com
.mediarithmics.comThese cookies are created on the third-party domain .mediarithmics.com (or on the custom domain if used).
Cookie name
Description
Life duration
mics_vid
mediarithmics third-party cookie identifier
1 year
mics_lts
The last time the browser has been seen
1 year
mics_uaid
Legacy cookie that will be deprecated
1 year
chk
In the case of a call on events.mediarithmics.com without a cookie mics_vid, this cookie is written to check that the user browser supports third party cookies. It contains a randomly generated UUID.
1 hour
Cookies installed on the first-party domain
These cookies are created on websites where mediarithmics javascript tag is installed.
Cookie name
Description
Life duration
mics_vid
Duplication of mediarithmics third-party cookie identifier bearing the same name. Used for caching purposes to avoid unecessary calls.
1 year
mics_lts
The last time the browser has been seen
1 year
mics_<site_token>
First-party identifier for the browser (also called "installation ID")
1 year
Local storage variables on the first-party website
Local storage is only used on websites where mediarithmics javascript tag is installed.
Key
Description
_mediarithmics
Per site token: lastFeedRefreshDate
Is created only if you have added the syncFeeds
<site_token>_mics_up
This variable is only present if the Edge feature is activated.
It stores user data, structured as a user point model, including device characteristics, the browsing history on the first-party website and the segments to which the user belongs to.
mics_sgmts
This variable is only present if the Edge feature is activated.
It stores the list of segments to which the user belongs to (duplicate from the above one).
Additional cookies and local storage variables when using client-side feeds
Client-side feeds are connectors that involve loading additional javascript, provided by mediarithmics or by a partner (e.g. Facebook Pixel) within the user's browser.
If you are using client-side feeds, it is likely that additional cookies and local storage variables are created. Please refer to the related documentation for additional details.
Description of the javascript tracker behaviour
The list of calls is generated by the javascript tag.
URL
Description
mediarithmics static javascript tag. Contains the implementation of methods used in the snippet.
Configuration parameters regarding the tag on the website.
Also contains a randomly generated first party identifier ("installation ID")
Checks if the user belongs to a segment with a tag feed attached
Starts the cookie-matching process with Google and Xandr (if activated)
Ends the cookie-matching process with Google and Xandr (if activated) by inputting the ID
Asks for the creation of a mediarithmics third-party cookie identifier (mics_vid).
If cookie-matchings with partners are configured, the response will install pixels for those partners.
Create a tracking event in the datamart related to the site.
The following additional calls are made if the Edge feature is activated.
URL
Description
Allows the translation of the browser UserAgent into device characteristics.
static.mediarithmics.com/tag/2/evaluator.min.js
Downloads the local segment evaluator.
events.mediarithmics.com/v1/sites/<site_token>/segment.js
Downloads the definition of Edge segments.
Other redirects that might happen in the process
URL
Description
events.mediarithmics.com/v1/check_cookie/pixel
events.mediarithmics.com/v1/update_mapping/pixel
cookie-matching.mediarithmics.com/v1/get_or_create
Last updated