What is the FPLC cookie?
FPLC is an HTTP cookie found on websites using Google Analytics, particularly when the cross-domain linking feature is enabled (tracking visitors across multiple domains owned by the same entity). It is set by the Google Analytics script (gtag.js or analytics.js) loaded on the page.
The cookie typically appears on a visitor's first interaction with the site, right after the analytics script executes in the browser, provided it has not been blocked by a consent mechanism.
What data it stores
FPLC generally stores an identifier or technical value related to the cross-domain tracking session, used to correlate visits from the same user across different properties. The exact value format is not publicly documented in detail by Google and may vary.
The data collected through this mechanism is sent to Google Analytics servers for processing and statistical reporting.
What it is used for
The main purpose of FPLC is to support the continuity of Google Analytics measurements when a user navigates between different domains belonging to the same business (for example, a main site and a separate online store subdomain).
For the site owner, this cookie helps produce more consistent traffic reports, avoiding the same person being counted as two distinct visitors when moving from one domain to another.
Does it require consent?
CookieFix classifies FPLC under the statistics (analytics) category, as it is tied to Google Analytics. Under GDPR and the ePrivacy Directive (2002/58/EC), cookies in this category are not strictly necessary for the site to function, so they require prior, explicit visitor consent.
- The site owner must describe this cookie in the cookie policy.
- The script generating it must be blocked until consent is given.
- Consent must be as easy to withdraw as it was to give.
How to block or delete FPLC
A visitor can delete or block FPLC from browser settings (Chrome, Firefox, Edge, Safari), under the cookies and site data section, or use script-blocking extensions such as the official Google Analytics Opt-out add-on.
For site owners, the correct compliance approach is to prevent the Google Analytics script from running at all before consent is given. A CMP platform like CookieFix automatically blocks this script from loading until the visitor consents to the statistics category.
Frequently asked questions
It's not risky in the classic sense, but it contributes to tracking browsing behavior across domains, which is why it's treated as indirectly personal data and requires consent.
Its typical duration is around 20 hours, making it one of the shorter-lived Google Analytics cookies.
Yes, any cookie set by Google Analytics, including FPLC, must be explicitly listed in the site's cookie policy, along with its purpose, duration, and provider.
Yes, FPLC is not required for basic site functionality; it only helps produce more accurate statistics across related domains.