About Elin_Pedersen

Elin_Pedersen · ‎06-24-2020

Fab! This is just what I need. Thank you, Sanford!

Elin_Pedersen · ‎06-22-2020

I'd like to include a rep's name and email address in some emails, and pull in lead owner details in case the person is a SFDC lead, and account owner details in case the person is a SFDC contact associated to an account. However, the standard MKTO tokens only offers lead owner vs account owner, like {{lead.Lead Owner Last Name}} and {{company.Account Owner Last Name}}. I obviously don't want to use both, so thinking this should be possible using a script token instead? I am however no code expert, so was hoping someone had done this already and could share a solution? Or is there a better way to do this, perhaps?

Elin_Pedersen · ‎06-03-2019

Hi Dave, thanks for your reply. I usually use display:none for my booleans for landing pages, but since email is a different beast I went with this "comment-out-approach" instead. I second your practice that such elements shouldn't contain variables like text, since it clearly doesn't work, but since it works for strings and images, I'm thinking why not. It's very convenient to have this flexibility in an email template, and as long as the final html passes the test, then I feel safe about using this method. Thanks again for your input, much appreciated!

Elin_Pedersen · ‎06-03-2019

Hi Sanford, thanks for your reply. Sorry I didn't include the full code. I haven't tested the final html of this particular template yet, since the problem seems to be in the MTKO editor, given this method works well with other variables. I have however tested this extensively on several responsive email templates where I use boolean toogles to control what elements to show or hide, and it works perfectly together with image and string variables. I've done lots of testing on Litmus where I have exported final code and have found no issues so far. Until now when I wanted to combine the boolean hack with mktoText. Anyway, I'll keep in mind your tip about the syntax highlighter.

Elin_Pedersen · ‎06-03-2019

Thanks, Grégoire. Yes, this is the workaround I ended up applying as well. It works, just find it odd that it works perfectly with mktoString, mktoImage etc - just not with mktoText. Anyway, thanks for your reply!

Elin_Pedersen · ‎05-29-2019

Hello, I've created a template with many different modules and variables which all work great, with one exception: I have a mktoText class td inside an element for which I've added visibility control using the mktoBoolean declaration, and it seems I can only use one of the two, but not a combo. Here is my mkto variable in the email header: <meta class="mktoBoolean" id="top-intro-show" mktoName="Show top intro" default="true" true_value="-->" false_value="" true_value_name="YES" false_value_name="NO" mktoModuleScope="true"> And here is what the html looks like:  I've used this boolean trick to turn many other elements on and off, and it works perfectly in combination with other variables, like a mktoString defined in the header. With the above, if I don't use the boolean variable and use  instead in the html, the text element shows up in MKTO. If I use the boolean varible however, the slider is there and works as expected, but then the text element doesn't show. Does anyone have an idea as to why, and what I need to do in order to combine these two? It has to be a mktoText declaration, it cannot be string.

Elin_Pedersen · ‎03-18-2019

Marketo support has confirmed that the view source option no longer works due a change in the latest release with regards to the mkt-tok, and the fact that it no longer sticks in the url of the page when viewing an email as a web page. The mkt_tok is still there, but it doesn't stay in the url path of the browser anymore. You can spot it for a split second and then it's gone. This is what support mentioned about this change: "... we confirmed with engineering that this is due to the release and a byproduct of an intended and necessary change for security reasons. The removal of the mkt_tok, was so that the end user "cannot bookmark, forward, or let search engine cache it" according to engineering. Since that value can be used for cookie-ing with Munchkin, it was theoretically possible for the URL to get indexed on a search engine. Meaning anyone who clicked the link would get cookied as that person." They also confirmed that the approach going forward of getting to the code through a browser would be to save it as a file - view source will not work anymore because of the "missing" token. They did however provide another workaround to mimic the view source code approach I used before, and it works, although requires a bit of cutting and pasting: Send yourself a test email with the "view as web page" link included. In the email, right-click this url and copy it. In the browser, paste "view-source:your-copied-url-from-the-email" into the path. On that page you will see the complete url with the actual token - copy the entire url. In the browser, paste "view-source:the-entire-token-url" into the path. There's the code.

