What is the ytidb::LAST_RESULT_ENTRY_KEY cookie?
ytidb::LAST_RESULT_ENTRY_KEY is a localStorage key set by YouTube (Google) when a YouTube video is embedded on a page, or when a user visits youtube.com directly. It is part of the YouTube player's internal mechanism for selecting the fastest available video server.
It typically appears as soon as the YouTube embed player loads and attempts to play content, depending on the embed player's configuration, regardless of whether the visitor presses play.
What data it stores
The stored value is a technical identifier related to the outcome of the last connection attempt to YouTube's (Google) video delivery infrastructure, used to optimize delivery speed. The exact value format is not publicly documented in detail by Google.
The data is kept locally in the browser's localStorage under the youtube.com/googlevideo.com domain and is not visibly transmitted to third parties beyond Google/YouTube infrastructure.
What it is used for
Its main purpose is technical: YouTube uses this information to quickly decide which video server subsequent requests should be routed to, reducing load times and improving video playback performance.
For the site owner embedding YouTube videos, the effect is indirect — it contributes to smoother playback of embedded video content, without serving an analytics or advertising purpose for the host site itself.
Does it require consent?
CookieFix classifies ytidb::LAST_RESULT_ENTRY_KEY as preferences/functional, tied to the YouTube video player. Since it is stored by a third-party domain (YouTube/Google) and is not strictly necessary for the host site to function, it should be treated as requiring prior visitor consent under GDPR and the ePrivacy Directive (transposed in Romania via Law 506/2004).
Site owners must disclose it in their cookie policy and ensure the embedded YouTube player (and thus the localStorage write) does not load before the visitor consents to the relevant preferences/marketing category.
How to block or delete ytidb::LAST_RESULT_ENTRY_KEY
Visitors can delete this entry from their browser's site data settings (Local Storage/Site Data) for the youtube.com domain, or use a private/incognito window.
- In-browser: Settings → Privacy → Site Data → search youtube.com → delete
- On-site: administrators can use a CMP such as CookieFix, which automatically blocks the embedded YouTube player (and therefore the localStorage write) from loading until the visitor accepts the relevant category
Frequently asked questions
It's a localStorage entry, not a classic HTTP cookie, but under ePrivacy law it is treated the same way since it stores data on the user's device.
No, it does not contain directly identifiable personal data — it's a technical marker about YouTube video server connection performance.
Yes, since it's stored by a third-party service (YouTube) and isn't strictly necessary for the host site, it should be treated as requiring prior consent.
By using a CMP that delays loading of the embedded YouTube player until the relevant cookie category is accepted, or by manually clearing it from browser settings.