Knowledgebase

Sort by:
Issue How to use tokens to personalize some of the information displayed in a Marketo form.     Solution It is possible to use Marketo tokens in the following form elements: Field Labels - Edit a Field Label in a Form Hint Text - Add Hint Text to a Form Field Tooltip Instructions - Add Tooltip Instructions to a Form Field Fieldset Text - Add a FieldSet to a Form Rich Text boxes - Add Rich Text to a Form
View full article
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 technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include:   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 TSEs 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 TSEs 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 Service Level Targets.
View full article
Issue What is the difference between mktNoTrack and  mktNoTok? Solution Adding the mktNoTrack class to an email link tells Marketo not to add a tracking link to the URL. Without the tracking link, the recipient is not redirected through the tracking server before going to the target URL. Use this when you specifically don't want to track Clicked Link in Email events in the Marketo database. Adding the mktNoTok class to an email link tells Marketo not to add the _mkt_tok parameter to the target link.  Used when the target link does not behave properly, for example, a mailto: link that should not have extraneous URL info or a static file that won't download when there are query parameters. The click activity will still be tracked, but the associated lead info will not be carried onto the page for use in functions such as form prefill.
View full article
Issue You want to use a Marketo Form in an email. Solution Forms cannot be used in email. Forms rely on using scripts to be able to pull and send data, but email clients will usually scrub or prevent the execution of scripting languages such as Javascript for security reasons. Note: Including scripts in your email can increase the chances of your email being classified as spam as well.    
View full article
Issue After setting up visibility rules on a form, you are not seeing the dynamic values for the field when you are testing the form. Solution The most likely reason that the dynamic values are not displaying is because of a discrepancy between the visibility rules and the field values. The value for the visibility rule must match the field values.   Example: A common example of this is Country/State dynamic visibility. Based on the Country selected, the State field will show with dynamic values. So say that on the form, there are 50 values for the State field and there are also specific values under the visibility rules that are associated with the Country selection. It is likely that the values in the visibility rules do not match up with these 50 field values. If you select US and the dynamic values are the full State names, such as California, but the value in the State field is CA, the visibility rules will be attempting to display a value that does not exist.   The solution is to either change the visibility rules' values, or change the field values, so that the values match.    
View full article
Issue Marketo forms that are embedded on external web pages see loading errors. Examples of this could be that the fields load with delay, or once submitted the form lags before moving to a follow up page.     Solution Two things to check: Is there custom CSS in your form? Is the embed code on your form customized?   Isolate the cause You can isolate the root of the lag by testing your form on a Marketo Landing Page   1. Locate the embedded form with in your instance 2. Build a landing page to test the form: Landing Page with a Form 3. Place your form on the new testing landing page, approve the page and close it. 4. Load the Landing Page using the URL   If the form loads with no delay, the issue lies with the embed code used to push the form onto the external page. Please work with your custom developer to find a resolution.   If the form is loading with a delay (and there is custom CSS):   1. Clone your form 2. Remove any custom CSS from with in the form 3. Build a landing page to test the form: Landing Page with a Form 4. Place your form on the new testing landing page, approve the page and close it. 5. Load the Landing Page using the URL   If you are not seeing any loading errors, the issue lies with in the custom CSS of your form. Please work with your custom coder to improve the loading speed of your form. Note: Occasionally, incorporating the form embed script into containers (custom coding) and utilizing custom JavaScript may lead to delays in form functionality. In such instances, it is recommended to collaborate with your developer to identify a solution, as Marketo Support does not troubleshoot issues specifically related to custom coding. If you are still seeing lag errors on your form loading on the Marketo Page, please submit a ticket with support@marketo.com    
View full article
Issue After adding an IFrame to an email in the Marketo email editor, the IFrame seems to disappear when you view the email in an email client (such as Outlook, Apple Mail, or Gmail).     Solution The reason why you can see the IFrame in Marketo but not in your email client is because not all email clients support IFrames. If yours does not support them, the IFrame will be blocked and will not appear in the email. You can try viewing the email in another email client to see the IFrame.
View full article
To enhance the stability of Marketo’s email assembly infrastructure, we are disabling some Velocity Script functionality on June 14, 2019. What change is being made? The following Velocity Tools will permanently be disabled for use in email script, on June 14, 2019. My Tokens: classTool contextTool resourceTool Some common use examples of these tools include: $class. getClass() $context. When are these changes taking effect? These changes will take effect in the June 2019 Release on June 14, 2019. How did it work before? The way Velocity Tools are used in your email scripts is highly dependent on the structure of your code and varies on a case-by-case basis. To identify how you are currently utilizing Velocity Tools in your email design, please consult directly with your developer. Documentation on each tool can be found on Apache’s website at the links below: classTool : https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ClassTool.html contextTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ContextTool.html resourceTool: https://velocity.apache.org/tools/devel/apidocs/org/apache/velocity/tools/generic/ResourceTool.html Why is this changing? We regularly review our infrastructure to ensure it meets the highest standards for stability and security. During a recent review, we identified that a small subset of Velocity Tools could potentially impact the health of our message assembly servers, and as a result, we made the decision to disable these permanently. What do I need to do? If you are currently using Velocity Tools in your email scripting, you will need to review and update your script to use alternate methods before June 14, 2019. Documentation on supported Velocity Scripting can be found on our Developers’ site at http://developers.marketo.com/email-scripting/. Any email script tokens still referencing Velocity Tools after the June 14, 2019 deadline could fail to compile, resulting in emails not rendering as expected or complete send failure. We have identified impacted customers using these Velocity Tools and will alert them individually via Marketo Notifications. Considering the customized nature of Velocity Scripting, Marketo Support is not able to assist with the authoring or troubleshooting of custom code. Please reach out to your developer for assistance. If you no longer have access to a technical resource, you may also contact your CSM to coordinate a scoping call with our Professional Services team.
View full article
Issue When approving emails, the system shows the following error: "Note: detected the following lines in text version that are longer than 1000 characters: Line 6 and they are not fixed. The email is now approved".     Solution This error is an indicator that there is a large line of text in the text-only version of the email that is over 1000 characters. This occurs when there are long links in the email which will not publish correctly in the text version of it. But still the email will be approved and can be sent. Check for excessively long links in the text version of the email and simplify them if possible. You can test it by sending a text version of the email to yourself, or by checking the Text Only version in the Email Editor.    
View full article
Issue Description When editing a template and you validate the HTML, you receive an error of 'Error: Nested Editable Element: ...' with the id of the element following causing you to not be able to approve the template. Issue Resolution This is due to having an element with a 'mkto...' class nested inside another element with a 'mkto...' class. Below is an example:  <div class="mktEditable">      <div class="mktEditable"></div> </div> You will need to remove the 'mkto...' class reference from one of the elements to be able to pass validation and approve the draft as in the corrected example below:  <div class="mktEditable">      <div class="newClassName"></div> </div>
View full article
Issue The URL for the landing page shows as "https" even though you do not have SSL set up on your Marketo instance, causing the browser to display a "Not Secure" warning.   Solution This can happen if the primary domain and DNS are SSL secure, but Marketo is not.  For instance, if your primary domain is "https://www.mycompany.com" (SSL secure) then the DNS, which is also SSL secure, will push down the "https" transfer protocol down to all the CNAMEs on that DNS.  This will force the Marketo landing page using the CNAME to use "https" in the URL, even though it is not secure. There are two ways to resolve this: Work with your IT department to see if there is a non-SSL option for your DNS Purchase SSL for your Marketo instance so that both your primary domain and your Marketo pages are SSL secure. If you would like to add SSL to your Marketo instance, please contact your Account Manager to see about adding that to your subscription.     
View full article
Issue Using a browser with JavaScript disabled causes display and validation problems with Marketo forms.     Solution When JavaScript is disabled in a browser, it can cause a couple of different behaviors. For embedded forms, the form will not load on the page because it is loaded by JavaScript. For non-embedded forms on a Marketo landing page, the form will load but it will be a bare bones version of the form that does not validate field input, because validation is handled by JavaScript. If you want to display a message to users with JavaScript disabled, you can use the “noscript” tag to display a message that prompts users to enable it in order to render the page correctly: https://www.w3schools.com/tags/tag_noscript.asp Here’s an example using that with an embedded form: <script src="//app-sjst.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1001"></form> <script>MktoForms2.loadForm("//app-sjst.marketo.com", "507-ILX-247", 1001);</script> <noscript>You have JavaScript disabled! Please enable JavaScript for the best experience on this site.</noscript>   For a Marketo landing page, I added an HTML Element with just the last line from the example above: <noscript>You have JavaScript disabled! Please enable JavaScript for the best experience on this site.</noscript>   Alternatively, you can use a redirect solution like this, which will send users with JavaScript disabled to another page: <html> <head> <noscript> <meta http-equiv="refresh" content="0; URL=http://www.marketo.com"> </noscript> </head> <body> <p>Fancy redirect page if JavaScript is not detected.</p> </body> </html>  
View full article
Issue Links sent to a customer using AppleMail are not rendering properly. Solution This issue is cause when there is no protocol assigned to a link so AppleMail appends applewebdata:// to the beginning of the url instead of HTTP:// or HTTPS:// The work-around for this is to include the protocol in the link. If there's no protocol (e.g. http://) then the rendering engine will insert applewebdata:// as the protocol for any links.     
View full article
Issue Issue Description "${button-link}" appears on the Email Link Performance report in place of the URL the buttons point to.     Solution Issue Resolution To stop this "${button-link}" from appearing on the reports, edit the text version of the emails to replace the "${button-link}" with the URL the button points to. This occurs because the text version of the email didn't get edited to provide a valid button link. The "${button-link}" value is part of HTML templates and if the setting 'Copy HTML to Text version of email' is checked then those values get copied across. From there, if the text version doesn't get edited or reviewed after that copy over happens, tracked links for "http://${button-link}?mkt_tok=..." will be sent out for those leads that get the text version of the email in place of the URL the button points to. The next question after hearing this solution is often, "If this is just for the text version, who is reading the text version of emails?", and the answer is that it's probably automated link scanners or security software visiting the link and triggering the click to show on reports. 
View full article
Issue You're receiving an error that states 'Not Allowed - Error approving <asset-name> - {{token-name}} : Token key not found' when trying to approve an email asset. Solution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}' Check that the field name of the token does not have any incorrect spelling (e.g. Email Address) If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.
View full article
Issue Issue Description How to enable multiple selections in a picklist/select field in a Marketo form.     Solution Issue Resolution In the Field Properties, choose Field Type "Select" Edit Values to include your desired picklist options in the field Check the box for "Multiple Selections" This is a article attached image
View full article
Issue An embedded Marketo form on your company website showed up in the past, but is now not showing on the page.     Solution Embedded forms may not show if you have mixed content on your website (meaning that your website is using HTTPS, but the embedded form from Marketo is using HTTP). To resolve this, you need to ensure the content from Marketo is also using a secure connection. You can purchase an SSL certificate to use for your Marketo forms by contacting your Customer Success Manager/Sales Account Manager.    
View full article
Issue Clicking "Automatically copy over from HTML" or "Copy from HTML" in the Email Editor fails to copy the contents over to the Text Only version of the email. Solution This can occur if there are no editable sections in the email asset. Only in editable sections of an email will be copied over to the Text version of an email. Here is additional documentation: https://experienceleague.adobe.com/docs/marketo/using/product-docs/email-marketing/general/creating-an-email/edit-the-text-version-of-an-email.html?lang=en A quick workaround would be to manually copy and paste the content you wish in the Text Version, and in the future build/use templates to make emails with editable sections.    
View full article
Issue You would like an links in an email to be tracked, but need to eliminate the tracking URL parameter on the tracked links. Solution In the Email Editor, you can uncheck "include mkt_tok" in the Edit Link box. This is a article attached image Adding a class "mktNoTok" to any Anchor Tag will allow you to keep the Link Tracking, but disable the Tracking Token Parameter from the URL. You may also edit the Head of the email HTML to make large sections with this class.    
View full article
Issue You created a picklist field in SFDC and want to know if that field will sync down to Marketo with the field type of picklist.     Solution Marketo has a picklist option in form fields, but not in Lead Database fields. When you sync a field from SFDC that has the type of picklist, this field will show in Marketo with a type of String. However, when you create a form, the field type for your field will show as "select," which is a picklist.  
View full article