I've uploaded a file under People > Customer Attributes, which maps customer ID to a variable (called restrictedItemsCatalogId) containing a numeric value. I am trying to use this inside of recommendation criteria in order to filter out items from being shown to a given customer. How I'm envisioning this working is:
If restrictedItemsCatalogId on the product does not match restrictedItemsCatalogId on the user profile, include this item in the recommendation.
When I do a Target trace I can see the restrictedItemsCatalogId and value in the user profile data, however, when I try to include this variable (as it's shown in the trace) in inclusion rules inside the recommendation criteria it does not let me save the criteria. I am attempting to do this with Profile Attribute Matching.
So this question has two parts:
Is this something Customer Attributes can be used for?
If so, how can I access this data inside of the recommendation criteria?
I've looked through all the documentation I can find on Customer Attributes, but there doesn't seem to be much on what to do with it in Target once you've gotten the file uploaded.
@amberb67455123the Profile Attribute Mapping dropdowns in recs only show profile.attributes and user.attributes , hence we cannot use customer attributes(crs.attributes) directly for inclusion rules in criteria.
One workaround would be to capture customer attribute data in user.attributes using profile script and then use it within criteria.