Knowledgebase

Sort by:
!!EASTER EGG!! The ball with the Marketo logo in the upper-left corner of the screen is your Superball.  Here's a quick trick to make it bounce like it did when you first got into your Marketo instance: Hold down Ctrl (Command for Macs) + Shift, then hit the 's' key. Happy bouncing!    
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 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 After updating the Unsubscribe HTML and Text in Admin>Email, newly added tokens may not render as expected. Solution To resolve the behavior, you'll need to do the following after updating the Unsubscribe settings in Admin: 1) Navigate to the various emails within the instance and un-approve them. May require removing references to the email first. 2) Re-approve the emails. 3) Add back any references to the email asset.   Why this needs to be done: When the email asset is approved it goes through a validation process for all the tokens that are used and this includes the global unsubscribe settings. When editing in Admin >Email > Unsubscribe the validity of tokens is not checked upon saving those changes. If a invalid token is added, something like {{lead.nonExistingField}}, no errors are thrown and it'll return that string value. The verification is done when the "approve" email functionality is used on email assets. This steps retrieves valid tokens list used in the email and adds/updates them in a backend table for use/reference. The update to the global unsubscribe settings doesn't cause the stored information to reference the newly changed settings in Admin. To cause that validation process to go through successfully and update the information on the back end, you'll need to un-approve and re-approve the various emails within the instance to use the new global settings.
View full article
Issue You put a variable inside an email token and when the email was sent, the variable rendered as text rather than as a link: Example: ${queryParameters} Should expand to: {{my.CertainURLHREF}}?utm_source=${utm-source}&utm_content=${utm-content}&utm_medium=${utm-medium}&utm_campaign=${utm-campaign}&ajs_uid={{lead.Email Address}}&ajs_event=Email%20Clicked With the various tokens populated Instead it expands to this: https://app.fakewebsite.biz/profile/55555555?utm_source=$%7Butm-source%7D&utm_content=$%7Butm-content%7D&utm_medium=$%7Butm-medium%7D&utm_campaign=$%7Butm-campaign%7D&ajs_uid=adam.tow+test@voxmedia.com&ajs_event=Email%20Clicked   Solution Essentially, email template variables are used at design time to make building out an email easier. Tokens are used at send time to make data variable per program without having to edit the asset or lead. Putting email template variables inside tokens won't work for this reason. It is just how the current design works and you will not be able to put email template tokens inside my tokens or lead tokens. Unwrapping variables before you put them within the token will allow them to function properly. This removes the simplicity of the variable, but retains the functionality.
View full article
Issue You see a popup that says 'Limited Access' when you attempt to edit or delete an asset in the Design Studio, even though you should have the required permissions/privileges for the workspace it is located in.   Solution When an asset is shared from one workspace to another, only the original copy can be edited or otherwise modified, even if you have permissions for every workspace it appears in. If you attempt to alter the asset inside one of the folders it has been shared to, you will see a popup informing you that you don't have sufficient privileges to do so. To edit the asset, make sure you are working with the original copy of that asset, located within the workspace where it was first created. Who This Solution Applies To People using Workspaces
View full article
Issue Email Script Token contains a reference to an email address token but it is not rendering the email address when the email is sent.       Solution The email address token is not inserted correctly and was manually typed. In order for the email address to render, it must be selected from the Lead object field option on the right-column of the token editor and inserted (see: https://docs.marketo.com/download/attachments/1900577/five.png?version=1&modificationDate=1491232683000&api=v2 )     "If you are typing in tokens free-form ensure to check/activate all corresponding tokens in the tree or they will be treated as plain text and won't work." https://docs.marketo.com/display/public/DOCS/Create+an+Email+Script+Token
View full article
Issue Issue Description Get the error 'Cannot get email content- Customer does not belong to any POD' when the URL from the 'view as webpage' link is forwarded for review     Solution Issue Resolution This is expected behavior as of the 2019Q1 release. After clicking on the view as webpage link, the mkt_tok value will be removed. Attempts at sharing the URL after this point will fail. The mkt_tok value should not be shared. It uniquely identifies the recipient.  This is a security enhancement.  The preferred method is to use Send Sample to send the email to teammates, or forward the email.
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 Issue Description When adding a superscript for items like © or ® , the email editor displays the superscript correctly but when the email is received, a space is added between the descriptive word and the superscript.     Solution Issue Resolution Open the email editor and edit the HTML by clicking on the "<html>" icon. Change your <div> tags to <p> tags in the html code. Send yourself another sample email to confirm the space is removed. Be sure to review these changes with your developer to ensure no unintended changes occur due to this change.
View full article
Issue Issue Description After submitting a form on a landing page, the Thank-you page fails to load, or it loads the wrong page.   Solution Issue Resolution The Thank-you page used by the form can be defined in two places, at the Form level and at the Landing Page level. If these two are in conflict, the setting on the Landing Page wins.  To troubleshoot this issue, compare the two Thank-you options and make sure the Landing Page is either set to the correct page, or that it allows the Thank-you to be form-defined.  
View full article
Issue Issue Description When opening the downloaded HTML of a new email created from a template in Marketo, the email appears to be broken in colour and format. The preview of the downloaded HTML of the email does not have the same styling of colour and format compared to the preview in Marketo.   Solution Issue Resolution This only occurs when the email has not yet been approved, and only affects what the email looks like when it is downloaded. The color and format of the downloaded email appears different to the email previewed in Marketo is because in the downloaded HTML, variables (e.g. ${variableName} ) containing the styling are not rendered. Once the email is approved, when the HTML of the email is downloaded, the variables containing the styling will be rendered.
View full article
Issue Issue Description Getting 'Communication Failure' error popup repeatedly when doing normal operations within the application.   Solution Issue Resolution Disable all browser extensions especially any dealing with ad blockers as they seem to be the primary cause of this issue.  
View full article
Issue Issue Description Google is changing production of their robots.txt parser to an open source format and removing support for some widely used but unsupported  code:   In the interest of maintaining a healthy ecosystem and preparing for potential future open source releases, we're retiring all code that handles unsupported and unpublished rules (such as noindex) on September 1, 2019. For those of you who relied on the noindex indexing directive in the robots.txt file, which controls crawling, there are a number of alternative options:   -Link to Blog Post from Google:  https://webmasters.googleblog.com/2019/07/a-note-on-unsupported-rules-in-robotstxt.html?m=1     Solution Issue Resolution This should not affect any Marketo Landing pages if the Noindex, NoFollow code has been put in the Robots meta tags as per the documentation:  https://developers.marketo.com/blog/block-crawling-and-search-indexing-of-a-marketo-landing-page/ This will only affect your landing pages if NoIndex, NoFollow are in the robots.txt file and not in the header meta tags.
View full article
Issue Sometimes, you may receive an auto response from an email that has been sent through a batch campaign. The auto response email will not show the lead's email address instead it does contain the HTML of the email along with the Marketo decorated link. Is there a way to decipher this to determine which lead record this corresponds to?   Solution You could try opening a new browser window and either clear your cookies first or use the browser's private browsing feature (makes a cookie sandbox) so you don't confuse Marketo and tie that person's lead to you by accident. Anyways, in your cookie-free browser, click the link and then go to a form that Marketo prefills for you and you may see the email address that was originally targeted.    
View full article
Issue You have been utilizing the default tracking links to send Emails to leads in Marketo and decide to change the default tracking link to your own branding tracking. When you do so, this breaks the links in emails you have already sent. Solution The branding tracking link should be one of the first steps that the customer(s) need to do when they obtain their instances. If you decided to change the default tracking link to a branded tracking link after utilizing them in emails, you should be prepared in advance that any email sent prior to the change will generate the 404 Error. We recommend not sending any emails within a week or two of the change so that an email sent on Monday is then broken on Tuesday.  
View full article
Issue You have two SFDC picklist fields mapped to one Marketo field but it isn't showing all picklist values for both SFDC fields. Solution When two SFDC picklist fields are mapped to one field in Marketo, the only values that will show in Marketo will be the values that exist in both picklists.  Review the picklist values in Salesforce and add any missing values to the picklists so that they match exactly.
View full article
Issue Sometimes, you may notice that editing the text version also affects the HTML version of the email. Is there a way to edit the text version without the same edits occurring to the HTML version? Solution Changes to TEXT never apply to the HTML version. It's likely because when you "save" an element, it will add the "root block element" to the HTML side if one isn't present. So, your HTML is probably not handling it correctly. You can change the "root block element" to none in the Admin > Email > Editor Settings dialog. https://docs.marketo.com/display/public/DOCS/Using+the+Rich+Text+Editor        
View full article
Issue How to move Design Studio assets when migrating to a new instance. Solution Clone the assets into a Program, then import the Program into the new instance. For Forms, make sure the fields also exist in the destination instance. Same for Lead tokens in Emails/LPs. Dynamic Content & snippets are not supported in Program Import.
View full article
Issue You are trying to edit an existing email template, and it has the status of "Approved with Draft" However the draft is not showing up in menu tree and when you try to edit and save, you get the error "Not Allowed – Template already has a draft." Solution Issue Resolution Refresh the browser or check is the draft is opened in another window. Try logging out and logging back in Try using a different browser to check it further Check if there is a template with the same name that exists elsewhere (Design Studio) Rename the template and check if that is working If the issue persists, please reach out to Marketo Support for further assistance    
View full article