Marketo Removing Code for Image Scaling for Outlook at 125%dpi | Community
Skip to main content
June 19, 2015
Solved

Marketo Removing Code for Image Scaling for Outlook at 125%dpi

  • June 19, 2015
  • 6 replies
  • 7666 views

We’re having an issue with email rendering on Outlook 2013 (125% dpi) wherein the images stray from the set boundaries of the parent table. Upon further inspection, we’ve noticed that Marketo appears to be removing the header markup necessary for correct image scaling in Outlook at 125%dpi. I’ve attached screenshots of the code from before and after sending through Marketo.

Is there a way to stop Marketo from removing that code, or another workaround to adding it?

Pre Marketo code -

<!DOCTYPE html> 
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />

Post-Marketo code -

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />

Any help would be much appreciated.

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

We will be releasing this feature with a patch outside of our normal release schedule and I want to explain how it will work. The items will be applied to our production code tonight (10/13) and will be available for activation starting tomorrow. It will not be turned on automatically for all customers. We will, however, enable the feature on an ad-hoc basis for those that are interested. If you would like this feature enabled, please email me atjcooperman@marketo.com and tell me the Munchkin ID of your subscription.

While this functionality has been thoroughly tested, we won't be enabling this for all customers for 1-2 months. It is a large change and it is important that you understand (and communicate to your team) the behavior before choosing to enable this.

With this feature enabled, you will see the following behavior:

  • Custom DOCTYPES will not be stripped from your Email Templates when creating new Emails in Marketo.
  • Custom HTML attributes will not be stripped from your Email Templates when creating new Emails in Marketo.

         Please Note:

    • Your custom DOCTYPE will persist only if it is the very first line of your Email Template or what you are pasting into Email Actions > HTML Tools > Replace HTML. If the DOCTYPE is anywhere else, it will be stripped and replaced with Marketo's default DOCTYPE.
    • If you have existing Email Templates that already have custom DOCTYPES, they will now persist into your new Emails once the feature is enabled. Because this is a change from today's behavior, we highly recommend you make sure this will not cause issues for your existing emails. Same goes for existing Email Templates with custom HTML attributes.
    • If you omit a DOCTYPE in your Email Template or what you paste into Email Actions > HTML Tools > Replace HTML, the default Marketo DOCTYPE will still be added. You cannot create an Email without a DOCTYPE.
    • The Email Template "Preview" option will not show your custom DOCTYPE. This is expected so you can disregard this. Your emails will still have the DOCTYPE. This also applies to custom HTML attributes.

Again, please reach out directly if you'd like this enabled starting tomorrow (10/14) for your subscription. We will roll this out to all customers shortly after.

Thanks,

Justin

6 replies

Josh_Perry1
Level 5
June 20, 2015

Have you reached out to Marketo about this?

June 22, 2015

We have, but they don't have an answer for us yet. I thought perhaps the community might have some experience with similar issues.

July 28, 2015

is this still the case where Marketo strips out this code. Can anyone confirm?

xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office">

Kinda need this for background images to display in Outlook. without it this system is 3 years behind the times?

August 7, 2015

Marketo couldn't find an answer for us, so the issue still stands. If you figure it out, please share!    

Dan_Stevens_
Level 10
August 13, 2015

Jackie - I just came across your post today.  FYI, we're experiencing the same issues:

IDEA:

DISCUSSION: Marketo is rewriting/omitting a significant amount of code in our responsive emails withint he HEAD area

We were originally told that this would be fixed in June, then August, and now the earliest is October.  Unfortunately, we cannot wait that long and therefore need to identify alternative solutions - like knak.​  A bit frustrated though that we would have to pay for a solution that should be capable within Marketo (where we have a huge portion of our budget).

September 16, 2015

Any fix for this yet?

Dan_Stevens_
Level 10
September 16, 2015

As I mentioned above, this is slated to be included in the October release.

September 16, 2015

"We were originally told that this would be fixed in June, then August, and now the earliest is October. "

Yes, thanks but it doesn't hurt to apply a little extra pressure. Our client is using outlook, I need this fix for them to approve the emails we send.

Also stating June, August & October doesn't fill me with confidence they'll get it done.

September 18, 2015

