Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Tuan, please send me your entire email template as an attachment to jcooperman@marketo.com Also explain briefly which block of code you believe should be controlling sizing and what you are seeing as the result in other ESPs vs. Marketo.Justin
Synthia,This should work fine if you are using a rich-text program token and placing it in the landing page template (or landing page itself). Make sure the landing page is within the program where you have defined the token. If you are having issues, please let me know and I can look into it for yo...
Can you post the code as Josh mentioned? Otherwise, I am not sure what you're trying to do. I can let you know what is happening.
It's somewhat complicated how this all works. We don't support all emojis in our subject lines. We only support text symbols that are generally then converted into emojis by the recipient's email client (or operating system). There is a set of accepted text symbols that will universally work on all ...
https://docs.marketo.com/display/DOCS/System+Tokens+Glossary
It won't do anything to existing emails. But, if you look at my comments above, if you have an existing email template that has things like a custom DOCTYPE then all of a sudden when you create new emails from that template, that will persist.
Yes, please keep us updated about what support says here. What you described should work.
Email links have "mkt_tok" parameter applied, which does work. But that works through cookies. Munchkin will cookie the lead and then send the activity info to Marketo via JavaScript. If you use private browsing, cookies are not operational. So it makes sense that no tracking will work in that case.
We already support this, somewhat. In subject lines, we don't let you use all types of emojis that you could inside of an email. We only allow you to use text symbols that have default emoji representations of them. For example, if you enter most these symbols ☂ Symbols — CopyPasteCharacter.com in a...
Here is the product team's official stance on this:For pre-fill to work on embedded forms, it requires a publicly accessible API that retrieves lead information, which can include personally identifiable information such as email addresses, mailing addresses, names, and phone numbers. For us to mak...