I've actually just posted an article about it, so it will be easier to reference an alternative approach to the QA links - you can find it here: https://experienceleaguecommunities.adobe.com/t5/adobe-target-blogs/struggling-with-qa-links-here-s-your-work-around/ba-p/713477

Sometimes those helpful QA links just don’t work as expected. Instead of constantly resetting and copying them only to find they still aren’t working, save yourself the frustration. Follow this guide for an alternative approach to QA your activity without the hassle.

@ManasaKo1 Here's my understanding of what you've done so far/the expected journey: The activity you've created involves displaying different promotions based on the visitor's location: If a visitor is from Hyderabad (HYD), a 40% discount banner is shown on the homepage hero section.If a visitor is ...

@ManasaKo1  Can you elaborate on what your question is?

Hi @MauG CategoryAffinity is saved to the Target profile which is based on the cookie. So as long as the cookie isn't changing it will remember it across sessions. However, the Visitor Profile where the is saved is by default set to expire after 14 days - so if the visitor don't return to the site w...

Good stuff. Glad to hear you got it working!Appreciate if you can mark the thread Resolved by choosing a correct reply. This helps others with similar problems to quickly find the answer.

To elaborate what @Gokul_Agiwal mentioned regarding access.   You can ensure certain users only have access to create activities on a specific environment by utilizing and combining Properties with Workspaces. A property is mapped to a workspace. You create a Property and a Workspace for each enviro...

The URLs were just example URLs, not real ones to give you an idea. You can see a real example here.

Yes, entity.id is all you need. And you'll have to pass it on every product detail page. Like this:http://domain.com/products/headphones/bose1234Entity.id: bose1234 http://domain.com/products/headphones/sony1345Entity.id: sony1345

Based on your screendump it seems you're populating all the product values in 1 request. You need to only pass the information that is relevant to the product that is being viewed.