Knowledgebase

Sort by:
Issue Can you remove a CRM from Marketo? Solution You cannot remove a CRM integration from an instance. Once the CRM of your choice is clicked (Dynamics or Salesforce) the instance is set to use that CRM for the remainder of its life. Once the login and mappings have been setup for a instance, the CRM instance or org cannot be changed as well. If for a reason you do need to change the CRM or the linked instance, you would want to reach out to your Customer Success Manager to get information on provisioning a new Marketo instance.  
View full article
Issue Can you sync Marketo multiple programs to a single Salesforce campaign? Solution Marketo only allows a 1:1 Relationship with Program/Campaign synchronization. If you try to sync a program to a campaign already used by another program you will recieve a error or prompt advising you cannot do it.    
View full article
Issue Error "API is not enabled for this Organization or Partner" occurs during Marketo - Salesforce integration.     Solution This is a Salesforce generated error and indicates that API access is not available in your SFDC instance.  For more information, see this Salesforce documentation: http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_concepts_core_data_objects.htm . To resolve this, contact Salesforce to enable API access.
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
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
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
Issue Marketo program Members are taking a long time to get updated in SFDC Campaigns.   Solution The Marketo Program to Campaign sync is not real time and will take time to update. The feature is dependent on the Marketo to SFDC background bi-directional sync. Marketo will generally sync SFDC and Marketo objects in the following order: Lead Account Contact User Task Opportunity Opportunity Contact Role Campaign Campaign Member Campaign Member Status As per the order, Campaign related objects are towards the bottom of the list. This means that all objects above it are synced first, and if there are any backlogs on those objects, the Campaign objects can queue up and cause delays.      
View full article
  This is a article attached image Upon signing a contract with Marketo you are provisioned a Marketo instance and a Support Service. There are four different types of Support Services which are available to meet different customer support needs: Online (Legacy) Business  or PREMIER SUPPORT BUSINESS (Legacy) Premier or PREMIER SUPPORT ENTERPRISE (Legacy) Elite or PREMIER SUPPORT ELITE Each Support Service has a different Service Level Target (SLT). An SLT is the amount of time Marketo Support targets to make first contact with you after a support case has been submitted. SLTs differ for each Support Service and priority level. Priority levels range from Priority P1 to Priority P4. Here are the SLTs and priority levels for each Support Service:   Priority Online (Legacy) Business PREMIER SUPPORT BUSINESS (Legacy) Premier PREMIER SUPPORT ENTERPRISE (Legacy) Elite PREMIER SUPPORT ELITE P1 1 hour 1 hour 1 hour 30 minutes 30 minutes 30 minutes 15 minutes P2 4 hours 3 hours 2 hours 2 hours 1 hour 2 hours 30 minutes P3 6 hours 5 hours 4 hours 4 hours 2 hours 2 hours 1 hour P4 3 days 1 day 1 day 1 day 1 day 1 day 1 day   Here are the descriptions for each priority level: Priority Description P1 Mission Critical:  Core business function down or potential loss of mission critical data P2 Urgent:  Major feature or workflow is not functioning. Mission critical workflow and majority of user community is not blocked P3 Important:  Normal usability or task completion is impacted but functional, or workaround is available P4 Minor:  Minor issue requiring a correction. Normal workflow is not impacted   Find more information About Support here!  
