Using Marketo-hosted images and other files on secure (https) non-Marketo pages | Community
Skip to main content
A
Anonymous
June 30, 2015
Solved

Using Marketo-hosted images and other files on secure (https) non-Marketo pages

  • June 30, 2015
  • 3 replies
  • 2742 views

We are considering a transition from http to https during our site overhaul. Will we be able to use files and images hosted in Marketo on these non-Marketo pages? Can we wholesale convert all Marketo-hosted files to https, and make https the default for new files?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Grant_Booth

    Hi Gordon,

    Our professional services team can work with you to enable SSL on your landing pages, images, and files: just email services@marketo.com. There is a charge associated with this although I'm not certain how much. If you don't wish to change your files and pages in Marketo to https, you'll want to copy the files to be hosted as https in your own server. I don't believe there's a way to mass-download images and files, however.

    Grant

    3 replies

    Grant_Booth
    Grant_BoothAccepted solution
    Level 9
    June 30, 2015

    Hi Gordon,

    Our professional services team can work with you to enable SSL on your landing pages, images, and files: just email services@marketo.com. There is a charge associated with this although I'm not certain how much. If you don't wish to change your files and pages in Marketo to https, you'll want to copy the files to be hosted as https in your own server. I don't believe there's a way to mass-download images and files, however.

    Grant

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    June 30, 2015

    You'll need to ensure that Marketo has bound your SSL cert to your LP/asset domain before making this switch. Otherwise, leads will see mixed content warnings that are, at best, unprofessional -- and, at worst, break your layouts. A direct link to a non-https download will be okay, though (that's not mixed content, as you are replacing the document completely).

    Edward_Unthank_
    Edward_Unthank_
    Level 7
    July 1, 2015

    You can switch to https for Marketo-hosted landing pages, like Grant said.

    I did a professional services contract to do this back in March of this year and the cost was $1,200. If you're dependent upon Marketo for consulting throughout the process, this is a fine price. If you're largely technically independent and just hand off the certificates and private keys to Marketo professional services, some might consider this very expensive for very few hours of work. But there's no way around it, because engineering needs to be involved no matter what.

    Getting the certificate set up is not difficult, same process as if you were going to do so without Marketo at all.

    The largest chunk of time investment in making this happen is switching all existing references from "" to ""—all images, JS, CSS, and other external references called within a secure landing page need to switch these over or you'll have trouble with compatibility. If you've had Marketo for only a few months, not a big deal. If you have lots of landing pages and references and assets, this can be a huge and tedious to-do list. It's also one of those things where if you aren't proactive, you won't get automated emails telling you something is wrong, you'll just have prospects who have a mediocre or undesirable experience and you won't hear about it. You'll have to do an internal audit of all your internal assets and get a list of all changes that need to happen, then switch them over.

    (Or, if you were writing code with "//" instead of "" or "", you'll have an easier time with this!)

    Cheers,

    Edward Unthank | Founder, Etumos

      Steve_O_Neil
      Steve_O_Neil
      Level 2
      August 6, 2015

      Hi Edward,

      Just working through the switch from http to https external asset links now.

      We have a large number of external assets using http.

      In your opinion would we be better to remove the protocol entirely or change to https?

      All the best,Steve

      Terms & ConditionsAccessibility statement

      Loading footer...