Skip customer id validation in Pega CDH Container for custom channel
We want to skip the customer id validation in the PegaMKTContainer/v4/Container, in order to be able to call to container for customers as well as prospects, for a custom channel.
We found the DSS MKTEnableCustomerValidation which updated to true, in order for Pega to skip the customer id validation, but based on the code, SubjectID is optional only for web and mobile channels. See the documentation here:
What would the impact be if we update the container service to include our new custom channel into the list of channels where SubjectID is optional? Any other features would be impacted/we would have to update?
Thank you!
Pegasystems Inc.
GB
@VasilicaN ⚠ This is a GenAI-powered answer. All generated answers require validation against the provided references.
here's what you need to consider:
@VasilicaN ⚠ This is a GenAI-powered answer. All generated answers require validation against the provided references.
here's what you need to consider:
- Impact of Making SubjectID Optional for Custom Channel:
- Security Implications:
- The change would allow anonymous access through your custom channel, similar to how Web and Mobile channels currently work
- This means you could process requests without customer identification, which is useful for prospect interactions
- The system would still maintain proper data segregation and security controls
- Functional Changes:
- The container service would process requests from your custom channel without requiring customer validation
- This aligns with the current behavior of Web and Mobile channels
- The MKTEnableCustomerValidation DSS would still control the overall validation behavior
- Required Updates and Considerations:
- Configuration Changes:
- The channel configuration in CDH would need to be updated to include your custom channel in the list of channels that allow optional SubjectID
- The PreContainerValidations data transform would need to be modified to accommodate this change
- Ensure your custom channel is properly configured in the Channels tab under Next-Best-Action Configurations
- Testing Requirements:
- Test both authenticated (with SubjectID) and anonymous (without SubjectID) scenarios
- Verify that your custom channel correctly handles both cases
- Ensure proper fallback behavior when customer validation fails
- Other Features Impacted:
- Customer Identity Management:
- The change affects how customer identity is handled for your custom channel
- Existing customer profile merging and identity matching features will still work when SubjectID is provided
- Anonymous interactions will be handled similarly to Web/Mobile channels
- Adaptive Models and Learning:
- Response capture and adaptive learning will continue to work
- For anonymous interactions, the system will use alternative identifiers (similar to Web/Mobile channels)
- Historical tracking and analytics will need to account for both identified and anonymous interactions
- Risk Mitigation:
- It's recommended to:
- Initially test the changes in a non-production environment
- Monitor customer validation patterns after implementation
- Document the channel's new behavior for future reference
- Consider implementing additional logging for anonymous interactions if needed
References:
@AmyRohe is this something you could help with?
Pegasystems Inc.
IN
@VasilicaN I see this was answered on the INC ticket that was raised.
Accenture
RO
I am not sure about these 2 steps:
Configuration Changes:
- The channel configuration in CDH would need to be updated to include your custom channel in the list of channels that allow optional SubjectID
- The PreContainerValidations data transform would need to be modified to accommodate this change
For the first point is it the channel configuration that has to be updated or only the data transform? I think the phrasing here might be missleading.
For the second point I think I should update the ExtendedContainerProperties and not the PreContainerValidations.
Can someone confirm? As I see the above is an AI generated response.