Knowledgebase

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 You are unable to abort a triggered Smart Campaign currently in progress. Solution The "Abort Campaign" function only works for batch campaigns. To stop leads from going through the flow of a triggered campaign, do the following: Deactivate the trigger campaign in the Schedule tab. This will prevent new leads from entering the campaign flow steps. It will not stop leads that have already entered from continuing through the flow. Use a "Remove from Flow" step to remove existing campaign members from the flow. This can be done a few different ways. View Campaign Members > Select All > Lead Actions > Special > Remove from Flow If the leads are in a Wait Step, you can add a Remove From Flow step after the Wait Step in the trigger campaign Create a small batch campaign with a "Member of Smart Campaign" Smart List filter and a "Remove from Flow" flow step that specifies the trigger campaign you want to remove them from.

Issue Issue Description You may see this warning message on your website, "The SSL certificate used to load resources from munchkin.marketo.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See g.co/chrome/symantecpkicerts for more information. Solution Issue Resolution Marketo's security and operations team are aware of the plans for Chrome to distrust Symantec issued certificates and we are working on the replacement project before this happens.

Issue Description You have the Munchkin tracking code on your non-Marketo web page but visits to the page are not being tracked. Issue Resolution If you have customized the Munchkin tracking code, it may not work. Marketo only supports the Munchkin code as it is provided in your instance. If you need to alter the code, you would need to work with your web developer to determine why the customized code is not working. To find the supported Munchkin tracking code: Go to Admin > Munchkin. Select the version of Munchkin you intend to use. Place the Munchkin code on your page as outlined in our document on adding Munchkin tracking to your site. Is this article helpful ? YesNo

Issue Issue Description An email with inserted bold/italic font in email subject line is not approving, with an error of "Cannot Update Stale Object," or does approve but the special font text disappears upon approval. Solution Issue Resolution The subject line in an email is intended to be plain text. Some have found success inserting basic symbols, or even emoji with specific encoding, though the rendering of these characters is dependent on the receiving server. Related: Using Emojis in Marketo Emails

Executable campaigns are a powerful new feature designed to allow you to make your campaign logic modular, reusable and maintainable. However, staying within the limit of three nested executables can be difficult when your campaign trees get complicated. This article describes a simple method of classifying your executables into three categories to help you stay within the nesting limits while also remaining productive. Three Categories for Executable Campaigns This classification system has three categories with simple definitions: Tier 1: These campaigns may not be executed by other executable campaigns Tier 2: These campaigns may not execute other Tier 2 campaigns Tier 3: These campaigns may not execute any other campaigns By classifying your campaigns in this way, and abiding by their restrictions, you can avoid bumping up against the nesting limit. Now we have a way to avoid the nesting limit, but how should you map your existing campaign logic and lifecycles into these categories? Let’s look at Tier 3 first, as it is the foundation of this model Tier 3 – Task/Unit - May Not Execute Any Other Campaigns Tier 3 cannot execute any other campaigns, and this is where individual tasks should be implemented. Your organization can define what a task is in this context, but I think that it is useful to borrow the definition of unit from software development: A unit is the smallest testable part of any software. In the context of Marketo, a unit is the smallest testable part of any campaign. Let’s look at a common example for lead lifecycles: Taking a country input and outputting a country code to a different field. The above is an abbreviated example using flow-step choices to match the value of Country to a particular country code. Supposing we wrote a test for this, we would expect a lead who enters the flow with an empty value of “United States of America” to receive a Country Code value of “US”. This or similar steps could be a unit for your business, but you do not need to limit your units to single steps. Your Tier 3 task campaigns should tend to be short sequences of work which are used in multiple contexts Tier 2 – Orchestration – May Not Execute Other Tier 2 Campaigns Tier 2 (as well as Tier 1) are more flexible than Tier 3 campaigns as they can execute other campaigns themselves. These executables can be used to string sequences of other campaigns together alongside standalone flow steps. An example would be a Standard Data Enrichment campaign. Where normalizing a country code is a unit or task, this is a sequence of one or more data enrichment tasks that can be maintained and modified separately from the logic of the individual tasks themselves Tier 1 – Last-Mile – May Not Be Executed by Other Executable Campaigns You may find that your business does not need to use Tier 1 campaigns, and that you can satisfy your organizational needs with just Tier 2 & 3 campaigns. However, Tier 1 campaigns allow an additional layer of flexibility for you to manage your campaigns. Typically, one of these campaigns will call a mix of individual flow steps, and Tier 2 & 3 campaigns to assemble a flow for a typical lifecycle event, like a Standard New Lead Flow. These typically include data enrichment, normalization, scoring, and routing flows, which can be created as tier 2 or 3 campaigns.

