Hello all:We have an Experience Fragment that utilizes custom AEM Components. Some of the elements in one of these Components get an event handler attached to them through a "clientlib" JS script in AEM. When using these Components through AEM, the event handlers are attached consistently and the code works as expected. The issue arises when we export the XF to Target and use it in an Activity. Approximately 90% of the time, the code works fine. The events are attached and client-side behavior i...

Hello,Is it possible to (1) create an Activity that adds event handler that calls `adobe.target.triggerView()` (Custom Code Modification), and then (2) create another Activity that uses this View in the VEC (like you would for any SPA)? Or is it strictly necessary that triggerView() be added in the SPA/code base itself outside of Target? I have tried using the QA link for Activity 1 when creating Activity 2 but without success.

Hello,This may seem like a bit of a silly question, but is there any way to use Target Server side alongside AEM? I would not think it is possible since I am not sure where one could "hook" the usual server-side logic (calls to Target's Delivery api), but not sure if I am missing something?

Hello,I am attempting to troubleshoot an issue we have with Target and Customer Attributes.I have setup the data source in Customer Attributes, configured Target as the Subscription, and called `setCustomerIDs()` as required in my code.The data seems to be flowing fine. Using the ID lookup tool, I saw that an ECID was being linked with the Customer ID. In Target, the Attributes are available when creating an Audience. A query to https://client-code.tt.omtrdc.net/rest/v1/profiles/thirdPartyId/xxx...