Identifying Landing Page Domains in Your Instance
As of August 2019, Secured Domains will be included as a base offering for all subscriptions, to ensure our customers are set up for digital security best practices when it comes to their marketing efforts. The base offering will secure your first Landing Page domain and first Tracking Link domain - additional domains may be purchased a la carte.
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.
Adding Additional Secured Domains to Your Marketo Subscription
If you need to secure more than the 1 Landing Page domain and 1 Tracking Link domain included in the base Secured Domains package, contact your Marketo Customer Success Manager to add additional domains a la carte to ensure you're covered. This should be discussed/audited at each renewal to ensure you're only paying for what you use.
The Secured Domains for Landing Pages Process
If HTTPS in NOT currently enabled in your instance, the process to secure your pages includes steps that must be completed on your end before we can provision and enable HTTPS. On our side, we’ll provision your Marketo domains on Cloudflare servers and install the necessary SSL certificates to create secure server end points to serve your landing pages over HTTPS.
A summary of the steps linked above are listed below: First, you’ll need to review, update and reapprove your landing pages:
Unapprove and re-approve all landing pages. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for unapprove and re-approve via the “Landing Page Actions” menu.
If you use Marketo Forms 1.0 on a non-Marketo webpage, you will need to update the post URL to HTTPS (Forms 2.0 does not need to be updated).
If you do a server-side post to a Marketo Form and use your CNAME as the Post URL, you also need to change that to HTTPS. Please note that server-side form posts are not supported and you should make a Marketo form submission in the background instead.
If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning.
If you use a Marketo Form on a non-Marketo page, you will need to update the follow-up URL to HTTPS if you’ve explicitly referenced a HTTP page.
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!
OTHER HELPFUL FAQs
What exactly does Secured Domains include or cover?
As of August 2019, all NEW customer subscriptions will include 1 unit of Secured Domains for Landing Pages & Tracking Links - existing customers will have the opportunity to update to the new pricing and packaging at renewal, and secure additional domains a la carte. The base offering will secure 1 Landing Page domain and 1 Tracking Link domain per instance. This covers provisioning each domain behind our security net (WAF/CDN/DDoS protection), and the SSL certificate.
Do I need to provide a TLS/SSL Certificate?
No. Secured Domains includes the required SSL certificates, and shifts the responsibility of managing ALL aspects of procuring and renewing the certificate to Marketo. Since the certificates also auto-renew annually, there is no need to continually provide us a new bundle/key every year. You will be updated to the new Secured Domains managed solution at either your next SSL certificate renewal, or Marketo renewal, whichever comes first.
What Certificate Authority issues the certificate(s) for the Marketo’s Secured Domains for Landing Pages product?
The certificates are authored by DigiCert.
What type of certificate is provided?
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.
Will my domains be on a shared SSL certificate with other companies?
No. Each of your domains will get its OWN certificate. That means you will not be on a shared certificate with other companies.
What Marketo configuration is required to complete the Landing Page SSL Setup?
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
How do I see the Landing Page domains in my instance?
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:
If I am using Domain Aliases in my Marketo subscription, do I have to secure each of these?
Securing your Marketo landing pages requires you to secure all domains used in your instance, including your Domain Aliases.
Are Domain Aliases for different countries counted separately?
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).
Can I choose which domains to secure?
No. Technically, we provision and secure domains in an all-or-nothing fashion by domain type (Landing Page or Tracking Link). This means whatever is configured in your instance will be provisioned, and you will be charged accordingly for all domains secured; if you have unused domains, please ensure you delete them so you're only charged for what you use.
What counts as a 'unique' domain? (How is this product charged?)
Reference the screenshot above that denotes CNAME + domain = full domain. For example, your top-level domain is company.com domains, and your subdomains include go.company.com (your tracking link), info.company.com & help.company.com (two landing pages). Commercially, this would count as 3 total domains (1 TL + 2 LP domains).
If I have a CAA record, can it affect my certificate issuance?
Yes. CAA records must be configured to allow DigiCert issuance, or we will not be able to issue a certificate for your domain. Your IT team MUST whitelist DigiCert in your DNS before we can successfully complete provisioning. Further information: https://www.digicert.com/dns-caa-rr-check.htm
Can I provide my own SSL certificate(s) to secure my domains?
On a pre-approved exception-basis ONLY. To avoid unnecessary cost, please do NOT renew your own SSL certificate until you have spoken to Support or your CSM and received an exception.
A major time- & stress-saving benefit of Secured Domains is that Marketo fully manages and auto-renews your SSL certificates each year. While we temporarily accepted 3rd party certificates for an interim period of almost two years, we will no longer be accepting customer-provided certificates unless you have a business/industry requirement (e.g. an EV certificate).
IMPORTANT: Another reason to use the certificates included with Secured Domains - Apple (Safari browser) announced in Feb. 2020 it will no longer accept SSL certificates valid for greater than 13 months. We expect Chrome and Firefox to follow suit. This means customer-provided certificates must be manually renewed and sent to Marketo each year - an unnecessary cost, risk, and hassle. If you do qualify for an exception, you will be 100% responsible for renewing your own certificate AND sending us the bundle/key well in advance of it's expiration date (we recommend AT LEAST 10 business days) to ensure it doesn't expire - expired certificate Support cases will only be categorized as P3 priority. Please ensure they are valid for only one year to comply with browser policies.
We require an Extended Validation (EV) certificate. Can Secured Domains accommodate this?
Serving Extended Validation (EV) certificates is an example of a business requirement where you WILL need to procure the EV certificate/private key and provide this to Marketo. Secured Domains must be added to your subscription to host any SSL certificate as we now provision all Marketo domains behind Cloudflare protections. The SSL certificate included with Secured Domains is not an EV certificate, and is therefore absolutely an allowed exception.
Will URLs to the existing non-secure (HTTP) Marketo Landing Pages continue to work?
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.
Does securing my Marketo landing pages also secure my corporate website?
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.
If I don’t use Marketo Landing Pages, do I need Secured Domains?
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.
Ultimately, Secured Domains is required EXCEPT if you:
Do NOT use Marketo landing pages (including unsubscribe page)
DO NOT use view as webpage
DO NOT use forward to a friend
DO NOT store anything in images and files
DO NOT load embedded forms using their landing page domain
Can I add additional Domains to my instance and secure these too?
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. Additional domains are charged a la carte, cost is dependent on the number of domains you are adding.
If I previously secured my Marketo Landing Pages with the SSL for Landing Pages Service, do I need to switch to Secured Domains for Landing Pages?
Yes. We have discontinued the one-time fee "SSL for Landing Pages" product 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.
Do I need to secure my tracking links as well?
You should, per best practices. This is why we've included 1 tracking link domain as a base offering for all Marketo subscriptions. Links formatted as HTTPS will also aid in deliverability as more email clients are starting to 'dock' emails with unsecured links. If your domain enforces a strict HSTS policy on all subdomains you will NEED to secure them for the redirect to your landing page to work properly. For more information on HSTS and Marketo subdomains, please see the following documentation SSL: The HSTS policy and your Marketo subdomains
Is this article helpful ?
Previously, customers could choose whether they wanted to secure their pages and tracking links via SSL. The responsibility of procuring, maintaining, renewing, and securely sending the certificates to Marketo lie entirely with the customer – Marketo just hosted them. In 2017, Chrome and Firefox announced they would begin marking any unsecured pages with clear ‘NOT SECURE’ warnings in their 2018 releases to encourage the use of SSL, and even distrusted certificates from certain providers. This essentially designated the certificate as a foundational security necessity to prevent customers fleeing from unsecured sites.
This change reinforced the increasing need for companies to protect their data and mitigate against online security threats. Recent studies have shown that ~45% of organizations are targets of Distributed Denial of Service (DDoS) attacks, typically lasting a few hours, and potentially costing companies not only lost revenue, but also customer data and overall trust. 
Simply put, an SSL certificate just isn't enough anymore, which is why Marketo updated how we manage SSL certificates and the overall security of our customers' landing pages with the introduction of Secured Domains, a comprehensive managed service, in early 2018.
How is Secured Domains different than an SSL certificate?
In contrast to our previous solution, Secured Domains is less focused on the SSL certificate itself, and rather the security and performance benefits gained from our partnership with CloudFlare, an industry leader in secure solutions. Secured Domains not only includes the necessary SSL certificates, but, more importantly, provides robust security protection thanks to the investment made to secure our servers, which host Marketo landing pages, behind CloudFlare’s trusted security infrastructure.
With CloudFlare’s enterprise-grade tools securing our servers, we protect against security vulnerabilities and attacks on your Marketo pages.
Managed Web Application Firewall (WAF): keeps your pages secure by filtering and deflecting malicious attacks
DDoS Protection: keeps your pages live by absorbing attacks and preventing the pages (and Marketo's infrastructure) from crashing
Content Delivery Network (CDN): a load balancer to distribute page views based on geolocation, which allows landing pages to load more quickly
Secured Domains also shifts the ownership of the SSL certificates onto Marketo, which eliminates the hassle of having to coordinate the procurement/management/renewal by Marketing & IT teams. Best of all, because our certificates automatically renew each year, Marketers no longer need to worry about landing pages crashing due to expired certificates. For more information, please see our Technical FAQ: Secured Domains for Landing Pages.
How do I learn more about Secured Domains?
If you’re an existing customer, please contact your Marketo Customer Success Manager to discuss. If you are unsure how to get in touch with your Customer Success Manager, please contact CustomerCare@marketo.com .
If you’re considering Marketo for your marketing automation solution and would like more information on Secured Domains and how it can improve your site security and performance, please contact GRP-Marketo-Sales@adobe.com.
Due to the security and risk mitigation enhancements we've made to protect Marketo servers, all SSL certificates are now uploaded to CloudFlare. Marketo customers will be required to use the SSL certificates (authored by DigiCert) included with the Secured Domains offering unless an EV certificate is currently used or required by industry regulations (i.e. Banking/Healthcare/Government). As of September 2019, Secured Domains will be automatically included as a base solution in all Marketo subscriptions come renewal.
 Tim Matthews, Imperva, DDoS Impact Survey Reveals the Actual Cost of DDoS Attacks, 12 Nov. 2014
Issue Description In Notifications, you may encounter a Web Services Error message that contains details as below along with the Error Code and Count (i.e. number of times the error occurred). For example:
The Web Services encountered the following error.
Error Code Count
Issue Resolution More information about the Web Services Error Codes are documented here:
It is recommended to consult with the owner of any custom Admin -> Launchpoint services configured (typically IT, your API developer, or a third party service provider) to review the API calls being made to Marketo.
The owner of the custom integration should already be logging any error codes requiring review, or ignoring those errors that are temporary and can be automatically retried.
If further assistance is needed, create a support ticket and provide details of the Request and Response of the API call containing the error code. Similar to how the example API Requests and Responses are documented here: http://developers.marketo.com/rest-api/lead-database/#describe
Who This Solution Applies To Customers using API integrations.
Is this article helpful ?
Issue Description What BCC options are there for email sends?
Issue Resolution Marketo support can enable BCC on request. If an email address is to be BCC'd on a batch email send, they'll get 1 BCC for every 1 email Marketo sends. (10k email sends = 10k BCC emails). This can be useful for archiving and compliance purposes, but should not be used for simple campaign confirmation. If you just want to make sure the email went out as scheduled, the easiest way is to create yourself as record in the database, and include yourself in the batch send.
NOTE: Dedicated email address setup for the BCC email traffic must be able to handle high volumes of email. Discuss with your IT Team or email service provider to verify their Email Server can handle the estimated volume of incoming email.
If the Email Server is not well equipped this feature can cause your Email Server to backlog, become unavailable temporarily, or reject the BCC emails.
Is this article helpful ?
System Uptime and Reliability
Email Deliverability Score
ReturnPath Sender Score
0 to 100
ReturnPath Sender Score
0 to 100
How does this impact Marketo?
How does Munchkin operate?
On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser. All subsequent web activity on that browser is recorded against this anonymous record. In order to be associated with a known record in Marketo, one of the following methods should be used:
The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link.
The person may fill out a Marketo Form.
REST Associate Lead call must be sent.
Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.
How is Marketo planning to address ITP concerns?
Do I need to do anything to take advantage of these updates?
In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following:
A Landing Page CNAME
Secured Landing Pages (i.e. HTTPS)
For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track
For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com
What happens if I do nothing?
Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.
When will the solution be launched?
These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020.
Google Chrome Update (Feb. 2020):
Google recently announced that the Chrome browser will block all third-party cookies within two years; however, s ince Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions:
Updates made to an embedded Form are not immediately reflected on the web after the Form is approved.
To improve page load times, Marketo Forms are served from a cache. It may take up to 4 minutes for newly approved changes to forms to display on the web. This only applies to embedded forms on non-Marketo pages; forms on Marketo Landing Pages will continue to update immediately after approval.
To preview changes immediately, you can use the Preview functionality. https://docs.marketo.com/display/public/DOCS/Preview+a+Form
In order to manager authorized support contacts you must be set up as a Support Administrator on your Support Entitlement with Marketo.
1. Log into the Marketo Community and click Support.
2. Click Manage Authorized Contacts to approve or disapprove authorized contacts.
3. The top of the Manage Authorized Contacts page provides information about contact totals. If the Allow Marketo Support to Add Authorized Contacts is checked, it means that the customer has granted permission to Marketo Support to add authorized contacts.
4. To authorize a contact, check the Is Authorized checkbox next to the contact's name. In order to appear on the list of available contacts, the user must have clicked Community (while logged into Marketo) at least once.
5. To un-authorize a contact, click the Authorized checkbox next to a contact name to clear the checkmark. Click OK in the popup. If a contact on the list is no longer an employee at your company or that person does not need to manage cases, you can remove a contact from the listing entirely, by deslecting the Authorized box, and selecting the No Longer checkbox. Click OK in the popup.
Great! You can now manage Authorized Contacts for your account.
NOTE: Securing any Marketo domains requires the "Secured Domains" product first be added to your subscription. A base offering will be automatically added to all customer subscriptions at next renewal, but to make any SSL or domain changes, or purchase coverage for additional domains, please contact your Marketo Customer Success Manager (CSM) for more information.
Marketo’s Secured Domains for Landing Pages secures any and all landing page domains defined in your instance to be served via HTTPS. Serving your pages securely assures that you’re providing critical security and data integrity for both your pages and your visitors’ personal information.
Below you’ll find the 5-step process to secure your Marketo landing pages with Marketo’s Secure Domains for Landing Pages. Please note, there is an automated support case that gets created on your behalf when the purchase of Secured Domains for Landing Pages is completed.
Step 1. Verify your Landing Page Domain, CNAMEs and any Domain Aliases are setup
Before you can secure your landing page domains and any domain aliases (subdomains), you must first set these up in Marketo. If you are a new Marketo customer working through your implementation, please work with your implementation consultant on the landing page domain(s) setup and timing to cut over to HTTPS. If you’re securing your landing page domains for a previously implemented instance, please verify that your domains and domain aliases (subdomains) are set up in your instance. Below are some links to help:
Edit Landing Page Settings – to set you Landing Page Domain
Customize Your Landing Page URLs with a CNAME – to understand and set up CNAMEs (subdomains)
Add Additional Landing Page CNAMEs – to set up multiple CNAMEs in your instance (subdomains)
Be sure your redirect rules and domain aliases are updated to use https:// instead of http:// .
Step 2. Edit and update the HTML code of your existing landing page templates to HTTPS
Next, you'll need to review and update your Marketo landing pages to ready them to be served securely. Please complete the following two actions in order before moving on to Step 3:
If you purchased Marketo before January 2016, please un-approve and immediately re-approve all landing pages last updated before January 2016. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for un-approve/re-approve via the “Landing Page Actions” menu. We recommend completing this step in batches of a maximum of 10-20 pages at a time. Instructions for doing so can be found here: Approve Multiple Landing Pages at Once - Marketo Docs - Product Documentation.
You can see the "Last Updated" timestamp in the Landing Pages section of Design Studio.
Open the HTML code for each landing page template. C hange all URLs listed in the HTML currently formatted as "http ://" to instead read "https://"
TIP: Ctrl+F "http" to automatically highlight all URLs that must be updated:
Simply add "s" after each http reference until ALL have been updated to https
Missing even one URL's http reference will cause the "Mixed Content" browser warning: vs.
SAVE THE PAGE AS A DRAFT
Do not approve the draft. You will approve the drafts after Support activates SSL in Step 4.
NOTE: Once you secure your Marketo landing pages to be served over HTTPS, you should not link to HTTP (unsecured) assets or pages from your secured landing pages.
For more detailed guidance, please see our recorded instructions below
Video Link : 2237
Step 3. Respond to the TSE via the existing support case
The TSE will then begin the process on our end to generate certificates to cover all the domains and subdomains configured in your instance.
Once notified, please allow 3 business days for Marketo to create your secure server endpoint. Marketo's Support team will contact you when this is complete. We appreciate your patience during this 3-day setup process.
Step 4. Marketo Support Will Activate Your Secured Domains for Landing Pages
Once we've generated and issued the necessary SSL certificates for your domains, we'll notify you that it is done and activate SSL for your Landing Pages.
NOTE: There will be a brief "cut-over" period between when HTTPS is enabled by the TSE and when you are able to complete Step 5 below. During this time, landing pages may show up to customers with a mixed-content warning; however, all links and emails will continue to work properly without disruption, and your customers are not at any risk. Be ready to complete Step 5 quickly once instructed to minimize this period.
Step 5. Re-approve your landing pages and verify success
Once your Support Engineer has activated the switch to HTTPS for your instance, y ou must immediately take the following actions:
Approve all draft pages that you edited from Step 2 above. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages to approve via the “Landing Page Actions” menu.
If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning.
Verify your pages are loading and rendering as expected. Contact Marketo Support with any issues you may encounter.
Questions & More Information
For more information, including and FAQ, please see the Marketo Secured Domains for Landing Pages Overview & FAQ.
Is this article helpful ?
NEW WebAPI (REST) integration now available for Microsoft Dynamics
NOTE: This is currently ONLY available for Dynamics online & on-prem versions 9.x using ADFS 2016 and above. Pre-ADFS 2016 (on-prem v8.x and older with ADFS versions earlier than 2016) authentication is done using client credentials only – clientid/secret is not possible. Since o ur existing WebAPI integration mandates a clientid and secret, it is only supported for Dynamics 365 Online and Dynamics on-prem instances v9.x in conjunction with ADFS 2016 and above.
If you do not use these supported Dynamics/ADFS configurations, the native SOAP integration will continue to work for the foreseeable future; however, we are no longer developing SOAP enhancements.
As part of the continued investment in our Microsoft partnership, the native Marketo Engage / Dynamics SOAP integration is being upgraded to a more robust and stable connection using WebAPI (REST) that will better support future upgrades and releases.
The Marketo Engage and Microsoft Dynamics teams are encouraging all customers to proactively adopt WebAPI in preparation for the forthcoming scenario where SOAP API is no longer supported. The upgrade should only take 5-10 minutes by your Dynamics admin and present no loss of data with your existing sync. This is a critical step to ensure your WebAPI connector activation can be completed.
We encourage all Dynamics customers with the supported version/ADFS configurations to upgrade before May 2020, our target time frame to begin releasing new features via WebAPI.
The attached Customer Setup document only applies to Dynamics Online (365) and on-prem v9.x with ADFS 2016 and above. If you have questions or need help with your specific configuration, please open a support case for assistance.
As of November 30, 2019, all the familiar content on the Marketo Engage Status Page has been migrated and is now available on the Adobe Status Page . This move allows us to leverage Adobe’s more robust and efficient monitoring platform for not only the standard alerts and scheduled maintenance, but also hotly-requested functionality including pod-specific status updates and proactive notifications!
October 31, 2019: The functionality to subscribe to notifications at the solution and pod level released on the Adobe Status Page. Customers may begin exploring and subscribing to various notifications.
November 30, 2019: Marketo Status Page was deprecated and a redirect to Adobe Status Page was put in place. Moving forward, please refer to this article for up-to-date System Uptime and Deliverability Scores.
January 8, 2020: To better prepare you for upcoming changes and scheduled maintenance, we have increased the previous two-day ‘lead time’ of these notifications based on impact. Service Maintenance 30-day lead notifications are now available on Web/Mobile/Tablet surfaces and via Email notifications.
Opt-In to Adobe Status Page Subscriptions
1. Navigate to https://status.adobe.com
2. Click Manage Subscriptions
3. Sign in using your Adobe credentials or click Create an Account to log in
4. Select Experience Cloud drop-down
5. Select Adobe Marketo Engage then click Continue
Prior to selecting a regional location(s), you will want to identify what data center and pod/server your instance is located in. You can deduce this information by looking at the URL of your instance. The CNAME = the pod or server your instance is on.
The example above indicates that this instance is in our Ashburn data center on pod A. This user would select the regional location Marketo Ashburn and then pod ABA as shown below.
The abbreviations for all our data centers are as follows.
ab = Ashburn
sj = San Jose
sn = Sydney
lon = London
Note: This method can also be used to identify what Real Time Personalization (RTP) pod/server your instance is in.
6. Select regional location(s) and event type(s)
7. Select the environment(s) or product(s) you would like to subscribe to and click Continue
8. Review your subscription preferences and click Done
How do I see previous issues or maintenance?
1. Go to: https://status.adobe.com/
2. Click "Experience Cloud"
3. Click "Adobe Marketo Engage"
4. Select the appropriate Service
5. Click the dots on the date line to view the details of what occurred on that day
What do the colors mean on the Status page?
1. Blue is for maintenance
2. Red is for a major issue
3. Orange is for a minor issue
Full Details of all Marketo Support Offerings:
Support Levels Offered
Service Level Response Targets
http://nation.marketo.com : Online Support Portal for Case management and Knowledgebase search
firstname.lastname@example.org : Email to Case Submission
email@example.com : Contact Support management regarding Support services
firstname.lastname@example.org : Questions regarding Support or Community access
Regional Contact Information
Hours: M-F, 6am to 6pm Pacific
Toll Free US: +1.877.270.6586
New Year's Eve
New Year's Day
Thanksgiving Day and the Day After
Europe, Middle East, & Africa:
Hours: M-F, 8am to 5pm GMT
Europe: +353 (0)1 242 3030
UK: 0800 151 3030
English, French, German, Portuguese
New Year's Day
St. Stephen's Day
Hours: M-F, 9am to 6pm Aus AET
ANZ: +61 2 8310 7646
New Year's Day ANZAC Day
Christmas Day Good Friday
Easter Monday Boxing Day
Hours: M-F, 9am to 5:30pm JST
JP: +81 3 6478 6080
New Year's Holiday Marine Day
Coming of Age Day Respect for Senior Citizens Day
National Founding Day National Holiday
Spring Equinox Day Autumnal Equinox Day
Day of Showa Sports Day
Constitution Memorial Day Culture Day
Green Day Labor Thanksgiving Day
Children's Day Emperor's Birthday
Substitute Public Holiday Year End
After-hours Support for Production Down Issues:
Online: Enter a Support Portal Case with Priority=P1
Phone: Call Support Line and follow the P1 prompts
Initial Response SLT
We ask that you use the following priority definitions when setting your case priority:
Production down: Production system, application or critical feature / function is down
Production impaired: A major feature or function is not working correctly and is blocking full use of the Marketo system, but existing production campaigns are working correctly and other features are operational.
Minor issue: A minor issue is impacting usability of the system, but a workaround is available and major features/functions are working correctly.
Issue Description Unable to find the approved email in the dropdown in one program when the email is the child of a different Email Program. Issue Resolution You will not be able to find the approved email in the dropdown if the email is being used in an A/B test. When adding an A/B test, the selected email will no longer be available for use in any other program. In order to send this email out separately, you will need to clone it and then you will be able to use the clone in a smart campaign in order to send it out.
Issue Description You have a smart campaign setup and the flowstep called “Change score” activity is not logged or missing in the activity log. Issue Resolution If the records who qualify for the flowstep already have the same value which you have specific in the flow step, the activity will not be logged. The activities will not be logged because there is no change being made by the campaign.
Issue Description Where to find details for the support contract for your Marketo account. Issue Resolution General details on Marketo's support offerings are found here - About Support. For specific details on your account's support level, please contact your CSM. If you do not have the contact info for your CSM, email MarketoCares@marketo.com for assistance.
Issue Description The support admin for your Marketo instance has moved on to another position or is no longer with the company and you need to update the Support Admin information. Issue Resolution Please contact the CSM for your account to have the Support Admin information updated. If you do not have the contact information for your CSM, please email MarketoCares@marketo.com for assistance.
Issue Description When trying to import a list of people into Marketo via a list import, their names are being left blank despite being listed clearly in your CSV. Example CSV headers: NAME Email John Smith JS@email.com Smith John SJ@email.com Greg Jones GJ@email.com Issue Resolution Full Name is a system managed field that is blocked from being updated by list imports. You will want to split the one column of Name, into two columns of First Name and Last Name. This document from excel shows how to split the one Name cell into two different cells. https://support.office.com/en-us/article/Split-a-cell-f1804d0c-e180-4ed0-a2ae-973a0b7c6a23
Issue Description Unable to attach internal support articles from Sharepoint to case. Issue Resolution Attach this article instead and replace this article's title and URL with the title and URL of the internal Sharepoint article Who This Solution Applies To Marketo Technical Support Engineers
Issue Description Upon reviewing the activity log of a record you've noticed their activity log seems to be missing data. Usually the activity type is a "Change Data Value" and the details show "Missing history details". If you double click on the activity nothing happens, there is no Activity Details popup window. Issue Resolution This message appears in the activity log when the characters in a field exceed the maximum number of characters allowed in that field. Basically you've hit the character limit for the field. The character limit is 60,500 character. The resolution is to reduce the number of characters in the field. Also evaluate if you need all the information in that field and optimize so that the character limit is not met.
Issue Description When trying to add a user to Marketo we get 'User creation errors - "This userid is in use. Choose another email" ' due to the fact that email addresses need to be unique across ALL Marketo instances. Issue Resolution One creative way to get around this is to at a '+tag" to the email address befor the '@' sign. For example if we get the error adding a user record for 'Name@domain.com' we can simply use the '+' sigh and a tag of your choosing (in this case '1') and use the email address of 'Nameemail@example.com'. The system is happy as this is a unique email address yet all emails will still be delivered to the appropriate inbox for 'Name@Domain.com'