Why do linked images within Microsoft 365 attributes not show in my template? – Exclaimer Knowledge Base

Scenario

You are populating an attribute within Microsoft 365, such as a Custom Attribute, with a linked image. However, the image itself does not appear within the Template Editor or when an email has been sent.

The below screenshot displays the custom attribute for a linked image:

The below screenshot displays the image placeholder within the Template Editor (or in the sent email):

Reason

The image may not show up for many reasons; some of the most common reasons are:

The hosted URL for the image isn't public-facing, so it will not show up at all.
The attribute used hasn't been updated or synchronized through to Exclaimer Cloud.
The signature has been rendered as a bitmap image.

Resolution

NOTE: The steps described here assume that you have already created an email signature. For more information, see how you can create an email signature.

Please click on the required options listed below to go through the detailed description:

To check if the linked image URL is public-facing or not

Test the link outside the attribute by copying the link into an incognito window or into the image/logo window in the editor:

- If the image appears, then the link is public-facing.

The below screenshot displays the image within the Image/Logo window:

To do a manual data synchronization

Manual data synchronization allows the data to come through to Exclaimer Cloud - this is a faster method.

If you are using custom attributes, they may need to be synchronized with Exclaimer Cloud.

NOTE: For more information, see how you can use custom attributes with Exclaimer Cloud.

To check if the signature is rendered as a bitmap image

Check if you are using a custom font that has been uploaded or if there is a background image that is causing the signature to render as a bitmap.
If you are not using any custom fonts or background images, check whether the signature canvas and/or the golden yellow line of the table for Render Mode has been set to Normal or Bitmap.
If Render Mode has been set to Bitmap, due to the use of custom fonts or background images, the hosted image within the attribute will not work.
By default, Render Mode is set to Bitmap to allow recipients to see the custom font and background image at all times, within every email.
You can use custom fonts without rendering as bitmaps or you can use background colours instead.
If you remove custom fonts and background images then automatically the signature Render Mode will be set to Normal.
If the Bitmap option has been selected by mistake, you can set the signature Render Mode to Normal without any issues, and the image will appear within the signature template.

The below screenshot displays the image within the Template Editor (or in the sent email):