What is the bkdc cookie?
bkdc is an HTTP cookie associated with the .bluekai.com domain, belonging to Oracle BlueKai, a data management platform (DMP) used for targeted advertising and audience segmentation. BlueKai was acquired by Oracle and is now part of the Oracle Advertising suite.
The cookie usually appears not directly from the site itself, but through advertising tags, pixels, or marketing integrations (DSPs, media agencies, ad networks) that rely on BlueKai's infrastructure for exchanging audience data. It can be set via calls made from the visited site to the bluekai.com domain.
What data it stores
bkdc typically stores an identifier associated with the visitor's browser, or technical information related to syncing that identifier across partner platforms (a process known as "cookie syncing" or "cookie matching"). The exact value format is not publicly documented and may vary.
Data collected through BlueKai cookies is sent to Oracle/BlueKai servers and may be combined with other behavioral signals (pages visited, inferred interests) to build audience profiles used in programmatic advertising auctions.
What it is used for
The main purpose of the bkdc cookie is targeted advertising: it allows Oracle BlueKai and its partners to recognize a visitor across multiple sites, place them into audience segments (interests, browsing behavior), and sync that identifier with other advertising platforms (DSPs, ad networks).
For the website operator, this cookie has no direct functional role — it supports monetization through more relevant advertising and campaign efficiency for partners operating within the Oracle Advertising ecosystem.
Does it require consent?
bkdc is classified as a marketing/advertising cookie. Under GDPR and the ePrivacy Directive (2002/58/EC, transposed in Romania via Law 506/2004), this type of cookie requires the visitor's prior, explicit, and informed consent before being placed or read.
- The site operator must declare this cookie in the cookie policy, with accurate purpose and duration.
- The script or pixel that sets bkdc must not load before the visitor consents to the "marketing" category.
- Rejecting consent must be as easy as accepting it, and consent must be withdrawable at any time.
How to block or delete bkdc
A visitor can manually delete or block the bkdc cookie via browser settings (Chrome, Firefox, Edge, Safari), either by clearing cookies for the bluekai.com domain or by enabling general third-party/tracking cookie blocking. Anti-tracking browser extensions can also block BlueKai scripts automatically.
For site operators, the correct approach is automatic site-level blocking: a CMP such as CookieFix prevents scripts or pixels that set bkdc from loading until the visitor explicitly accepts the marketing category, helping ensure technical compliance with the prior-consent requirement.
Frequently asked questions
It's an HTTP cookie set by Oracle BlueKai, used to identify visitors for targeted advertising and to sync data identifiers between partner platforms.
It doesn't contain information like a name or address, but the identifier it stores can qualify as personal data under GDPR since it allows tracking of an individual's online behavior.
Yes. As a marketing/tracking cookie, it requires the visitor's prior consent under GDPR and Romania's ePrivacy-based legislation.
Its typical duration is around 6 months, though the exact lifespan may vary depending on the partner's configuration that sets it.