Disabling writing to contact history

If you do not want production runs to update the contact history tables, you can configure the Call list or Mail list process to prevent logging. However, the best practice is not to disable contact history logging.

About this task

Test runs do not populate the contact history tables, so if you want to run a contact process without writing to contact history, you can do a test run.

Contact history is updated when a flowchart contact process runs in production mode with the contact logging options enabled. If you want to prevent a contact process from writing to contact history, you can configure the process to disable logging during production runs.

Important: The best practice is not to disable contact history logging. If you run a campaign in production mode without logging to contact history, you will not be able to accurately re-generate the contact history at a later date if any of the underlying data changes.

Procedure

Double-click the contact process (Call list or Mail list) for which you want to disable contact history logging.
Click the Log tab.
In the window for configuring logging of contact transactions, clear the Log to contact history tables and the Log into other destinations checkboxes.

Note: To change the Log to contact history tables option, the OverrideLogToHistory configuration setting must be set to true and you must have the appropriate permissions.
Optionally, click More Options to access the Contact history logging options and select Create treatments only. This option generates new treatments in the Treatments table but does not update the contact history.
Click OK.

Results

When you run the contact process, no entries will be written to the contact history tables or to alternate logging destinations.

Note: This does not affect how eMessage and Interact load data into the Campaign history tables. Those products use their own ETL processes to extract, transform, and load data into the Campaign contact and response history tables.