Knowledgebase

Sort by:
Issue After moving an asset to a new folder, you are unable to see the asset in the tree, or see duplicates of the asset in both the new and old location. Occasionally, this may occur even when you have not recently moved the asset. Solution Sometimes when an asset is moved from one folder to another, it may not display correctly in the navigation tree.  This is generally due to a caching issue.  Try refreshing the browser or logging out of your Marketo instance, then logging back in.  If this does not clear the issue, contact Marketo support to have us clear the tree cache for your instance.
View full article
Issue Do users within a Marketo instance get automatically subscribed to receive emails about upcoming Marketo webinars? Solution Users with a login in Marketo are not automatically subscribed to receive emails about upcoming Marketo webinars. The users would need to subscribe to the communications by filling up a form on any Marketo landing pages (e.g. https://www.marketo.com/company/contact)    
View full article
Issue Description How to disable Niko from ToutApp extension Issue Resolution To remove Niko, simply click on the blue Tout envelope at the top right of your browser, then manually uncheck the box next to "Show Niko as I browse the web". Refresh the page, and Niko should disappear. Who This Solution Applies To ToutApp users with Niko
View full article
Issue Description You receive "Object reference exception error" in Outlook Issue Resolution The reason this error is occurring is because the ToutApp Outlook add-in depends on a reference object in a newer version of the .NET framework than the version of .NET currently installed on your machine. To resolve this, download the updated version (http://www.microsoft.com/en-us/download/details.aspx?id=42643) of the .NET framework from Microsoft's site, and install it on your machine. Once it's installed, please reboot the computer.  After you've successfully installed and rebooted, go ahead and open Outlook. You should see it start up without issue, and the ToutApp add-in should be present and fully functional. Who This Solution Applies To Customers with ToutApp
View full article
Issue The issue appears when a custom view is created in MSI that contains dependant fields. The error message:  "The dependent picklist '<dependant field name>' requires its controlling field '<parent field>' to be present on the page." will be displayed when you are trying to add the dependant field. For example:  "The dependent picklist 'Sub-Classification' requires its controlling field 'Classification' to be present on the page." Environment Salesforce MSI Solution Need to omit the dependant field in the custom view. Root Cause We curently do not support creating a view in SFDC MSI with a dependant field.
View full article
Issue There is a DMARC policy bounce in ToutApp for Gmail email addresses.     Solution This is due to a DMARC policy on your organization's name domain which is preventing the emails from being delivered to Gmail email addresses. Visit the Google support portal on this https://support.google.com/mail/answer/2451690 Have your team check your DMARC policy.      
View full article
Issue You see a soft bounce on a lead and in the details you see it show System send failure: Reply-To address parse error (value of the address) Solution Confirm the tokens you are using are for the proper field and that the value for the field is an email address. The parse error occurs when we cannot generate or create a proper email address in the From Email or the Reply To Email fields. The error will show in the parenthesis the value we tried to put in.. For example Service Department is in the parenthesis, this would be an example of a incorrect field being used.
View full article
Issue: You are unable to put the cursor into a form field to enter data in a form. Solution: Edit the landing page to ensure that there are no element boxes overlapping the form fields. Nice! You just figured out what the issue was and leads can now access all form fields to input their data.
View full article
Issue The GoToWebinar integration is not able to see a webinar that has been set up as a "Simulated Live" record type. Solution GoToWebinar requires v2 for the GoToWebinar API for the "Simulated Live" webinars.  Marketo is still on v1 of the API so "Simulated Live" webinars are not supported at this time.    Who This Solution Applies To Customers integrated with GoToWebinar
View full article
Issue You go to a Marketo form that has prefill enabled and see that it contains some other person's information. Solution Form prefill can display another person's information if a Marketo email sent to one person is then forwarded to someone else.  Clicking on another person's tracked link cookies you with their information and causes it to prefill in the form.  To correct this, clear the cache and cookies on your browser.  If you would like to make sure this does not occur with your customers, please disable form prefill for the fields on your form.  There is nothing wrong with the forms or landing pages themselves, it is simply a matter of another person's cookie being placed on the browser by the forwarded email tracking link.  
View full article
Issue Description When we delete the static lists from a program after a period of time, will the leads they contain no longer be member of the program?   Issue Resolution The individuals should still be a member unless you change their membership status to remove them. Remember lists are simply collections of individuals so you can easily process or associate them, they don't automatically get "membership" unless you had corresponding flow steps that you used when putting them on the list.     Is this article helpful ? YesNo
View full article
No - It’s done automatically and behind the scenes. The algorithms used by our proprietary technology automatically present relevant content to your audience segment using digital behavior, keyword search terms, and firmographics such as: geolocation, employee size, revenue size, and industry.   The recommendation engine uses predictive analytics and machine learning to predict which content asset will most likely to be individually relevant for each one of your website visitors to read.
View full article
Overview These instructions will show you how to add a filter to Segments that will prevent a visitor from seeing the same campaign twice. When done this way, each visitor will only see the associated Campaign once and won't see it again.   This is a article attached image   1. Locate and select the User Context API filter (in the API category). This is a article attached image     2. Select "Campaigns - Viewed" from the "Select field to add" drop down. This is a article attached image   3. Select "is not" and insert the Campaign ID. This is a article attached image     Where to find the Campaign ID The Campaign ID is the identifier used by RTP to specify which Campaign you are referencing. It can be found in the URL for the campaign once you've navigated to it. Look for the number in the end of the URL, just after "reactionId=".            This is a article attached image   4. Click the plus sign to add a second field to the filter. Choose "Campaigns - Viewed" as the second field, same as the first.   5. Select OR from the AND/OR field. 6. Select "is empty" for the second Campaigns Viewed filter option. S This is a article attached image     Finally please make sure that the campaign is not marked as "Sticky", as this will make it appear every time.   You're all set! This segment will now only match visitors who have not seen the campaign yet.
View full article
Included in this article Overview Use Sync User Login Check Field Level Security Overview If you've ever had trouble getting a field or field value to sync between Salesforce and Marketo, the most common problem is that the Salesforce sync user doesn't have permissions to access that field.   Since different users have different permissions to access fields based on their roles, not every field or record is visible to every user. However, there can be cases when a user needs access to fields which are not accessible. For example, if a program needs to be tested but the field is not accessible, or the user may have been simply missed from the permissions. In such cases, you can check whether the sync user can see that field.     Use Sync User Login To find if your sync user has permissions to access the field, check the Salesforce integration ID. Navigate to Admin > Salesforce and check the Credentials. This will give you the login ID. Your Salesforce Admin should have the password for that login ID.       Next, log into your CRM using those SFDC sync user credentials.       Navigate to the lead/contact record.       Check to see if the field shows on the lead record. If the field is not visible, that means that your sync user does not have permissions enable to access that field.       Check Field Level Security If the field isn't visible, we need to check the Field Level Security for the fields. This is where the fields will be listed with checkboxes indicating whether the field is to be accessible or not.   1. Go to Setup.       2. Navigate to your Profile.       3. Go to the section “Field Permissions.”     Here you’ll be able to see the fields and their corresponding permissions. Restricted permissions could be a reason why the SFDC sync user cannot see a field or record. Therefore, you may need to make changes here to allow permissions to view it.
View full article
Issue Often times variables are used in emails and guided landing pages for marketers to quickly and easily change a link URL in a CTA button. However these links cannot be made dynamic when used with a variable. Solution The variable needs to be removed and replaced with an editable section or a rich text element. Once this is done the editable section or rich text element can be made dynamic. This will require some prior knowledge of HTML as the code of the asset itself will need to be changed. The links below will guide you through the syntax that needs to be used to modify your HTML. Create a Guided Landing Page Template Email Template Syntax    
View full article
Issue How deleting or archiving programs will affect the Lead field: Acquisition Program.     Solution If you delete a Marketo Program, the field will append a "deleted" at the end of the Program Name. For example, if the Program Name was "July 2016 newsletter" for Acquisition Program, after deleting the Program, the field value would change to: "July 2016 newsletter  -  deleted (####)". The numbers represent an activity ID on the backend. Note: Archiving Programs does not affect the Acquisition Program.    
View full article
Issue Lead activity log shows "Change segment" or "Add to Segment" for a segmentation (i.e. "Change Title to "Directors") The named segmentation ("Title") does not show up in the segmentation list in Database Environment Marketo instance with the Target Account Management feature Solution Even though the activity log shows a segment activity, the segment is actually a Persona, which is a feature of Target Account Management.
View full article
Issue You have a Marketo form embedded on a non-Marketo page.  When you open developer tools in your browser you see: "Error loading form: Object error: true errorCode: 400 message: "Subscriber <Your Munchkin ID> is not valid" "   Solution The form embed code you are using is looking for your instance in the wrong place. Check the URL when you first log in to Marketo, make sure the sub domain in that URL matches what is in your embed code. For example: If you see https://app-sjst.marketo.com/ then make sure you have that same "app-sjst" in your embed code. Please note: This may vary between your sandbox and production instances.        
View full article
Issue Description How to identify in which campaign the "Delete Person" flow step is used   Issue Resolution You can identify it by going to "Campaign Inspector" in Marketing Activities.   From there you can filter down by type of Smart Campaign and search "Delete Person" and the resulting list will be Smart Campaigns containing that flow step.   If you do not see the Campaign Inspector, navigate to Admin > Treasure Chest to activate it.     Is this article helpful ? YesNo
View full article
Issue When using the "Sync to Salesforce" flow step and setting up choices, selecting "Do Nothing" uses the Auto-Assignment Rules in Salesforce. Solution This is expected. For this flow step, the choices are basically asking whether the record should be assigned to a specific person or not. When it is not specified (i.e., "Do nothing") the assumption is that you still want the record to be synced to Salesforce, otherwise they would not be in that step, but that there's no particular desire to assign it to a specific person. Thus, since SFDC records need someone to be the owner, the Auto-Assign rules are used by default  
View full article