Email with token that could be text or an image breaking on "view as a webpage"

[Brianna_Bridges]

So we have an email that is going out that will have variable data in a lot of fields, with some of the fields populating text and some of the fields populating a checkmark image if the recipient has met their goal, otherwise if they haven't it will be a dollar amount of how many more purchases they meed to meet their target.  Using the image src="marketo image url" in the field for those that have met their goal, it seems to work fine on our test emails sent, however the problem seems to lie in the "View in Web Browser" version of the individual email, where the text fields with dollar amounts are showing up fine and populating for the lead as expected, but the checkmark image is not showing up, instead it shows the actual image source url HTML rather than the image itself.

Is there any way to fix this?

[Josh_Hill13]

How are you accomplishing this? Velocity script? Segmentation?

Perhaps the answer is to not allow people to view this as a web page.

[Brianna_Bridges]

We are just using tokens and field values - the problem is that we don't know which lead will be getting a checkmark (if at all) and in which part of the chart table - it could be a dollar amount or it could be the checkmark if the goal is met, so we have to do the calculations for each lead individually and if it adds up to the right amount, then we have the checkmark in that lead's field. So it's all happening with individual lead field values, hence why tokens make the most sense....  We were using a character entity to create the checkmark and it was working ok, but we have a stakeholder that wants the checkmark to appear more uniformly so we're having to use an image to accomplish this.  It's working great on our email tests, just the view in browser that isn't working.  We are supposed to have that on all our emails (as its a best practice) and have had that functionality available on previous emails to the same leads, so to remove it now would probably not bode well.  Not sure why it isn't working in the view in browser, where we're using the system token for that....

Any ideas?