Hi @Jonathon_wodnicki , Do you have a screen shot of the syntax for the delivery variable and the target mapping config?I have tried a few different variations and either get nothing or the subject script (before personalization) in the broadlogRcp table.When I print out the delivery variable in the...

Thanks for taking a look at this Ishan.  Yes this will create a new delivery and the links will be fine going forward.  I was wondering if there was a way to update the tracking of the initial delivery as this one has broken links because they are not on the tracking server.

I have a continuous email delivery that is using offers from a single category.The links that were in the offers before the continuous delivery was created resolve fine on the tracking server.However, when new offers were added to the same category after the initial delivery has been created and ema...

@Darren_Bowers thanks for your reply.  If I use a data activity in my workflow I can insert a string > 1024 into the data schema.  This must be a limitation with the xtk.session.Write function.

I have a workflow that is using the xtk.session.Write function to insert some data into a custom data schema.When I log the variable with the data the entire string is there in the audit log.  However, the data is truncated to 1023 characters in the data schema.  The attribute length in the data sch...

Thanks Jon for taking a look at this. my question was really around personalization in the offer content, but it looks like you indirectly answered my question with "xml fields like @Title won't work here." I was trying to use the text content ([proposition/offer/view/textSource] ) field which is si...

We have been using offers in our email deliveries that contain personalization just fine.For deliveries that have a file extraction, reference to [proposition/offer/view/textSource] is empty.  The text content in the offer contains something like  "Hi <%= recipient.firstName %>" In the file extracti...

They differ with these 3allowDebug="true"  allowHTTP="true"sessionTokenOnly="true"Since I am passing the session and security tokens over HTTPS, it should be accepted.I did notice that the public security zone has a proxy configured with a localhost IP mask: proxy="127.0.0.1, ::1"Does this mean that...

The service request works fine if it is made from an IP configured in the VPN security zone using the same operator.  e.g. From my machine all requests are fine.Firewalls are not an issue ... the logon request works fine and I am getting a response from the application when it returns the HTTP 403. ...

I have defined a SOAP method on a custom data schema.  The system that will be calling this service is hosted in a cloud infrastructure, not fixed IP address.I created an operator for the service to authenticate with and linked it with the Public Security Zone as the authorized connection zone.  The...