I still think your profile script is returning true/false, but your segment logic is not looking for true/false Visitor Profile: user.2025_Downloaded_PDF Equals (case insensitive) downloadPDF Can you confirm your profile script is returning as you expect or try and update your segment logic?

@chris-luckett  Honestly, I don't remember all the details behind the decision, but if I recall correctly, it was easier to to expand their google feed which they already used, rather than develop a a full api solution. Initially, the api was a temp solution.  It was not due to performance. Let me k...

I encourage you to also post it in this thread: https://experienceleaguecommunities.adobe.com/t5/adobe-target-discussions/announcement-facing-issues-with-the-new-adobe-target-ui-you-re/td-p/762841 @Gokul_Agiwal is putting together a list to share with engineering and gather feedback.

Hi @chris-luckett This is an interesting use case. I've had a similar case previously. Without more details, I'm not sure if this addresses your specific case. Previously we solved this by creating an attribute that controlled whether the product was a promotion or not. e.g. promoActive = false/true...

No, that's not required.

I've done nothing else than what is documented in the video.   Yes, without setting up the catalogue it will work.

I've received a couple of questions via DMs, which I'll post here for everyone to see the answer:   Q: Do I need to upload my products via the feed for Recommendations to recommend them in a criteria? A: No. You want to implement entity.id (this is the minimum requirement) on all product detail page...

@Sankaran No, there's no prior steps other than what i documented in the video. I'm only implementing the entity.id - no upload was made.

@Jyoti_Yadav if you see it in the interaction, but it isn't rendered, it sounds like you haven't added the renderDecision to your event. With the webSDK rendering of target content only happens if you ask for it, which is done through the renderDecision. alloy("sendEvent", { renderDecisions: true })...

@m_alcantara  I'm not entirely sure what the main cause is, but i see some discrepancies in what you're describing.  You say you use WebSDK, but adobe.target.trackEvent is an at.js function - do you have both implemented? If you in your trackEvent passed it as a profile parameter, you could skip the...