Knowledgebase

Sort by:
To ensure all your activities show up under the Activity History (as opposed to Open Activities) make sure you have a "Completed" values in the Task Status list and that it's a "Closed" state. Here is how to check it:   In SFDC, go to Setup > App Setup > Customize > Activities > Task Field.  Click on Status In the Task Status Picklist Values list, check if you have a "Completed" value.  If you do have it, skip to step 5. You need to create the "Completed" value.  Click on the New button Type in Completed and click on Save Click the Edit link next to the Completed value Check the box next to Closed and click on Save. Once the steps above are completed, you should now Completed in the list with "Closed" checked like this:    
View full article
Say you want to keep specific Salesforce fields or records from syncing into Marketo. You can use Salesforce Profiles to restrict access to that data.     In short, Marketo will only sync fields and records that are visible to the sync account in Salesforce. If you don't want records or fields brought into Marketo, use the record- and field-level permissions to prevent the sync account from seeing them. A few notes before you begin... Depending on your version of Salesforce, you may not be able to change these settings. For example, field-level security is available only in Enterprise and Unlimited editions. This will require you to make changes in Salesforce on the account you use to sync with Marketo. If this account is also used by anyone else, these changes will impact that person's view in Salesforce too. You need administrator access in Salesforce to make these changes. If you hide a field in Salesforce that has already been synced to Marketo, it will still display in the Marketo user interface until you hide it with the Field Management tool. Even though you'll still see the field in Marketo, changes to that field will not get pushed to Salesforce.      
View full article
Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO.   Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: From the My Cases navigation y ou can access the following case views: My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues  Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases   To view specific case details, click a case number. From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting   If your case has been closed there are two options available to you.   Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.
View full article
The Custom Validation error messages that are seen in the Marketo activity logs are due to the validation rules the client would have in their SFDC instance. They are located in Setup > Customize > [Object/activity] > Validation Rules.   However, there may be times that there maybe no validation rules in the above noted location. Nonetheless, there maybe AppExchange packages such as Dupe Catcher that may have their own validation rules.
View full article
Article Text 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
Article Text Included in this article Overview What Causes Data Mismatch Sync Delays from Backlog Checking for the backlog How do you fix it? Campaign to add leads to SFDC  Campaign set up incorrectly Sync user permissions Field Value Validation Field Type Validation Overview Sometimes the data you see in your CRM system doesn't match what you see inside of Marketo. This document will show you the common reasons to help troubleshoot where the problem could be coming from.     What Causes Data Mismatch The vast majority of data mismatches result from sync backlogs, so much of this doc will go over sync backlogs. However, since there are a number of other ways this can happen, here are the most common ones to watch out for: Sync delays from backlog Incorrect set up of campaigns to add leads to SFDC Campaigns Sync user permissions Field Value Validation Field Type Validation     Sync Delays from Backlog Whenever an update is made to a record, it generates a System Modification Time Stamp, referred to as a SysModStamp. The creation of a SysModStamp on a field that is visible to the sync user will queue the record to be resynced. Whether the update is made on the Marketo side or on the CRM side, it will trigger the record to be resynced to update the information on the other end through the regular Marketo to CRM sync cycle.   When large numbers of updates are made like from a field value changing, then large numbers of records are altered, causing new SysModStamps on those records. This in turn results in large numbers of lead record updates that need to be resynced between Marketo and your CRM.       The sync of leads flows at the rate of approximately 10,000 records per hour. If you've updated 10,000 records at once, you can expect the sync of that data to take roughly an hour to complete. If you've updated 20,000 records at once, you can expect the sync of that data to take roughly two hours to complete, and so on.   Thousands of updates are synced over in just one API call as opposed to making a single API call for each individual update. Updates synced between Marketo and your CRM through the sync cycle occur in batches—large groups of updates made all at once to allow the data to be transferred more efficiently. That means 10,000 updates to the Lead Object, 10,000 updates to the Contact Object, then 10,000 updates to the Account Object, all within one sync cycle.   The sync cycle won’t let one Object dominate an entire sync cycle with large numbers of updates. Any updates over 10,000 will wait until the next sync cycle.       Checking for the backlog Long sync cycles are an indication that there are a lot of updates being made.   To check when did the last sync happened   1. Go to Admin       2. Go to integration for your CRM (e.g. Salesforce) in the tree on left       3. Go to the top right corner to see the information of Last Synced. Compare the time shown there to the current time. If it's a long time difference, you've probably got a significant backlog of updates waiting to sync.       How do you fix it? Stop making more updates.   Once the records are queued up to sync between Marketo and your CRM, there's no way to cut it off and stop it from going through the sync. The data will sync through, but essentially you'll have to just wait for it. If you can stop making continued updates until after the backlog has cleared, you'll be helping it to clear faster.       Campaign to add leads to SFDC  Campaign set up incorrectly There can also be cases when you are pushing leads to SFDC Campaigns via Marketo Programs or Smart Campaigns. If you have a flow action where you enter an incorrect campaign name or the corresponding status, the leads flowing through this campaign will have issues while syncing.   If you've synced the lead from Marketo to the SFDC Campaign but accidentally synced it to the wrong one, you'll have a data mismatch there.   Ensure that you have the campaigns with correct names and statuses       Sync user permissions Sometimes a lead won’t sync to CRM because the SFDC sync user doesn’t has permissions enabled to allow the Marketo sync user access to it. Ask your CRM Admin to update the permissions so as to allow Marketo sync user access to the record.     Field Value Validation If there’s a validation in your CRM on certain fields, and the field value in Marketo doesn’t qualify for the validation, the lead would not sync.You'll see "FIELD_CUSTOM_VALIDATION_EXCEPTION" error messages, which are your indication that this is where the problems are coming from.   For example: Let’s say there’s a validation in Salesforce to accept on “CA” as a value for the field “Country”, and Marketo field has it’s value as “Canada”. The lead would not sync to SFDC. To resolve this, ensure that field value aligns with the validation in SFDC.     Field Type Validation Field types must be compatible between Marketo and Salesforce. If the field types are different in Marketo vs CRM, it won't be able to sync properly.   For example: If the field in SFDC has the type of “Float” and field in Marketo is “Score”, then they aren't compatible and won’t sync. To resolve, ensure that the fields have similar or compatible types in Marketo and CRM
View full article
  Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 25 months, or 37 if you have purchased the premium data retention option. The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.         Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List     4. Add these two Flow Steps to the Campaign Flow: Flow Step 1 : “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2 : “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing       This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing.       Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.      
