Knowledgebase

Sort by:
Issue Description You noticed that there are form actions missing from the  Form Actions  dropdown. The following options should be missing: Approve Draft (If form is in a draft state) Preview Clone Form Embed Code Preview Draft (if form is in a draft state) An example of this dropdown may appear as: Issue Resolution This is due to the form having been created using an outdated version of the Marketo Form Editor. You may want to consider re-creating this form with the current Marketo Form Editor, and archiving the outdated form. Keep in mind that if you archive the form, you will want to reference the new form in smart lists and smart campaigns.
View full article
Issue Description Hidden form is not populating even though Autofill is set and default values are assigned. Issue Resolution One reason for this behavior is because the hidden form field is set to required. This is not supported for hidden fields and can only happen if the field is set to required before the field type is set to hidden. To fix this, we need to change the field type to something else, uncheck the required box, and set it back to hidden. Then approve the form and landing page and you should be good to go.
View full article
Issue Description 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. Issue Resolution The reason you are seeing this error is because the token mentioned in the error does not exist in the asset. To fix this error, you will want to remove this token from the asset. This can be done by choosing to edit the asset and searching the code of the asset for the token in question, and finally removing this token from the HTML of the email.  If you do not find it in the HTML, check the text-only version as well. This commonly happens when the asset is not in the same program as a my.token referenced in the email. 
View full article
Issue Description When filling out a form in preview, an external Thank You Page is not working. Marketo is not redirecting to the Thank You Page.  Issue Resolution This is expected. A workaround is to create a test Marketo Landing Page and place the form for testing. 
View full article
Issue Description When attempting to approve an email or send a sample email you get the following error message: Validation Error approving [email name] — An error occurred when processing the email Rendered_Email_Velocity_Error_Area_?! </div> <p> String index out of range: xxx”   Issue Resolution This typically happens when you have a Velocity script token in the text version of your email. Velocity script tokens are not supported in email text versions. You’ll need to manually replace this line with the appropriate link or use a my token. Instructions how to edit the text version and use my tokens can be found here - http://docs.marketo.com/display/public/DOCS/Edit+the+Text+Version+of+an+Email http://docs.marketo.com/display/public/DOCS/Using+URLs+in+My+Tokens Who This Solution Applies To Customers using Velocity script tokens 
View full article
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 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 Description The picklist options are updated in Salefsorce for a field that is syncing with Marketo and is used within a Marketo Form, but the form does not automatically reflect these updates. Issue Resolution When field picklist options are updated in Salesforce, the Marketo forms using this field are put in a Draft. This will allow the form draft to be reviewed to ensure the picklist values on the form match what's in Salesforce before being reapproved.   Who This Solution Applies To Clients syncing with Salesforce
View full article
Issue Description You enabled a field for email CC and it is working for some email CC recipients, but some records on the CC are not receiving the email. Issue Resolution If any of the CC email addresses are known leads in your Marketo database and marked as unsubscribed they will not receive the email, even if the email is marked as operational.
View full article
Issue Description When selecting an image to display on a landing page, the image shows as a featureless grey box. There are also spaces in the image's file name. Issue Resolution Ensure that there are no spaces in the image's file name in Marketo. If there are, remove the spaces from the file name and re-upload. 
View full article
Issue Description The user role has all the permissions to Design Studio, but whenever trying to preview an email, a limited access message is displayed: "You do not have sufficient privileges to perform this action" Issue Resolution The user role must have permission to 'Access Database'. The full access to Database is not needed, just the main access by selecting 'Access Database' and unchecking everything else underneath The reason for this permission is the fact that when previewing emails, you can select to preview an email as a specific lead. In order for this to happen, users will need access to leads. 
View full article
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. 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 reason why it appears that the color and format is 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 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 Description Velocity scripted tokens are not displaying the default value in the asset if the information required for the token is not in the database.o Issue Resolution Email Script tokens are not designed to work with the   {{my.token:default=Some Value}}   syntax, which is for simple tokens.   Rather, you must output the default value within the code (using   #if/#else ,   $display.alt   or any other conditions) then include just   {{my.token}}   in the email. Examples can be found here:  https://developers.marketo.com/email-scripting/
View full article
Issue Description After submitting a form on a landing page, the Thank-you page fails to load, or it loads the wrong page. 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 Description Default value in pick-list does not show when using a Choice to display different pick-list options with Visibility Rules Issue Resolution Make sure you have included the default values for the Choice within the Visibility Rules as well as selected in the pick-list values for the field.
View full article
Issue Description My Tokens not appearing in an email as an option to insert Issue Resolution It is highly likely that the email is not in the program or campaign folder containing the My Tokens. Examples:  The email could be located in Design Studio The email is within a program but the token is not defined in the program it is in or the campaign folder it is in In all cases, the email must be within the program or campaign folder that contains the My Tokens.
View full article
Issue Description Landing Page is not selectable as a Web Page constraint value for a Fills Out Form trigger Issue Resolution Check if Landing Page is Approved Check if Landing Page is within the same workspace as the Smart Campaign with the Fills Out Form trigger [Note: this condition is only applicable if there are workspaces within the instance] Check if Landing Page is NOT within an archived folder Check if Landing Page has a form associated with it. If not, then it will not appear as a selectable option as Web Page constraint. While it is possible that a form can be inserted directly into the HTML of the landing page template, the landing page will not be associated with the form in this way. For a Landing Page to be a selectable option as a Web Page constraint it must be associated with a form by inserting the form to the landing page via the UI as illustrated in our docs below: http://docs.marketo.com/display/public/DOCS/Add+a+New+Form+to+a+Free-Form+Landing+Page http://docs.marketo.com/display/public/DOCS/Add+a+Form+to+a+Guided+Landing+Page
View full article
Issue Description An email with inserted bold/italic font in email subject line is not approving, with an error of Cannot Update Stale Object, or does approve but the special font text disappears upon approval.  Issue Resolution The subject line in an email is intended to be plain text.  Some have found success inserting basic symbols, or even emoji with specific encoding, though the rendering of these characters is dependent on the receiving server. Related Document.
View full article
Issue Description Possible disadvantages of maintaining Engagement/Nurture Program emails in Design Studio. Issue Resolution Housing all of your emails for email nurture content in Design Studio could cause the following issues:  1. Reporting: Reports can specify Emails in Design Studio, however they will show results for any send of the individual email and will not be constricted to the program they were sent from. 2. Asset re-use in Engagement Programs: When using an engagement program, an asset is scanned for its ID. If that asset has been previously sent to a record via any other send, the engagement program will skip that send for that record. This could become a problem when reusing email assets housed in design studio in different engagement programs.  3. My Tokens: my.tokens will not properly render as they are based on a program folder. The assets that reference them need to be in the folder as well. In my testing, assets in design studio do not have a frame of reference for mytokens. Emails will not populate mytokens if they are housed outside of the program that owns the tokens.  With all of this noted, o recommendation is to utilize detailed templates in design studio and continue to clone your engagement programs and alter them as necessary. Although this presents some busy work in the short term, it pays off dividends in the long term when it comes to reporting, the use of my.tokens, and guaranteeing that records are sent the assets you are specifying in your programs. 
View full article
Issue Description Some tokens in "Show Custom HTML Form for Known People" under Form settings don't populate. Issue Resolution There are four default tokens that Marketo puts in by default: {{lead.FirstName}} {{lead.LastName}} {{form.Button:default=Download}} {{form.NotYou:default=Not you?} Only the four tokens above can be used. Any other token will not work here. Who This Solution Applies To
View full article