Knowledgebase

Sort by:
Issue Clicking a tracked link in an email either leads to a 404 page or the fallback page. Environment Tracked links Tokens Specific Characters: "#", "$", unbalanced brackets "{" or "}" Solution Do not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well. For example: www.google.com/ebook-download.html?ebook={{lead.ebook}}# This will not work and will either direct to a 404 page or redirect to fallback page. When hovering over the link you will see that it is not a normal tokenized link, it will contain something along the lines of: $mktEncrypt.encrypt($mkturl2)/<random characters> Root Cause When using tokens in the url of a tracked link, the email is processed and the tokens are substituted and populated with the correct information. The engine that assembles this information have some characters reserved for use such as #.
View full article
Issue CORS Policy Error for form submission occurring intermittently   Solution   1) Confirm there is only one form embedded on the page.  2) Create a blank landing page on the same domain as the page with the issue 3) Embed your form using the exact code provided by Marketo 4) Confirm whether the error occurs on the blank page with the Market embedded code 5) If you are still experiencing CORS Errors after conducting this testing, then create a support ticket with the following details: -The form -The test landing page you used -The domain that you are experiencing issues with -Screenshots of the error received   Root Cause If you have customized the embedded code, Marketo Support is not able to troubleshoot custom code. Multiple embedded forms on a single page can cause the forms to not work incorrectly. Multiple forms embedded with different domains may require your IT team to make sure resources are requested correctly from one domain to another. Environment Marketo form embedded on a non-Marketo webpage  
View full article
Issue Updating an Email Template is creating a draft for existing emails without the desired changes     Solution When changes are made to an Email Template in the Design Studio that is already in use and those changes are approved, it will create a Draft for any existing Email that was created from that Template. If the draft is not reflecting changes you would like to see made, you may have included the changes within a mktEditable or Editable class <div> tag. The content within a mktEditable class element within an email template are ignored from any changes as they are considered to be "default content". Any content within these elements will not see any changes made to them based on changes to the template, and will only be seen when creating a new Email asset. You can update an editable section to remove it's editable status, however this will remove any changes to the content done in any email. You can see which elements can be classified as Editable here: https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax    
View full article
Issue A landing page is taking a significant time to load. Solution The load time of a landing page is generally due to resources that have a large file size or due to third-party scripts. This can be identified by using tools like https://tools.pingdom.com/ that breaks down the loading time of individual resources and scripts within a landing page. Another way to inspect the loading time of resources and scripts within a landing page is using the network feature of the developer tools in Google Chrome, Firefox, Safari or any other web browser: https://developers.google.com/web/tools/chrome-devtools/network-performance/reference https://developer.mozilla.org/en-US/docs/Tools/Network_Monitor https://developer.apple.com/safari/tools/    
View full article
Issue Description Link(s) placed into Email(s) by a Token is not tracked and does not show successful click activity in the lead/person record. Issue Resolution Sometimes there are situations in which URLs, and other content, are placed in emails by using {{tokens}}. When Marketo sends emails, you can think of building the email in 2 steps: Marketo searches the email code for "http" or "https" and wraps the tracking code around the URL Marketo inserts the values of {{tokens}} into the email. If the {{token}} value is http://www.domain.com , that would be expected to not track because of the above 2 steps. After the {{token}} value is inserted, Marketo does not go back to wrap tracking code around http/https. The {{token}} doesn't look like a URL when the system applies the tracking code because the tokens don't pull the values in until the next step after. The solution to tracking tokens is to place http:// or https:// on the outside of the token, like such: http:// {{token}} That way, when Marketo builds the email, in step #1, the system recognizes the http and knows it's a URL. Then the tracking is wrapped around the http and the {{token}} as well. Then in step #2, the {{token}} value is inserted into an already-wrapped link. A unique caveat to keep in mind is that if the {{token}} value contains http, but http is on the outside of the {{token}}. Let's say the URL you want to insert is http://www.domain.com . You have to move the http:// out in front of the {{token}}, but you don't want to also have it inside the {{token}} as well. If your link ends up being http://http://www.domain.com it will break. To get around this, you'll need to remember to take the http:// out of the {{token}} value. {{http://www.domain.com}} would instead be http://{{www.domain.com}}
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 "${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 Description Tracked links in emails resolve to "Your connection is not private", or other security warnings in the browser, when clicked. Issue Resolution The browser is expecting the branded link domain to be secured with a SSL certificate. Subscriptions without Secured Domains for Tracking Links: Please contact your Customer Success Manager to discuss purchasing a subscription to Secured Domains for Tracking Links. Subscriptions with Secured Domains for Tracking Links: Please contact Marketo Support to provision a SSL certificate onto your tracking link domain. More information can be found here https://nation.marketo.com/docs/DOC-6231-overview-faq-secured-domains-for-tracking-links
View full article
Setting an email to "operational" does the following No unsubscribe link automatically added Email will be sent to leads set to Unsubscribed Email will be sent to leads set to Marketing Suspended   Note - when sending an operational message, Unsubscribed and Marketing Suspended leads will still be included in the "blocked from email" count on the schedule tab of the campaign.   When is it OK to use the operational setting?   Sending marketing email to unsubscribed addresses is illegal. For this reason, you should be extremely careful to only use this setting in extremely limited circumstances. Using this setting incorrectly violates Marketo's Terms of Service, and most antispam laws. There may be legal consequences for using this setting incorrectly. Good uses of the operational setting fall into two categories: Transactional messages Relationship messages   What's a transactional message? A transactional message is part of a transaction that a lead has initiated and you are responding to. Here's some examples of transactional messages: Receipts for purchases Registration confirmations Download links in response to form fill-outs Requested assets (whitepapers, spec sheets, etc.)   What's a relationship message? A relationship message describes something that affects your business relationship with the lead. Here's some examples of relationship messages: Downtime notifications Changes to terms of service Recall notices End of service notifications   Operational messages should not contain any marketing content at all. In other words, do not use the operational setting to send a message that contains a receipt and a promotion, only a receipt.
View full article
Issue Best practices for avoiding corruption in cloned assets. Solution When cloning assets you should always clone from the original asset. Say that you have email A, and you clone that original email into version B, and then clone version B into C, and clone C into D, etc.  There is potential for asset corruption when clones are cloned repeatedly. It is best to clone the original rather than making clones of clones. When creating assets, whether they are individual assets like emails or complex assets like programs, set one as the master asset and clone all copies from the master.
View full article
With the evolving best practices and awareness around data privacy, Marketo will be upgrading how we handle form pre-fill. What change is being made? Starting April 24, 2019, Marketo will only pre-fill form fields if the URL used to navigate to the Marketo landing page contains a valid mkt_tok URL parameter value (which occurs when users click tracked links in Marketo emails). What that means is, any time a person is viewing a Marketo landing page with a form, the URL being used must contain the mkt_tok token in the query string, otherwise the form on that landing page will not be pre-filled. If the URL in the browser window does have a valid mkt_tok tracking token, then the form within the page will pre-fill as expected with data corresponding to the person record associated with that mkt_tok. Also note that if you are embedding Marketo Landing Pages within other web pages using an <iframe>, the mkt_tok would need to be passed from the parent page to the <iframe> URL if you intend for form prefill to work within the <iframe> ​How did it work before? Previously, Marketo landing pages would rely on Munchkin tracking cookies to identify known person records, and forms would pre-fill based on that cookie. Form pre-fill did not require being linked to a Marketo landing page from a tracked email link. Why is this changing? This upgrade is being made to provide a more consistent and more secure experience with Marketo’s forms. We have identified that, in the past, people have experienced scenarios where data pre-filled into a form didn’t always correspond with the actual person viewing the page. For example, people using a shared computer or those who may have been cookied incorrectly by clicking through a forwarded email, could end up viewing incorrect data associated with a different person. To provide a more consistent customer experience, and as a security enhancement, Marketo is upgrading the conditions under which the form pre-fill will display known customer information. In short, pre-fill will only work when users clickthrough links in Marketo emails, demonstrating that they have ownership of the email address associated with the known person record. Below is a list of different scenarios and how form pre-fill will work moving forward. Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature. Scenario Will the form pre-fill? Notes Clicking a tracked link in a Marketo email to a Marketo landing page with a form which has pre-fill enabled Yes The email link must have mkt_tok enabled. Links that are not tracked or that have mkt_tok disabled will not work. Navigating directly to a Marketo landing page with a form which has pre-fill enabled No A direct link to the landing page will not have the mkt_tok present in the HTTP request. Refreshing a Marketo landing page with a form which has pre-fill enabled No The mkt_tok is stripped from the URL after Marketo Landing Pages load so refreshing the page will not include the mkt_tok in the URL. As a result, pre-fill will not work. Clicking a link in a sample email to a Marketo landing page with a form which has pre-fill enabled No The sample email will not have a valid mkt_tok attached to the link and so will not pre-fill the form. If you wish to test form pre-fill you will need to use a real email from a Marketo campaign. Navigating to a non-Marketo page that includes an embedded Marketo form which has pre-fill enabled No This behavior does not change with the upgrade. Pre-fill has never been supported for Marketo forms that are embedded on non-Marketo pages. Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabled With custom implementation The form within the Marketo Landing Page that is being loaded in the <iframe> will pre-fill if the mkt_tok value from the original HTTP request is passed along to the <iframe> URL Visiting a Marketo page with a mkt_tok that is not associated with the same person record as an existing Marketo Munchkin cookie currently stored on the browser No This will prevent the wrong person’s information from being displayed in cases where a computer is shared, or an email with a mkt_tok tracked link is forwarded to another person that may already be cookied as a known person in your database. Copying a Marketo tracked link from an email and sharing/pasting it externally (email, blog, chat, social media post, etc.) that enables another individual to click the tracked link Yes The tracked link in a Marketo email will redirect to a URL with the mkt_tok included, so anyone clicking this link will reach a page and see pre-fill data associated with the known person record from the “to” line of the email.
View full article
Issue The format of the landing page is distorted in comparison to the version displayed in the landing page preview.  Environment SSL Certificates Landing Page Domain Landing Page format is different from preview Landing Page contain unsecure content Landing page template has http instead of https   Solution Ensure all the links used in HTML code used in the landing page template is referencing "HTTPS" and not "HTTP". You can follow the steps outlined in the document below on how to edit landing page template.  Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/edit-a-marketo-landing-page-template.html **NOTE: If the landing pages is approved, a draft version of the landing page is created for any landing pages which is using the landing page template. You can mass approve those landing pages via following steps outlined in the document below. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/approve-multiple-landing-pages-at-once.html?lang=en Root Cause Once you secure your Marketo landing pages to be served over "HTTPS", you should have not links referencing "HTTP" (unsecured) assets or pages. 
View full article
Issue Form in Design Studio will not convert the time format upon language selection. English form with date format dd/mm/yyyy Below is a form using settings with form language selecting German. The date format remains the same "dd/mm/yyyy" when the expected value should be "tt/mm/jjjj" as per language date format Environment Marketo forms and common web browsers such as Chrome, Opera, Firefox. Root Cause This behaviour is related to the browser language settings. It automatically translates the date in the format of the selected language in the browser. Example of the same form with different browser language selected, the date format is changed by the browser 
View full article
Issue LinkedIn leads generated through LinkedIn Lead Gen form does not populate Inferred State/City/Country values. Solution Use field mapping between Marketo and LinkedIn to make sure inferred State/City/Country fields are mapped to respective LinkedIn fields so that they are captured in Marketo. Root Cause The inferred State/City/Country is populated via the person tokens and that information is normally captured when a lead fills out a Marketo form. If instead, the form used is a LinkedIn form, then that information is not passed over to the Marketo lead fields. Environment Marketing Activities LinkedIn Lead Gen
View full article
Issue When creating a new Landing Page asset in Design Studio, an approved Landing Page template does not show up in the template drop-down list. Any attempt to clone an asset which uses this template throws error indicating it cannot be cloned. Solution In Design Studio, 1. Select the template in question on the left-hand side folder tree 2. On the right-hand side, mouse-over template name and click the pencil icon that appears on the right corner of template name 3. Change the template name to a temporary name 4. Click the pencil icon again and revert it back to the original name Root Cause This is due to corrupted template name which happens due to simultaneous edits or renaming of templates multiple times. Environment Landing Page Design Studio
View full article
Issue -Error editing image in email: “image URL does not exist” or “image URL cannot be found”   Solution Option 1 -Set up SSL for landing pages (Recommended!  SSL should be a baseline configuration for all landing pages and tracking domains). Add SSL to Your Landing Pages - Marketo Docs - Product Documentation Option 2 (Not recommended!   Warning! This is a security risk.) -Allow browser to view unsecured content (can choose to turn this setting back off in the browser after viewing the content) This link below describes how to enable this content in Chrome. https://docs.adobe.com/content/help/en/target/using/experiences/vec/troubleshoot-composer/mixed-content.html This link below describes how to enable this content in Firefox. https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox Option 3 -Try to use a different browser or try turning off all browser extensions. Root Cause If the issue was sudden, it is likely due to the browser needing an update. Check if there are any updates that need to be done. Environment -SSL not enabled on Marketo instance -Browser blocks unsecured content
View full article
  Issue User Receives Communication Failure Error / bandaid when creating a new Email from a custom Template due to unapproved snippet. Resolution Email templates can contain code to reference a snippet by ID: <div class="mktoSnippet" id="FooterText" mktoName="Footer Text" mktoDefaultSnippetId="3"></div> If the snippet is not approved then a new email asset cannot be created, and instead a bandaid error occurs.   The snippet should be approved first before the template is used.    If the ID of the snippet in the HTML is 3 and the pod sj27, the URL to the asset would be Login | Marketo  
