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

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue Description After sending a group email or campaign with a list of contacts, some contacts are being removed after the emails are marked as spam. Issue Resolution One of the greatest benefits of ToutApp is to utilize the group email function and dynamically change fields for specific contacts. Of course, that does not work out if there aren't any people in your group. Here are a few items you would like to check: Are you using a custom SMTP server? If so, then check with your IT team to have them investigate if these emails are being bounced. Sometimes custom servers will only send the action to perform to ToutApp. Are you using a custom header? Custom headers are used to send emails that have your reply to or from list your company domain rather than via ToutApp. There are some instances that if you are not using a custom header, then emails will be marked as spam. Are you up-to-date? It is always best to make sure that your Outlook plugin and/or Chrome extension are updated Still no working? This is an opportunity to test. Try switching your Email Delivery Channel, send an email without a template, or reset your connections. Who This Solution Applies To ToutApp Is this article helpful ? YesNo

Issue External tracked webpages are not showing up in "Visited Webpage" or "Filled Out Form" Smart List filter. Solution Munchkin tracked pages will not show up in Smart List filters until a known lead visits the webpage. To make sure the webpage shows up, do the following: Make sure that you have the Munchkin tracking code on those webpages. Use a test lead to visit the page and you may have to fill out a form or send an email to the lead to make sure that the lead is tracking on your machine. Check the test lead's activity history to make sure the visit is logged. Try entering the webpage in the filter again. Note :- Customizing Munchkin code can also be responsible for the same.

Issue Description When attempting to add an additional Facebook or LinkedIn Launchpoint service, it does not appear as an option in the drop down. Issue Resolution While we only support one Launchpoint service for each integration type, we support multiple accounts through the Launchpoint service that the customer adds. The user account that is used to authenticate the service will need to have the appropriate permissions to each business page that is going to be used by the instance.

Issue Issue Description Smart Campaigns with email flow steps do not show when they ran on the Marketing Calendar. Solution Issue Resolution Smart Campaigns must be scheduled using the "Run later" selection for one time batches. If the campaign was set using the "Run now" option for a one time batch then there is not a "scheduled" run time to reflect on the Calendar. In order to have Smart Campaigns reflect on the Calendar use the "Run later" option.

At Marketo we take security seriously. As a part of an industry-wide initiative, Marketo is upgrading our web authentication and encryption to enhance our security protections. The rollout is scheduled to occur on December 12, 2015. Who will be affected? Only a small number of users will be affected, only those who have an integration to Marketo from a system that is over ten years old and hasn't been updated recently. See this list for more info on what systems and versions are supported. The following users will not be impacted: End users accessing Marketo.com through modern browsers (see list) Customers using integration partners such as Informatica, Dell Boomi, and Scribe. Customers using Launchpoint partners. Rollout schedule The following rollout schedule is planned: Service URL SHA-2 Rollout Date API access mktoapi.com Dec 12, 2015 API access mktoresp.com Dec 12, 2015 Part of MLM Application marketodesigner.com Dec 12, 2015 All other Marketo domains already use SHA2 certificates.

Issue Issue Description Marketo secure tracking links give an insecure connection message when clicked, but this happens only when accessed from an internal corporate network. Solution Issue Resolution If the error only happens on your corporate network, it is most likely caused by internal DNS routing that is specific to your network configuration. Work with your company's IT department to determine what changes need to be made to your DNS routing to resolve this issue. Who This Solution Applies To Customers using Marketo Secure Tracking Links

Issue Description A lead ran through a smart campaign and should have been sent a push notification but there is no activity of this happening even though the lead is a member of the campaign. Issue Resolution Assuming other leads are receiving the push notification (which suggests the app itself is not to blame) the first thing to check is the lead record itself. If the lead is marked as Marketing Suspended or Black Listed, this will prevent the record from receiving a push notification. Mark these fields as "False" and send the record through the campaign again, the lead should now be sent the push notification. Who This Solution Applies To Customers using Marketo's mobile app integration

Issue Issue Description Marketo Secured Landing Page using domain aliases give an invalid SSL certificate error on load. Solution Issue Resolution Confirm that the domain alias is a CNAME and not another type of record such as an A RECORD. Within Marketo's Documentation for setting up landing pages and tracking links, it only specifies a CNAME configuration. This is the only configuration that is supported. If another configuration happens to work, it does not mean it will continue to do so and will throw an error once SSL is enabled. Below is a diagram showing the configuration that is supported by Marketo. The Top Level Domain is owned and hosted by the Customer. Separate sub-domains, or CNAMEs, are created, one for each Landing Pages and Tracking Links. These CNAMEs then reference Marketo. Other ways of configuring this are not supported due to not being reliable. An A RECORD for example, can point a Domain directly to an IP Address. This can be unreliable because an IP Address can easily and frequently change. As a Domain name is usually synonymous with a Company name, any change is infrequent and usually manual. *Tracking Links only require a sub-domain and SSL if you wish to have them branded. If instance reflects the 'mkto.aa######.com' for tracking links, they are covered under Marketos SSL certificate. Who This Solution Applies To Customers with Secured Landing Pages who also use domain aliases

