Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

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

Issue You come across a few leads who failed to sync to SFDC and would like to have the list of leads who faced the same issue. Solution Unfortunately Marketo doesn't have a specific type of filter to leads who failed to sync to SFDC. However if they are new leads who haven’t synced to SFDC, then you can filter them by using the filters "Person was created" and "SFDC Type" with condition "is empty". If you want to find the list of leads (previously synced to SFDC) who failed to sync among a particular group of leads, you can filter by following the below steps. 1. Create a new Boolean type field in SFDC namely "Sync Error?" and with the default value as "true". 2. Wait for the field to sync into Marketo. 3. Create a Smart Campaign to select those group of records and the flow steps to change the value of the Boolean field "Sync Error?" to ”False" and then "Sync person to SFDC". 4. Once the campaign has finished running, you will be to pull a report on SFDC on the list of leads who have the value "True" for the field "Sync Error?". It means that the value was not updated to SFDC as the record failed to sync. With this list you will be able to select the records and resolve the sync issue. You can also create a smart list of leads who were never able to sync with the following filters: Lead was synced to SFDC : Assign to : is not empty SFDC Type: is Empty

Issue Syncing a SFDC custom field that is not on the Lead, Contact, or Account object. Solution Any custom field created in Salesforce that is not linked with Lead, Contact or Account objects will not sync to Marketo. Only the Lead, Contact and Account objects can be synced down to Marketo by default. If you would like to have any custom field synced to Marketo, it must be associated to a Lead, Contact or Account object in Salesforce. Custom Objects created in your Salesforce instance can be part of Marketo too. To use a custom object in Marketo, it must be associated to a Lead, Contact or Account object in Salesforce as well. For more information on syncing Salesforce Custom Objects, please see the documentation here: SFDC Sync: Custom Object Sync. Fields on the SFDC Custom Object do not become fields in the Marketo lead database, but can be used as filter constraints on Custom Object filters - Add/Remove Custom Object Field as Smart List/Trigger Constraints.

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

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.

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.

Issue When using the Filter 'Member of SFDC Campaign' in the Smart List and checking the people tab to see which records are qualified, this message occurs: Could not evaluate rule 1 (SFDC Campaign 'Campaign Name' not found) Note: it may state could not evaluate rule # - # can be any number, if the filter is number 5. # will equal 5 Solution The Fix Ensure the that the SFDC Campaign being referenced in the Smart List is an ACTIVE campaign The Why This error occurs due to the SFDC Campaign not being an active campaign in SFDC. You may be wondering "Then why can I select the SFDC campaign in the drop down?" This is because the Smart List Filter specifically 'Member of SFDC Campaign' similar to 'Has Opportunity' filter reference a backend table in Marketo. This backend table is updated when a SFDC Campaign is removed or renamed. Therefore, Marketo does not directly perform an API call to check if the campaign is selectable, but rather uses the backend table as reference. One way to check in Marketo if the SFDC Campaign is active is to check the 'Added to SFDC Campaign' Trigger in a Smart Campaign's Smart List as that dropdown will only show active campaigns.

Issue: You or your sales reps are getting an error when editing your leads or contact records in Salesforce saying "The record you were editing was modified by Account Marketo during your edit session". This error will usually occur in Salesforce when you are in the Edit page in while at the same time the Marketo sync is updating that same record by our periodic API sync. While this error occurs very rarely, and usually by performing mass updates from Marketo (usually by batch campaigns). Resolution: Here are some steps you can take from a Marketo perspective to resolve or significantly reduce the chances of this error occurring: 1. Change the process that you use to update records in Salesforce - You can successfully reduce this error by using Inline editing (by double clicking on the individual field on the record) as opposed to doing a mass update of multiple fields on 1 record (by using the Edit button). Inline Editing - As the screenshot below shows, this done by double clicking on the individual field on your record then updating the field and then pressing the "Save" button or double pressing on the Enter key on your keyboard. Mass Editing - this is done by first pressing the "Edit" button on the record's detail page, which will then take you the the Edit page where you can mass update multiple records then press the "Save" button. 2. Increase the Salesforce sync interval time - Another option to reduce the the possibility or receiving this error is to reduce the number of times that Marketo syncs with Salesforce. This option in effect increases the time between Marketo and salesforce syncs. (The default is 5 minutes.) The downside to this option is that updates made in Marketo will take a longer to sync to Salesforce and vice versa. If you want to proceed with this option, you will need to contact Marketo support to get your sync wait time increased.

Issue 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. Solution 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.

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.

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.

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.

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:

