We have a situation in which retrieving content for page while using a long list of targeting attributes exceeds the length allowed for a URL. For example:
In this case, the number of targetGroups a user is member of can be extensive, leading to a failing request due to URL overflow.
A future-proof solution to this problem would be to support a request body through POST.
An alternative solution could be allowing userAttributes of the same key to be provided in a single list using a separator:
?userAttributes.targetGroup=women,beauty,skincare