@LuziaV have you tried passing the entity attributes as mboxParams as demonstrated under this document : https://experienceleague.adobe.com/docs/target/using/recommendations/entities/custom-entity-attributes.html?lang=en .   Another option could be to use "window.adobe.target.getOffer()" function . ...

@rob2020 have a look at this document : https://experienceleague.adobe.com/docs/experience-platform/edge/personalization/adobe-target/a4t/client-side.html?lang=en , I hope this would be helpful.

@garimamalhotra  To debug this further , I would recommend to first check if there is any recs data generated for this activity or not . Go to Target activity and then click on three dots :  If you see the data getting captured then this means that the algorithm is generating results.   Now as sugg...

@CurtisYoung1987 If you are implementing Target using Launch then there is a simple option of firing triggerView based upon selector ID : Which may help you in achieving the use case . Else the other option would be to trigger the triggerView function on event/action for a specific element . Was ab...

@Mr_Moorthi  as suggested , the issue is related to the mbox host . Please check the Host section under Administrator tab in Target UI and then ensure that the Host settings are not enabled . If they are then please add the domain of the current page in the list. Document : https://experienceleague....

@NidhiAgrawal1 as you can see in the console log , it states "Invalid QA token : Wrong client" . Could you try activating this activity and then check if you see the correct content. This error usually occurs when we are trying to reactivate an old ended activity. Please try creating a new activity ...

@analyticsenthu  Primarily this would be a question mainly for Analytic team . A4T integration would not cause any issues for evar or prop events.We may need to check the rules configured for firing these rules. Could you share more context around how are you firing these evars and props (which are ...

@KeithDavo  This issue could be related to how your website is configured. We have observed similar issues when we have different selectors for mobile view and desktop view.So Target VEC operates on the screen size and does not count the user-agent part. When we use mobile Targeting then it's actual...

@Mr_Moorthi could you share the request URL and request payload on "gasingh@adobe.com" . I will quickly review it and share the insights.If things need to be investigated , you may need to open a client care ticket.

@NidhiAgrawal1  to further narrow down the problem could you please try using QA audiences and then set the activity live ? Just try using any QA audience such as "Current URL query string parameter contains "Test123". This would help you in identifying if the issue is with QA link or your setup. We...