Metadescription different between actual email and marketo | Community
Skip to main content
March 17, 2016
Question

Metadescription different between actual email and marketo

  • March 17, 2016
  • 3 replies
  • 2951 views

Hi guys,

Just to make sure my terminology is clear - when I say "metadescription" what I mean is the preview text that shows up in an email, i.e.

"Save the Date - Our Web Clinic! You're invited to our upcoming Web Cl..."

The bolded part would be the subject, the following part would be the preview text / metadescription.

OK, now to the problem:

I have a metadescription set to this text:

You're invited to our Web Clinic: {{my.WebinarName1}}  

   View this email in your browser.

Accessing this by going edit email -> clicking on the header area -> changing from HTML to Text and editing it there.

However, I'm still receiving emails with different meta text, that is:

You're invited to our {{my.WebinarName1}} Web Clinic

How do I make sure the metadescription matches what I want it to be?

Thanks!

Andrew

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Grégoire_Miche2
Level 10
March 17, 2016

Hi Andrew,

Have also updated the text version of your email ?

-Greg

March 17, 2016

Yep, but the text that is showing up in the preview wasn't in the main-body email text either.

Grégoire_Miche2
Level 10
March 17, 2016

Hi Andrew,

This is weird. The preview text is captured form the first text that appears in the email that is sent. Can it be that something is hard-coded in your email template ?

-Greg

Josh_Hill13
Level 10
March 17, 2016

Are you saying the token is appearing instead, or that the wrong text is appearing?

March 17, 2016

the latter - the tokens are fine, the wrong text is appearing (not the tokenized text - that's rendering properly; it's that somehow the preview text is pulling from somewhere I can't find)

Andrew

March 17, 2016

It is very weird. I checked through the email template's HTML and it isn't there (unless I somehow missed it). Also, it'd be very strange to hard-code stuff that includes tokens / etc into our email template, I'd be very surprised if that happened.