View full article
Issue When a Marketo field is synced to a SFDC field with a picklist, that picklist will be synced to Marketo when the field is added to a Marketo form. The values section of the field in the form will show the values from SFDC. However this does not occur with the standard state field in Marketo. Solution The state field's form picklist is not updated because it is automatically populated with the 50 US states.  To get around this, you can either manually update the values in the picklist in the form, or you can use a custom Marketo field. This field can be remapped to the state field in salesforce with assistance from support.
View full article
Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools.   Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2   Step 3 Step 4   If you experience issues, please email marketocares@marketo.com
View full article
Issue Issue Description Using the option to create a new Salesforce Campaign within the program sync feature, the Salesforce Campaign does not have the same status selection that the Marketo Program has.     Solution Issue Resolution T he Marketo Program will sync the membership only after adding members, and will update the status selections in the Salesforce Campaign to match.
View full article
Issue A record in Marketo failed to sync to Salesforce due to a Field Validation error.  Errors may include the following: Failed: FIELD_INTEGRITY_EXCEPTION:  INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST: bad value for restricted pick list field. Solution The lead was unable to sync to Salesforce because the value for a specific required field was missing or did not match the rules Salesforce had for the data in the field.  For example, the field in Salesforce could be a picklist and the value Marketo is trying to pass in the field is not in the picklist.  Salesforce always requires a Last Name and a Company Name value for all records, so if your lead is missing data in these fields, the sync will fail. To resolve this, check Salesforce to see what the acceptable values are for the field specified in the error, and make sure the Marketo record has the necessary information.  If you need further assistance with this, we recommend working with your SFDC Admin to determine why Salesforce is rejecting the record. This commonly happens when  Country/State picklist is enabled on your SFDC instance. As a consequence, SFDC will reject any record with country/state value does not belong to the list and so you will have to make sure that countries are set correctly everywhere in Marketo, and especially: in forms in data management campaigns in imports For example, if you try to pass the value "New York" to Salesforce, it will not be accepted. Salesforce will only accept "NY". The error messages you're seeing are coming from Salesforce because the State fields have been standardized to only accept certain pick-list values. In order to get these records to sync with Salesforce you'll need to update them to have valid values. Contact your SFDC Admin to get the list of accepted values for that field and update the record in Marketo with the appropriate value that is accepted by SFDC. If you feel like pick list is not necessary on SFDC, you could just disable the state or country pick lists in SFDC by following the below document https://help.salesforce.com/articleView?id=admin_state_country_picklist_enable.htm&type=5     Who This Solution Applies To Customers integrated with Salesforce    
View full article
Issue A lot of people suddenly synced from Salesforce to Marketo. They have been in SFDC for a long time, so you're wondering why they suddenly synced.     Solution People sync from Salesforce for a number of reasons. If they aren't new leads, then they probably met some criteria that caused them to be visible to the Marketo Sync User and sync down. One thing to keep in mind is that if the visibility rules change, Marketo won't actually see those people until a field that Marketo can see changes. Marketo looks at the "sysmodtime" stamp on a record. This indicates the last time a record was modified. If the record was changed since the last time the sync ran, then Marketo updates the record on the Marketo and SFDC side with the newest information. There have been cases where the visibility rules changed, but the new records that Marketo could see weren't updated for a considerable period of time. (This could be as long as years.) However, if something eventually changed and updated the sysmodtime, these leads would all sync to Marketo. The change can be anything, but if it's a large number of people, it's frequently a change on the Account object, which then filters down to the Contacts and Leads. If you're still unsure why a large number of people have synced to Marketo, the first thing to look at is what information changed, since Marketo only syncs people when they are updated with new information.
View full article
Issue Will custom settings, such as Launchpoint integrations, API configurations and SFDC sync settings, remain in place when doing an instance copy, or will they be overwritten?     Environment Non-Microsoft Dynamics integrated Instance Solution All permanent configuration settings which can be done to a Marketo instance are reset to the default values or settings in the destination instance. Everything is copied except for the below list: Lead Database and activity history are not copied CRM configuration is reset on the destination instance. Users are not copied. CRM Field Mappings are removed in the destination instance except for standard mappings, and must be set during the Field Mapping Stage of CRM sync initialization. RCA information is not copied. Program subscriptions are not copied. Campaign History is not Copied. CNAMES for Email links and LPs are not copied. All Account-string based properties are modified accordingly. Munchkin ID of the destination instance is preserved. Sales Insight Admin Configuration is Reset. Outlook licenses are not copied. All pre-existing data on the destination instance will be destroyed. Asset IDs for emails, landing pages, and programs will match Launchpoint and API integrations are not copied   If data may exist on the destination instance prior to the copy process, this may require that you work with your Success Manager to obtain a replacement instance for the copy to be completed. NOTE* This process is not applicable to customers utilizing the native Microsoft Dynamics integration.
View full article
Issue Your Salesforce sync cycle is taking longer than usual.  How long is too long?     Solution By default, Marketo starts each Salesforce sync cycle five minutes after the previous cycle completes.  Each sync cycle may take a couple of minutes or a couple of hours, depending on how much data needs to be written across.  If you notice your sync cycles seem to be taking longer than usual, here are some things to check. Have you done a large update recently?  This can create a backlog that can take time to work through. Have you added new fields to any of your synced Salesforce objects?  The more fields on the object, the more data needs to be written across, extending the sync cycle. If you would like to streamline your Salesforce sync, do an audit in Salesforce of fields visible to the Marketo Sync User.  If there are any fields that are not used in Marketo, remove visibility to them so Marketo does not waste time syncing them.  
View full article
Issue Leads are not syncing from SFDC to Marketo after the sync user has gained access to them.     Solution Make a change to the lead records to queue them to sync. SFDC has permissions that allow specific users to access some leads but not others. Your Marketo SFDC sync user is a user that can have this setting applied. The sync user can also have that restriction removed to allow access to those leads. When Marketo checks Salesforce for people to update, it is looking for leads who have had record updates since the last sync. Changing visibility rules in SFDC to allow the sync user access to those leads does not update the records themselves, only the accessibility to those leads by the sync user. This means that if the sync user couldn't access the leads before but now can, they still won't sync to Marketo until they have a field update. You can change a field value, but another option is to run the Data Loader in SFDC for those affected leads. That will create a new modification indicator, which will trigger Marketo to sync those records down.    
View full article
Issue You created a picklist field in SFDC and want to know if that field will sync down to Marketo with the field type of picklist.     Solution Marketo has a picklist option in form fields, but not in Lead Database fields. When you sync a field from SFDC that has the type of picklist, this field will show in Marketo with a type of String. However, when you create a form, the field type for your field will show as "select," which is a picklist.  
View full article
Issue You receive the error "Failed: cannot retrieve values for sfdc id" when trying to sync a record between Salesforce and Marketo.     Solution You can get this error message if the lead owner associated to the lead is not visible to the Marketo sync user. To troubleshoot this issue, do the following" Log into Salesforce using the Marketo sync user listed in Admin > Salesforce Confirm the record is visible to the Marketo sync user. Confirm the lead owner associated with the record is visible to the Marketo sync user. If the lead owner is not visible to the Marketo sync user, work with your SFDC Admin to allow the sync user to see it, or change the lead owner to something that is visible to Marketo. Once this is done, try the sync again.        
View full article
Issue Marketo Email templates that have been used are showing or appearing within the Salesforce Email Template Picker/Chooser. Solution The templates are created when Marketo syncs lead email activities to Salesforce.  You can disable these activities from syncing in Marketo Admin > Salesforce > Edit Sync Options. Unselect the Email activities or Sales Email activities you have synced.  The templates will no longer be created, but you also won't get these activities pushed from Marketo anymore. This applies to both Sales Insight and normal Marketo sent emails.     If you would like to note an email was sent to a lead without enabling these activities, you can utilize Interesting Moment Flow Steps or Create a Task to sync via the activity log!   Who This Solution Applies To Customer using Sales Insight for Salesforce    
View full article
Issue When creating a Smart List with a "Member of SFDC Campaign" filter, the SFDC Campaign is visible on the drop-down list, yet it throws an error when selected and the Smart List is loaded: "Error running Smart List: Check your Smart List configuration" Solution Things to check: The campaign has been re-named in SFDC or has been deleted. It could also be that somehow a "space" has been entered before the campaign name. For example, Marketo is looking for "SFDC Campaign Name" and SFDC has it as " SFDC Campaign Name" or "SFDC Campaign Name ". The campaign is present and active in SFDC, but is not visible to the sync user. The Marketo Sync User details can be located in [Admin > Integration > Salesforce > Username] This can be checked by logging in to SFDC as the Marketo sync user and verify that the campaigns are present with the correct name and activated for that sync user.    
View full article
Issue Lead owners are required when syncing a lead to Salesforce, but is there a way we can sync them without assigning a lead owner? Yes there is, and it's called lead queues!     Solution How to do it: Lead queues must be set up in Salesforce first. Like lead owners, the queues must be visible to the Marketo Sync user before they can be selected. Select the lead queue you want leads to be assigned to in the 'Sync Lead to SFDC' or 'Change Lead Owner' flow steps. Qualified leads that pass through this flow step with then be synced to Salesforce and assigned to the lead queue rather than a lead owner. A few important notes: Only leads can be assigned to a lead queue, contacts cannot and must be assigned an owner. Assignment rules in Salesforce can conflict with the request sent from Marketo. Double check these assignment rules to make sure there are no conflicts.  
View full article