Adobe Target

You can use your first- and third-party Oracle Data Cloud platform cookie data in Adobe Target to experiment, create personalized experiences, and deliver content

Delivering audience data to Adobe Target

To deliver data to Adobe Target, use the create audiences and Delivering Audiences workflows. After those steps, you generate a JSON return tag in the Oracle Data Cloud platform, deploy it on your sites, then complete configuration in the Adobe Target

Generate a JSON return tag and connect it to your global mbox

To pass your data to Adobe Target, you need to create a container, generate a JSON return tag, and deploy the tag to the same page where your Adobe Target global mbox is implemented. The global mbox is coded at the top of the page and is used pull in offer code from Adobe Target to change content elsewhere on the page.

You then add code to your site to parse the campaign and category IDs returned by the JSON return tag into the profile attributes of your mbox so that they are available as visitor profile attributes when you create your audiences in Adobe Target. This allows you to associate different customer experiences in the mbox based on your campaign- or category-level data. (Campaigns and campaign IDs are created automatically by the Oracle Data Cloud platform. You do not create them explicitly in the platform UI.)

Note: This document mentions campaigns. Although users do not explicitly create campaigns in the UI, the Oracle Data Cloud platform creates them automatically to manage audience data delivery. Each campaign has a unique ID. The campaign name corresponds to the audience name.

To generate a JSON return tag and connect it to your global mbox:

  1. In the Oracle Data Cloud platform, select Manage Containers.
  2. Click Create New.
  3. Use the following settings for your container:
    • Name: Enter a descriptive name such as Adobe Target JSON return (or another name that makes it easy to identify your container’s purpose).
    • Country Blocking: Accept the default of the Netherlands.
    • Data Transfer Enabled: Leave this check box selected.
    • Default Auction Limit: Keep the default value of 4 for the number of slots to be allocated on your site for firing third-party pixels.
    • Campaign Access: Keep the default of Only Me.
    • Data Transfer Boost: Clear this check box.
      Image showing the Create New Container dialog with populated fields
  4. Click Save and Generate Code. The Generate Code dialog is displayed.
  5. In the Generate Code dialog, click the JS tab for the JSON return tag type.
    Image showing the Generate Code dialog with populated fields
    Each time a user in your audience visits a web page hosting this JSON return tag, a JavaScript object named bk_results is returned to the page that includes the campaign ID and the categories for which the user qualified. You will pass this data into your global mbox to identify the campaigns and categories users are in. The tag has the following syntax:
    <script type="text/javascript" src="https://stags.bluekai.com/site/siteID?ret=js&limit=pixelLimit"</script>
    Where:
    • http or https: Specifies whether you are making calls to the platform via HTTP or HTTPS. If you are optimizing a secure web page, select HTTPS from the Protocol list.
    • siteID: The unique identifier used to manage your site in the Oracle Data Cloud platform. When the platform receives a request from your container tag, it knows that the incoming data belongs to your site.
    • pixelLimit: Specifies the maximum number of pixels that can be fired during a single page view. You can omit this parameter when adding the JSON return tag code to your page.
  6. Click Copy and then paste the JSON tag before the mbox.js file reference in the <head> element of each web page you plan to optimize as demonstrated in the following example.
  7. To synchronously connect your JSON return tag and global mbox, add the following code to the parametersFunction() method in your mbox.js file:

    This code parses the campaign and category IDs in the bk_results object returned to your page and passes it into the mbox's parametersFunction(). This makes the campaign and category IDs (bkcampaignIDs and bkCategoryIDs) available as visitor profile attributes when you create your target audiences in Adobe Target.

    Alternatively, you can use the asynchronous global mbox code or the asynchronous profile pixel code and an asynchronous Oracle Data Cloud core tag.

    If you use Adobe Target Classic, you can add code to your JSON return tag to link your Oracle Data Cloud platform data with a single mbox.

Asynchronous global mbox

