Hi @kchaitanya thanks for the reply. the idea for audiences is what we use currently (but means we have to maintain a lot of designs just with a small change). And this only works if the difference in the design is solely based on the mbox parameter. but think of a design where you want to add somet...

we are trying to setup a new design for recommendations. everything works fine appart from language split.   goal: display different attributes based on page language   setup: in the target call we added a new parameter "language" that can be used in the design   problem: everything works fine and t...

additional information: If you use Adobe Launch for the configuration, just add the secure in the extension settings: https://experienceleague.adobe.com/docs/experience-platform/tags/extensions/client/id-service/overview.html?lang=en#variables

If you have different offers/products for different countries, I could think of two options:   1) "Product attributes":  add meta data to the products reflecting all different data you need (eg. having a filed where you add country availability) and then filter the right products using collections 2...

Hi @Gaureshk_Kodag thanks for the additional information. Meanwhile I have some more insights: - UTF-8 is the expected encoding - In our tests, the header row (with indication of "# key,reco1,reco2,..." is not needed. The upload was successful without header row and all keys were working as expected...