Quantcast Cookies

Quantcast collects information sent to us by browsers that encounter our Tags, including, for example, browser type, browser time, time of access, screen resolution, IP address, referring site URL, current site URL, and search strings. Some information that Quantcast collects is configured by website publishers. The table below summarizes information Quantcast may receive from browsers:

Parameters passed via url parameters
Parameter (Example)Description
r=288408424Random number that prevents the browser from using cached data instead of contacting Quantcast’s servers
a=p-bcLY1rnM-2-Publisher’s unique Quantcast Measure ID (unique to the publisher, not the browser)
fpan=0True/false field for indicating whether the first party cookie was newly set on this request
fpa=P0-637818636-1294088227693A value of a first party cookie value set in a non-Quantcast domain such as a publisher’s domain; the first-party cookie appears in the browser as a cookie named “__qca”
ns=0True/false field for whether the pixel is firing from the top level window (i.e., this answers the question: is the pixel firing from inside an iframe?)
ce=1True/false field for whether cookies are enabled in the browser
je=1True/false field for whether javascript is enabled in the browser
sr=1920x1200x24Screen resolution
enc=nDoes the browser support URL encoding for ref, url, and ogl parameters?
dst=1True/false field for whether daylight savings is in effect
et=1348600176786Unix timestamp
tzo=240Time difference in minutes between UTC time and local time
ref=http%3A%2F%2Fm.kotaku.comEncoded referring URL
url=http%3A%2F%2Fm.kotaku.com%2F5985087Encoded URL of page where pixel fired

Encoded ogl data

This refers to Facebook’s Open Graph Data. It reflects website customizations that enable the publisher’s website integration with Facebook.
labels=“Author.John Doe”
Publisher-configured labels to segment the audience
event=loadThe type of browser event that caused the pixel to fire. Load refers to page load. Other common examples are refresh and click events.
rf=0Rule Fetch status indicating if publisher-configured rules have been fetched from Quantcast
cm=TRUSTArc Consent Manager status (may be blank)
source=tealiumName of a publisher’s tag manager integration, if applicable
gdpr_consent=General Data Protection Regulation (“GDPR”) consent string, if applicable. This parameter may be sent from your browser after receiving consent from a Consent Management Provider. If no consent string exists (if GDPR does not apply, for instance), this parameter is absent
gdpr=0A “1” Indicates that GDPR applies to the request; a “0” indicates that it doesn’t apply
qjs=Indicates that the pixel request was initiated by a script (as opposed to an image-based pixel, for instance)
A value indicating the type of the value of the user-hash passed in the ‘uh’ parameter.
(0 = Email, 1 = SHA256, – / 2 = Unknown)
Hashed version of customer provided id for the current user.
Value of pubcommon id
Version of quant.js used to generate this ur
the domain of the website the request comes from
Parameters passed via cookie-headers
Parameter (Example)Description
mc=5bb75135-bd606-808bc-f1290A value of a third-party cookie set in the quantserve.com domain which is a domain managed by Quantcast; the third-party cookie appears in the browser as a cookie named “mc”
d=EE8BcwGtGoEAs9-TDCo774OTmYcMv7AL73ori6KSyKwsPt4bOfTBn5I8n1fugPyNEOzCgu2OHBwJ7wv6ggACYbvGwgGOxIwMJ9V6eLnbnqK-_HbFcsC8gQbFcsC5cGxXLAuYIGxXLAvplqnPI2AzFoAA value of a third-party cookie set in the quantserve.com domain. The value of this cookie is a compact encoding of the mc cookie’s membership in retargeting segments and information about third-party partners of Quantcast, such as advertising exchanges. The third-party cookie appears in the browser as a cookie named “d”
Cookie value indicating the current user has opted out of quantcast services
Metadata about the quantcast opt out