Hi @ayush-804, is the problem still there - or was it just a temporary problem?

Hi @ayush-804,is the XF published - and does the following work in the browser? Public URL + /content/experience-fragments/zzzzz/1234.html   Best regards Perrin

Hi @AbinashMi1,could you explain exactly how you built the audience for this activity?

Hi @aaronlng_92 ,looks like a timing issue to me as well. This probably works in the preview in the VEC. But as @Matthew_Ravlich_ACG writes I would use a script with a mutation observer to wait until the element exists and then set the styles with JavaScript accordingly. If all this doesn't help - y...

Hi @mparticleu19460, If you have the visitor-id you can fetch the profile accordingly: https://developers.adobetarget.com/api/#fetching-a-profile   Best regards

Hi @Moorthi_MSD,I have no problems playing Target activities on MS Edge. If I were you, I would try to create a new activity - with your corresponding audience - to test this, simply execute an HTML offer with <script>console.log("Test123")</script> , for example, to see if it works. Perhaps you can...

What is the current situation? I currently have the problem that redirectOffers are running in Activities on a page with the WebSDK (asynchronously via Adobe Launch / Data Collection). The preHiding snippet is also used. Yes, at the first alloy sendEvent the style with the id alloy-prehiding is remo...

Hi @StevenMo1,   The normal way here via Target on the client side is a redirectOffer. The alternative is that almost the entire DOM is exchanged accordingly via an HTML offer. Depending on the setup, this sounds easier than it is. It must be ensured that all components are automatically initialized...

Hi @Michael_Soprano,if you want to debug requests - I recommend that you either do this via the Adobe Experience Platform Debugger, for example (you can also log in to the respective account here). All logs etc. are also listed here.   Otherwise you can also filter the requests by "interact" in the ...

Hi @ArijitAJ, Looks like a temporary solution to me, because it will soon no longer be supported by Chrome. If I understand correctly, this is just a workaround - but it doesn't solve the problem, does it?   thirdPartyCookiesEnabled | Adobe Data Collection   Google has announced plans to discontinue...