Housing Email Nurture Content in Design Studio

A document by KCS Integration on behalf of 5414ba7966cf11ecf3e00a3b558da04353c30904 on May 3, 2019Last modified by Roxann McGlumphy on May 10, 2019
Version 2Show Document
  • View in full screen mode

Issue Description
Possible disadvantages of maintaining Engagement/Nurture Program emails in Design Studio.

 

Issue Resolution
Housing all of your emails for email nurture content in Design Studio could cause the following issues: 

 

1. Reporting: Reports can specify Emails in Design Studio, however they will show results for any send of the individual email and will not be constricted to the program they were sent from.

 

2. Asset re-use in Engagement Programs: When using an engagement program, an asset is scanned for its ID. If that asset has been previously sent to a record via any other send, the engagement program will skip that send for that record. This could become a problem when reusing email assets housed in design studio in different engagement programs. 

 

3. My Tokens: my.tokens will not properly render as they are based on a program folder. The assets that reference them need to be in the folder as well. In my testing, assets in design studio do not have a frame of reference for mytokens. Emails will not populate mytokens if they are housed outside of the program that owns the tokens. 

 


With all of this noted, o recommendation is to utilize detailed templates in design studio and continue to clone your engagement programs and alter them as necessary. Although this presents some busy work in the short term, it pays off dividends in the long term when it comes to reporting, the use of my.tokens, and guaranteeing that records are sent the assets you are specifying in your programs. 

 

 

Attachments

    Outcomes