Re: copyright year in footer to auto-update in an email? Is this really possible?

Christine_LeBla
Level 3

copyright year in footer to auto-update in an email? Is this really possible?

Hi,

 

Marketo apparently has a token for this, but I do not believe it will work. ESPs are going to translate it to pull in the copyright year on emails?
Is there a bullet-proof way to have the copyright year auto update in my email templates for whenever they get sent out to recipients?

 

Thanks!

6 REPLIES 6
SanfordWhiteman
Level 10 - Community Moderator

Re: copyright year in footer to auto-update in an email? Is this really possible?

What token are you referring to, and what do you mean by "ESPs are going to translate it"?

Christine_LeBla
Level 3

Re: copyright year in footer to auto-update in an email? Is this really possible?

Email Service Provider

{{system.dateYear}}  ...tested this and it does not render the year.

SanfordWhiteman
Level 10 - Community Moderator

Re: copyright year in footer to auto-update in an email? Is this really possible?

Sounds like someone hallucinated that token. Where did you see that documented? (Also not sure what you meant by “ESPs translate” still — email recipients’ servers don’t understand tokens.)

 

In any case, use this: The definitive guide to setting up copyright year {{my.tokens}} for Emails and LPs 

Christine_LeBla
Level 3

Re: copyright year in footer to auto-update in an email? Is this really possible?

LOL! Yes, some kind of a 'GPT'. 😂

- I suppose I will just omit the year, or someone will need to remember to edit it each year.

SanfordWhiteman
Level 10 - Community Moderator

Re: copyright year in footer to auto-update in an email? Is this really possible?

Wait but I linked to the code that does it automatically.

Jo_Pitts1
Level 10 - Community Advisor

Re: copyright year in footer to auto-update in an email? Is this really possible?

@Christine_LeBla , I know @SanfordWhiteman  has provided you the solution, but I also want to clear something up.

 

The tokens get converted from a token to whatever content the token actually holds at the time the email is built, but before it is sent.  a {{my.xyz}} token is fundamentally no different to a {{lead.xyz}} token in that regard.  There is the obvious nuance with velocity tokens that they are 'executed' at the time the email is built, and then the output from them is put into the email.

 

The ESP does no 'translation'.. they are simply presented with a complete email.

 

Cheers

Jo