Knowledgebase

Sort by:
Issue Sometimes you may get this error when trying to sync a Marketo Program to an SFDC Campaign -  "Not allowed: Salesforce campaign contains incompatible statuses", even though the statuses match in the Marketo program and SFDC campaign.   Solution Check for the statuses in the Marketo program channel and SFDC campaign - you will see the same statuses. This error occurs if there is any case-sensitive error in the statuses. For example, if your Marketo program has the following statuses: Attended, Registered, Unable to Attend and the SFDC campaign has Attended, Registered, Unable to attend. Then you will encounter the above error. You have to change the status in Marketo as "Unable to attend" or change the status in SFDC Campaign as "Unable to Attend"  in order to fix this.    
View full article
Issue By default, new Marketo person records will not automatically sync to Salesforce to create new Lead records. There are other actions required to get these new records into Salesforce. Solution In order for new Marketo person records to sync over to create new Salesforce Lead records, they will need to be run through a Sync Person to SFDC flow step or be given a member status in a Program that is synced to a Salesforce Campagin. Sync Person to SFDC flow action: You can sync a new Marketo person record to Salesforce using this flow action as either a single step flow action or as a flow step in a smart campaign. Single-Step Flow Action: In Lead Database, select the Marketo person records you want to sync, click Person Actions > Salesforce > Sync Person to SFDC Flow Step: Creating a smart campaign that utilizes the Sync Person to SFDC flow step will sync the Marketo person record to Salesforce. Note: Other SFDC flow steps, such as Change Lead Owner, or Change SFDC Campaign status, will also sync the record to Salesforce, since the record must be in Saleforce in order for these steps to execute. Program Member Status Sync: Giving a new Marketo person record a member status in a Program that is synced to a Salesforce Campaign will sync that new person record to Salesforce during the next scheduled Salesforce sync.    
View full article
Issue When trying to sync a lead to SFDC, it fails with an error message "_createSObjects failed - AgreementTaskTrigger: execution of BeforeInsert caused by: System.NoAccessException: Script-thrown exception ()" Solution Your Salesforce instance has a custom  SFDC trigger that fires when you create a lead in SFDC (in the example, the trigger is named "AgreementTaskTrigger") but the trigger was not able to execute, so the sync failed.  To investigate this, you will have to set up a debug log on the Marketo sync user in SFDC and have your SFDC admin look into the details. If you disable the trigger in SFDC, the sync will work without an issue.  
View full article
Issue When you use the "Add to SFDC Campaign" flow step, and the lead isn't already in SFDC, this step will sync the lead to SFDC, and you want to know which assignment rules will be applied.   Solution The SFDC auto-assignment rule will be used. To explain this further, if for some reason you don't have lead assignment rules firing properly in Salesforce, it will be assigned to what is called the "Default Lead Owner" in Salesforce. It's not just "Add to Salesforce Campaign" that uses what is called "implied Salesforce actions". All of the following flow steps will sync the lead to Salesforce first before running the flow step if the person is not already synced to Salesforce: Add to Salesforce Campaign Change Status in Salesforce Campaign (this will sync them AND add them to the campaign first) Change Owner Convert Person Create Task      
View full article
Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.
View full article
Issue When a lead fills out the form in Marketo, SFDC sync for the new lead fails with an error  "Duplicates_Detected." Solution This error, "Failed: DUPLICATES_DETECTED: Use one of these records?" is a message Salesforce is sending back to Marketo, rejecting the attempt to sync the record. This means there's a setting in SFDC preventing duplicates from being created, possibly due to a custom deduplication rule on the SFDC side.   Recommended steps : Check the dedupe settings and check for these leads in SFDC based on the things other than the email address like first name, last name etc. You may need to work with your SFDC admin to determine why Salesforce rejecting the record as duplicate.      
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
Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.
View full article
Issue When a lead fills out the form in Marketo, SFDC sync for the new lead fails with an error  "Duplicates_Detected." Solution This error, "Failed: DUPLICATES_DETECTED: Use one of these records?" is a message Salesforce is sending back to Marketo, rejecting the attempt to sync the record. This means there's a setting in SFDC preventing duplicates from being created, possibly due to a custom deduplication rule on the SFDC side.   Recommended steps : Check the dedupe settings and check for these leads in SFDC based on the things other than the email address like first name, last name etc. You may need to work with your SFDC admin to determine why Salesforce rejecting the record as duplicate.      
View full article
Issue Description You have recently added a new field to a SFDC Custom Object which is synced to Marketo, but you do not see that new field available on the object in Marketo. Issue Resolution To have the new fields pulled over to Marketo, disable your SFDC global sync within Marketo and then refresh schema for custom objects. This should pull over the new fields on that custom object to Marketo. Once the schema is refreshed, please make sure that the global sync is turned back on. We would also suggest that you refer the below document which will guide you on the above steps. However, the below document is meant for first custom object sync. The same steps need to follow up for the existing object sync as well. SFDC Sync: Custom Object Sync Who This Solution Applies To Customers integrated with Salesforce
View full article
Issue Description You need to know if Salesforce Group Edition is compatible with Marketo   Issue Resolution Having a look at the comparison between the Group Edition and Professional Edition: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/dev_package_features_pe_ge.htm   We can see that a lot of features from the Professional Edition have been stripped in the Group Edition, m ainly the removal of Workflows, Campaigns and Custom profiles. These will most likely hinder how the Marketo CRM Connector operates.   The minimum would to be to have the Professional edition when syncing a native Salesforce CRM as per our Documentation on Sync Setup.   https://docs.marketo.com/display/public/DOCS/Setup   Who This Solution Applies To Salesforce users Is this article helpful ? YesNo
View full article
Issue Description You have two SFDC picklist fields mapped to one Marketo field but it isn't showing all picklist values for both SFDC fields. Issue Resolution When two SFDC picklist fields are mapped to one field in Marketo, the only values that will show in Marketo will be the values that exist in both picklists.  Review the picklist values in Salesforce and add any missing values to the picklists so that they match exactly. Who This Solution Applies To Customers integrated with Salesforce.
View full article
Issue Description When sending an email through the ToutApp Panel within Salesforce, what email server is used? Issue Resolution The Salesforce plugin will utilize the settings for your ToutApp.com sends. In ToutApp.com you can choose to send via the ToutApp Servers or via your company's outgoing email server.
View full article
Issue Description After deleting a lead or contact in Salesforce that has been synced to Marketo as a person record, attempting to merge that synced Person record with another Person record in Marketo keeps failing.   Issue Resolution When a merge is performed in Marketo, the Marketo Sync User will first automatically attempt to merge the associated records in Salesforce. If the records have been deleted in Salesforce this attempt to merge the records in Salesforce will fail, meaning that the rest of the merge operation will fail in Marketo.     To complete this merge, the best option is to perform the merge through the API. The Merge Leads endpoint allows you to skip the automatic Salesforce merge attempt that will always run when performing the merge through the Marketo UI. Marketo support does not troubleshoot or write custom API calls like this, so it is best to work with your in-house developer or IT staff to create these API calls.   http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Leads/mergeLeadsUsingPOST     Is this article helpful ? YesNo
View full article
Issue Description You would like to use the 'SFDC Oppty Campaign ID' as a constraint for the smart list filters ' Has Opportunity' and 'Opportunity was Updated', however, it does not appear as an option.     Issue Resolution By system design, there are some opportunity fields such as 'SFDC Oppty Campaign ID' that are restricted and cannot be made visible in Marketo as a constraint or filter.   One workaround is to create a custom field in Salesforce on the Opportunity object that holds the same value as the 'SFDC Optty Campaign ID' field. As a result, this field will appear in Field Management and become visible as a smart list constraint or filter in Marketo. If you would like to implement this, reach out to your SFDC admin.   Who This Solution Applies To Customers that have Salesforce integrated with Marketo Is this article helpful ? YesNo
View full article
Issue Description Large amounts of edits being made by "Unknown" user show up within the audit trail.   Issue Resolution If you have recently edited a field in Salesforce that utilizes a pick-list field type, the updates to the field will cause updates to propagate to any pages which use a form that uses that field.   Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo
View full article
Issue Description Marketo Email templates that have been used are showing or appearing within the Salesforce Email Template Picker/Chooser.   Issue Resolution 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 Is this article helpful ? YesNo
View full article
Issue Description When examining a lead's activity log, you notice a Sync Error which reads "CANNOT_EXECUTE_FLOW_TRIGGER: The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID ______________. Flow error messages: An unhandled fault has occurred in this flow. An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help."  Issue Resolution That error message is generated by Salesforce when Marketo tries to sync a lead that does not meet a trigger flow rule that is setup in your Salesforce instance.  Marketo has no visibility into this error message other than what is returned by Salesforce. Please take the full details of this error message to your SFDC Administrator or Support. They will be able to identify the flow or process which is preventing the sync update and make any necessary adjustments. Who This Solution Applies To Customers integrated with Salesforce
View full article
Issue Description 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! Issue Resolution 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. Who This Solution Applies To Marketo users that have an instance connected with Salesforce and are looking for a way to sync leads without them being assigned to a lead owner.
View full article
Issue Description Activity History in Saleforce shows this message: [Email details are being uploaded from Marketo...please check back later] when emails are sent out from the Marketo Outlook Plugin.   Issue Resolution This message is created because of insufficient privileges for the Marketo sync user inside of SFDC. There is a permission for “Edit HTML Templates” that needs to be enabled for the sync user in order to prevent this problem from occurring.   Background:   When you send an email using the Marketo Outlook plugin, it is sent through the user's Exchange server rather than Marketo's email servers. Many users have an email signature that is automatically added to the email. This adds additional HTML to the email, which does not match the template already in Salesforce Sales Insight.   Normally, Marketo would create a new template which Salesforce could then display in a link in the Activity History. However, in this case, the Marketo sync user does not have the necessary permissions, so this error results.   To fix this, enable the "Edit HTML Templates" permissions to your Marketo Sync User.   Who This Solution Applies To Customer who are using Sales Insight for Salesforce and Outlook Is this article helpful ? YesNo
View full article