Server Data Transfer FAQs

These questions and answers can help you better understand Server Data Transfer.

What if our server will be off-line for any period of time for maintenance or other scheduled down times?

If you know your server will be down for a period of time, you should set your data campaigns to Idle during that period. Contact your Client Service Manager with any questions regarding this issue.

Why is a pixel still required for Server-side Data Transfer (SDT)?

Oracle BlueKai uses the pixel URL as an identifier to trigger a server-to-server response. Oracle BlueKai looks for and matches on a defined pattern from the buyer to initiate a server-side data transfer (we regex the pixel). The pattern can be any part of the pixel URL path (subdomain or parameter). By using this method of "activating" a server-side data transfer, Oracle BlueKai enables you to provide clients with a pixel exactly like the current pixel transfer workflow for use in the Oracle BlueKai system. When Oracle BlueKai sees a pixel that matches with a defined SDT format, Oracle BlueKai automatically uses SDT.

Can the ID-swap pixel be placed in an iFrame?


Is there a default time span for expiration?

All cookies should be expired after 30 days. However, we recommend that buyers match expiration to ad campaign recency wherever possible. For example, if you are buying Travel to reach an audience traveling within the next seven days, you should expire the cookies after that 7-day period.

Which element that we receive in the JSON POST or GET actually defines the data (CampaignId, CategoryId)?

Data is represented by CategoryId. A user can possess multiple CategoryIds, and there may be multiple CampaignIds in the JSON POST or GET. A data campaign in our system is an entity that is set up to target an audience. An audience consists of data categories. Therefore, a user might qualify for one or more campaigns, and each campaign can contain one or more category IDs.

Do you re-send all of the segments for a user with every POST or GET?

No, we send a partial update. Only segments for which data has not been transferred within the last 30 days are sent for a particular user.

Can you send the data to multiple data transfer URLs?

Oracle BlueKai sends the data to only one endpoint. You typically parse the data, as needed, based on the Campaign ID and/or the Pixel URLs that are returned in the JSON POST or GET. We are able to append specific parameters to the Pixel URL on a campaign-by-campaign basis.

What happens when a user indicates they do not want to be tracked by Oracle BlueKai? How is that information communicated to us? Do we need to delete the data from our database for that user?

When a user opts out, Oracle BlueKai deletes all category-level information about that user in its profile store and persists the opt out with an 'ignore flag' stored server-side. Oracle BlueKai may also store the users' opt out status as a cookie in users' browser cache. After an opt out has propagated through the system, Oracle BlueKai will no longer transmit any information, including opt out status, about that user.