Can we tokenize pictures in Email Assist?

Any update on this one?

This would be nice to have since end-users can now have profile pictures. A specific use case would be embedding a CSM’s profile photo (or another desired photo) into the body of an intro email sent via Journey Orchestrator to make it more personalized. 

Hello All,
This is a great idea, as of now this is not planned.

Hello Team,

Any plans of this being included in the Product Roadmap..One of my customer tried bringing this up..

Hi All,

Can we talk  more on the usecases for which tokeneized images would be needed.

Is there any pressing usecase apart from including CSM’s pic in email?

Thanks

Samarth

We need this! Specifically embedding a CSM’s profile photo into the footer of an intro email to humanize and increase response rates

Hi @ssamarth - we would use tokenized images to white label emails for our partners. So, for example, if we have a partner and we are emailing their customers through journey orchestrator, we would like to be able to insert the logo of the partner that owns that customer. 

Hope that makes sense. This would be very useful!

This is not the solution to the problem, however, this can be used as a workaround if it’s critical to display tokenised images in Gainsight.

Pre-requisite

• Upload the required pictures on a platform where you can generate a public link.
• Extract all the links and keep em in an excel

Steps

• Create a URL field type on the MDA object, example: CSM Profile Picture URL (This will be created on User object)
• Import all the URL’s via rules engine or manually update on each user record (choice is yours)
• Create the email template with a placeholder image (it should be a URL image)
• Go to the code editor and ensure that the code of the placeholder image looks similar to this - <img src="https://example.com/path-to-your-image.jpg" alt="Circular Cropped Image">. If you have got an email designer you might just see width, height and padding also defined in it but you should still see src syntax which will have a URL against it.
• Add a token with it being mapped to URL field type which you previously created
• Go to the code editor and look for the code for token you should see something like this - ${embd::4ee53055-d3d1-471e-90ad-a8c31fe1fe94}​
• Pick this link up and replace it with URL in the image placeholder code and you should have something like this - <img src="${embd::4ee53055-d3d1-471e-90ad-a8c31fe1fe94}​">

Be mindful that if you delete the original token, the image will not render anymore.

In my opinion this is a very cumbersome implementation and chances of error are quite high, it cannot be done at scale if you are unable to automate the pre requisites.

You can still use it if it’s critical for you to tokenise the image, maybe you have a separate segment of customers who you would like to send personalised emails to create a better experience.