Knowledgebase

Sort by:
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 You are utilizing Forms on Marketo Landing Pages, and want to run reporting on these forms.     Solution Currently Marketo has reporting for Email assets and Landing Pages. We do not have the ability to report on Forms specifically. One option would be to use Web Page reporting  -  this reported information would be limited to Marketo Pages with numbers of records who filled out the form, listed under "conversions." You could then create a Smart List to identify leads who have filled out these forms.        
View full article
If you sent an email from the Lead Database (as a Single Flow Action), as part of a campaign, or as a test email but didn't receive it, here are some tips.   Check the "From:" address   When sending a test message, make sure to check the "From:" address setting on your message. To do this, go to the Email Settings tab of the email editor. In the "From:" field, make sure that you either have a single valid email address, or a valid email address as the default, if you are using a token.   Many people want to send their messages from the lead owner. When you use the send test feature, the email address you are sending to doesn't have a full lead record, and so it doesn't have a lead owner. Since Marketo cannot send an email with no "From:" address, test messages without a valid email address in the "From:" field will not send.   Send as a Lead   If you have verified that the email had a valid From: address and you still aren't getting it, make sure to create yourself as a lead and send using a flow action.   See if the mail was sent   If you sent the email as part of a campaign or Single Flow Action, check the campaign's Results tab or your lead detail page to see if that mail was already sent to you. If it hasn't been sent yet, try waiting a little while longer.   Check your Junk Mail   In your email client, check your Junk Mail or Spam folder to see if the mail landed there. If it did, you should change the content of your email.   Check your corporate spam filter   Your corporate mail server may have blocked emails from Marketo; you should contact your IT department to see if this is the case. Please see our instructions for whitelisting Marketo's email servers: Add Marketo to Your Corporate Email Whitelist   Try sending to a different recipient   If you sent the original mail to your corporate account, try sending to a personal account on Yahoo or Gmail. If you sent it to a personal account, try your corporate mail account.    Use Marketo's Email Deliverability product   The Email Deliverability PowerPack, with Design Informant and Inbox Informant, can warn you when your mail is being rejected because of its content and help you identify junk mail pitfalls. Also, using Domain Keys and SPF improve the chances of your email landing in your leads' inboxes.   Contact Marketo   If you still can't figure out what happened contact Marketo to see if we can help.
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
Issue Is there a way to prevent opening a new browser window when a mailto/email address link in an email is clicked? Solution The reason why the link clicked in an email redirects to a new browser window occurs is because the link is a tracked link. As per design of Marketo tracked links, they are required to be loaded in a browser first which is why the mailtolink/email address clicked is loading in the browser first. If you wish to load the link clicked in the same window and not redirect to a new browser window, you will need to disable tracking on the link. https://docs.marketo.com/display/public/DOCS/Disable+Tracking+for+an+Email+Link    
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 The same email looks different in different email clients, and does not match what is shown in the Email Previewer.     Solution Different browsers and email clients render HTML and CSS differently. While there are standards set forth by W3C, there is room for flexibility. At a high level, it is expected for emails to look different, even within the same platform such as Outlook 2013 vs Outlook 2010. With that said, you can code against some of these anomalies by adding extra code in CSS to account for the differences. You should consult with an HTML/CSS designer to make these changes. In all likelihood, the issue is related to how Outlook(or any other email client) is rendering the email and reviewing the Outlook settings as well as email and template code should resolve any issues customers are experiencing as when we send test emails to both outlook and gmail both are generally rendered differently (gmail seems a bit fine though). FAQs Where should I start trying to determine whether this is a Marketo or Outlook issue? In most cases if the email is loading within another email client without issue then Outlook would be the best location to review. Is there a way for me to see if it is a template problem? Yes, does the issue occur when an email is created and sent with another template? What are the steps to troubleshoot? In general, to provide the most accurate troubleshooting steps, a bit more information will be helpful. I have provided a few general tips below which may be helpful. As a rule of thumb, Outlook sometimes requires custom coding to appear as it does in other email clients since they use their own word engine to render the html. If the images when they are downloaded are not displaying as expected, we would typically recommend reviewing any code in the email since Outlook uses its word engine to render html and additional code may be needed for Outlook specifically as a result. A developer may be required to implement any custom code required to display the emails as expected. You may consider reaching out to the Community to understand what other users have done to overcome similar obstacles. I have provided a few links below which may be relevant. Is there any reference Documentation ? https://nation.marketo.com/docs/DOC-4765-why-does-my-email-looks-different-on-various-version-of-the-same-platform-like-outlook HTML Email Display in Outlook Marketo emails don't render properly in MS Outlook app for iOS Re: Help - My Emails Look Terrible in Outlook 2016 Here are a few resources that may help with Outlook rendering issues: It’s Not You, It’s Outlook – The Complete Guide for Email Marketers http://www.verticalresponse.com/blog/its-not-you-its-outlook-the-complete-guide-for-email-marketers/ Gallery of Common Outlook Rendering Issues Gallery of Common Outlook Rendering Issues MICROSOFT OUTLOOK CONDITIONAL STATEMENTS http://labs.actionrocket.co/microsoft-outlook-conditional-statements Outlook 2007/2010/2013/2016 and Word HTML http://www.howto-outlook.com/faq/wordhtml.htm 12 Techniques for Excellent Emails in Outlook.com How to Create Excellent Emails for Outlook.com A Guide to Rendering Differences in Microsoft Outlook Clients https://litmus.com/blog/a-guide-to-rendering-differences-in-microsoft-outlook-clients Surface Pro 3 and Outlook Email Rendering Redirecting
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
Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Summary: Say you want to validate a custom field before someone submits a Marketo form on a Marketo landing page, then let Marketo do it's standard validation.   You can do that by overriding the formSubmit function in Javascript.  You can override it with a Custom HTML element for a single page; you can also add this Javascript to your landing page template so it affects many landing pages.   First, build a Javascript function to execute your custom validation (formIsValid() in the example below).  It should return a value of "true" if the fields validate. If not, return false.   Open the landing page for editing and drag a Custom HTML element onto the web page.  Paste in this Javascript and add your custom validation to the formIsValid() function.   <script type="text/javascript" src="/js/public/jquery-latest.min.js" language="Javascript"></script> <script type="text/javascript">      // set no conflict mode for jquery   var $jQ = jQuery.noConflict();   function myFormIsValid() {     var thisIsValid = true;     // Put your custom validation here.     // If anything goes wrong, set thisIsValid to false.         // for example, show an error message if the email contains "bob"     if ($jQ("#Email[value*=bob]").length > 0) {        Mkto.setError($jQ("#Email ~ span").prev()[0],"No Bobs allowed!");        thisIsValid = false;     } else {        Mkto.clearError($jQ("#Email ~ span").prev()[0] );     }     return thisIsValid;   }   function formSubmit(elt) {     if (!myFormIsValid()) {        return false;     }     return Mkto.formSubmit(elt);   } </script> Here's another example that checks if a required checkbox, such as a terms of service agreement, is filled before submitting: <script type="text/javascript" src="/js/public/jquery-latest.min.js" language="Javascript"></script> <script type="text/javascript">      // set no conflict mode for jquery var $jQ = jQuery.noConflict(); function myFormIsValid() {     var thisIsValid = true;       // show a message if they fail to check the box     if ($jQ("#TermsOfServiceAgreement").attr('checked') != true) {        Mkto.setError($jQ("#TermsOfServiceAgreement ~ span").prev()[0],"Please agree to the terms above.");        thisIsValid = false;     } else {        Mkto.clearError($jQ("#TermsOfServiceAgreement ~ span").prev()[0]);     }     return thisIsValid; } function formSubmit(elt) {     if (!myFormIsValid()) {        return false;     }     return Mkto.formSubmit(elt); } </script>   Follow these instructions if you want to retrieve the form fields via Javascript: Setting or Getting a Form Field Value via Javascript on a Landing Page The example above also shows you how to set an error field If you want to set or clear an error message on a field, you can use these two functions in your validation function. Note: These only work on form fields from the Marketo form designer. Replace the highlighted yellow bits below: Email -- the ID of the field where you want to show an error error message -- the text you want to display for this error           // error -- highlight the field           Mkto.setError($jQ("#Email ~ span").prev()[0], "error message");             // no error -- clear the field           Mkto.setError($jQ("#Email ~ span").prev()[0]);  
View full article
Issue Description In an attempt to approve an email, a 'Not Allowed' error message is being displayed with the following details: {{lead.Email Address}} : Token key not found Issue Resolution 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 A lead has an Unsubscribe activity logged in their activity history, but they continue to receive emails after the Unsubscribe.     Solution An Unsubscribe activity is logged when the lead clicks the system Unsubscribe link embedded in a Marketo email.  However, if that link takes them to a Preference Center that allows them to select from multiple options, they may not choose the full unsubscribe option and may continue to receive selected emails.   To confirm if this is the case, find the Unsubscribe activity in their activity log and double-click on the activity to open it. This will show you the choices they selected in the email preferences form.  In the example below, the lead did not fully unsubscribe, they only chose to unsubscribe from specific content. Since they did not choose the global unsubscribe, they will continue to receive some emails.    
View full article
Issue The deep link in a Marketo email does not redirect to the designated App.   Solution By design in Marketo, when tracking is enabled for a link, the link will be wrapped with a tracking link like 'http://test.website.com/[unique sequence of characters]'. So when a tracked link is clicked, the link 'http://test.website.com/[unique sequence of characters]' is first loaded in a browser then redirects to the actual link in the same browser. Therefore, as some deep link configuration can depend on the actual link first loading, a tracked link in Marketo does not redirect to the App. One workaround here is to disable Marketo tracking link so that the deep link will redirect to the App. However, the trade-off of this is that the click link activity will not be recorded in Marketo.
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
Question: I have leads that are getting created without providing information for fields which I have made required.   Answer: Marketo's field validation makes use of javascript. Most browsers have javascript enabled by default so this should be fairly rare, but a user could change their settings and turn javascript off. This would allow them to submit a form without providing all the required information.    This situation may also occur if a lead submits the first progressive profiling form and subsequently submits a second form with different questions, while also changing the email address (indicating either a different person using the same PC or the same person with two email addresses). Marketo will generate a new lead record, but it won't include the data captured in the first form. To identify if this is the case, examine the "Fills Out Form" activity and check if there is data submitted from a later progressive profile form. If so, this is likely the cause. To address this issue, follow these steps: Create a smart list with an Anonymous IP filter. Enter the anonymous IP address of the lead. The smart list may identify multiple records associated with the anonymous IP address. Merge or manually update the records as needed based on the identified information. By following these steps, you can reconcile the data and ensure that the lead records are appropriately managed.
View full article
Issue Does Marketo have the ability to edit the email header detail for particular email sends? Solution Marketo currently does not provide an option via the UI to customize the headers of emails. Custom headers can be built at a cost. For more information, reach out to your Customer Success Manager.
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 -Error editing image in email: “image URL does not exist” or “image URL cannot be found”   Environment -SSL not enabled on Marketo instance -Browser blocks unsecured content 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 | Adobe Marketo Engage 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 This issue could be caused by SSL not being enabled. If the issue was sudden, and SSL is enabled, it is likely due to the browser needing an update. Check if there are any updates that need to be done.
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 When you send an email that was cloned from a previous campaign and updated, the sent email shows the old content rather than the new content. Solution This can be caused by Dynamic Content in the email.  If you clone an email with Dynamic Content but only update the default content, then the old content will be sent to leads who are not part of the default segmentation.  Open the email in the editor and see what email elements are displayed in the Dynamic tab.     Check the different segments in the editor and see which ones have the old content. You can update the dynamic content for each segment or simply make the content static, which will make the email use the default content for all leads.    
View full article
Issue Reporting on separate links in an email that both point to the same URL Solution When there are duplicate links in an email, the performance of those links will be consolidated into a single row in the Analytics report, so if there are three links that point to the same URL, there will only be a single line for that link on the Performance report. If you would like to differentiate between these duplicates, you can add URL Parameters. Example: www.google.com   and    www.google.com?parameter=second-link In this example, Marketo Link Performance Reporting will show each individual link on Analytics Reporting, but both links will go to the same place.
View full article