@Sankaran  1. Good. I assume these don't have entity.id set as you set those on the add to order button. 2. Yes, if you don't want the page load itself to be considered a view, then you need to pass on the click. I've not done this before, but it won't be an issue. Recommendation don't care how/when...

Correct. There's nothing different in Target when you use WebSDK - the WebSDK is just the technology passing data to Target. So if you do that correct, then it will work just like i showed in the recording. 

I’ve noticed quite a few threads and questions in Experience League around Adobe Target Recommendations recently - and it’s no surprise, because it can be tricky to wrap your head around how everything fits together.  Some of the recurring pain points I see are: Feed vs. implementation How Recs are...

When it comes to running experiments in Adobe Target, what slows you down the most? A) Data foundation — stitching the right signals and audiences togetherB) Organization — approvals, politics, and decision-makingC) Something else entirely (tell me what!) Drop your vote (and share a war story if you...

hey @Sankaran that's because I'm selecting Recently viewed criteria. This doesn't evaluate based on the current product i'm looking at, but the previous ones. Which allows me to deploy it on any page. If i had picked a criteria like-people viewed this also viewed that, it would have to be deployed o...

Correct!

Hi @Michael_Soprano  Feeds are not necessarily required if you pass in all the necessary data via the site itself (webSDK or at.js).  The feed won’t be created automatically, but it isn’t a requirement to run recommendations. Its a way of enriching/adding meta data to your products.  I’ve used feeds...

In my experience, the hardest part of experimentation often isn’t the tool itself – Adobe Target is powerful and flexible – but the context it lives in. For some organizations, the blocker is the data foundation: experiments become guesswork if the right data streams aren’t stitched together, or if ...

So the only way you can 'fuel' the criterias is by using the entity.id on the site - products created in the catalogue, but don't have entity.id set on the product page on the website will not generate any behaviour and will therefore not be part of any critierias. Hopefully this makes sense?

Assuming this is the api you've used: https://developer.adobe.com/target/administer/recommendations-api/#tag/Entities/operation/saveEntities  Then i wouldn't expect them to show. I assume that the one actually showing is collected via entity parameters on the site? With the API you've created new pr...