Capturing responses to actions with the CaptureResponse service
CaptureResponse is a REST service that supports the POST HTTP method. This service allows callers to capture responses to actions triggered via Real-Time Containers.
The URL pattern for this service is:
This service can also be used to initiate the first action in its request. To utilize this feature and include action initiation, use the following URL pattern:
To help you configure the service, you can refer to the following Swagger document: Swagger document for Container and Capture Response v3.
POST Service Request
For the POST request, the service expects a JSON Object with the following attributes:
|Optional||Customer identifier. Set here if the same for all responses, or in
|Optional||Singular user-friendly name of the context entity (for example,
Customer, Account). Set here if the
same for all responses, or in |
|✓||Name of the Container to trigger.|
|Optional||List of actions for which you want to capture a response. Results from the Container service can be mapped into this array.|
|✓||Customer identifier for the context entity|
|✓||Singular user-friendly name of the context entity (for example, Customer, Account).|
|✓||Name of the action.|
|✓||Issue to which the action belongs.|
|✓||Group to which the action belongs.|
The identifier of the original decision that resulted in the actions being selected for the customer.
All actions yielded for the customer in the same decision share the same InteractionID. The CaptureResponse API requires the InteractionID from the Container response in order to match the response to the original decision result, so that the adaptive models learn from the interaction. If the response is matched to the correct decision result, the merged response, with all SR properties, is captured in Interaction History. If the InteractionID isn't matched, the response is still captured in Interaction History but no adaptive model learning will take place.
|✓||Action rank based on Strategy configuration.|
|✓||Direction in which the interaction was initiated, Inbound or Outbound.|
|✓||Channel the interaction occurred on.|
|✓||The customer disposition of the action.|
|Optional||Name of the associated customer journey.|
|Optional||Name of the associated customer journey stage.|
|Optional||Name of the associated customer journey step.|
|Optional||Category to which the action belongs.|
|Optional||Cost of this product or service to the customer.|
|Optional||Business friendly description of the action.|
|Optional||Benefits to the customer.|
|Optional||Why this action is relevant for the customer.|
|Optional||Short description of the action.|
|Optional||Name of the paid audience.|
|Optional||Unique identifier for the action.|
|Optional||Description of the pricing.|
|Optional||Criteria for customers to be eligible for this action.|
|Optional||Action propensity value.|
|Optional||Agent compensation amount if customer accepts action.|
|Optional||Internal class for the action results.|
|Optional||Action priority based on Strategy configuration.|
|Optional||Name of the action bundle.|
|Optional||URL to the associated action image.|
|Optional||Indicates if this action is a bundle parent.|
|Optional||Variation of the action (for example, 64gb, 128gb, 256gb).|
|Optional||The name of the action treatment.|
|Optional||The internal company cost of the action.|
|Optional||Work ID of the active Campaign associated with this Container.|
|Optional||The value the customer receives from this action.|
URL to invoke the CaptureWebClickThrough API.
The encrypted parameter in this URL contains the actual click-through URL specified as part of the action’s details. Typically, this leads to a link or file that provides more details about the action.
A sample invocation request is shown below:
For the response, the service returns a JSON object with the following attributes:
|OK for successful result, Error otherwise.|
|Confirmation message when successful, error message in case of an error.|
A sample service response is shown below:
"Message": "Response captured successfully"
Previous topic Making custom Strategy Result properties available for real-time container data flows Next topic Capturing responses to actions in the Agent Assisted channel with the CaptureOrder service