View full article
To customize the validation message, you can add javascript to the template of the landing page the form is on.  Unlike default language settings on a form, customized messages work only on landing pages using the modified template.   Note: Please ensure that you have access to an experienced Web developer. Marketo Technical Support is not set up to assist with troubleshooting code.     Open up your landing page template for editing.   For all languages you wish to modify, paste this javascript code (with your modifications) at the end of your template before the </body> tag.  For more languages, see this javascript file.   <script type="text/javascript"> Mkto.messages = { English : { required : "This field is required", selectRequired : "Please select a value for this field", emailInvalid : "Please enter a valid email address", telephoneInvalid : "Please enter a valid telephone number", pleaseWait : "Please wait" }, French : { required : "Ce champ est requis", selectRequired : "Sélectionnez une valeur pour ce champ", emailInvalid : "Entrez une adresse e-mail valide", telephoneInvalid : "Entrez un numéro de téléphone valide", pleaseWait : "Veuillez patienter" }, German : { required : "Dieses Feld ist erforderlich", selectRequired : "Wählen Sie einen Wert für dieses Feld", emailInvalid : "Geben Sie eine gültige E-Mail-Adresse ein", telephoneInvalid : "Geben Sie eine gültige Telefonnummer ein", pleaseWait : "Bitte warten" } }; </script>     Tip: You can include multiple languages in a single template.  The language selection on the form will determine the language that gets shown.
View full article
Sometimes you may see a link in your email that isn't decorated when you mouse over it.  That same link isn't tracked when you click it.   Check that there is a link The most common solution is to add a link to the email.  Many email clients will automatically add links to when the text looks like a URL.  For example, here's a link as it was typed in an email: But Outlook renders that text as a link: To fix this, edit the email and add a link to the URL by highlighting the text and clicking the link icon in the HTML editor. It may seem redundant to put a link on a URL, but this will allow the link to be tracked.   Check the <a> tag   If you edited the HTML, check to make sure it's correct.  Check if the: href is enclosed with quotes <a> is opened and closed correctly   Check for class="mktNoTrack" If you edited the link with class="mktNoTrack", the link will not be decorated by Marketo.  You'll have to remove that class from the email template or email body, depending on where it is.   When using tokenized URLs, make sure the "http://" is outside the token Tokens are populated in the email construction process after the tracking links are inserted, so in order for Marketo to understand a tracking link needs to go there, it needs to see the "http://" before the token is inserted in the email.
View full article
Here's how you can use tokens and URL parameters to automatically assign leads to Salesforce campaigns after filling out a form.  These tokens work in all of the Salesforce campaign flow steps:   Add to Salesforce Campaign Change Status in Salesforce Campaign Remove from Salesforce campaign   Get the Salesforce campaign ID and status   You need two things to begin this process -- the name or ID of the Salesforce campaign you want to sync to and a valid status in that campaign.  You can get the ID for the campaign by opening that campaign in Salesforce and copying the last 15 characters from the URL.  Here's an example campaign URL; the ID is highlighted:   https://naX.salesforce.com/ 701F00230001Z9z   To get the valid statuses, click on "Advanced Setup" on the campaign's page     The status should be listed there:     Create new fields   First, you need to create two new fields -- "SFDC Campaign ID" and "SFDC Campaign Status" -- both of type "string".  You can create these on your lead and contact records in Salesforce, or contact Marketo support to add those custom fields in your Marketo account.   Create or edit the form   After you create those fields, the next step is to incorporate them into your forms.  Create a new form or edit an existing form, then drag those two fields into your form.  Make them both hidden fields and set them to populate from a URL.  If you're unfamiliar with them, this article on hidden fields has details on how they work. Making a Field Hidden on a Form When setting the values for those fields, use a real Salesforce campaign ID and status as the default value.  Here's how you might edit the settings for those fields:   SFDC Campaign ID: Default Value: [a real Salesforce campaign ID or name] Populate from: URL Parameter Parameter name: campaignID   SFDC Campaign Status: Default Value: [a real Salesforce campaign status for the campaign you chose] Populate from: URL Parameter Parameter name: status   And here's what your form might look like when done:   Now you have a form that automatically add leads to the default Salesforce campaign you selected and that you can override with URL parameters.   Create a Smart Campaign   Next, you need to create a campaign that will add these leads to the selected (or default) Salesforce campaign.  We'll trigger this campaign to launch whenever someone fills out your form: In the flow, first you need to sync the lead to Salesforce so that you can add it to a campaign.   Then you can add it to the Salesforce campaign using the values in the SFDC Campaign ID and SFDC Campaign Status fields.  To do this, use the tokens for those fields in your flow step:  {{Lead.SFDC Campaign ID}} for the campaign name and {{Lead.SFDC Campaign Status}} for the status.  If you type "{{" in the fields, the auto-suggest will help you enter that text correctly:     Your finished flow should look like this:     Finally, in the schedule tab set this campaign to run every time and activate it.     Launch your landing page   If you modified a form already in use, you can now go to that landing page, fill out the form, and watch as your lead gets synced to the Salesforce campaign you chose.  If this is a new form, create and approve a new landing page which uses that form.  After filling out the form, you should see the lead added to the default Salesforce campaign specified in your form:     Use URL parameters to override the default campaign and status.  For our forms, the campaign is set by the "campaignID" URL parameter and the status by the "status" URL parameter.  For example, this URL:   http://offers.marketo.com/offers.html? campaignID=701A00000009K3l&status=Responded will assign the lead to the Salesforce campaign "701A00000009K3l" (the Salesforce internal ID) with the status "Responded."  If either value has spaces or special characters, make sure that you URL encode them before adding them to your URL.   Using tokens in other Salesforce campaign flow steps   These tokens work in all of the Salesforce campaign flow steps -- Add, Remove, and Change Status in SFDC campaign.  Follow the same directions as above but substitute the appropriate flow step in place of the Add to SFDC Campaign step.   Diagnosing errors   If your leads are not syncing to your Salesforce campaigns, first go to the Activity Log for that lead and double click the line that has the failed flow step. The information that appears will help you figure out what the problem might be. The most common errors you'll encounter are: Spelling errors in your tokens -- use the autosuggest to help Using an SFDC campaign ID or name that doesn't exist -- check the spelling of the campaign or ID The lead doesn't exist in salesforce -- sync the lead to Salesforce before adding him/her to your campaign Using a status that doesn't exist for that campaign -- change the status to one that does exist for the campaign, or add a new status to the campaign in Salesforce
View full article