Problem with Lead.First Name Token in an email Preheader

[Justin_Cooperm2]

I remember some other community threads that discussed it previously, but can't find them now. Search in here is painful

[Carl_Delafonta2]

Hi Justin,

Thank you for you input. This is something I didn't know. I will talk to our web integrator and ask him to add the preheader in our templates.

Thanks for your help guys!

Carl

[Grégoire_Miche2]

You are right, Justin, I remenber that we discussed this just after the roll out of the email editor v2. Or was it about making the preheader a dynamic content?

I could not find the idea, so I created it :

-Greg

[Carl_Delafonta2]

Hi Justin Cooperman​,

I still have some concerns related to this issue. I have seen some cases where the {{lead.First Name}} token generated the wrong name in the body of an email and in the email subject line. It happened for one of our nurture email. You can see the ticket I have open with Marketo Support for more info and screenshots related to this issue (Case no. 00745941).

Also, I was wondering, what happens if I don't use the Marketo Preheader fonction? From my understanding, If I don't check the preheader box in the email settings, Marketo will use the first caracters of the body text of the email as a default preheader. If the body text of the email contains some tokens, will they be supported in the default preheader ?

Thank you for your help on this!

Carl

[Grégoire_Miche2]

Hi Carl,

On the second point, if your preheader module (that sits that the very top of the email) contains some tokens. the tokens will be rendered correctly before sending the email and the token value will be ursed normally for the email preview in email clients that use this fuinctionality.

-Greg

[Carl_Delafonta2]

Hello Michel,

Thank you for your response. That's what I will do for now.

Carl

[Justin_Cooperm2]

Regarding the first point, the tokens should always be replaced with values corresponding to the person being sent the email. I will take a look at the support case, not sure what happened in your specific case.

Regarding the second point, Gregoire already explained a bit, but it is only the Marketo Preheader feature in "Edit Settings" that won't support lead tokens. If you don't enable the Marketo Preheader (it isn't enabled by default anyway), then your email will simply go out with HTML as your Email Template is constructed for. Email clients generally use the first text available to show as the preview, but you could of course put your own preheader in the top of your template to make this happen. Generally it's a hidden/not visible region that would just serve to fill the preview for your email. Any token would work there, since it's just part of the body of the email itself. All tokens work in the body of a Marketo email.

Justin

[Carl_Delafonta2]

Hi Justin,

Thank you for your reply. I will wait for an update on the first point. I would like to understand why it happened, to make sure that it doesn't happen again.

For the second point, I understand perfectly and will adjust my next emails accordingly.

Thank you,

Carl

[Scott_McKeighe2]

Is a fix for this issue on the roadmap soon? I just discovered this as well, and the output our customers are seeing pivot between a token's default value (e.g., Hello Friend), or someone else's first name.

[Justin_Cooperm2]

Hi Scott,

Tokens should always be replaced with the value on the corresponding lead's record. It should never include someone else's content and if you are seeing that you should file a support ticket immediately. The only thing that isn't supported at the moment is using any token in the Marketo Preheader field. Tokens should work in the body of the email elements or email template itself.

Justin