What is the fedops.logger.sessionId cookie?
„fedops.logger.sessionId” is part of Wix's internal system called FedOps (Federated Operations), used by Wix to monitor the health and performance of components (widgets, apps) loaded on pages built with its site builder.
It is set automatically by Wix scripts as soon as a Wix-built site loads, regardless of visitor actions. It is not added directly by the site owner but comes bundled with Wix's technical infrastructure.
What data it stores
It stores a unique session identifier generated to group monitoring events (errors, load times, service calls) associated with a single visit to the site.
The exact value format is not publicly documented by Wix and may vary. Data collected through this identifier is sent to Wix's telemetry infrastructure, used for diagnosing technical issues on the platform.
What it is used for
- Helps Wix detect errors and performance issues in the applications loaded on the site.
- Allows correlation of technical events (slow loading, failed requests) within the same browsing session.
- Contributes to the overall stability of the Wix platform for all sites built on it, including the site owner's own site.
- As far as publicly known, it is not used for marketing profiling or targeted advertising.
Does it require consent?
CookieFix classifies fedops.logger.sessionId under the „statistics” category (technical analytics/monitoring). Even though its purpose appears to be internal platform maintenance, it is not strictly necessary for the site's visible functionality, so it should be treated as requiring prior consent under the ePrivacy Directive (Law 506/2004 in Romania) and GDPR.
A Wix site owner should list it in the cookie policy, noting the provider (Wix) and its technical purpose, and ensure it is not activated by default before the visitor gives consent.
How to block or delete fedops.logger.sessionId
A visitor can clear localStorage data through browser settings (e.g., under „Privacy and security” > „Clear browsing data”, selecting site data), separately for each site visited.
For site owners, blocking it automatically before consent is more effective than manual deletion. A consent management platform (CMP) like CookieFix can stop the associated Wix scripts from running until the visitor gives consent, in line with the „consent before placement” principle required by ePrivacy.
Frequently asked questions
It's a localStorage entry, not a traditional HTTP cookie, but ePrivacy rules treat it the same way because it stores information on the user's device.
It appears automatically on any site built with Wix because it's part of the platform's internal FedOps monitoring system; the site owner does not add it manually.
Yes, since it's classified as a statistics/technical monitoring element and is not strictly necessary for displaying the site, prior consent should be obtained.
It generally doesn't affect functionality visible to visitors, but it's part of Wix's infrastructure, so fully disabling it depends on the options the platform and the CMP in use provide.