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, including UA_UsrResponseType (Campaign response types) and UA_RespTypeMapping (mapping of response types between Campaign and eMessage).

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.

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.

The ETL process uses this parameter to fetch records that have been downloaded by the RCT into the local eMessage system tables. Because large values can impact performance, the list of available values is restricted to the valid values shown below. If you anticipate large volumes of records, adjust the batchSize together with the sleepIntervalInMinutes to process records at regular intervals.

If runOnceADay is Yes, you cannot set a sleep interval.

Any valid path that the Campaign server can access with Read and Execute permissions. For example: D:\myscripts\scriptname.exe