By default, Marketo serves landing pages by HTTP, and historically we’ve given our customers the choice of whether or not to secure their Marketo landing pages to HTTPS. With the recent changes to Chrome browser, there’s increasing interest in securing Marketo landing pages to avoid the “Not Secure” warning visitors will see when entering data on HTTP pages. Marketo’s Secured Domains for Landing Pages product secures any and all landing page domains defined in your instance so they will be served via HTTPS. Contact your Marketo Customer Success Manager to purchase Secured Domains for Landing Pages for your subscription.
Note: This new product replaces our previous SSL for Landing Pages service. Marketo will begin selling Secured Domains for Landing Pages on December 1, 2017.
Marketo’s Secured Domains for Landing Pages product secures up to 4 domains (per unit purchased) to enable secured (HTTPS) landing pages for your instance.
If you’re a new Marketo customer with a new subscription, one of the steps in setting up your instance is to set your CNAMES, landing pages domain name, and any domain aliases. For more information see, Customizing Your Landing Pages URL with a CNAME and Adding Additional Landing Page CNAMEs. Once this is done, you’ll be ready to count the unique domains (as described below) and initiate the Secured Domains for Landing Pages process (if purchased or included in your instance).
Have you had your Marketo subscription for a while and want to know how many landing page domains you’ve got setup in your instance? If you’re a Marketo Admin, you can see your landing pages domain name and domain aliases by clicking on Landing Pages in the Integration section of the Admin console:
On the Landing Pages tab, you’ll see your landing pages Domain Name. The first part of the URL (info.) is your CNAME and the second part (gladiatorapps.com) is the domain. Here’s an overview of the pieces that make up a full domain name:
Next, you’ll also need to check the Rules tab and look for Domain Aliases. In the example below, there are two domain aliases. One has the same domain as the landing pages domain (gladiator.com) and the other has a different domain (theappninjas.com).
For the instance in the example above, it has been set up with two unique domains (gladiatorapps.com and theappninjas.com). It’s important to note that when it comes to securing your Marketo landing pages, the Secured Domains for Landing Pages process will secure all of the domains in your instance. It’s an all-or-nothing action, meaning you cannot chose which domains to secure for HTTPS and which to leave HTTP. And don’t worry – we’ll count these up for you so we can scope your subscription correctly.
Contact your Marketo Customer Success Manager to add Secured Domains for Landing Pages to your instance.
If Marketo Secured Domains for Landing Pages has been added or is a part of your subscription, the process to secure your pages includes steps that must be completed on Marketo’s side as well as steps that you’ll need to complete in your instance prior to us enabling HTTPS.
On our side, we’ll install the necessary security certificates to create secure server end point to serve your landing pages over HTTPS.
On your side, to ready your instance for the conversion to HTTPS, you’ll need to review, update and reapprove your landing pages:
Once you’ve completed the steps above, it’s time to coordinate the cutover to HTTPS with Marketo. You’ll need let Marketo Support know that you’re ready to initiate the cutover process. To help ensure a smooth transition, we’ll work with you to plan a time when you have few or no upcoming batch campaigns running, and also a time when your team is available, if needed, to make a few updates in your Marketo instance.
RECOMMENDATION: After the cutover, you may notice that images are not displayed in the Marketo email editor or preview mode. Rest assured your emails will send correctly and the images will render for recipients. To see the images in Marketo, you must adjust the image URLs from HTTP to HTTPS in the editor. Again, whether you take this step or not, the images will render properly for your email recipients. In the example below, you would adjust the HTTP to HTTPS.
That’s it! Once our team enables Secured Landing Pages for your instance, your landing pages will be served via HTTPS. Of course, it’s a good idea to do some validation of your pages after the cutover to be sure your pages are loading correctly, images are loading, and that you didn’t miss any hard-coded HTTP links. Moving your pages to HTTPS, you can rest assured that you’re providing critical security and data integrity for both your pages and your visitors’ personal information. Good job, you!
Marketo’s new Secured Domains for Landing Pages product available in December 2017, manages all aspects of procuring, managing and renewing a certificate and key for you. You do not have to provide a certificate. If you purchased a SSL for Landing Pages service prior to this date and provided a certificate, you will be updated to the new process at your next certificate renewal.
The certificates are authored by Digicert.
We produce a pack of two certificates; The primary certificate uses a P-256 key, is SHA-2/ECDSA signed, and will be presented to browsers that support elliptic curve cryptography (ECC). The secondary or fallback certificate uses an RSA 2048-bit key, is SHA-2/RSA signed, and will be presented to browsers that do not support ECC.
As part of our Secured Domains for Landing Pages each of your domains will get its own certificate. That means you will not be on a shared certificate with other companies.
Up to 40 subdomains per unique top-level domain may be covered. As an example, with your company.com domains, the subdomains go.company.com, info.company.com, help.company.com etc. may be covered. Please keep in mind that company.com, company.com.uk, company.com.ca are separate top-level domains.
Securing your domains is all-or-nothing, meaning the process automatically secures all domains/subdomains you've set up in your instance.
Yes, CAA records must be configured to allow Digicert issuance, or your certificate will not be able to issue. Further information: https://www.digicert.com/dns-caa-rr-check.htm
We do not recommend providing your own certificates.
Serving Extended Validation (EV) certificates requires you to procure the EV certificate/private key and provide this to Marketo. The standard Secured Domains for Landing Pages does not include EV certificates.
One or more CNAMEs for the Marketo Landing Pages must be configured in the Admin section of the application as described here: Setup Steps - Marketo Docs - Product Docs
Each Secured Domains for Landing Pages product secures up to 4 domains. You’ll need to purchase multiple quantities to cover all the unique domains in your instance. Contact your Marketo Customer Success Manager for scoping/pricing.
Securing your Marketo landing pages requires you to secure all domains used in your instance including your Domain Aliases.
Marketo Admins can see your landing pages domain name and all domain aliases by clicking on Landing Pages in the Integration section of the Admin console. On the Landing Pages tab, you will see your full Landing Page Domain Name. On the Rules tab, you will find all Domain Aliases set up for your instance. For the Secured Domains for Landing Pages you will need to count the number of domains used in your instance. When counting domains, please provide the number of unique domains – only the orange part below:
When counting domains, you might have: info.mydomain.com, info.mydomain.au, info.mydomain.de. In this case mydomain.com, mydomain.au and mydomain.de are all counted as separate domains (in this example there are 3 unique domains that must be secured).
Your existing HTTP URLs will continue to work and will automatically be redirected to the secure (HTTPS) pages. There are only few situations where you may have to manually update the URL, specifically when you include a Marketo landing page on a secure website using an iframe. In this case, you will need to load the secure version of the landing page, otherwise the end user will get a security warning.
No. Marketo Secured Domains for Landing Pages only affects the landing pages served by Marketo. It does not affect any pages on your corporate (non-Marketo) website.
You may if you are embedding Marketo Forms on secured non-Marketo webpages. The default form code snippet that Marketo provides uses //app-aba.marketo.com which is a Marketo domain that can be served securely on a HTTPs parent page (the // indicates the request will use whatever protocol the parent uses). With this, your Marketo form will take on the security level of the page it’s embedded on regardless of whether you’re using our Secured Domains for Landing Pages product. However, if you prefer not to have any reference to “marketo” on your corporate website, you may choose to change this code snippet from //app-aba.marketo.com to //<MY_LP_CNAME> to serve the form. In this case, you would need the Secured Domains for Landing Pages product since the LP CNAME will need a security certificate associated with it to serve securely.
Once you’ve secured your landing page domains with the Secured Domains for Landing Pages process, you will need to contact Marketo when adding additional domains/domain aliases. Please contact your Marketo Customer Success Manager. There may be an additional charge depending on the number of domains you are adding.
We have discontinued the SSL for Landing Pages service and process, so you will need to switch. Your Customer Success Manager will work with you to add Secured Domains for Landing Pages at your next SSL certificate renewal or at your subscription renewal, whichever comes first.
If your domain enforces a strict HSTS policy on all subdomains you will need to also purchase our Secured Domains for Tracking Links service. Please contact your Marketo Customer Success Manager to purchase this add-on. For my information on HSTS and Marketo subdomains, please see the following documentation SSL: The HSTS Policy and Your Marketo Subdomains