Send data to Oracle DMP (BlueKai)

Oracle Data Management Platform (DMP), formerly known as BlueKai, is a cloud-based big data platform that enables marketing organizations to personalize online, offline, and mobile marketing campaigns with richer and more useful information about targeted audiences.

This topic describes the steps that are required to send delimited files (CSV, PSV, and TSV) to Oracle DMP from Amperity:

  1. Get details

  2. Add destination

  3. Add data template

Get details

Oracle DMP requires the following configuration details:

Detail one.

The username.
Detail one.

The host public key.
Detail one.

For passphrase credentials, the passphrase; for private key credentials, the private key.
Detail one.

The remote folder to which Amperity will send data.

Important

A “/” (forward slash) must be used as the first character for this value. For example: “/folder/name”.
Detail one.

The public key to use for PGP encryption.

Add destination

Configure Amperity to send delimited files (CSV, PSV, and TSV) directly to Oracle DMP.

To add a destination

Step 1.

Open the Destinations tab to configure a destination for Oracle DMP. Click the Add Destination button to open the Destination dialog box.

Name, description, choose plugin.

Enter a name for the destination and provide a description. For example: “Oracle DMP” and “This sends delimited files (CSV, PSV, and TSV) to Oracle DMP”.

From the Plugin drop-down, start typing “sftp” to filter the list, and then select Oracle DMP.
Step 2.

Credentials allow Amperity to connect to Oracle DMP.

The credential type is set automatically to passphrase or private-key. You may use an existing credential or you may add a new one.

Choose an existing credential or add credential.

Select an existing credential from the Credential drop-down.

– or –

Select Create a new credential from the Credential drop-down. This opens the Credential dialog box.

Enter the name for the credential, and then add a description. Select sftp.bluekai.com from the HOSTNAME drop-down list. Enter the username and passphrase.

Update the settings for the SFTP destination.

When finished, click Save.
Step 3.

Each destination has settings that define how Amperity will deliver data to Oracle DMP. These settings are listed under the Settings section of the Destination dialog box.

Settings for SFTP destinations.

Complete the following SFTP Settings:

  • The path to the Remote folder.

    Tip

    If the path to the remote folder contains a space, use a backslash () character to escape that space. For example, a folder named “From ACME” should be entered as “From\ ACME”.

  • The File format. Select the file format – CSV, TSV, or PSV – from the drop-down list.

  • Optional. The Escape character that is required by Oracle DMP.

    Note

    If an escape character is not specified and quote mode is set to “None” this may result in unescaped, unquoted files. When an escape character is not specified, you should select a non-“None” option from the Quote Mode setting.

  • Optional. The Compression format. Encoding method options include “Tar”, “Tgz”, “Zip”, “GZip”, and “None”.

  • Optional. The PGP public key that is used to encrypt files that are sent to Oracle DMP.

  • Optional. The Quote mode that should be used within the file. From the drop-down, select one of “all fields”, “all non-NULL fields”, “fields with special characters only”, “all non-numeric fields” or “None”.

    Note

    If the quote mode is set to “None” and the Escape Character setting is empty this may result in unescaped, unquoted files. When quote mode is not set to “None”, you should specify an escape character.

  • Optional. Select Include success file upon completion to add a .DONE file that indicates when an orchestration has finished sending data.

    Tip

    If a downstream sensor is listening for files sent from Amperity, configure that sensor to listen for the presence of the .DONE file.

  • Optional. Select Include header row in output files if headers should be included in the output.

  • Optional. Select Row number to include a row number column in the output file. Applies to CSV, TSV, PSV, and custom delimiter file types.

    When enabled, you may specify the name of the row number column in the output file.

  • Optional. Select Exclude Parquet extension from the directory name for managing how Apache Parquet files are added to directories.
Step 4.

Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them.

Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII.

What is restricted access to PII?

Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.

You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options:

Allow business users access to this destination.

Note

To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to Oracle DMP.

The other two settings may be configured within the data template instead of the destination.
Step 5.

Review all settings, and then click Save.

Save the destination.

Important

You must configure a data template for this destination before you can send data to Oracle DMP.

Add data template

A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.

About paid media campaigns

