The engagement score is not calculated (reliably) until 48 hours after the send. ... View more

Hey Pete, I've also had inconsistent results when trying to hide stuff for mobile in email. Another approach to this that might be more effort is to think about this the other way around and coding the image to be hidden and then using media queries to show it at larger sizes - which generally means more CSS is accepted b/c your in a "bigger" (i.e. desktop/tablet) environment rather than a mobile system. It's probably a lot more work to turn a template 'upside-down' and code it to be mobile first, but that's the only sure-fire way I could think of to accomplish this with any consistency. ... View more

Hey Pete, I had a look thru the HTML -- copied it into a new template in Marketo and scrolled thru. I didn't see anything obvious that would flip the order of the sections you've got built here. The one thing that does stand out is all the capitalized CSS. Im not sure what (if any) impact this could be having on your render, but from the sounds of it there is something that Outlook (some versions) are interpreting differently than others and that usually has something to do with "specialized code" (like all caps). A few years back I remember a hack for Outlook that involved capitalizing the "M" in margin to solve a bug with Outlook spacing display, maybe this is something similar. In the case of the capital Margin, I choose to use padding or "height" instead and moved on from that mess by using another method to create the space that was more "friendly" to Outlook. Another thing to think about here is that Outlook is all over the place in terms of the different engines they use to render the HTML and I've even seen situations where "Outlook code" (VML) works for one variation but not others -- a hot mess all the way around. I might try and create a new version of the template sans-capitalization and send that off for a test to Outlook, maybe you can kinda narrow in on what (if any of it) might be causing this display issue. I'll usually walk it all the way back to "no-caps" for something like this and then test-as-I-go adding a little at a time until it breaks or I get to the finish line. While looking thru the code, I read a comment in there about creating a new row and renaming the elements inside. Im curious if this might have something to do with it. I've seen some strange behavior in email assets before when changing the IDs of editable areas on a template-level for an editable area that already "exists" in the email (i.e. the module is on the canvas and you change the IDs on the template, then re-open the email). I've usually solved something like this by creating a new email once the template is in a finalized state and testing from there. If this is a test email you've been working with thru changes to the template, maybe try and spin up a new one using the approved template and see if that makes a difference? ... View more

Outlook modifies the way it handles HTML once it gets forwarded--basically, it will strip certain code that an email comes in and then tries to re-render it using the Microsoft Word engine. The correct answer 99% of the time is to go "welp, we tried" and not worry about it too much. In this case, though, I'm curious about the code you presented for a couple of reasons--one being wrapping the image in <p> tag (I'm guessing you have default p tags still on; you should probably turn them off) and the other being how retina/high-DPI images in general are used. If you have a 1200px image, you're likely intending for the image to render in a 600px wide area. The trick is to still lock your image to 600px in terms of width (and let height calculate automatically, if possible) and then the 2x resolution underneath it will be accurately picked up by high-DPI devices while still scaling normally for everyone else. I talk about this a bit in this blog article: https://www.demandlab.com/insights/blog/images-in-email-the-best-practices-guide/ ... View more

Try my code w/matchMedia, should do the trick. ... View more

Hey Pete, I'm not entirely clear from reading your question, so correct me if I'm wrong: you've had two staff members leave, and now need to prevent their details being populated into the body of emails and prevent sales alerts being sent to them. It's a bit unclear from your question, but I'm assuming you're using lead tokens (i.e., the token is structured as {{lead.Token Name}}, not {{my.Token Name}}). It'd be helpful if you could provide screenshots, but as a starting point, if you're using lead tokens then what you're doing is asking Marketo to pull the value of that field on the lead record - which means it's not the token that needs to change, but the values in the field that token references. How best to do this may depend on your set up - if you're connected to a CRM, whether you have assignment rules for these in Marketo or only CRM side, whether the CRM will allow you to overwrite this setting from Marketo or not, etc. I'd start by figuring out those points. ... View more

Okay. Thank you Sanford. I built the customer field and insert the token. Will test accordingly. ... View more