When doing a list import, sometimes the dialog box won’t advance past the Step 2 section where columns are mapped to Marketo fields. If you look closely, you’ll see that there is a Marketo Field selected that has a red squiggly underline underneath it. If any of the fields have this, you won’t be able to click on Next to get to Step 3 and the import dialog box will get “stuck” at this point. This problem is caused by having two columns in your list mapped to the same one Marketo Field. Two pieces of data can’t be pushed into the same one field, so it stops the import in its tracks at this point until you change it to select a different field. If you mouse-over that field, you’ll get the error that shows that the field is already in use. The quickest way to fix this is to simply choose a different Marketo Field to map the list column to. Once there aren’t any more Marketo Fields used twice, the import dialog box will advance to Step 3. Problem solved!

This document provides an overview of the recent Munchkin Activities Recording Issue that impacted a subset of customers across our data centers beginning on April 24, 2019. All customers that were impacted were emailed details of the incident on May 1, 2019. If you are unsure if your instance was impacted, please reach out to Marketo support at support.marketo.com. Start time: London data center, April 24, 2019, 4:30 PM PDT Sydney data center, April 26, 2019, 2:00 PM PDT San Jose and Ashburn data centers, April 26, 2019, 5:30 PM PDT How to identify what data center your instance is located in: You can deduce the server locations by looking at the URL of your instance. The CNAME=the pod or server your instance is on. The example above indicates that this instance is in our Ashburn data center. The abbreviations for all our data centers are as follows. lon = London sn = Sydney sj = San Jose ab = Ashburn End time: Updated patch was pushed April 30, 2019, 3:40 PM PDT Service affected: A subset of Marketo customers may have experienced Munchkin activities coming from web pages (clicks, visits) that were not being logged in activity logs. Since the activities were not immediately registered, any Trigger Campaigns set to initiate when those activities occurred would not have been triggered. What happened: This issue originated from a patch deployed during a recent release. The patch was designed to update the process used to determine if a subscription’s web traffic should be retained. An error in the patch code caused one of the evaluation parameters to be missed, resulting in web traffic activity not being logged. Remediation: Once the cause was identified, our team developed and deployed a patch on April 30, 2019, to correct the piece of code that introduced this issue. To backfill the activity data that was not recorded during the impacted timeframe, our team has developed a script to restore the data back into our activity logs, so no data will be lost. We expect this data fix to be complete on May 24, 2019. Campaigns that would have been initiated by the activities that occurred during the impacted timeframe will not be replayed. If you need assistance to identify which smart campaigns were active during this incident, our Campaign inspector is a great tool to assist you. You can use this to search for active campaigns that use specific triggers (“visits web page” or “clicks link on web page”). Replay Impacted Smart Campaign: After you have identified the smart campaigns that may have been impacted, create a new smart campaign using the following smart list filters. For smart campaigns triggered by clicking a link on a web page, use the following filters. Select the applicable link and timeframe based off what data center your instance is located in. The second filter is to prevent activities that were not impacted by this incident. For smart campaigns triggered by a web page visit, use the following filters. Select the applicable web page and timeframe based off what data center your instance is located in. The second filter is to prevent activities that were not impacted by this incident. After the smart list is set up, the flow steps should mirror the flow steps of the original smart campaign that you wish to replay. If you experience any issues with replaying the impacted smart campaigns, please contact Marketo support at support.marketo.com, or through any of the methods listed here.

Issue Description We have a custom landing page template and we were able to see that landing page is not rendering perfectly on the editor but works as expected when published. How can I troubleshoot on this issue? Issue Resolution As you are facing the issue on a custom template, we suggest you to follow the below steps. Download a template form the URL- https://docs.marketo.com/display/DOCS/Guided+Landing+Page+Template https://docs.marketo.com/display/DOCS/Guided+Landing+Page+TemplatesIn Marketo, navigate to the Design Studio. Click Landing Pages in the left-hand tree, then select Templates. In the menu bar, click Import Template. Choose the downloaded file, enter a template name, then click Import (make sure to pick a descriptive name and indicate that editing mode is Guided). Create a new Landing page with the recently downloaded template without making any changes. If the default background image works on this landing page as expected, it confirms that the issue lies with the custom coding that was added to the template. Marketo Support is not set up to assist with troubleshooting custom code. The best point of contact will be your web developer who should be able to resolve the issue for you. Please be aware that the landing page editor may not load all external resources in the editor or previewer, which can cause them to look different than the published version. If the background image doesn’t render on this newly downloaded template as well, contact support and we will be able to troubleshoot your issue.

Issue You need to set up DKIM for deliverability with Marketo, but another system you use already has DKIM set up with the default m1 selector. Solution You can create a Support ticket to request a custom DKIM selector be created (usually m2) for use in the "From Email" field on Email assets. Let support know what selector you want to use, and the domain you're want it to apply to- this is the domain value used in email assets, so for example@company.com, the domain would be "company.com" This will allow your existing integration to utilize the m1 selector, and Marketo can have DKIM under another domain.

