Email Script Year

[Kim_Gandy1]

I'm working my way through all programs in our instance to add email script for year. I'm using $date.get('yyyy') from this community discussion, though Marketo support said it may cause email approval issues, so test drive $date.getYear() as well.

My question is that depending on the campaign, my team is cloning programs/emails or creating new. I know they won't remember to add script to each new program, and I don't want 2016 in any emails for the new year. In order to catch every email, does it make sense to both of the following:

1. Add script to all existing programs and input into existing emails.
2. Change year to 2017 in email templates in Design Studio. This would catch new program/email when user forgets to add script to new program.

I'm sure I'm overthinking this, so I'm open to any suggestions.

[SanfordWhiteman · Accepted solution]

Remember that tokens can be at the folder level as well.

It seems to me like by not trusting them to make the script token available and giving them a hard-coded fallback, you're just making it easier for them to not care. At a certain point, (in)action has to have consequences, and if they won't clone a shell program, that's on them....

[Josh_Hill13]

folder token

[SanfordWhiteman]

That's all I should have said.

[Scott_McKeighe2]

Folder level token is your best bet, especially if everything lives inside a parent/global folder in Marketing Activities (that way it just pushes down to everything beneath it). I'd also recommend tokenizing your company address, in case your company is like ours, and likes to move around a lot.