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.
Setting the value to Yes ensures that information about eMessage offer contact and response history is coordinated between Campaign and eMessage. For example, email response data will be included in Campaign reports.
You must also set Campaign | partitions | partition[n] | server | internal | eMessageInstalled to Yes for this partition or the ETL process will not run.
If the value is Yes: You must specify a startTime; the ETL job then runs until all of the records are processed; and the sleepIntervalInMinutes is ignored.
If the value is No: The ETL job starts as soon as the Campaign web server starts. The ETL job stops after all of the records are processed, then waits for the time specified by sleepIntervalInMinutes.