Greetings, I have done some testing and I have found a resolve that allows you to use background images  100% of the time.

The issue with outlook rendering at 125% isn't because of Marketo. It's a software iterations of Outlook(I am actually trying to compile a list of which ones possess these issues). Somewhere in the program it renders background images at 96dpi(dots per inch also referenced as PPI[pixels per inch]) at random. So upon display Outlook will decided to rend the image at the standard 72dpi or 96dpi and this is why the issue isn't consistent either.

The resolve to solve this issue is output your full width image out of the imaging software at 96dpi opposed to the standard 72dpi. Outlook wont be able to expand it so your image will always render as 100% accurate.

I currently push out 100% responsive emails  that work in every single client except Lotus every other email possess a background image and displays accurate every time since this has been influenced.

Dan_Stevens_
Level 10
September 18, 2015

I agree that the issue is how Outlook renders responsive-coded emails (at least the approach that many use) when Windows is scaled to anything other that 100%, but the fact that Marketo doesn't allow the custom xmlns code in the HTML tag of the template, is preventing the defacto fix for this widespread issue (which has been well-documented across the web, e.g., here and here).

Also, Outlook/Windows isn't expanding our images - instead it's expanding the pixel width of the table layout (we don't use background images; furthermore, we also tested this by exporting all images at 96dpi - no luck), making the main/banner "look" like it's smaller - when in fact it's the layout to the main container of the email that isn't being respected here.

The good news is Marketo is finally on this issue and hopefully we'll see this fixed in next month's release.

Dan_Stevens_
Level 10
September 23, 2015

Now slated for December

September 30, 2015

Eagerly awaiting this fix.

Justin_Cooperm2
Justin_Cooperm2Accepted solution
Level 10
October 13, 2015

We will be releasing this feature with a patch outside of our normal release schedule and I want to explain how it will work. The items will be applied to our production code tonight (10/13) and will be available for activation starting tomorrow. It will not be turned on automatically for all customers. We will, however, enable the feature on an ad-hoc basis for those that are interested. If you would like this feature enabled, please email me atjcooperman@marketo.com and tell me the Munchkin ID of your subscription.

While this functionality has been thoroughly tested, we won't be enabling this for all customers for 1-2 months. It is a large change and it is important that you understand (and communicate to your team) the behavior before choosing to enable this.

With this feature enabled, you will see the following behavior:

  • Custom DOCTYPES will not be stripped from your Email Templates when creating new Emails in Marketo.
  • Custom HTML attributes will not be stripped from your Email Templates when creating new Emails in Marketo.

         Please Note:

    • Your custom DOCTYPE will persist only if it is the very first line of your Email Template or what you are pasting into Email Actions > HTML Tools > Replace HTML. If the DOCTYPE is anywhere else, it will be stripped and replaced with Marketo's default DOCTYPE.
    • If you have existing Email Templates that already have custom DOCTYPES, they will now persist into your new Emails once the feature is enabled. Because this is a change from today's behavior, we highly recommend you make sure this will not cause issues for your existing emails. Same goes for existing Email Templates with custom HTML attributes.
    • If you omit a DOCTYPE in your Email Template or what you paste into Email Actions > HTML Tools > Replace HTML, the default Marketo DOCTYPE will still be added. You cannot create an Email without a DOCTYPE.
    • The Email Template "Preview" option will not show your custom DOCTYPE. This is expected so you can disregard this. Your emails will still have the DOCTYPE. This also applies to custom HTML attributes.

Again, please reach out directly if you'd like this enabled starting tomorrow (10/14) for your subscription. We will roll this out to all customers shortly after.

Thanks,

Justin

Justin_Cooperm2
Level 10
October 14, 2015

This is now in our production environment!

I've only received two requests so far to enable the feature. Please don't be shy! Let me know if you want this enabled in your subscription and make sure you tell your team about the behavior change (noted above).

Dan_Stevens_
Level 10
October 14, 2015

I just finished testing... AND IT WORKS!!!!  Thanks so much, @Justin Cooperman  ​ !  BTW, it's not just the DOCTYPE that caused the issues, but Marketo was also stripping the xmlns definitions within the <HTML> tag, just after the DOCTYPE.  These critical three lines of code are now also being preserved.