Issue Salesforce is going to change your instance sub-domain from NA#1.salesforce.com to NA#2.salesforce.com. What measures should you take in order to make sure that our sync works? Solution Marketo accesses SFDC with the API login endpoint, so a change in the login domain that you use would not affect the Sync user. Marketo and SFDC sync should continue to work irrespective what domain SFDC belongs to. If a change happened to SFDC that affected the sync user, such as its credentials or the SFDC OrgID changed, then Marketo would need to be updated If there is an issue with your sync after updating the SFDC domain, try the following to resolve the issuce. Change your SFDC Sync User's password. Issue a new security token. Re-enter the credentials within Marketo Admin >Salesforce. If it doesnt resolve the sync issue, contact Marketo support and they will be able to help you out.

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

Issue You may notice that there may be a block in SFDC that stops syncing unsubscribes from Marketo to SFDC. After fixing the block in SFDC the new unsubscribes will sync as expected. Here is how to get all the unsubscribes that happened before this fix to sync into SFDC. Solution You would need to set up a campaign to reset the field value. Smart list: Unsubscribed = true Flow: Change data value "unsubscribed" -> False Change data value "unsubscribed" -> True That would take everyone who is currently unsubscribed, switch to false and then back to true. That should cause the true value to sync up to SFDC for all of those records. However, make sure you do this at a time when you are absolutely positive there are no email campaigns going out.

Issue 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. Solution 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

Summary Mismatch between "Added to [custom object]" and "Has [custom object]" filters for a SFDC Custom object Issue You build a Smart List for "Added to [custom object]" for your SFDC Custom object and you notice the number of records qualifying is lower than expected. The "Has [custom object]" filter pulls more records, however, and matches what you see in SFDC. Environment SFDC/Marketo Solution This is expected behavior if you have records that were already associated to the SFDC Custom object before they were pushed to Marketo. If you have records that were already associated to the SFDC Custom object before they initially synced to Marketo, those records would not have an "Added to [SFDC Custom Object]" activity on their record in Marketo, which means they would not qualify for the "Was added to [SFDC Custom Object] Smart List filter" In this scenario, it is recommended to use the "Has [SFDC Custom Object]" filter to get the accurate numbers, as this should include all Marketo records that are associated to the Custom Object, even if they were added to it prior to being synced and created in Marketo. Root Cause Records already being associated to the SFDC Custom object before they were initially synced to Marketo.

Issue Program member custom fields are not syncing data to Salesforce campaign member fields even though they are mapped. In this setup, the sync for Campaign Members is being performed by 'Add to SFDC Campaign' or 'Change Status in SFDC' flow-steps, but the Program itself is not set to sync with an SFDC Campaign. Environment SFDC Integration Solution This is the expected behavior, as the program member custom fields will only sync data to campaign member fields when the Salesforce Campaign Sync is setup for the Instance/Program in question. Using flow steps to sync SFDC Campaign Members will not carry over data for Program Member Custom Fields. Root Cause SFDC Campaign Sync is not enabled. Enable/Disable Campaign Sync Enable/Disable Campaign Sync | Adobe Marketo Engage Program Member Custom Field Sync Program Member Custom Field Sync | Adobe Marketo Engage

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Adding a Contact to a Salesforce Queue Creates a Duplicate Lead

Filter Out the List of Leads Who Failed to Sync to SFDC

Syncing Custom Field Created in Salesforce Standard and Custom Objects

Marketo Emails Are Showing Up in the Salesforce Email Template Selector

SFDC Integration Error: API Is Not Enabled for This Organization or Partner

State field not pulling picklist from SFDC

Smart List Error – Could Not Evaluate Rule 1 (SFDC Campaign ‘Campaign Name’ Not Found)

Getting Error “The Record You Were Editing Was by Modified by Account Marketo during Your Edit Session” in Salesforce

“Opportunity Campaign ID” Field Not Available in Smart List Filter Constraint Options

How to check if an SFDC sync user can see a field

Smart List Error for Member of SFDC Campaign Filter

How to Sync Leads to Salesforce without Assigning a Lead Owner

My Activities in Salesforce Appear as “Open Activities” Instead of in the “Activity History”

Change in SFDC Instance Domain

Assignment Rules used for Add to SFDC Campaign Flow Steps

Sync past Unsubscribes into SFDC

SFDC Error Unable to process due to no XML response from Salesforce

SFDC Activity History Shows Message: [Email Details Are Being Uploaded from Marketo…Please Check Back Later]

Mismatch between "Added to [custom object]" and "Has [custom object]" filters

Program Member Custom Field Data Not Syncing To SFDC Campaign Members