Instead of synchronously firing the JSON return tag and global mbox code, you can add asynchronous global mbox code to the end of your mbox.js or at.js file. Using this code enables you to fire the JSON return tag asynchronously (if it has not already been loaded) and pass the results into the global mbox, without having to modify any code on your web pages.

To use this code:

  1. Modify line 5 of the following sample by replacing siteID with the site ID from your container's JSON return tag.
  2. Append the modified code to the very end of your mbox.js or at.js file.
  3. If you are doing data collection with the Oracle Data Cloud core tag on the same page you are executing site optimizations, use the asynchronous version of the Oracle Data Cloud core tag.

Asynchronous profile pixel

Instead of synchronously firing the JSON return tag and global mbox code, add asynchronous profile pixel code to the end of your mbox.js or at.js file. Using this code enables you to fire the JSON return tag asynchronously (if it has not already been loaded) and pass the results into your Adobe Target profile pixel, without having to modify any code on your web pages.

To use this code:

  1. Modify line 5 of the following sample by replacing siteID with the site ID from your container's JSON return tag.
  2. Modify line 6 by replacing company with your company's name that you use in Adobe Target (this is included in the clientCode parameter in your mbox.js or at.js file).
  3. Append the modified code to the very end of your mbox.js or at.js file.
  4. If you are doing data collection with the Oracle Data Cloud core tag on the same page you are executing site optimizations, use the asynchronous version of the Oracle Data Cloud core tag.

JSON return tag for Adobe Target Classic

If you use Adobe Target Classic, you can add code to your JSON return tag to link your Oracle Data Cloud platform data with a single mbox.

To use this code:

  1. Add the following code directly below the JSON return tag in the <head> element to generate a comma-separated list of the campaign IDs and category IDs in the bk_results object that is returned directly to your page when the JSON return tag is fired:
  2. In the <body> element, insert an mbox div (<div class="mboxDefault">) for each area of the page to be optimized and insert the mboxCreate() function directly below the closing mbox </div> tag.
  3. Pass the insertProfileBKCampaignIds and insertProfileBKCategoryIds variables as parameters in the mboxCreate() function as shown in the following code sample:

Verifying campaign and category IDs in the mbox

To verify that your campaign and category IDs are passed to your mbox:

  1. Use a browser inspector to look for a URL-encoded, comma-separated list of campaign IDs and category ID, such as:

    bkCampaignIDs=%2C130750%2C112721%2C&profile.bkCategoryIDs=%2C686531%2C679495%2C

  2. If you do not see the campaign and category IDs, make sure that the audience delivery has a status of Active.
  3. If the delivery is active but you do not see the campaign and category IDs, make sure you properly deployed the JSON return tag followed by the mbox.js reference in the <head> tag of your web page and properly added code to your mbox.js file to parse and process the data returned by the JSON return tag.

Create an audience in Adobe Target

You can specify the targeting conditions for your mbox in the Adobe Target platform by creating an audience, creating a new profile-based rule, and selecting an Oracle Data Cloud platform campaign ID or category ID.

To create an audience in Adobe Target:

  1. Log into your Adobe Target account.
  2. Click Audiences.
  3. Click Create Audience.
    Image of the Adobe Target UI showing the audience list
  4. In the Audience Name box, enter a descriptive name that makes it easy to identify your Oracle Data Cloud platform audience. For example, include the campaign or category name and ID.
  5. Click Add Rule, and then select Visitor Profile.
    Image of the Adobe Target UI showing the create audience dialog
  6. From the Visitor Profile list, select the bkcampaignIDs attribute if you are targeting at the campaign level or bkcategoryIDs if you are targeting at the category level. The attribute name in the drop-down list matches the profile.name you specified in the mbox's parametersFunction() method.
  7. Select the equals operator and then enter the campaign or category ID you are targeting.
  8. Click Save. You can now create activities that use your Oracle-powered audience.