Skip to main content

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

Creating an interaction history summary data set

Updated on July 5, 2022

Simplify decision strategies by creating data set records for interaction history summaries. These data sets aggregate interaction history to limit and refine the data that strategies process.

Use interaction history summaries to filter customer data and integrate multiple arbitration and aggregation components into a single import component. For example, you can create a data set that groups all offers that a customer accepted within the last 30 days and use that data set in your strategy to avoid creating duplicate offers.

Note: If your system includes Pega Customer Decision Hub, you can define interaction history summaries and associate them with customer records in Customer Profile Designer, without the need to access Dev Studio.
  1. In the header of Dev Studio, click ConfigureDecisioningDecisionsData SourcesInteraction History Summaries.
  2. Click Create.
  3. In the Data Set Record Configuration section, define the data set:
    1. In the Label field, enter the data set label.
      The identifier is automatically created based on the data set label.
    2. Optional: To change the automatically created identifier, click Edit, enter an identifier name, and then click OK.
    3. In the Type list, select Summaries.
  4. In the Context section, specify the ruleset, applicable Strategy Result class, and ruleset version of the data set.
  5. Click Create and open.
  6. In the Data source list, select one of the following types:
    • Data set
    • Data flow
  7. Choose the data source from the list, depending on the data type that you selected in the previous step.
    Result: The system displays the Group by section. The appearance of the section varies depending on the Data source selection.

    Note: If the source is not configured (the Aggregation record is not created), then the system displays the Configure source button. Click the button to configure the data source by choosing the Access group and Event timestamp. Keys will also be displayed, based on the source definition.

    You do not need to configure the data source for Customer Profile Designer, as the system generates the Aggregation record in the background.

  8. In the Group by section, select the properties by which you want to group the data.
  9. In the Aggregates section, add aggregates, and then specify when conditions for the aggregates, if applicable:
    1. Click Add aggregate.
    2. In the Name field, enter the existing property (for the aggregate output).
    3. In the Function field, specify the aggregate function.
    4. In the Time window list, specify the time span for which you want to aggregate data:
      • Select All time option, to aggregate data from the entire interaction history.
      • Select Last, and then specify the time window, to aggregate data from a specific time period.
      Note: Starting from Pega Platform version 8.6, you can have more then one time window for the summary data set as a result of the separate time periods of the aggregate. As a best practice, logically sort those aggregates into smaller number of data sets if possible.
    5. Optional: To add when conditions for the aggregates, in the Condition section, click an empty field, and then specify the when condition.
    For example: To ensure that the customer does not receive duplicate offers, define the aggregate and when conditions, and then use the data set in the strategy of your application to prevent offers for which the value of the CountPositives property is greater than 0 for a specific customer. Use the following settings:
    • Name: .CountPositives
    • Function: Count
    • Conditions: pyOutcome = Accepted
  10. Optional: To specify the aggregation start time, in the Start aggregating as of section:
    • Click The first record in the source radio button to start aggregating from the first record.
    • Click A defined date radio button to start aggregating from a date that you specify.
  11. Optional: To further limit the data that the data set aggregates, in the Conditions section, define the filter conditions.
  12. Click Save.
  13. Optional: To save processing time, turn on preaggregation for the new data set:
    1. In the header of Dev Studio, click ConfigureDecisioningDecisionsData SourcesInteraction History Summaries.
    2. Next to the data set for which you want to turn on preaggregation, click ManageMaterialized.
      Preaggregated data sets save processing time because they include the latest interactions. Data sets that are not preaggregated do not include the latest interactions and therefore they query the database.
  • Applying sample scripts for archiving and purging

    The interaction history tables contain transactional data which may grow fast. By using the sample scripts, the users can archive the data in the archiving database and delete (purge) the records from the source database. The scripts allow you to move the FACT table records, merge the Dimension records, and delete the records from the FACT table. Before you use any of the scripts, back up the source and target interaction history tables and create indexes on the columns. Indexes improve performance when you read data from the archived tables.

  • Interaction History methods

    You can use a rule-based API to associate known customer IDs with IDs that are generated by external interactions through different channels and devices or to separate them.

  • Accessing interaction results

    Ensure that you stay up to date with recent interaction results by filtering and analyzing the interaction history records.

  • Extending Interaction History

    Learn about the underlying configuration of Interaction History and how to extend it to match your business objectives.

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