I have also created a new library where I changed the custom message to have an exclamation mark now and left this library in Staging. Now I can see the local site show the message with the exclamation mark but it still doesn't say launch is loaded.

I have the library published already. But I am using the staging environment. Does it only work on staging when it is in the staging part of the publishing?

So I have installed the switch, and it doesn't seem to give me anything useful. This is what I see on the we-retail site:This menu appears so it doesn't seem like launch is triggering correctly. However, it shows the "Target Loaded" message that I added in the Custom Code in the Launch rules.

Also, interestingly enough. Launch is not found either but the Rule that I put in fires.....

I don't. I am currently just working off of my local instance. Which is the Launch Debug switch?

Using the Adobe Experience Cloud Debugger, It seems Target is not found. So it isn't being loaded at all.I am looking at the Luma demo site and it seems like the ID is implemented correctly.

It seems to be necessary to implement it from the docs, so I was going to give it a try. I am currently using Target 2.x but I also tried it with the 1.x as well.

It does NOT make the target call. This would make sense since I am loading the target libraries but its not showing. I think this is the step I am missing: Add the Experience Cloud ID Service Currently trying the solution. Will update this discussion after.

Hello all,I am currently trying to set-up an Adobe Target demo on a local AEM 6.4 instance. I integrated AEM with Target using Adobe Launch and currently have it set-up with the following rules:This was done following this tutorial and I added a message box at the end notifying me when the actions h...

Can I give this question a bump?