Knowledgebase

Sort by:
Distributing leads to sales reps is easy.  Marketo, however, only supports random distribution.  This gives a pretty good approximation of the round robin technique.   Prerequisites: Create A New Program Create A Child Campaign      1. Go to the Smart List tab of the campaign you created, find and drag in the Lead is Created trigger. Tip: Use the trigger that logically would come right before you want to assign the lead to a rep. This is a article attached image        2. I've added the constraint "SFDC Type is empty" so that records that already exist in Salesforce do not get re-assigned.          3. Go to the Flow tab, find and drag in the Change Owner flow step.      4. If you have 3 lead owners click on the Add Choice button 2 times.  You always want the number of choices to equal the number of owners in the round robin minus one. This is because the last person goes in the Default slot.      5. Find and select Random Sample.      6. 100% divided by 3 sales reps is 33%, enter "33".      7. Find and select the first sales rep.      8. Repeat steps 4, 5 and 6 for every remaining choice. Be sure to fill out the default choice also. This is a article attached image        9. Activate the campaign and it should now distribute leads randomly to your lead owners.
View full article
Technically, you cannot move records backwards in a progression status.  The only so called “backward” status that you can change the record to is a progression status of “Not In Program”; however, doing this removes them from the membership of the program.  If you do this procedure, this will allow you to re-add them with a different status.   We mentioned technically this cannot be done but logically, there is another method that allows you to juggle the record’s progression status but in a more lateral movement with what appears to be in a “backward” state.  This is all dependent on how you have your channel steps configured.  To access your channel steps, please do the following:   Choose Admin Choose Tags Click the + next to Channel Locate the channel you wish to configure and highlight it Click the drop-down menu towards the top of Tag Actions, and select Edit   You should now see a pop-up window that allows you to configure the status steps for that channel like the following example:   This is a article attached image     If you configure statuses that have the same step number, this will allow you to move the record in a lateral movement which, in a sense, is somewhat like a backward progression but it really isn't.  With the example screen capture, I can do a change in progression status of “Invited” to “Attended Show” and vice-versa because the step is with an identical number. If I wanted to change in progression status of “Invited” to “Engaged” and back, it will not work because the step value is not identical. You can reference more information about this in the Create a Program Channel article.
View full article
Want to gauge how many leads clicked through a link you have in your social media or other outlets? This can be done using URL Parameters at the end of the URLs you use. Basically, you just add a little bit of code to the end of the hyperlinked URL. When leads click through and arrive at your Landing Page, that code can be captured into a hidden Form field. Here’s how to do it.   Quick Overview of URL Parameters In the structure of a URL, there are two main parts. The first part is used for navigation, and the second part is used to pass data along. The two parts are separated by a question mark. For example, let’s look at this URL:   www.myawesomewebsite.com?URLParameter=ThisIsAParameter   The first part of the URL, “www.myawesomewebsite.com” is the main part of the URL used for navigation. The whole rest of the URL from the question mark on, “?URLParameter=ThisIsAParameter” is referred to as a querystring. It isn’t needed for navigation to the page specified, but can be used to pass the extra data you want to include.   This is a article attached image   The querystring contains the URL Parameters, which are used to push data into the hidden Form fields. In the querystring “?URLParameter=ThisIsAParameter” used here, “URLParameter” corresponds to the name of the parameter you use when designating the value for the hidden Form field, and “ThisIsAParameter” will be the value that is actually entered into that field. You can add additional values into additional other fields by adding those into the format of the URL separated by an ampersand like this:   www.myawesomewebsite.com?URLParameter=ThisIsAParameter&URLParameter2=ThisIsValue2&URLParameter3=ThisIsValue3   In this example, you’ve got the same initial value being pushed into the first hidden field, but now two more hidden fields will store the next two values as well. The name of the parameter for the second hidden field would be “URLParameter2” and the value put into it would be “ThisIsValue2”. The third hidden field parameter name would be “URLParameter3” and the value put into this field would be “ThisIsValue3”. This is a article attached image Applying This to Social Media Use So, how does this let you track leads coming from each of your social media sources? Well, in setting up your different promotional channels, when adding the hyperlink, you can customize the URL parameter for each channel so that the values passed will input the information specific to where they came from. The parameter values will change from one social media outlet to the next, but the structure and format will stay the same.   Let’s use the social media sources of Twitter, LinkedIn and Facebook as examples. Since you’re looking to identify the source of these leads, you’d likely want to name your parameter as “Source” so that it’s easily identifiable. Using the same base URL, let’s see how you’d structure the URLs. For hyperlinks placed on Twitter: www.myawesomewebsite.com?Source=twitter For hyperlinks placed on LinkedIn: www.myawesomewebsite.com?Source=linkedin For hyperlinks placed on Facebook: www.myawesomewebsite.com?Source=facebook   When leads fill out the form on your landing page, the Source field will then tell you exactly where they came from! The best part, this is completely customizable and scalable. You can add more parameters and hidden fields to capture additional information like what campaign it is for.   Documentation How to make form fields hidden: https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/forms/form-fields/set-a-form-field-as-hidden How to define hidden form field value: https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/forms/form-fields/set-a-form-field-as-hidden (Look for the section on URL Parameters in particular) Using the URL builder to generate the URLs you’ll be using: https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/demand-generation/landing-pages/personalizing-landing-pages/using-the-url-builder    
View full article
Included in this article:   Overview Limitations Error Handling and Troubleshooting Overview No-Draft for Snippets allows you to distribute snippet changes without drafting approved assets using it. All assets using the edited snippet get the updates and maintain their respective status: Approved assets get the snippet updates and stay approved Drafts get the snippet updates and stay in draft mode No-Draft is automatically enabled for all Administrator roles. An admin can then enable this feature for any additional role. While No-Draft Snippets are very useful, they do have some limitations and issues that tend to arise. This article will show you what those limitations are and how to troubleshoot issues that can come up.   Limitations This feature is designed to save time with the snippet approval workflow. There are a few limitations to be aware of: No-Draft will not work if you replace one segmentation with another one in the same snippet. However, No-Draft will work if you change, add, or delete a segment within a segmentation that is referenced in the snippet No-Draft will not work if you add/remove a segmentation to a previously approved snippet By design, No-Draft will fail if you make a dynamic snippet static, or a static snippet dynamic. If your use case requires this scenario, then we recommend you create a new snippet to be used across your assets. If you must update the existing snippet, then you will need to approve it using the Create Draft option, then re-approve the assets using the snippet (in other words, the old behavior) No-Draft does not auto-approve drafts Users without the No-Draft permission can still approve a snippet, however it will generate drafts of approved assets No-Draft works only when approving one snippet at a time Assets using the snippet are locked for approval until No-Draft is done processing Snippet updates made to approved assets cannot be rolled back No-Draft applies only to snippets   Error Handling and Troubleshooting If something goes wrong, an error message is delivered to the Notification section of Marketo. You can subscribe to this notification and receive email alerts in their inbox. Users must subscribe to No-Draft in each workspace with the permission enabled.   If an error does occur, chances are that the update process was not completed. Some assets may have the updated snippet content and others may not.   To resolve, redraft the snippet and re-approve. 1. Select the snippet and click Edit Draft. 2. Make a small edit in the snippet editor to create a draft (such as pressing the keyboard’s spacebar). 3. Click Approve Snippet. 4. In the dialog box, select Update all to start over.   This should fix the issue. Contact Marketo Support if the problem persists.
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. 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 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"     Solution 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 that, when previewing emails, you are able to 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 Clicking on a link in a Marketo e-mail that re-directs to a non-Marketo webpage destination does not open the page.     Solution Complete the troubleshooting step below. If they do not resolve the issue, include the results in a Marketo Support Ticket. Check the CNAME is correctly setup for the email tracking link  Check that the Default Branding Name matches the CNAME in Step 1 (check for typos).  If you are unsure you can visit CNAME lookup on mxtoolbox and enter the default branding name to check. Under the Domain field enter your default branding name. Do you have SSL for tracking links enabled? If Yes, tracking links in emails should start with HTTPS:// If No, tracking links in emails should start with HTTP://   If you do not have SSL enabled, but when you click the link it resolves to HTTPS://,try a different network and see if it still occurs. Your network may be configured to automatically use HTTPS automatically even if the link is specified as HTTP. (Check with your network admin)   If you are re-directed to the non-Marketo landing page but the page does not load: Check with the website admin if there are any redirect rules setup on the website. Try cutting out parts of the additional URL Parameter to see if that fixes the issue to identify which part of the URL parameter is causing it. Sometimes lead tokens or the mkt_tok may affect a redirect rule, since mkt_tok generates random characters and sometimes the token contains percentage '%' characters. It very common for websites to interpret a % followed by a character as an encoding. Seen in this website here   If you are unable to resolve the issue in the steps above, provide the test results and information in a Marketo Support Case.
View full article
Issue: My landing page is showing the wrong title, why is this and how do I fix it?   Solution: When you clone a landing page, the title of the old page carries over to the new one. In order to update the page title please see Edit Landing Page Title and Metadata for detailed instructions.
View full article
Question: How do I add a link to my lead/contact's Salesforce detail page when sending an alert from Marketo?   Answer: If the lead or contact is in both Marketo and Salesforce at the time when the alert email is sent, then the link to the Salesforce detail page will be automatically appended to the alert email sent by Marketo.   Note You will need to use the "Send Alert Info" token within your Alert email while designing your email in the Design Studio of Marketo. This is a article attached image Below is what the generated alert looks like once it is sent from Marketo (note the link to the Salesforce detail page is automatically inserted):   This is a article attached image   Note if the lead or contact is not in Salesforce then there is no link to the Salesforce detail page:   This is a article attached image
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 When you click on ‘Forward to Friend’ link on an email template, it redirects you to the below 404 error page.   This is a article attached image     Solution The ‘Forward to Friend’ link will work only in a sent email and not on an email template. To test this functionality, you need to create an email using the template which contains "Forward to Friend’ link and then send the email to your test lead using a run action.  It will not work properly with a send sample. Open the email and click on the "Forward to Friend" link. Once clicked the email will open on a webpage and then the below "Forward to Friend" box will be visible.   This is a article attached image   To know more about "Forward to Friend", refer the below document.   http://docs.marketo.com/display/public/DOCS/%27Forward+to+a+Friend+Link%27+in+Emails    
View full article
Issue You have Visibility Rules enabled for a field on your form, but the field is not shown or hidden as expected based on the values in the other fields.     Solution If you have enabled visibility rules for Field B but the field is not showing/hiding as expected when the correct value is chosen in Field A, one possibility could be the with the setup with the selected operator in the rule.  When using visibility rules for Field B, the "is" operator will use and reference the displayed values of Field A, but "contains" will use the stored values.   For example, let's say you have a visibility rule that should display the a particular field when 'Marketo Lead Management' is selected for the "Product Interest" field. The displayed value for the field (the one shown to the customer) may be "Marketo Leads Management" but the stored value for the field (the value written to the lead record) is "MLM". If you set up the visibility rule as "Product Interest is Marketo Leads Management", the rule will look at the Display Value and see a match.  However, "Product Interest contains Marketo Leads Management" will look at the Stored Value, which is "MLM." It will not see the match, and the field will not be displayed. 
View full article
Issue: When I try to approve an email I get the following error: Error approving Email Name - Sending IP is empty or not valid This is a article attached image Solution: You likely have multiple dedicated IPs and you did not choose which one to send this email from. 1. Edit Draft of the email in question. 2. Select which IP Address you want this email to sent from and click Save. This is a article attached image 3. Close the email editor and under Email Actions click on Approve.      
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 Embedded Marketo form not visible in Firefox Private Browsing mode. Solution Firefox's private mode will be enabled by default. When you embed a Marketo form in your own webpages and view it in Firefox's private mode, it will disable the Javascript as part of the tracking protection of this browser. JavaScript is needed for the forms to appear on the landing pages or webpages. The "Tracking Protection" in the Firefox browser will need to be deactivated for the form to appear. Here is an article from FireFox regarding the Tracking Protection: https://support.mozilla.org/en-US/kb/tracking-protection    
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 Email won't be approved due to too many custom tokens Solution Sometimes when approving an email with a large number of of tokens, the following error message will appear: 'The number of custom tokens in the email exceeds the limit '   This is a article attached image   This means that you have too many custom tokens in the email and that if you wish to approve the email, you will need to remove one or more of your custom tokens in the email.    Its important to note that this only applies to custom tokens, which are tokens based on a custom field in Marketo.  This means that while you will be allowed to add more of the standard tokens to the email and approve it, you will not be allowed to go beyond the 40 custom token limit we have in place for the non-standard tokens. Here you will find all the standard tokens in Marketo
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 Outlook 2013 / 2016 / 2019 / 365 and Word HTML - HowTo-Outlook 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 Outlook Email Rendering Issues and How to Solve Them - Litmus Surface Pro 3 and Outlook Email Rendering Redirecting
View full article
Issue Email asset does not show which template it was built on and shows the word "none" instead of the name of the template that was used to create that asset. Solution Any edit directly to the HTML code of an email will break the connection between the email and the template. Changes made to the template will no longer flow down to the email. After making those change you will see a template name of None instead of the name of a template. When editing the HTML in the email, you will see this warning message: This is a article attached image
View full article
  What is the Email API? What is the Email API used for? What is Email 2.0? Does the Email API Work on Email 2.0 Assets? Will the Email API Break when Enabling Email Experience 2.0? How Are 1.0 Assets Upgraded to 2.0 Assets? What to Do When an Email Was Accidentally Converted to Email 2.0 format?     What is the Email API? API stands for Application Programming Interface and the Email API allows an automated process to create and edit emails in Marketo. There are also other API calls that involve emails, such as Approve Snippet (assuming the Snippet is used in an Email) and Clone Program (assuming the Program contains Emails). There are also API calls to create and update Email Templates. Essentially, the API can do many things that you can also do through the Marketo user interface, but then in an automated fashion.     What is the Email API used for? There are many scenarios: an external system could create Emails in Marketo using data that lives outside of Marketo. A translation service provider could clone a master Email, translate it to many languages, then save them back into Marketo as localized Emails. A reporting system could extract Emails from Marketo to use in reports that are generated outside of Marketo. An external system could Clone a Program that contains Emails, then populate the Program Tokens and schedule the Email to be sent out at a specific time. There could be an external email template creation system that creates new Email templates in Marketo through the API.     What is Email 2.0? “Email Experience 2.0” is the new Marketo product feature with the enhanced email editor, documented here: https://docs.marketo.com/display/public/DOCS/Email+Editor+v2.0+Overview. It can be switched on in Admin > Email > Edit Email Editor Settings. All Emails and Email Templates also have a version number, either 1.0 (the old version) or 2.0 (the new version). If we refer to “Email 2.0 asset” we mean an email or email template in the new upgraded 2.0 format.     Does the Email API Work on Email 2.0 Assets? Yes.     Will the Email API Break when Enabling Email Experience 2.0? No. Enabling Email 2.0 will not automatically upgrade Emails or Email Templates to the new 2.0 format. The Email API can still create new Emails and Email Templates in the 1.0 format.  However – after enabling Email 2.0 – any Email or Email Template that is created or edited and approved through the Marketo User Interface will automatically be upgraded to the 2.0 format.     How Are 1.0 Assets Upgraded to 2.0 Assets? If you edit an “Approved" or “Approved with Draft” 1.0 Email with Email 2.0 enabled, the draft is converted to the 2.0 format. You can still discard the draft to go back to the approved 1.0 format. Once you approve the email and it becomes 2.0, the Email cannot be converted back to 1.0. If you edit a “Draft” 1.0 Email (never been approved), this will automatically be converted to 2.0 with no option to revert back to the 1.0 format. The same applies to Email Templates.     What to Do When an Email Was Accidentally Converted to Email 2.0 format? If an Email or Email Template was accidentally converted to the 2.0 format, you’d have to copy the asset contents to a text editor, disable Email 2.0, then create a new 1.0 asset using the content that you copied.
View full article