hi @varun790  - there are 2 ways to achieve this: 1. Response tokens: A. Enable the geo.country response-token B. Use your applications's code to read it using Custom events (https://experienceleague.adobe.com/docs/target/using/administer/response-tokens.html?lang=en ) C. Update the cookie with the...

In addition to what @alexbishop suggested, one approach that has worked for us is to "add" a module on the page to deliver the personalised message instead of changing the existing content. The approach works for personalisation use-cases as the main objective is to deliver the message. For any expe...

thanks @Amelia_Waliany for this recognition - much appreciated! This community is a perfect example of how collaboration without boundaries can help peers and bring people together to solve common challenges. I would like to pass my sincere thanks to all members who use this platform to ask question...

hi @RicardoDe  - do you mean using same session-id all the time (even if the visitor is returning back after 30 minutes)?   Using same thirdPartyId with multiple session-ids works so I am hoping using single session-id should not have any issues as long as your entire reporting is visitor-based (and...

great @michaela7702973  - your new setup is perfect and fits to the solution I provided. Glad to know it worked for you, well done!   Regards Rajneesh

hi @michaela7702973  - since you are using same URL parameter but two different values for your audiences, I'll suggest configuring two profile-scripts instead of one, for each param-value combination. That will give you much better control on personalised experience delivery.    Let me know if you ...

hi @DivyaAshankar  - could I please ask you to try returning the products from profile scripts using simple string? Looking at your profile-script, you are anyways passing only one product - I tested it locally and it works perfectly.  Once its resolved, we can discuss the array situation.    Thanks...

@mmoos - I just took an activity live with front and back promotions and its working as expected. I would suggest raising a client-care ticket.    Regards Rajneesh

thanks @RicardoDe - this is an interesting finding. Creating parallels with how client-side implementation works, I believed having session-id is mandatory for Delivery-APIs, will try omitting it to understand the behaviour in more detail.   For the second part where you see expected behaviour while...