SanfordWhiteman

I like your parlor trick, man. To get even more tricky:H1[class^="04"].PM {/* rules for 4:00 - 4:59pm */}H1[class^="03"].AM {/* rules for 3:00 - 3:59am */}

We have a Salesforce trigger that creates a new "Marketo Activity" custom object with the owner and such fixed up (and then we delete the original generic Activitiy). Something to think about.

@Ian using the html element to increase specificity is fine, but just a type selector has very weak specificity and there's no guarantee it won't be overriden by something you guys add in the Marketo CSS. The (I hope correct) assumption that you won't use !important still makes that the safest bet I...

What @Justin said, plus realize that if somebody clicks a link, that becomes a "Synthetic Open" even if they never downloaded images, or if they just saw the text-only version of the email. In other words, you can't use Opens to gauge the useability of images in your emails (both tracking images an...

In this instance I'd look closer at your DNS. What exactly has your IT department done to verify that your domain is OK? You could have one nameserver that's giving wrong results, for example. The more nameservers you have, the harder it is to find when just one is acting up. One broken NS will ...

@Edward you can fix that webfont issue by sending Access-Control-Allow-Origin: * with WOFF2 resposnes. Your server is sending ACAO on WOFF responses, but you have WOFF2 listed first, which Chome understands, so Chrome tries for WOFF2 but sees an illegal CORS request.Awesome looking work, by the way!

Well, don't really need to send an email. Have the new website check if they have a Munchkin tracking cookie. If they don't, redirect them back to the old site with a special query param that means "please send old cookie value and return to new website." Old site sees param, reads cookie (if ther...

@Devan remember your selectivity rules. The built-in CSS already has .mktoForm .mktoCheckboxList > label which is more selective than .mktoCheckboxList > label. You either have to use the same selectivity (yours will win because of the cascade) or use !important.

Should be easy to do given the API. Though you should figure out if you mean load the next form vs. show the next form. If it were me I'd probably render both forms at start but only reveal (visibility/display) the second one later. Otherwise you end up putting the whole form.render() inside your...

Add to Calendar links (technically, links to ICS files) are indeed click-tracked: they become typical links http://branding.example.com/aaEE1100uu --> http://landing.example.com/blahblah.ics. So I don't know what would be causing them to not show in your instance.