Issue Updating an Email Template is creating a draft for existing emails without the desired changes Solution When changes are made to an Email Template in the Design Studio that is already in use and those changes are approved, it will create a Draft for any existing Email that was created from that Template. If the draft is not reflecting changes you would like to see made, you may have included the changes within a mktEditable or Editable class <div> tag. The content within a mktEditable class element within an email template are ignored from any changes as they are considered to be "default content". Any content within these elements will not see any changes made to them based on changes to the template, and will only be seen when creating a new Email asset. You can update an editable section to remove it's editable status, however this will remove any changes to the content done in any email. You can see which elements can be classified as Editable here: https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax

As part of your efforts to maintain a healthy inbox delivery rate, you should be monitoring your email bounce rates. If your hard bounce rate climbs above 5%, you should take a closer look at what’s going on. If your hard bounce rate hits 10% or more, you should be concerned about your data quality. If you have a high hard bounce rate, it is likely that you have a high number of invalid addresses. An invalid address is an address that has never existed or no longer exists, so mail will never be delivered to these addresses. Marketo automatically stops sending to these addresses, so you do not need to worry about suspending or removing them. But having a high invalid address rate could cause you major delivery problems and reputation issues, and could indicate problematic data sources or list segmentation practices that should be reevaluated. A high invalid address rate can lead to outright blocking of your mail at major ISPs. Many ISPs monitor the number of invalid addresses being sent to at their domains by specific senders. Once a certain threshold is hit, those ISPs will block mail coming from the offending sender. ISPs behave this way because they view a high rate of invalid addresses as an indication of problematic data practices of the sender. At best, a high invalid address rate means you are not sending to an engaged, active audience. At worst, it means that you are sending to purchased or rented lists, which is a violation of Marketo’s Email Use and Anti-Spam Policy. Chances are, if you have a high invalid address rate, there are other issues with your data that could also contribute to. If you receive a notification that we have noticed a high invalid address rate associated with your mailings, you should ask yourself some questions about your list management practices. Below are some things to consider: - Have you recently added any new leads or lead sources? Purchased lists are often full of invalid addresses. We often find that purchased lists contain numerous addresses from domains that don’t even exist any more. While you can use purchased lists to bulk up the data you have for existing leads, you cannot use them to bulk up your lead database. -Have you recently targeted old or inactive leads? We strongly recommend that you never send to an address that you haven’t mailed to for over a one year. You should be mailing to your contacts at least every six months. This will help prevent high invalid address rates, and will also help keep you and your content fresh in your contacts’ minds. If you do have to send to older leads, you should break up your lists and send to your most recent and active contacts first. - Who are you targeting? Some senders have more problems with high invalid address rates because of their target audiences. For example, targeting .edu domains often causes high invalid address rates because these are school addresses that have a higher turnover rate. B2B campaigns may sometimes have higher invalid address rates because of similar turnover rates at businesses. The best way to avoid high invalid address rates is to send to opted-in, engaged recipients. To help with this, a lot of senders clear out their inactive leads every six months or so. An inactive lead is a contact that has taken no action in the given time period— they haven't opened an email, clicked a link, visited your webpage, attended a webinar, and so forth. This can help with both your high invalid address rates and spam complaints. Inactive leads are a dangerous group to continue mailing to because their behavior proves that they do not want to interact with your mail, and will therefore likely complain to us or to their ISPs about it. We have a great resource on how to create a Smart List to remove inactive leads here. If you still need some help, please feel free to reach out to our Support team (support@marketo.com). Additional resources: Dos and Don'ts of Effective Lead Generation Best Practices for Purchased Data

Issue You would like an links in an email to be tracked, but need to eliminate the tracking URL parameter on the tracked links. Solution In the Email Editor, you can uncheck "include mkt_tok" in the Edit Link box. Adding a class "mktNoTok" to any Anchor Tag will allow you to keep the Link Tracking, but disable the Tracking Token Parameter from the URL. You may also edit the Head of the email HTML to make large sections with this class.

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.

Issue General recommendations for managing and improving deliverability to China. Solution If you are looking for general recommendations around delivering to China, here are some resources both from our Community and external sources. Navigating email delivery into China Golden Shield Project overview Sampi China Email Marketing and Chinese Anti-Spam Laws Summary English language version of the Measures for Administration of Email Service on Internet Lehman, Lee & Xu English language version of the Measures for the Administration of Internet E-mail Services 2006

