Button's v:roundrect problem
By default, in BEEPro's template builder, when we add a button, the HTML generated will embed outlook specific code like:
<!--[if mso]><v:roundrect xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word" href="https://www.google.com" style="height:42px;width:78px;v-text-anchor:middle;" arcsize="0%" stroke="false" fillcolor="#8a3c90"><w:anchorlock/><v:textbox inset="0px,0px,0px,0px"><center style="color:#ffffff; font-family:Arial, sans-serif; font-size:16px"><![endif]-->
When we use Amazon SES to send out this email, the link tracking function is not able to recognize the href inside the v:roundrect tag. And it seems that we cannot modify the SES logic. And as a result, when recipient click the button in the email, the "clicked" event cannot be collected by Amazon SES.
Are there any way to disable the mso code generated for the button? Or any other solutions?
-
Hi Gary,
Thanks for sharing your question with the BEE community!
As you have seen, Outlook code is wrapped inside "conditional comment" statements. Those are formally normal HTML comments, but they get read and interpreted only by Outlook desktop clients - and that's the only option we have to grant correct rendering and behavior on those clients.
Most likely, Amazon SES treats those as "normal" HTML comments and skips link processing. One way to solve this could be to add a post-processing routine standing between BEE and SES handling Outlook-only links so that SES will do the rest.
Otherwise, we suggest getting in touch with Amazon customer support, asking them to update links inside conditional comments too.
There is no way to disable this code when using BEE Pro, as it is used to ensure rendering in Outlook.
Please note that with the current behavior, you will lose link tracking only on Outlook desktop for Windows, because these are the only email clients that read those links inside the conditional comments.
I hope this helps. Please feel free to let us know if you have any further questions or comments!0
Please sign in to leave a comment.
Comments
1 comment