For treatments for the Web and Mobile channels, you can specify the placement type, for example Hero or Tile. You can also specify the number of placements per page, either as part of a real-time container call or as defined in a PagePlacement DDR. The Web and Mobile strategies pick the top treatment based on the requested placement types.

The ProcessWebChannel strategy

The ProcessWebChannel strategy determines if the Channel treatment processing switch is on, and if so calls the WebTreatmentPlacements sub-strategy for web placement processing, otherwise this processing is skipped.

An extension point WebChannelExt sub-strategy is provided for any custom treatment placement processing.

The WebTreatmentPlacements strategy

The WebTreatmentPlacements strategy ranks treatments by priority based on the selected Propensity method in the Arbitration tab of Next-Best-Action Designer. The strategy then matches the placement types provided in the container or in the PagePlacements DDR and the prioritized treatments by rank. For example, if a container requested a Hero, Tile, Tile, Tile, this strategy ensures that the top Hero treatment and a ranked set of Tile treatments are selected.

The ProcessMobileChannel strategy

The ProcessMobileChannel strategy determines if the Channel treatment processing switch is on, and if so calls the MobileTreatmentPlacement sub-strategy for web placement processing, otherwise this processing is skipped.

An extension point MobileChannelExt sub-strategy is provided for any custom treatment placement processing.

The MobileTreatmentPlacement strategy

The MobileTreatmentPlacements strategy ranks treatments by priority based on the selected Propensity method in the Arbitration tab of Next-Best-Action Designer. The strategy then matches the placement types provided in the container or in the PagePlacements DDR and the prioritized treatments by rank. For example, if a container requested a Hero, Tile, Tile, Tile, this strategy ensures that the top Hero treatment and a ranked set of Tile treatments are selected.

The AssistedInboundChannel strategy

The AssistedInboundChannel strategy splits the actions into Call Center and Retail channels to allow for any additional channel specific processing, and then prioritizes by descending Priority, returning All actions.

An extension point strategy AssistedInboundChannelExt is provided after prioritization to allow for any additional assisted inbound processing.

OtherInboundChannel strategy

The OtherInboundChannel strategy simply contains a call to the OtherInboundChannelExt extension point strategy.