Upcoming Change to Chrome Browser In October 2017, the Google Chrome browser will change the notifications it displays for unsecured HTTP web pages. Secured HTTPS web pages will not be affected. In January 2017, Chrome started marking HTTP pages as “Not secure” if they contained forms that included password or credit card fields. With the release of Chrome 62, the browser will show the “Not secure” warning for all HTTP pages containing forms, and all HTTP pages visited in Incognito mode. Because form submittals can contain sensitive information beyond passwords and credit card numbers, Chrome will now warn users that a page is not secure whenever data can be entered/submitted. Eventually, Chrome plans to display the “Not secure” warning for all HTTP pages, regardless of whether they contain forms or are viewed in Incognito mode. Effect on Marketo Landing Pages It is important to note that this affects all HTTP web pages viewed in Chrome, not just Marketo landing pages. However, all Marketo landing pages will be affected if SSL has not been set up for the instance. This will not prevent people from viewing your landing pages or submitting your forms. The only change will be the “Not secure” warning displayed in the address bar. If you already have SSL set up for your Marketo instance, you will not be affected by the change in Chrome’s behavior. Steps to Take There are two options for responding to this change. The first is to do nothing. Your landing pages and forms will continue to work as before. The only difference will be the “Not secure” notification in the browser’s address bar. The second option would be to purchase SSL for your Marketo instance. There are advantages to having SSL set up on your Marketo instance. Not only does it provide increased security for your customer base, but Google has announced that it will give preferential search ranking to HTTPS pages. If you would like add SSL to your Marketo subscription, please contact your Marketo account manager. Here is some documentation on how to Add SSL to Your Landing Pages

Issue Description No data appears in the email performance report (configured for a specific time frame) even though emails have been sent to the leads. Issue Resolution The reason why the leads who were sent the email do not appear in the email performance report configured for a specific time frame is because "The Sent Date filter is based on the first date that the email was sent.". Email performance reports only show data for the first time an email was sent. docs.marketo.com/display/public/DOCS/Email+Performance+Report If the first time the leads that were sent an email falls outside of the specified time frame in the email performance report, the report will not show any results for those leads. Apart from that, it is also worth to check if the email performance report has any additional smart list filters that the leads may not qualify for. Is this article helpful ? YesNo

