Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Dynamic HTML Email Content in Recurring Delivery ACS

Avatar

Avatar
Validate 1
Level 1
acs-ratul
Level 1

Likes

0 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
acs-ratul
Level 1

Likes

0 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
acs-ratul
Level 1

02-11-2020

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.

View Entire Topic

Avatar

Avatar
Level 1
Shawn_Lomas
Level 1

Likes

0 likes

Total Posts

3 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
Shawn_Lomas
Level 1

Likes

0 likes

Total Posts

3 posts

Correct Reply

0 solutions
View profile
Shawn_Lomas
Level 1

11-01-2021

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...