Is it possible to modify OOTB campaign components or to introduce new components in Campaign Standard? | Community
Skip to main content
jezwn
Level 5
March 15, 2023
Solved

Is it possible to modify OOTB campaign components or to introduce new components in Campaign Standard?

  • March 15, 2023
  • 2 replies
  • 1814 views

I'm facing an issue with the Adobe Campaign image component. It works correctly in most of the cases, but when placed inside a 1:1 column and previewed the email delivery on Outlook and Office 365 apps, the image is cut off.

The image component HTML looks like the below,

<!--[if mso]><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td style="text-align: center;"><![endif]--> <img src="/path/to/image" width="340" height="227" title="Title" data-nl-imgep-perso-attr-alt="ALT" alt="ALT"> <!--[if mso]></td></tr></table><![endif]-->


The modifications required for the image to render correctly in all the outlook apps is as follows,

<!--[if mso]><table cellpadding="0" cellspacing="0" border="0" width="100%"><tr><td style="text-align: center; line-height:0;"><![endif]--> <img src="/path/to/image" style="width:340px; height:227px;" width="340" height="227" title="Title" data-nl-imgep-perso-attr-alt="ALT" alt="ALT"> <!--[if mso]></td></tr></table><![endif]-->

 

  1. A proper height and width in pixels for the <img> tag.
  2. line-height of 0 for the mso specific conditional which is wrapping the <img> tag.

 

Is it possible I could modify the image component HTML so that these changes can be applied globally and for any future usages. Or what would be the best way to address this?

Or is there any other solution from Campaign directly to resolve the image cut off issue on Outlook?

Thanks

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 David_Loyd

I would start here

With editing HTML in AC Standard.
https://experienceleague.adobe.com/docs/campaign-standard/using/designing-content/building-email-content/plain-text-html-modes.html?lang=en

 

Then move to Litmus to try different code snippets that help to solve the issue with outlook.

https://www.litmus.com/blog/a-guide-to-rendering-differences-in-microsoft-outlook-clients/

 

 

2 replies

David_Loyd
Adobe Employee
David_LoydAdobe EmployeeAccepted solution
Adobe Employee
March 15, 2023

I would start here

With editing HTML in AC Standard.
https://experienceleague.adobe.com/docs/campaign-standard/using/designing-content/building-email-content/plain-text-html-modes.html?lang=en

 

Then move to Litmus to try different code snippets that help to solve the issue with outlook.

https://www.litmus.com/blog/a-guide-to-rendering-differences-in-microsoft-outlook-clients/

 

 

jezwn
jezwnAuthor
Level 5
March 15, 2023

Thank you @david_loyd So, are you confirming there's no Campaign specific solution for this and we have to use testing platforms like Litmus to address any email client specific issues? One other question would be, why won't the Campaign image component doesn't work properly with Outlook like clients?

David_Loyd
Adobe Employee
Adobe Employee
March 15, 2023

 Email HTML standards are always evolving as we all know. So the HTML templates are just meant to be the basics, and its really up to the customer to evolve their email HTML practices based on their unique needs. 

Based on this litmus report (below) outlook only represents 4.4% of email clients. But your email list may have a different percentage break out. As HTML developers spending time to make sure the email is rendering in all email clients, they should do so with data that informs them of where to spend their time. For example in my past we ignored outlook all together, because our customer list was 90% gmail, 5% apple and 4% yahoo. There wasn't a need to invest into outlook rendering because that is not where are customer were spending their time.


https://www.litmus.com/email-client-market-share/

Adobe Employee
March 29, 2023

Unfortunately there is no way to modify the standard components which are available via Drag&Drop or to create new components.

 

I guess the right way would be to raise a ticket to support to get it fixed in the product code