Elin_Pedersen · ‎03-18-2019

Update from support: this has to do with the latest release and the removal of the mkt_tok in the url for the view as a web page. They confirmed that the workaround is to save the html, and get to the source code that way. Still a bit of a hassle, but at least it's something. The really annoying part is that the marketo hosted image url's are not complete in the downloaded file, so those have to be added/updated manually in order for images to display correctly when/if sharing externally. Unless anyone knows a smart way of embedding the full image urls for images hosted in the design studio?

Elin_Pedersen · ‎03-18-2019

Interesting.. If I view in browser, and save the html instead of trying to view source (I use chrome), then I can get to the code when opening my saved file. I didn't even think of that option. Thank you, Sanford! Still, it's very strange that view source doesn't work when saving does. I'll report that finding to the support team as well.

Elin_Pedersen · ‎03-18-2019

Thank you, Sanford. That's what I thought - that view as web page would allow me to do this. Can also confirm that we are using a branding domain. I've logged a ticket with support and they are looking into it now. Grabbing the code from the view as a web page is how I've done it before, and nothing in our setup has changed, so I suspect there is a bug somewhere following the latest release.

Elin_Pedersen · ‎03-18-2019

Thanks, Tiffany. I've also logged a support ticket, they are looking into it now. I'll update this post when issue is resolved, or a workaround is found.

Elin_Pedersen · ‎03-18-2019

I have an email that is quite complex with lots of modules, variables and also uses program token for content. I would like to export the html of a final version of this email, as it will render. However, it doesn't seem possible, as the code edit or html export option only offers the template/base email code with the variables defined. And trying to preview the email doesn't allow me to grab the source either, neither is this possible if sending a test email or through a smart campaign with the "view as web page" link added (get error: Cannot get email content- Customer does not belong to any POD). Does anyone know how I can grab the final code of an email, without having to rebuild it and replace all variables and tokens with actual values? It seems odd that something as basic as this isn't possible, but perhaps someone has a workaround here?

Elin_Pedersen · ‎06-12-2017

Thank you both! I applied Tony's fix, and set the link not to track as per Sanford's recommendation, and testing shows that it works fine. Much appreciated your help here.

Elin_Pedersen · ‎06-10-2017

Thanks for your replies. However, in this particular case, I cannot hard code the links since I use this token to populate the email address of account owners. And the other link scenario I mention is for adding a unique webinar access link, passed in from our event provider. So hard coding is simply not an option for either of these. Besides, these are not links I want to track, so not a concern. This is how the styled token looks like in my email html: <span style="color: #0d85c7; text-decoration: underline;">{{company.Account Owner Email Address: default=xxx@xxx.com }} </span> I use this method for other tokens without problems, but as soon as it’s a link to a page or email address, this issue occur in outlook. Any ideas out there why this happens and how to fix it? I tried MKTO support but they are just telling me to contact a developer, so not really helpful.

Elin_Pedersen · ‎06-09-2017

I have several emails with email addresses and other links applied via tokens. I've wrapped these tokens in span tags with inline styling, to ensure the link looks similar to other links in my email. However, this style is not carried over to outlook (2016). It looks good on web and mobile clients, but not in my outlook desktop client. Does anyone know how to make inline styling of tokens work in outlook as well?

Online Status	Offline
Date Last Visited	a week ago

Date Registered	‎06-13-2016 06:46 AM
Date Last Visited	a week ago
Total Messages Posted	15
Likes Received	5

Top Badges Earned

Re: Script token for lead owner vs. account owner ...

Script token for lead owner vs. account owner deta...

Re: Email template: mktoText inside a mktoBoolean ...

Re: Email template: mktoText inside a mktoBoolean ...

Re: Email template: mktoText inside a mktoBoolean ...

Email template: mktoText inside a mktoBoolean decl...

Re: Export html of final email - not with tokens &...

Re: Export html of final email - not with tokens &...

Re: Export html of final email - not with tokens &...

Re: Export html of final email - not with tokens &...

Re: Export html of final email - not with tokens &...

Export html of final email - not with tokens & var...

Re: Outlook ignores inline style of links from tok...

Re: Outlook ignores inline style of links from tok...

Outlook ignores inline style of links from tokens