View full article
Summary Marketo-only records must be manually synced, become a member of a default-program, encounter a Salesforce flow step in order to sync with Salesforce. Issue Records are in the Marketo database but are not syncing over to Salesforce automatically like I thought they would. Solution The sync between Marketo and Salesforce is bi-directional. However, in order for a record to be synced, one of the following conditions must be met: The record becomes a member of a program which is synced to a Salesforce campaign. This occurs when the background sync is used to keep members of a Salesforce campaign in sync with a Marketo Program status. This can easily be verified by navigating to the program and looking at the summary view. More information on this feature can be found here: https://docs.marketo.com/display/public/DOCS/Sync+an+SFDC+Campaign+with+a+Program https://docs.marketo.com/display/public/DOCS/SFDC+Sync%3A+Campaign+Sync The record encounters an SFDC flow step. Any time a record encounters a Salesforce related flow step in a smart campaign, this will cause the record to sync with Salesforce. Some of these flow steps have other implied actions, which you can read about here: https://docs.marketo.com/display/public/DOCS/Implied+Salesforce+Actions The record is manually synced to Salesforce through a single-flow action. This is an intentional user action. It can only occur when you find the record in your database or in the people tab of a smart list and select the option from the 'Person Actions' menu. More on how to do this can be found in this document: https://docs.marketo.com/display/public/DOCS/Run+a+Single+Flow+Step+from+a+Smart+List Root Cause Records had not encountered SFDC flow steps, become members of a program synced with a Salesforce campaign and hat not been manually synced to Salesforce. Environment Marketo with the built-in integration with Salesforce
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 90 days, 25 months, or 37 if you have purchased the premium data retention option. The official Marketo Data Retention Policy can be found here:  Marketo Activities Data Retention Policy   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
The fields and records that will sync from Salesforce are defined by the permissions of the Marketo sync user. Therefore, if you want to prevent specific records or fields from syncing with Marketo, change the permissions of the sync user so they do not have access to the records and fields you do want to sync. Alternatively, you can work with Marketo Support to set up a Custom Sync Filter that will prevent records from syncing based on the value in a specified field. Restricting Leads from Syncing to SFDC With Sync Filters 
View full article
Once your Marketo instance is integrated with a CRM, either Salesforce or MS Dynamics, that integration cannot be switched.  You cannot switch from one CRM to another, and you also cannot switch from one instance of your CRM to another instance.  If you need to switch CRMs, or if you need to connect Marketo with a different instance of your CRM, you will need to contact your Customer Success Manager to have a new Marketo instance provisioned.
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
Problem/Issue: When you view a lead’s activity history, you noticed a failed sync activity type with the following example: Reason/Cause: This message is very general and can be caused by a number of sync related errors. In order to get more information, you will need to double-click the error message and a separate pop-up window will appear. Search for the section labeled: “SFDC Error:” like the following example:     Fix/Solution: Depending what the error message is, Salesforce provides a website that lists all Core Data Types used in API calls.   You can access it by clicking here .
View full article
Issue: You have Opportunities in Salesforce but they are not showing in Marketo.    Solution: 1) Check Opportunity permissions in Salesforce - Your first line of troubleshooting this issue is to ensure that the Salesforce profile being used by your Marketo sync user has the Create/ReadEdit/Delete access on the Opportunities object in Salesforce.     2) Check the "Contact Roles" Related List - Ensure that the "Contact Roles" Related List in Salesforce under the Opportunity's detail page is populated     3) Ensure that the Marketo sync user has visibility in Salesforce to see the Opportunity - Log in to Salesforce with the Marketo sync user and ensure that the missing Opportunity in Marketo is visible to this Marketo sync user. If the Marketo sync user can't see the Opportunity then the Opportunity will not sync to Marketo.   4) Check to see the time that the Opportunity was created in Salesforce - Often times you have all the correct Opportunities permissions in Salesforce but the Opportunities are still not showing in Marketo because the Opportunity was recently created and you have not allowed enough time for that Opportunity to sync to Marketo. In this scenario, the only thing you can to is wait. If your sync is busy processing other items, you usually need to wait for these pending items to sync before the newly created Opportunity will sync to Marketo.
View full article
Marketo has the ability to see and pull data from Salesforce Formula fields, there is however a catch which will be explained in this article.   Everytime the Marketo Sync connects to Salesforce, it will scan records and look at the " SytemModStamp " (salesforce system field) for each one of them. It will compare this value with the stored value, which was pulled at the last scheduled sync. If the values match, Marketo will move on to the next record. If the values are different (new value later date than previous value) , then Marketo will do a compare and contrast of all fields on that record in both systems and update the information as needed.   When a normal non-formula field is updated and changed on a Lead/Contact record in SFDC, the SytemModStamp value is updated. This is how on next sync Marketo knows to do a compare/contrast check and pull updates. Formula fields do not behave the same way. A formula field is calculated based on data in fields called upon in the formula; this means that the formula field calculation itself will not update the SytemModStamp in Salesforce.   Chances are you already have existing records in SFDC and Marketo. If you were to create a formula field today in your instance of SFDC and have it sync down into Marketo, the data calculated for the formula field in SFDC will not come into Marketo right away. The reason for this is, the formula field has created data based on already existing data, this does not result in a SytemModStamp change.   Typically formula fields will be a calculation of data from fields which are somehow related to the lead/contact record. This means that moving forward, any change in the normal field, will result in a SytemModStamp change as well as a recalculation of the formula field. In this case, Marketo will see the updated SytemModStamp due to the normal field change. Marketo will do the compare/contrast excercise and find that the formula field also needs updating.   If you create a formula field in SFDC and would like to have all the historical data for the formula field to come into Marketo, you can force an update on the records in SFDC to update the SytemModStamp. This way, on next sync, Marketo will see the formula data and pull it in. Alternatively, you can simply allow for natural SytemModStamp updates in SFDC to occur which should result in a slow trickle of historical data from SFDC into Marketo for the newly created formula field.   You can only use data from a formula field in Marketo to segment data and filter. If you try to do a change data value, Marketo will accept the change, tries to sync it to Salesforce and fails to update there. Eventually the Salesforce calculated value will come back into Marketo.  
View full article
Issue Description: Salesforce refreshed your sandbox and it no longer syncs with Marketo Issue Resolution: As a safety precaution, once an instance of Salesforce is synced up with Marketo, we no longer allow the user to sync this particular instance of Marketo with any other instance of Salesforce. When Salesforce does a “refresh” of your sandbox, they are actually canceling your old sandbox account and creating a new account and pulling fresh data from your production. This means the refreshed sandbox is actually a different account and has a new OrgID. Marketo Support can assist by unlocking your Marketo sandbox to be synced up with a refreshed Salesforce sandbox. If you run into this scenario, please create a support ticket requesting that we enable the reset of the OrgID for your SFDC sandbox.
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.     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):     Note if the lead or contact is not in Salesforce then there is no link to the Salesforce detail page:  
View full article
Question: Is it possible to assign a lead owner during a list import?   Answer: No. The reason for this is because lead ownership is a Salesforce functionality and should be first done from within Salesforce. Here is one of the easiest options available to you within Marketo, if you are not able to do the assignment in Salesforce:   1) Upload yours leads into Marketo's Lead Database without lead owner information. i.e. your import CSV will not have any lead owner columns in it. More information on import leads at Import a List of Leads from a Spreadsheet into Marketo (Import List) .   2) Once the list import is successfully completed and your leads are in Marketo, you can use the "Sync Person to SFDC" flow action to assign lead ownership. More information on the "Sync Person to SFDC" flow action at Sync Person to SFDC .
View full article
When you ask Marketo to add a Salesforce contact to a lead queue, Marketo creates a duplicate lead in Salesforce and adds that to the queue instead. The reason why Marketo creates a duplicate is because Salesforce queues can only have leads in them, not contacts.  If you try to add a contact to a queue, Marketo can either do nothing or create a duplicate lead and add that to the queue.  We opted for the duplicate.   If you want to prevent this behavior in your campaigns, use a filter on "SFDC Type is Lead" to limit the action to only leads    
View full article