Note: Please ensure that you have access to an experienced JavaScript developer, because Marketo Technical Support is not set up to assist with troubleshooting custom JavaScript. Currently the form editor only allows you to change the color of the input text, not the text labels. You can, however, drag a “custom html” block into the landing page hosting the form and use the following code as a solution: <style type='text/css'> form.lpeRegForm ul { color:#FFFFFF !important; } </style> Replace the bolded section with the color code of your choice.

Issue Trigger Tokens in a Batch Campaign Flow are not functioning as expected, or result in an error. Solution Issue Resolution Trigger Tokens can only be used in a Trigger Campaign Flow and will not work in batch campaigns. While originally intended for Interesting Moments, Trigger Tokens will also work in Change Data Value flow steps. The associated Trigger Tokens will only function with the corresponding Triggers denoted by the green check-marks in the chart here.

We manage our network to provide our customers with the highest server availability and best deliverability possible. Marketo has a strong anti-spam policy and a team that handles blacklist notifications in our IP space and spam complaints. We also cooperate with most major anti-spam providers and ISPs. In addition, we maintain feedback loops for many of the most popular email providers. For more information on feedback loops and ISPs with whom we have this arrangement, click here. Blacklistings are usually caused by sending mail to a spam trap email address. For an explanation on what causes blacklisting, click here. When we receive notification of a blacklisting, we react in two ways. First, we go through the procedures to remove the listing from that blacklist as soon as possible. Second, we determine (if possible) which of our customers caused the blacklisting and work with them to improve their mailing lists to prevent a reoccurrence in the future. This is usually a cooperative process, most frequently, a review of mailing policies and strategic pruning of a customer’s lead database will return them to best practices.

The Marketo Sales Insight for Sales Training Package is designed to enable the Sales team to use Marketo Sales Insight quickly. During the live in-person or live-virtual training sessions, a Marketo expert will teach your Sales team the core features of Marketo Sales Insight as deployed in your organization. By sharing best practices and tips from a Marketo Sales Rep’s perspective, the Marketo expert will evangelize how MSI will help your Sales team to close more business faster. The package includes access to a Marketo expert during post-training, private Instructor Office Hour session. Learning Objectives: Learn to use Marketo Sales Insight to prioritize, focus on, and interact with the hottest leads and opportunities. In this custom training session, learn to use your Marketo Sales Insight deployment to do the following: Focus on your Best Bets and Watch List Monitor Interesting Moments that really matter to sales people Sell smarter using Marketo emails and Smart Campaign What you get: Live in-person or live-virtual training session led by a Marketo expert. Private Instructor Office Hour review session led by Marketo experts after the training. Customized training Content topics tailored to your MSI deployment. Scheduling – dates and times are set by you. Location – Training can be done at your specified location. Budget – Costs are eliminated for travel expenses and additional time away from the office. This is a fee-based on-site training package. Is this article helpful ? YesNo For more information: If you are interested in this training package, please contact education@marketo.com.

Issue A field value in Marketo is changed to "null" by the SFDC sync, but when you check the field on the Salesforce side, no change has been made. Solution It seems that there were differing values between integrated fields in SFDC and Marketo. The specific fields in Marketo had a value that was not present in the SFDC picklist fields. Reason why this happens: Fields are being nulled out on the Marketo side was because updates were made to these records on the SFDC side, making the most current version of the record which lead to these fields being nulled out on Marketo's end. Troubleshooting: Review First - If there is an alert setup for tracking these changes, this can be caught by finding a "Failed: no more information" error in the Activity Log of the leads. After this first "Failed: no more information" error, the Contact record in SFDC and the Person record in Marketo were no longer able to sync until the picklist value present in Marketo was added back to the picklist field in SFDC. Check SFDC side - Check to see if the field value was removed on the SFDC side. It might be filtered by the record types on the Contact object. In other words, the value was present for the picklist field on the Contact object, but it was not available if a Contact record was created with a certain record type. Once this value was added back to the Contact record types new Contact records and their fields are able to be updated by the Smart Campaigns. Once the SFDC Contact record picklist values had been added back to the Contact record types Marketo will sync again.

There are 3 kinds of visitors to your website: visitors using their company Wi-Fi, known visitors using an ISP, and unknown visitors using an ISP. RTP handles all three of these cases differently, and they are explained below. Visitors on Company Wi-Fi The visitor's company is recognized by the company's IP address Their visitor information, such as company name, industry, location, etc. is determined by the company who they are registered under Known Visitor on ISP Visitors are recognized by a previous form fill-out RTP will override the ISP name and identify the visitor by their company name and email address RTP does not override the location of known ISP visitors Unknown Visitor on ISP The visitor will be shown as coming from an ISP, such as AT&T, Comcast Cable, etc. His geo-location will be shown as the ISP's data center The location accuracy for ISPs is 95%, though state and city accuracy is less reliable as ISP tend to use proxies Since it's impossible to identify the company that these visitors come from, you can decide to exclude ISP visitors from seeing campaigns. While RTP can't identify the company, it is still possible to target these visitors by their online behavior (search terms, referrals, page visits, etc.

Issue Description In Notifications, you may encounter a Web Services Error message that contains details as below along with the Error Code and Count (i.e. number of times the error occurred). For example: The Web Services encountered the following error. Error Code Count 609 1 Issue Resolution More information about the Web Services Error Codes are documented here: developers.marketo.com/rest-api/error-codes developers.marketo.com/soap-api/error-codes/ It is recommended to consult with the owner of any custom Admin -> Launchpoint services configured (typically IT, your API developer, or a third party service provider) to review the API calls being made to Marketo. The owner of the custom integration should already be logging any error codes requiring review, or ignoring those errors that are temporary and can be automatically retried. If further assistance is needed, create a support ticket and provide details of the Request and Response of the API call containing the error code. Similar to how the example API Requests and Responses are documented here: developers.marketo.com/rest-api/lead-database/#describe Who This Solution Applies To Customers using API integrations. Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Sign Up for Service Degradation/Disruption Notifications

Unable to Abort a Triggered Campaign in Progress

The SSL certificate used to load resources from https://munchkin.marketo.net will be distrusted in M70

Munchkin Not Tracking Page Visits

Bold/Italic Font in Email Subject Line Gives Error or Does Not Render

Executable Campaigns - A Method for Organizing Nested Executable Campaigns

Email Template Updates Not Reflected in Existing Emails

High Invalid Address Rates: The what, how, and why you should care

Marketo Link Too Long? Keep Email Link Tracking, Disable Tracking URL Parameter

How Does Marketo See and Pull Data from Salesforce Formula Fields?

Deliverability to China - Resources

Upcoming Changes to the Chrome Browser

Email Performance Report returns no data

How can I change the color for the form label text?

Trigger Tokens in Flow Steps Render Incorrectly

How Does Marketo Respond to Blacklisting and Spam Notifications?

Marketo Sales Insight for Sales Training Package

Field Value in Marketo Erased by Sync from SFDC, but SFDC Shows No Change

RTP - How does RTP collect data on visitors

Web Services Error Notification