Back

IBM Universal Behavior Exchange (UBX) is a data integration platform that seamlessly connects your entire marketing ecosystem, breaking down silos and enabling customer behavior and identity data to flow freely across your technology stack. This gives marketers a holistic, real-time view of their customers, maximizing current investments and supporting new ones to keep up with customer expectations.

This article describes how to configure IBM UBX in your Universal Data Hub profile.

Table of Contents Placeholder

Requirements

  • IBM UBX Account
  • Tealium Events Endpoint Authentication Key

Supported Actions

Action Name Trigger on Audience Trigger on Streams
Publish Cart Abandonment Events
Publish Cart Purchase Events
Publish Event

INFO: Publish Event action can be configured to send data for over 100 different event type mappings. While Publish Cart Abandonment and Purchase Events actions are specialized to submit multiple related events to represent a shopping cart and individual items within. For more information, see: Publishing Multiple Related Events.

Configure Settings

Go to the Connector Marketplace and add a new IBM UBX Events connector. Read the Connector Overview article for general instructions on how to add a connector.

To configure the connector, follow these steps:

  • In the Configure tab, provide a title for the connector instance.

  • Provide your Endpoint Authentication Key.

  • Click Test Connection to verify API connectivity with the provided credentials.

For more information, see: Administering Endpoints.

Admin: Endpoint Registration

When creating a new IBM UBX Tealium endpoint in your UBX account, it needs to be registered with your Tealium Universal Data Hub account.

Steps to register endpoint:

  1. Obtain an Endpoint Authentication Key for the newly created endpoint in your UBX account.
  2. Add a new IBM UBX Events Connector in your Tealium UDH account.
  3. Navigate to the Admin tab.
  4. Enter your authentication key and deployment ID 'default' (US data center) or 'eu-deployment' (EU data center).
  5. Click the Register button.
  6. The registered endpoint's status will change from 'Pending' to 'Active' in your UBX account and become available for publishing.

Endpoint registration needs to be done only once per endpoint.

Action Settings: Parameters and Options

Click Next or go to the Actions tab. It's where you'll set up actions to trigger.

This section describes how to set up parameters and options for each action.

Action: Publish Cart Abandonment Events

Parameters

  1. Channel (Required): Select channel where the event was observed.
  2. Sub Channel (Recommended): Select sub channel to classify further where the event was observed. If selected channel does not have a fitting predefined sub channel to pick from, enter one manually as custom value or leave blank.
  3. Event Identifiers (Required): Map attribute(s) to uniquely identify cart abandonment event.
  4. Cart Data (Required): Map attribute(s) to cart aggregate data attributes.
  5. Cart Items Data (Optional): Map attribute(s) to individual cart items. Only Array type attributes are supported and must contain same number of elements.

For more information about event channel, see: Event Catalog.

Action: Publish Cart Purchase Events

Parameters

  1. Channel (Required): Select channel where the event was observed.
  2. Sub Channel (Recommended): Select sub channel to classify further where the event was observed. If selected channel does not have a fitting predefined sub channel to pick from, enter one manually as custom value or leave blank.
  3. Event Identifiers (Required): Map attribute(s) to uniquely identify cart purchase event.
  4. Cart Data (Required): Map attribute(s) to cart aggregate data attributes.
  5. Cart Items Data (Optional): Map attribute(s) to individual cart items. Only Array type attributes are supported and must contain same number of elements.

Action: Publish Event

Parameters

  1. Event Type (Required): Select type of event to publish.
  2. Channel (Required): Select channel where the event was observed.
  3. Sub Channel (Recommended): Select sub channel to classify further where the event was observed. If selected channel does not have a fitting predefined sub channel to pick from, enter one manually as custom value or leave blank.
  4. Event Identifiers (Required): Map attribute(s) to uniquely identify event.
  5. Event Data (Required): Map attribute(s) to event data attributes.

For a list of available events and attributes, see: Dynamic Event Library.

Vendor Documentation