Interact | offerserving

The offerTieBreakMethod property defines the behavior of offer serving when two offers have equivalent (tied) scores. If you set this property to its default value of Random, presents a random choice from among the offers that have equivalent scores. If you set this configuration to Newer Offer, serves up the newer offer (based on having a higher offer ID) ahead of the older offer (lower offer ID) in the case where the scores among the offers are the same.

has an optional feature that allows the administrator to configure the system to return the offers in random order independent of the score, by setting the percentRandomSelection option (Campaign | partitions | [partition_number] | Interact | learning | percentRandomSelection). The offerTieBreakMethod property described here is used only when percentRandomSelection is set to zero (disabled).

Random | Newer Offer

The optimizationType property defines whether uses a learning engine to assist with offer assignments. If set to NoLearning, does not use learning. If set to BuiltInLearning, uses the Bayesian learning engine built with . If set to ExternalLearning, uses a learning engine you provide. If you select ExternalLearning, you must define the externalLearningClass and externalLearningClassPath properties.

NoLearning | BuiltInLearning | ExternalLearning

The maximum number of milliseconds that the runtime server waits for an interactive flowchart to complete before getting offers.

The prefix prepended to treatment codes.

No default value defined.

Determines whether should use an offer's effective date in filtering out offers that are presented to a visitor. Values include:

0 tells to use the effective date to filter the offer, so that if the offer effective date is earlier than or equal to the current date, the offer effective date, the offer is served to visitors.

If there is an effectiveDateGracePeriod value set, the grace period is also applied to determine whether to serve the offer.

Any positive integer tells to use the current date plus the value of this property to determine whether to serve the offer to visitors, so that if the offer effective date is earlier than the current date plus the value of this property, the offer is served to visitors.

If there is an effectiveDateGracePeriod value set, the grace period is also applied to determine whether to serve the offer.

Specifies the name of the custom attribute in an offer definition that indicates the effective date grace period. For example, you might configure this property with a value of AltGracePeriod. You would then define offers with a custom attribute called AltGracePeriod that is used to specify the number of days to use as a grace period with the effectiveDateBehavior property.

Suppose you create a new offer template with an effective date of 10 days from the current date, and include a custom attribute called AltGracePeriod. When you create an offer using the template, if you set the value of AltGracePeriod to 14 days, the offer would be served to visitors, because the current date is within the grace period of the offer effective date.

Indicates whether should write information about visitor attributes used by the learning module to the log files. Note that settings this value to true may affect learning performance and log file sizes.