Hi @vijayc88216288, what you can do is that you create several activities (make sure that the variants are separated accordingly - and correspond to the actual activity) - which only serve for reporting.   It is a little more time-consuming. But in certain cases quite helpful. Because multiple goal ...

If this should really ever be implemented. In my opinion, it would also make sense if folders can also be used optionally via the API.

Hello @user96222 ,Thank you for your question. If I understand you correctly - it sounds more like an AEM issue to me. Here you are in the Adobe Target area. I think you can get better/faster help there: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/ct-p/adobe-experience-...

Hello @xcode2295,if there really isn't a pre-hiding snippet in the source code. Is it possibly via another rule in Adobe Experience Platform Launch that code is inserted on the page.   Basically a pre-hiding snippet is recommended when Adobe Target is loaded asynchronously. However, care must be tak...

Hi @gthakur8 , as @Gaureshk_Kodag has already explained, the DOM for this is not yet there at the beginning and is only generated at runtime. What can be done anyway - is that you check with JavaScript when the corresponding overlay is available and then the overlay is changed with JavaScript. To do...

Hi @ramvg, Maybe you still have something from a QA link in the cookie. I would delete this if necessary or try it in the Incognito Window. Here is also a post on how you can have mboxes disabled via session cookie. However, this generally only works with the at.js. When using the Mobile SDK, the m...

I'm not sure if that possibly applies: If this affects only one activity and works for all others directly after consent and first reload - it may be that an audience is not yet valid at this time, because only required information is not yet available.

What else I notice about the script. I don't know when exactly it is executed. But what can also be possible is that the script executes right at the page load via target - but at this time the button does not yet exist in the DOM.

I guess there is just a rule missing that checks if the consent for Adobe Target is given - and then loads Target accordingly.

Hi @tarun_jamana8469, How is the HTML markup structured? Does the button have an href attribute? Maybe this is already the problem from the timing point of view.