Admittedly, I do not know much about this space. Have you posted this in the AEM community? Sounds like a caching/edge-side includes issue to me and not specifically about Adobe Target. https://helpx.adobe.com/experience-manager/kb/optimizing-aem-site-caches.html I am also interested in this use cas...

It sounds like you are trying to get Target to establish a sort of journey. I am not aware of any out of the box functionality that could assist here, however, you could leverage the global Target call and response tokens to have knowledge of what kind of user your are working with. The idea would g...

Is the issue happening somewhere that you could share? If not, do you happen to have the targetGlobalSettings as an object anywhere?window.targetGlobalSettings = { cookieDomain: 'asdf.com', timeout: 200, // using custom timeout visitorApiTimeout: 500, // using custom API timeout ...

I think of it like a spreadsheet with the first column being the product id as a starting point (current product page, last viewed product, most viewed product) and all subsequent columns being potential recommendations which are generated upon creating an activity with a particular criteria in mind...

Adobe Target handles this out of the box as long as you have entity.id parameter for the Target call set up on the product pages. There is also a checkbox in the criteria creation screen to allow/disallow recommendations to be previously purchased (I think). In order for purchase to populate for the...

Just a thought ... What do they use as the customer id going into Target? Best case scenario would be to surface some sort of customer id in the client side (from server) once phone number or email is known and store that as a cookie or local storage (if only using one subdomain). Then you could use...

There are a few things that are probably worth looking into to help with your question. Adobe Target Recommendations is an e-commerce style product recommendation service. It has a catalog (feed) that keeps up with product views/purchases (if integrated) and then you can run activities to highlight ...

A server side implementation with no concept of your user could work as well. +1 to the solution above though.

I do not know of any way to accomplish this out of the box. You could implement your own getOffers/applyOffers into a single request with a promise that you only applyOffers in the use case that is pertinent to your scenario. Would need to have some developer assistance if you take this route: https...

Can you elaborate a bit on the scenario? The screen shot provided seems to show two Target requests. Are they two requests from the same page or separated by a refresh? What are you looking for that should change? Unless you set up mbox3rdpartyid, Target will rely on the TNT ID to determine the user...