Issue Issue Description "${button-link}" appears on the Email Link Performance report in place of the URL the buttons point to. Solution Issue Resolution To stop this "${button-link}" from appearing on the reports, edit the text version of the emails to replace the "${button-link}" with the URL the button points to. This occurs because the text version of the email didn't get edited to provide a valid button link. The "${button-link}" value is part of HTML templates and if the setting 'Copy HTML to Text version of email' is checked then those values get copied across. From there, if the text version doesn't get edited or reviewed after that copy over happens, tracked links for "http://${button-link}?mkt_tok=..." will be sent out for those leads that get the text version of the email in place of the URL the button points to. The next question after hearing this solution is often, "If this is just for the text version, who is reading the text version of emails?", and the answer is that it's probably automated link scanners or security software visiting the link and triggering the click to show on reports.

Issue Description Currency type fields are changing unexpectedly. It may appear that they are being rounded off at first glance, but a better description is that they are being approximated imprecisely. This is a feature of all floating point values. For example: if you enter the value as 8092384905, Marketo will truncate it to 8092390000. Issue Resolution This is an expected behavior. Currency type fields are stored as single precision float values which have 6-7 digits of significance. Since standard fields type cannot be changed, we suggest that you create a new custom field to hold the currency value. Human-readable Values: Strings Often the easiest work-around for larger currency values is to use a field of type "String". String fields are adequate for storing a value, but do not offer the capability to compare (between, greater than, less than, at least, at most) values. Comparable Values: Integers To preserve comparison capability, store the value as an integer which can take on values from -2147483647 to 2147483647. For US Dollars, this integer can represent the number of cents (pennies) and therefore currency values from ($21,474,836.47) to $21,474,836.47. Using this technique, the operators between, greater than, less than, at least, and at most will work, just remember you're what you're comparing: cents in this example. Even Larger Comparable Values: Compound Integers If even larger values are required, two integer fields (large and small) can be used to represent currencies (again, assuming cents) from ($46,116,860,141,324,206.00) to $46,116,860,141,324,206.00. To break up a currency value into two fields, divide the number of cents by 2147483647 and store in the large value field, then store the remainder (modulus) in the small value field. To compare a compound (two fields) value, compare the large values first and if they are equal, then compare the small values. Since compound fields will be hard for a human to read, it may be prudent to also store the value as a string depending on your requirements. Is this article helpful ? YesNo

Issue Initial MS Dynamics sync gives the error 'is missing prvReadSdkMessageProcessingStep privilege' Environment MS Dynamics CRM integration Solution Issue Resolution These permissions, found within Security Role, require a Microsoft Dynamics Admin to set and change., Navigate to Settings > System > Security and select Security Roles icon. Click on the Marketo Sync User to bring up the individual access level for each individual entity. For the sync to work the individual privileges are as follows: Under 'Core Records': Under 'Customisation': Under 'Custom Entities': Any role with Marketo needs to have all permissions. More information on Managing Users and Security Roles can be found on the Microsoft Dynamics Site: https://docs.microsoft.com/en-us/dynamics365/customer-engagement/marketing/manage-users Root Cause The error indicates the Marketo Sync User in Dynamics lacks some of the required permissions for the sync.

Issue Description In a recent engagement with support you had your Leads restored, or you plan on restoring your Lead Record. Lead records that are restored will not be able to sync backup with Dynamics. Issue Resolution If the instance is using Microsoft Dynamics sync then the restored lead will not be able to link between Microsoft Dynamics and Marketo. The lead will exist in Marketo (in the backend, it will keep the MS Dynamics GUID) but it will NOT sync data between the systems. If the lead is synced down from Microsoft Dynamics then it will create a duplicate lead which cannot be merged. Who This Solution Applies To Dynamics Users

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

ToutApp: Contacts are being removed from Groups or People tab

Webpage Not Showing up in Visited Webpage or Filled out Form Smart List Filter

Unable to add multiple Facebook/LinkedIn services

Marketing Calendar Does Not Show Some Email Smart Campaigns

Marketo Security Enhancements

Secure Tracking Links Showing Insecure on Internal Networks Only

Push Notifications not Sent

Secured Landing Page Aliases Giving SSL Certificate Invalid Error

How to Cache or Freeze a List with Random Sample

TROUBLESHOOTING—List Import Dialog Box “Stuck” on Step 2

Munchkin Activities Recording Issue – Trigger Replay Overview

Enable Multiple Selections From a Picklist in Marketo Forms

Troubleshooting background image not being rendered on landing page editor

Custom DKIM Selector

Email Link Performance Report Shows "${button-link}" Instead of URL

Currency type field is rounding off its value

MS Dynamics Initial Sync Gives Privilege Error

Restored Leads not syncing back up with Dynamics

Link performance report for specific campaign/program emails

Cannot access 'Login' field with 'Login in Invite User Dialog' feature enabled