So basically just replace all instances of<% document.write(context.whatever.variable); %>with<%= context.whatever.variable %> EDIT: After more extensive testing, seems to work perfectly for a block shared across Campaign mailings, Campaign landing pages and AEM newsletters.

At our company, some mailings use content blocks with document.write calls to personalize salutations, like  <% if( context.profile.salutation != "" && context.profile.lastName != "") { %> <span>Hi </span><% document.write(context.profile.firstName); %> <% document.write(context.profile.lastName); %...

@costa_n11, thank you. For our purposes, we needed to use "context.delivery.workflow.name" in an applicability condition, which also works perfectly. I won't be able to run a test until tomorrow, will update my reply after.

Hi, unfortunately, the approach isn't working for us. The mailing returns a "context.targetData is undefined" error instead of successfully sending. I'm at a loss why; does the segmentCode have to have a specific format/length? Cheers,Thomas Pichler

I've actually been looking into this and the problem seems to be that usingcontext.delivery.name == 'DMxxxx'doesn't work for the specific scenario I'm currently looking at. The scenario is than an Email with a fixed DM# gets modified, then a new mailing is sent out via a workflow. This generates a n...

For optimizing analytics, we're looking for a way to configure a brand so the UTM parameters passed will depend on the Campaign Standard e-mail being sent. We assume this must be possible, and that the way to do it is to use applicability conditions in the brand configuration that uses an e-mail's C...