Skip to main content


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

Reviewing Interaction History Aggregate / Summary data requirements

Updated on April 12, 2021

Before using the aggregated Interaction History in your strategy, you should analyse and review Interaction History Aggregate Summary data requirements.

Task IDTask-040701
Primary roleSenior Decisioning Architect
Secondary roleN/A
Tertiary roleN/A

 

It is important to note that NBA Designer ships with pre-configured summaries. This means that this step involves reviewing the contact policy timeframes that are shipped and see if more are required, as well as any other requirements. This information can be extracted from the business requirements. If no additional or different summaries are required, the next step can be skipped.

Currently the following properties are available for grouping:

  • Group by - For each Subject ID, Subject Type, and for each:
  • Action
    • BundleHead
    • BundleName
    • Group
    • Business issue
    • Label
    • Name
  • Channel
    • channel group
    • channel sub group
    • DeviceType
    • URI
    • UserAgent
    • Channel
    • Direction
    • pyTreatment
  • Outcome
    • pyBehaviour
    • Outcome
    • pyResponse
  • Additional dimensions
  • Application
      • Application
      • Application version
      • Component
      • Interaction
      • Strategy
  • Context
      • Control Group Validity End
      • Control Group Validity Start
      • Mkt Type
      • Mkt Value
      • Work ID
      • pyCategory
      • pyReason
  • Customer
      • Model control group
      • pyCustomerSegment
      • pyCustomerSubSegment
  • Fact
      • Cost
      • External Audience Id
      • IPAddress
      • referrer url
      • Revenue
      • utm_medium
      • Decision time
      • Fact ID
      • Interaction ID
      • Outcome time
      • Priority
      • Rank
      • External ID
      • pyFulfilled
      • Group ID
      • pyISFactID
      • Latitude
      • Longitude
      • pyMaxBudget
      • Propensity
      • pyRevenue
      • pyTargetBudget
      • pyWeight
  • Journey
      • Journey
      • Stage
      • Step
  • Operator
      • Division
      • Operator
      • Organization
      • Unit

Outcome

Once the review is completed, you will have the optional set of required changes to the IH Aggregates.

 

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us