Campaign uses its own ETL process to extract, transform, and load offer response data from the eMessage tracking tables into the Campaign contact and response history tables. The ETL process coordinates information across the necessary tables.

See Campaign | partitions | partition[n] | eMessage | contactAndResponseHistTracking.

ETL logging is enabled by default. The default file location is Campaign_home/logs/ETL.log. To adjust logging behavior, modify the campaign_log4j.properties file, whose default location is Campaign_home/conf.

See The Campaign and eMessage ETL log file.

3. Upgrades only: Adjust Campaign response tracking and mapping tables.

Upgrade customers who want to use eMessage offer integration must add the Link Click, Landing Page, and SMS Reply Message response types to the UA_UsrResponseType table, then update the UA_RespTypeMapping table to map the response types to eMessage.*

The UA_RespTypeMapping table is required to coordinate transfer of data across the necessary Campaign and eMessage tables.

See Adjusting Campaign response tables for eMessage offer integration.

4. Optionally, adjust Campaign performance reports.

Changes affect both the object-specific reports on the campaign or offer Analysis tab and the reports on the Analytics menu.

See the IBM® EMM Reports Installation and Configuration Guide.

*Only the Link Click response type is currently used for eMessage offer integration. The Landing Page and SMS Reply Message columns are not populated by the ETL process at this time.