Realtime Containers are not capturing the “impression” outcomes in the Interaction history, CaptureImpressionsInBatch activity is not being used in the HandleRealtimeContainerExecution_V2 or any other container calls.
It used to be a default process for any Real-time Containers.
Is this something that needs to be implemented explicitly in the latest versions?
@Balarama Krishnayya
The container configuration has a setting to have impressions automatically captured at decision time or to have the channel capture the impression. The default was changed to have the channel capture the impression as that is the documented best practice. This is a best practice as its bad to assume that just because a decision was made, that a customer would view that action. The channel is much better placed to understand when a customer was actually served up an action and that the customer was actually shown it (impression). This obviously also helps the system better learn about what is really happening with customer engagement, rather than creating false perceptions of impression that potentially never happened.
@Saleem_A Could you please let me know, what does it mean by channel capture? is there a mechanism to capture impressions via treatments?
Could you please elaborate?
Thanks
BRK
@Balarama Krishnayya The channel application should call the CaptureResponse API with the Impression outcome.
@Saleem_A Capture Response API is grouping all the RankedResults() based on the pySubjectID, pySubjectType, pxinteractionID, and it is inserting only one result into the interaction history.
When a Realtime Container results in multiple actions for a single pySubjectID, and the capture response is capturing only the first action.
May I know the reason for this approach?
@Balarama Krishnayya , you should call capture response for every result you intend to capture an outcome for. Just because you returned 4 results in a make decision, does not mean the customer viewed or clicked on all 4 returned results. Please see the capture response service documentation for more information: Pegasystems Documentation