Amperity provides the right set of data to support your brand’s paid media advertising with Oracle DMP.

  1. Merged Customers vs. Unified Paid Media

    The Merged Customers table contains each of your customers’ best profiles.

    The Unified Paid Media table contains all your customer’s known profile data.

    Your brand will require additional data templates to use the Unified Paid Media table alongside the Merged Customers table to support paid media campaigns.

  2. Enable dedicated data templates for each table.

    Use a consistent naming pattern to label data templates that use data from the Merged Customers table. For example: “Best profile”.

    Use a consistent naming pattern to label data templates that use data from the Unified Paid Media table. For example: “Full profile”.

  3. After data templates are configured for both tables, use the default attributes component on the Campaigns page to configure which attributes will be associated with the destination, including the table from which those attributes will be pulled.

    The selected table will affect your brand’s downstream match rates and overall customer matches within your paid media campaigns. The decision behind which table to use depends on your brand’s downstream use case and the type and amount of customer profile data your brand wants to use to match customers.

    You brand should expect to see higher match rates when sending audiences from the Merged Customers table, but a higher number of matched customer profiles when sending audiences from the Unified Paid Media table. Use A/B testing to compare the results from each table, after which your brand can use the audience that works best for your campaigns.

To add a data template

Step 1.

From the Destinations tab, open the menu for a destination that is configured for Oracle DMP, and then select Add data template.

This opens the Add Data Template dialog box.

Step 1

Enter the name of the data template and a description. For example: “Oracle DMP” and “Send delimited files (CSV, PSV, and TSV) to Oracle DMP.”.
Step 2.

Verify business user access to queries and orchestrations and access to segments and campaigns.

A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data.

Step 2.

If business user access was not configured as part of the destination, you may configure access from the data template.

Important

To allow business users to use this destination with campaigns, you must enable the Available to campaigns option. This allows users to send campaign results from Amperity to Oracle DMP.

If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign.
Step 3.

Verify all configuration settings.

Verify settings for the data template.

Note

When the settings required by the SFTP site were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns.
Step 4.

Review all settings, and then click Save.

Save the data template.

After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaign results to Oracle DMP.

Workflow actions

A workflow will occasionally show an error that describes what prevented a workflow from completing successfully. These first appear as alerts in the notifications pane. The alert describes the error, and then links to the Workflows tab.

Open the Workflows page to review a list of workflow actions, choose an action to resolve the workflow error, and then follow the steps that are shown.

Step one.

You may receive a notifications error for a configured Oracle DMP destination. This appears as an alert in the notifications pane on the Destinations tab.

Review a notifications error.

If you receive a notification error, review the details, and then click the View Workflow link to open this notification error in the Workflows page.
Step two.

On the Workflows page, review the individual steps to determine which step(s) have errors that require your attention, and then click Show Resolutions to review the list of workflow actions that were generated for this error.

The workflow tab, showing a workflow with errors.
Step three.

A list of individual workflow actions are shown. Review the list to identify which action you should take.

Choose a workflow action from the list of actions.

Some workflow actions are common across workflows and will often be available, such as retrying a specific task within a workflow or restarting a workflow. These types of actions can often resolve an error.

In certain cases, actions are specific and are shown when certain conditions exist in your tenant. These types of actions typically must be resolved and may require steps that must be done upstream or downstream from your Amperity workflow.

Amperity provides a series of workflow actions that can help resolve specific issues that may arise with Oracle DMP, including:
Step four.

Select a workflow action from the list of actions, and then review the steps for resolving that error.

Choose a workflow action from the list of actions.

After you have completed the steps in the workflow action, click Continue to rerun the workflow.

Invalid credentials

The credentials that are defined in Amperity are invalid.

To resolve this error, verify that the credentials required by this workflow are valid.

  1. Open the Credentials page.

  2. Review the details for the credentials used with this workflow. Update the credentials for Oracle DMP if required.

  3. Return to the workflow action, and then click Resolve to retry this workflow.

SFTP site unavailable

The SFTP site at sftp.bluekai.com is unavailable. This may be due to any of the following issues:

  • A configuration error within Amperity.

  • The SFTP server is unavailable or unresponsive.

  • The SFTP server does not have enough storage space.

  • Too many connection attempts were made to the SFTP server.

Note

Amperity will make multiple attempts to connect to an SFTP server before showing this workflow error.

To resolve this error, do any of the following.

  1. Verify the configuration for sftp.bluekai.com.

  2. Verify that the SFTP server is available and responsive.

  3. Verify the amount of storage space that is available on the SFTP server.

  4. Decrease the number of couriers in Amperity that are configured to connect to sftp.bluekai.com.

  5. Return to the workflow action, and then click Resolve to retry this workflow.