Thanks for the reply. I understand the basics of server-side delivery; e.g. how I would implement in a "typical" server-side app (i.e. a Spring MVC one). My question is what is the best/common practice with using it alongside AEM specifically. Are the calls to Target's API normally put in the Sling ...

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?

Thanks much for the quick response. Unfortunately, I cannot install the Groovy Console package in AEM. Is there a good alternative that does not require in new packages in AEM itself?Thanks!

Hello, We have a need to add meta tags in bulk to many of our pages in AEM (normally adding through Page Properties -> Meta Tag). I was wondering if there is a way to automate this/do it in bulk, either through cURL or other means?Thanks,Kelly

Hello, We are looking at implementing the customer attributes feature. I have reviewed the documentation both in the Target section as well as the "Experience Cloud Interface Component" docs.  I understand you upload customer IDs and associated attributes to the platform and that you must send this ...

Thanks for the information. Yes, it appears that the rule is firing correctly. The only extension used is Core (v1.8.3). The action type is a Custom Code that, in part, calls "adobe.target.trackEvent" to fire a custom mbox. It works consistently if I manually disable the link navigation event (that ...

Thanks for the response. Unfortunately, I cannot provide a URL or logs. Sorry, I realize this will make troubleshooting difficult. How would I distinguish between the rule firing and action script? Currently, the only way I can determine whether or not it is operating correctly is using the Debugger...

Hello,We have a a simple configured in Launch. The "trigger" event is merely Core -> Click with a simple CSS selector. There is no condition and the the "Action" portion is custom JS that fires a target mbox. However, we are having issues with this rule firing consistently. It appears to be a timing...