KnowledgeBaseBackup

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. Change 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         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, you 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 ? YesNo

What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry.  Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released.   How does this impact Marketo? As a result of these changes to cookie policy, 7 days after their initial tracked visit to your domain, the Munchkin cookies of visitors using Safari (or future affected browser versions) created with the existing versions of Munchkin JavaScript will expire, and on subsequent visits they will be tracked as a new visitor.   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? Marketo will implement a new web service to allow Munchkin cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript.   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, since 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: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-of-3rd-party-cookies-bbb7bb257fdb

Question: I am trying to add the Person Notes field to a Marketo form but the field does not seem to be available to drag into the form editor. Answer: Remember, all fields will pre-populate with data from the CRM system. Person Notes is a dangerous field to use in a form because sales people will often put text in there that they never intend the lead to see.  We removed it form the form editor for this reason. You can, if needed, add another field in your CRM and it will be available to use in Forms.   Is this article helpful ? YesNo  

  Marketo Support's Mission is: "To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success."   Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any questions or concerns. TSEs are responsible for troubleshoot issues within your Marketo instance. Common areas within a Marketo instances which TSEs will assist with are:   My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community   Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code:    Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API   Our technical support engineers are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.   Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.   Response Time:   Our Technical Support Engineers are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services.  We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to SLA's.

Issue Description Updates made to an embedded Form are not immediately reflected on the web after the Form is approved.   Issue Resolution 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

No, unfortunately we are unable to tell you what the spam trap address is. We don’t even know it ourselves! Spam trap addresses are proprietary to the blacklists that own them. Anti-spam professionals use spam trap addresses to track unsolicited emails. If a spam trap is known by the offending sender, the sender could simply remove the spam trap address from their lists and never actually address the data problem that caused that spam trap address to be included in their lists to begin with. Instead of asking what the spam trap address is, try to identify the source of the trap address and eliminate bad data sources from your mailing lists. You should be able to identify the email campaign that caused the blacklist issue, so you should start with those lists. To narrow it down and identify the problematic data source, you should consider the following: Have you recently added any new leads or new lead sources? What is the source of these leads? Any purchased or appended email addresses should be removed, because these data sources are often the source of newly introduced spamtraps. In addition, using purchased or appended email addresses for mailing is a violation of Marketo’s Email Use and Anti-Spam Policy. Have you added any older leads that have not been mailed to recently? Some email providers will turn an email address into a spam trap after a year of inactivity. If you have a list of addresses that has not been mailed to in a year or more, this list should be removed. Does your system use any custom fields to indicate customer status, event attendance, recent contact with your sales team, or other forms of engagement? If so, take advantage of this and isolate the inactive or non-responsive segments of your database using all of the activity data you have available. Is there anything about this specific mailing that makes it different compared to your previous email campaigns? Did you send any other mail on the same day? If so, you should compare the recipient lists. Think you have narrowed in on the problem? Check out our guide to blacklist remediation to find out what to do with that bad list and complete the remediation program.   Additional Resources: What is a spamtrap, or spam trap, and why does it matter? What is a blacklist? How does Marketo respond to blacklisting and spam notifications? Top blacklists - What you need to know Blacklist Remediation Successful Reconfirmation Blacklist Deep Dive Blacklist FAQ   Is this article helpful ? YesNo  

Issue Description Visit Web Page activity is tracked and showing up for one subdomain on your site, example.marketo.co, on a record but it is not recording activities for a different subdomain, pages.marketo.co.   Issue Resolution The reason that this behavior is taking place is because the domain that is being utilized has a two letter top level domain "example.co". For domains that end with a two letter suffix, “example.co”, the Munchkin script is setting the tracking cookie to the third domain level by default. This is to take into account two letter country codes such as “.jp”, “.us”, “.cn”, and “.uk”. This means that when someone visits “info.example.co”, the Munchkin script will assign a new cookie to “info.example.co” instead of “example.co”. When someone visits or is referred to a different subdomain, such as "pages.example.co” it will create a new cookie for this domain “pages.example.co”.   To prevent this from taking place you will need to add the Munchkin Initialization Parameter setting the “domainLevel” to “2”. This will cause the cookie to be set to the second domain level “example.co” when visiting either the Marketo or non-Marketo hosted landing pages. Details about the Munchkin Initialization Parameters can be found in this Developers Doc:   https://developers.marketo.com/javascript-api/lead-tracking/configuration/   Since the Marketo hosted landing pages will, by default, use the same 3 third level domain behavior, you will need to disable tracking at your template level using the steps at the end of this article:   https://docs.marketo.com/display/public/DOCS/Create+a+Free-form+Landing+Page+Template   This will disable the default tracking that all landing pages get in Marketo. Then, similar to external landing pages, your team will need to add the Munchkin tracking code to your Marketo templates, where you would have control to set the domain level to 2 (instead of 3). Once this has been updated on both the external landing pages and Marketo hosted landing pages, the tracking cookies will be set at the second domain level and work across the various sub-domains.   Who This Solution Applies To Customers with two letter domains   Is this article helpful ? YesNo