Dynamic HTML Email Content in Recurring Delivery ACS

[acs-ratul]

Hey Team,

Is there any way the HTML Email Content in a recurring delivery can be made dynamic. The HTML Content file is placed in S3 and can be made public if required for ACS to access.

I tried below solutions for the usecase -

1. Use Remote URL  - https://docs.adobe.com/content/help/en/campaign-standard/using/designing-content/building-email-cont...
2. Using Load Script(ACC) - https://docs.adobe.com/content/help/en/campaign-classic/using/automating-with-workflows/use-cases/de...

For the first (Using remote url and delivery parameters)- I am able to generate email out of the public html content from S3. But its not dynamic and sends out the email with the same html content which it sent for the first time when recurring delivery ran. 

For the second - Didn't find an ACS alternative since the solution is for ACS. Let me know if a ACS Solution exist.

let me know of any solution for the usecase or any more info is needed.

[johnwwilcoxmba]

I had a similar issue and what I ended up doing is create a custom resource with fields and html content which in a workflow I grab the data each night and update the custom resource.  I then have the custom resource fields in the dynamic recurring delivery.

John

[ramon_bisswanger · Accepted solution]

The file download should work if you disable the aggregation, i.e. each send out will create a new technical delivery.

In ACS that would be the common way to achieve it. You don't have JavaScript support etc. In ACS.

[acs-ratul]

Thanks a lot...

Can we also personalize the content...using scripts in the hosted html content?

and since the html content has to be public resource in this case. Is there a solution where it need not to be public and can be accessed in ACS.(Similar to the second approach defined in question)

[shelly-goel]

@acs-ratulFor personalization, you may use data-nl-expr and data-nl-type attributes on the elements that need to be personalized.

So the source of html template (remote URL) would look something like this:

<div contenteditable="true" class="text-container">
<p>Please type your text here. <span class="acr-field nl-dce-field" data-nl-expr="/context/profile/email" data-nl-type="string" contenteditable="false">Email (email)</span></p>
</div>

This is the source generated in ACS on personalizing email within ACS.

[Shawn_Lomas]

Are there any more updates on this @acs-ratul?

I'm trying to do something similar however I'm having a hard time passing in a variable that I've enriched upstream. I've even extended the delivery resource with a Delivery Code and can use it for personalization successfully when I manually set it in the delivery. Just not when I pull the data from upstream... 

[acs-ratul]

No Further Updates...Sry for the delay.. I was able to resolve it using no aggregation