BlueKai Registry

The Oracle BlueKai Registry allows consumers to manage their third-party data and opt-out preference relative to the BlueKai Audience Data Marketplace.

The BlueKai Registry is at Consumers can delete any single data attribute (for example, Reading) tied to their BlueKai cookie by clicking the circular ‘x’ to the left of the data attribute.

data attributes

BlueKai Registry Opt‐Out

Consumers can also completely opt‐out of BlueKai third-party data collection by clicking the Opt Out button on the BlueKai Consumer Opt‐Out page.

Implementing the BlueKai Registry

To get up and running with the BlueKai Registry, you must follow some simple and standard steps starting with customizing the copy of the registry page. The actual copy and copy format displayed on the BlueKai Registry can be customized to suit your creative and stylistic needs. Since the registry page is hosted on the BlueKai servers, it is necessary that any custom content/files be sent to BlueKai. Examples of such content/files include, but are not limited to, the following:

  • Images – Files such as png files, gif files and jpeg files

  • Stylesheets – Generally a CSS stylesheet we can host or a URL to a stylesheet we can link to

  • Copy Document – A text file that provides the copy the partner wants

  • Creative Guidelines – Usually a document that describes how to display text, colors, and images on the registry page in accordance with the rest of the site layout.

Once BlueKai has received all the proper materials and instructions necessary to customize the look and feel of the registry page, we will begin work on your custom instance of the Registry. Upon completion of the initial look and feel, BlueKai will provide a review period (typically 1 week) during which the partner can provide feedback and request any necessary changes. Overall, the full implementation process usually requires 2‐4 weeks depending on the responsiveness of the partner’s review and implementation team.

The partner can include the White‐Label Registry in an <iframe> tag on their site to make it easy to wrap the navigation, header, and footer elements around the registry. This helps provide a seamless look to the registry.

As an alternative to having BlueKai build out the full registry page, BlueKai may provide a feed of data categories on a per user basis directly to the partner through an API. The partner can then manage the full build out of the registry page. In this case, the API will return an HTML table with one data category per row. The following example shows the API call:

The following table lists other values that can be leveraged to control the style of the HTML table returned by the API.

Style Parameter Query String Parameter
Foreground color of the base path &fg=<hex color>
Foreground color of the full path &fpfg=<hex color>
Background color of the base path &bg=<hex color>
Background color of the full path &fpbg=<hex color>
Font of the base path &font=<fontname>
Font of the full path &fpfont=<fontname>
Size of base path font &size=<number>
Size of full path font &fpsize=<number>

Testing the BlueKai Registry

Upon completion of the implementation, the BlueKai Registry should go through primary tests.

First, the look and feel of the registry as well as overall performance should be examined across different browsers. Browser issues need to be assessed as to whether they are related to the partner’s copy and/or formatting or issues arising from BlueKai formatting.

Next, the ability for a consumer to amend their profile by removing individual data categories should also be tested. The partner can follow these simple steps to conduct this test:

  1. Clear your cookies.

  2. Visit the partner’s website and browse across a mix of content.

  3. Load the Registry in the same browser and make sure your profile includes data categories corresponding to your browsing behavior in step 2.

  4. Delete 1‐3 data categories in your profile within the Registry.

  5. Go to another page on the partner’s website.

  6. Reload the Registry.

  7. Confirm that the data categories you deleted in step 4 no longer exist in your profile.