Home
Integration guides
Unica Campaign and Acoustic Campaign Integration Guide for IBM Marketing Cloud
Response tracking tables for the integration
To support the Campaign and Acoustic Campaign integration, response tracking tables are required to store data about user responses to email, SMS, and push events.
Multi-thread Implementation of Event Download and Processing
If you are using Unica Campaign version 11.1 or later, multiple threads are used for UBX event download to Unica Campaign and ETL processing. Unica Campaign-UBX integration involve 2 phase of operations.

Integration guides
- Unica Campaign and Acoustic Campaign Integration Guide for IBM Marketing Cloud
  - Overview of the Unica Campaign and Acoustic Campaign integration
    The integration of Unica Campaign and Acoustic Campaign combines the marketing segmentation tools of Unica Campaign with the messaging capabilities of IBM Marketing Cloud.
  - Configuring the Unica Campaign and Acoustic Campaign integration
    To ensure a successful integration of Campaign and Acoustic Campaign, the following products must be configured: Unica Campaign, Acoustic Campaign, IBM UBX, and IBM UBX Toolkit.
  - Email: using Unica Campaign and Acoustic Campaign
    If Unica Campaign and Acoustic Campaign are integrated, you can use Unica Campaign to send personalized email communications from Acoustic Campaign.
  - SMS text messaging: using Campaign and Acoustic Campaign
    If Unica Campaign is integrated with Acoustic Campaign, you can you can use Unica Campaign to send SMS text messages from Acoustic Campaign.
  - Mobile push: using Unica Campaign and Acoustic Campaign
    If Unica Campaign and Acoustic Campaign are integrated, you can use Unica Campaign to send mobile push notifications from Acoustic Campaign.
  - Response tracking tables for the integration
    To support the Campaign and Acoustic Campaign integration, response tracking tables are required to store data about user responses to email, SMS, and push events.
    - Response and Contact Mapping
      When Unica Campaign and IBM Engage are integrated, the contact and response mapping is defined by default.
    - Email tracking data available as an event
      The following table lists the email tracking data that can be downloaded from UBX Toolkit to Unica Campaign.
    - SMS tracking data available as an event
      The following table lists the SMS tracking data that can be downloaded from UBX Toolkit to Unica Campaign.
    - Mobile push tracking data available as an event
      The following table lists the mobile push tracking data that can be downloaded from UBX Toolkit to Unica Campaign.
    - Integration database tables, ETL, and partitioning
      The Campaign integration with Engage populates database tables that Campaign uses for auditing and tracking. Consult with your database administrator to discuss how long you need to keep the data for querying. Depending on the volume of activity for your account, the tables can grow large over time.
    - Event types
      The tracking tables provide data to describe different types of message responses. The type of response is considered an event type.
    - Report IDs
      IBM Engage Report IDs appear in the tracking tables.
    - Reasons for contact suppression
      Engage sometimes does not send a message to an address for various reasons.
    - Purging data from response tracking tables
      You can periodically archive or purge the rows that have been processed by the ETL in order to free up space in the database.
    - Multi-thread Implementation of Event Download and Processing
      If you are using Unica Campaign version 11.1 or later, multiple threads are used for UBX event download to Unica Campaign and ETL processing. Unica Campaign-UBX integration involve 2 phase of operations.
- Unica Plan and Unica Campaign Integration Guide

Multi-thread Implementation of Event Download and Processing

If you are using Unica Campaign version 11.1 or later, multiple threads are used for UBX event download to Unica Campaign and ETL processing. Unica Campaign-UBX integration involve 2 phase of operations.

Pulling events published by Engage to UBX and putting those in contact/response tracking tables.
Process (i.e ETL) contact/response tracking tables and populate the Detailed contact history and Response history as per the event.

Previous to 11.1 release, only 2 main threads were used for these operations. One thread used for reading data from UBX and populate the event tracking tables. Second thread used for reading from event tracking tables and populating Detailed contact history and Response history for different events.

With 11.1, we are having 10 threads to download and populate events from UBX and then 10 parallel threads to process contact tracking event like email send and another 10 threads to process response tracking events like email bounce, email click, email opened. With this parallel processing, integration performance is significantly improved.

Note: As we are spawning multiple threads and to run these threads more CPU and memory will be utilized on Unica Campaign application server.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.