Hi,Usage example, from nms:amcIntegration.js; looks like you need [remoteContent/@remotePath], and to follow expected structure:  // Fetch content from AEM  if(application.hasPackage("nms:aemIntegration") )  {    template = xtk.queryDef.create(    <queryDef operation="get" schema="nms:delivery">    ...

Hi,Use a query activity on nms:trackingLogRcp. From there you'll have access to all the tables and fields in your list via 'Add data...' (select clause).Thanks,-Jon

It's an undocumented js function. The delivery param here is a delivery object, from a queryDef 'get' on nms:delivery. You can probably sub in your eachResp iterator there.

Hi,To fetch AEM content for a delivery, use nms.delivery.aemGetContent(delivery).To select paths in queryDef, use alias="html" in the <node/> element.Thanks,-Jon

Hi,Use nms.delivery.aemGetContent(delivery).Thanks,-Jon

Right, that's tracking calculation click formula plus extra analytics params.

Oh I meant selecting the data in the control typology is expensive, since it's n / batch-size lookups added per delivery.That was meant to be written as 3 options in descending order of overhead.

Hi,Try the documented jsapi cryptString() function on account id, add cryptedAccountId to all your personalization, or batch select cryptedAccountId's in the script (expensive).NB there are several undocumented encryption functions so cryptString() may not match the computed col's xtk AESEncrypt() c...

Maybe something with your local certs or a network filter. Easier to debug from the cmd prompt if you have access and openssl client is installed.All protocols work with api.omniture.com, except ssl3 which was expected:$ openssl s_client -connect api.omniture.com:443 -tls1_2CONNECTED(00000003)depth=...

Hi,Check your db encoding, should be utf-8/16/32.Thanks,-Jon