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

My Salesforce activities are not showing up in Marketo and when I go to the Admin section I see the following sync error: soqlBatchQuery failed - INVALID_FIELD: CreatedDate, Description, Id, IsAllDayEvent, IsDeleted, OwnerId ^ ERROR at Row:1:Column:70 No such column 'IsAllDayEvent' on entity 'Event'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names. This is due to lack of permissions for the Marketo Sync User on the Salesforce side. Please have your Salesforce Administrator log into your instance of Salesforce and carry out the following steps: Log into Salesforce with Admin rights Click on your name drop-down and click on Setup In the left hand column, under App Setup, click on Customize Then click on Activities and then Event Fields Click on the All Day Event Field Label then "Set Field-Level Security" Here make sure to check the box under the Visible column for the Profile that the Marketo Sync User is associated to Click Save Once the above changes have been made on next sync we will begin pulling your Salesforce activities and once the next sync is over, the error message in the Marketo Admin section should go away.

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:

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.

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 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

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.

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.

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

Issue When there is a change to a field in your CRM that is mapped to a Marketo score type field, the next time the sync processes the change will be reverted and there will be a "Sync Person Updates" activity logged showing that the original value got pushed back from Marketo to the CRM. Solution Score type fields are designed to be managed solely by Marketo, since that is a unique field type to our system. Scoring is intended to be handled by the scoring campaigns that you set up in Marketo, and pushed to the CRM if necessary. If you have a score field that you intend to put processes in place where your CRM will be updating the values, simply make sure that the Marketo field that it is mapped to is an Integer type field.

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

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.

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 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

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Adding a Contact to a Salesforce Queue Creates a Duplicate Lead

Salesforce Activities Not Synching to Marketo and Show a Sync Error

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

Keep SFDC Fields or Records Out of Marketo

State field not pulling picklist from SFDC

Support Portal Access Issues

Marketo Program/Salesforce Campaign Status Mismatch

Large Influx of Records Syncing From SFDC to Marketo

Leads Not Syncing from SFDC to Marketo

Marketo Emails Are Showing Up in the Salesforce Email Template Selector

Smart List Error for Member of SFDC Campaign Filter

How to Sync Leads to Salesforce without Assigning a Lead Owner

Changes to Score Type Fields Made in the CRM Get Reverted by Marketo

Change in SFDC Instance Domain

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

Member Status Incompatibility When They Appear to Match in Marketo Program and SFDC Campaign

How to Sync New Marketo Person Records to Salesforce

Assignment Rules used for Add to SFDC Campaign Flow Steps

Email server used when sending Tout Emails from Salesforce

SFDC Sync Error: Cannot Execute Flow Trigger