What is the _lo_uid cookie?
_lo_uid is an HTTP cookie associated with Lucky Orange, a platform that analyzes website visitor behavior through heatmaps, session recordings, and conversion form analytics. It is set by the Lucky Orange tracking script, usually on a user's first visit to a site that has the tool installed.
The cookie appears as soon as the Lucky Orange tracking code loads and runs on the page, regardless of whether the visitor actively interacts with the site.
What data it stores
_lo_uid stores a unique identifier generated for the visitor, which Lucky Orange uses to recognize the same user on subsequent visits. The exact value format may vary and is not publicly documented in detail by the provider.
Data collected under this identifier (sessions, mouse movements, clicks, form interactions) is sent to Lucky Orange's infrastructure for processing and display in the client's dashboard.
What it is used for
The cookie's main purpose is analytical continuity: it lets Lucky Orange link a returning visitor's actions across sessions to a single profile, so the site owner sees consistent behavioral statistics such as click maps, scroll depth, and session recordings.
For a site administrator, this translates into insight into how users navigate the site, where they run into friction, or where they abandon a form or conversion flow.
Does it require consent?
_lo_uid falls under the statistics (analytics) category, since it is not strictly necessary for the site's technical operation but rather for measuring and analyzing visitor behavior.
- Under the ePrivacy Directive (as transposed locally, e.g. Romania's Law 506/2004) and GDPR, this type of cookie requires the user's prior, explicit consent before being placed.
- Site administrators must disclose this cookie in the cookie policy and correctly classify it under the “statistics” category in the consent banner.
- The Lucky Orange script itself must be blocked until consent is given, not just the cookie.
How to block or delete _lo_uid
Visitors can delete or block this cookie from their browser settings (Chrome, Firefox, Edge, Safari), typically under per-site cookie management, or by using private/incognito browsing. Anti-tracking browser extensions may also prevent the Lucky Orange script from loading at all.
For site administrators, blocking must happen at the script level, not just the cookie: the Lucky Orange script should only run after a visitor accepts the “statistics” category. A consent management platform like CookieFix can automatically block this script until consent is obtained, preventing the cookie from being set prematurely.
Frequently asked questions
It's an HTTP cookie set by Lucky Orange to uniquely identify a visitor and link their sessions and behavior recordings to the same user.
It's not a cross-site advertising tracking cookie; it's used strictly for behavioral analytics on the site itself, though it still involves processing behavioral data that requires consent.
It typically lasts around 2 years from when it's set, and may be refreshed on subsequent visits.
Yes, as a statistics/analytics cookie, it requires the visitor's prior consent under the ePrivacy Directive and GDPR, and the script must be blocked until consent is given.