Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring settings for adaptive models

Updated on July 5, 2022

Configure the update frequency and specify other settings that control how an adaptive model operates.

  1. In the navigation pane of Prediction Studio, click Models.
  2. Open the adaptive model that you want to edit, and then click the Settings tab.
  3. In the Model update frequency section, in the Update model after every field, enter the number of responses that trigger the update.
    When you update a model, ADM retrains the model with the specified number of responses. After the update, the model becomes available to the client nodes for scoring and the Pega Platform components that use the model.
    Note: You should choose model update frequency so that for the average model instance, it would be updated every 2 to 4 hours. For example, if a model instance (such as a web banner for an offer) has 166 impressions per minute, then 20,000 (2*60*166=20,000) may be a good number for the adaptive model rule in that channel. The default setting is 5000. If the model update frequency is set too low, then the demand on the ADM nodes will be high. In addition to this, a model update will also be done at least every 12 hours, to make sure all recorded responses are regularly processed.
  4. In the Recording historical data section, specify if you want to extract historical customer responses from adaptive models in your application.
  5. Modify advanced settings of a model by following the steps in one of the respective topics:
  6. In the Audit history section, to capture adaptive model details in the work object's history, select the Attach audit notes to work object check box.
    Caution: Enabling this setting causes significant performance overhead.
  7. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us