What is the presence cookie?
"presence" is an HTTP cookie set by Facebook (Meta Platforms) on the .facebook.com domain. It is associated with the platform's real-time presence features, such as indicating online status or supporting chat/notification connections while a Facebook account is active in a browser.
On third-party websites, the cookie can appear as a result of loading Facebook social plugins (like/share buttons, Facebook comments, video embeds, or the Facebook Pixel), which trigger requests to Facebook domains even if the visitor doesn't directly interact with those modules.
What data it stores
The cookie stores a technical identifier tied to the Facebook user's session and account, used internally by Facebook's infrastructure to maintain connectivity state. The exact value format is not publicly documented by Meta and may vary.
The data is sent to Facebook's servers (the .facebook.com domain), not to the site hosting the widget. Facebook may correlate this information with other profile and behavioral data collected across its advertising ecosystem.
What it is used for
From Facebook's perspective, the cookie supports real-time presence and communication features of the social platform, embedded in modules distributed across third-party sites (like boxes, comments, video embeds).
For the site hosting the widget, the cookie provides no direct functional benefit, but it is part of Facebook's wider tracking ecosystem, which can contribute to audience measurement and ad targeting across Meta's platforms.
Does it require consent?
CookieFix classifies "presence" under the marketing category (advertising/tracking), since it is tied to the Facebook domain and its cross-site tracking infrastructure.
- Under GDPR and Romania's Law 506/2004 (transposing the ePrivacy Directive), this type of cookie requires the visitor's prior, explicit consent before being set.
- Website operators must list it in their cookie policy, with the purpose and provider clearly stated.
- The Facebook script or widget that generates this cookie should only load after consent for the marketing category has been obtained.
How to block or delete presence
A visitor can delete or block the cookie manually from browser settings (Chrome, Firefox, Edge, Safari – per-site cookie management), or use tracker-blocking extensions targeting the facebook.com domain.
For website operators, proper blocking means Facebook scripts and social plugins should not load by default when the page is visited. A consent management platform like CookieFix can automatically block these scripts (like box, video embed, Pixel) until the visitor consents to the marketing category, preventing the cookie from being set prematurely.
Frequently asked questions
It's a session cookie set by Facebook on the .facebook.com domain, related to the platform's real-time presence features and social widgets embedded on other websites.
It's not technically dangerous, but it is part of Facebook's tracking infrastructure, which is why it's classified as a marketing cookie and requires consent.
Yes. As a marketing/tracking cookie, GDPR and Law 506/2004 require the user's explicit consent before it can be set.
Site operators can use a CMP that automatically blocks Facebook scripts and plugins until consent is given, while visitors can delete or block it directly from their browser settings.