Controlling queries to contact history

Using contact history improves optimality but can hinder performance.

About this task

When optimizing contacts, Contact Optimization has several rules to manage contact fatigue such as Max # Duplicate Offers, Max # Packages, and Min/Max # Offers. All of these rules include the over the time period or within the time period section.

If you always set the time period to 0 in all the rules, it indicates that this Contact Optimization session does not use time periods for any of the rules. In such a case, you can control how Contact Optimization queries the contact history tables during the Contact Optimization session run using the UseFutureContacts configuration property.

If you set UseFutureContacts to false, Contact Optimization optimizes joins with the contact history tables if your rules include time periods. If your rules do not include any time periods, Contact Optimization does not query the contact history tables at all, which can improve performance.

If you set UseFutureContacts to true, Contact Optimization always queries the contact history tables. While this impacts performance, it also ensures that placeholders for contacts that are sent in the future are considered when managing contact fatigue.