As I noted in the old thread SSL for branding domain not landing page it isn't possible to run an all-HTTPS environment with Marketo tracking in the mix. This makes it impossible to comply with security and risk directives common to the financial industry.
For the moment we are planning to attack this by gatewaying mail through our own servers and rewriting the tracking links, as well as proxying the branding domain on our own boxes. But I think the time is fast approaching (not there yet, I admit) where not having native HTTPS support is going to inhibit security-centric people from using Marketo, or at least from using
native tracking (which is one of the main reasons to use the platform, of course).
I hadn't made this an Idea yet, so here it is!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.