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 You have a Salesforce Custom Object that has a relationship to multiple objects, which shows up twice in Marketo with the same name. When trying to enable the second object in Marketo, you seeing an error like this: "An object with the same name is currently enabled for sync. Please give the object a unique name and retry." Solution Marketo requires that each custom object have a unique label. You will see this error when the labels in Marketo are the same for both custom objects. In order to enable it, you'll need to change the label in Marketo for the second custom object that is attempting to be synced. The easiest thing to do is append a letter in parenthesis to denote which object it is for (e.g., "Example Object (A)" for the Account). This will allow the custom object to sync into Marketo and the API information in the back end will remain unchanged, allowing the records and changes to sync from Salesforce into Marketo.

Issue Statuses are not showing for a channel when viewed in the Admin > Tags section of Marketo. Solution To view the statuses for a channel, follow these steps: Go to Admin > Tags. Expand the Channel tag type. Double-click on a channel to open the Edit Channel window. Scroll down to view the statuses. If you are unable to see statuses in the Edit Channel window, it may be due to the slight delay that can occur when Marketo is loading the values for a channel. If you leave the channel window open, the values should populate. The more statuses there are for a particular channel, the longer the delay can be before they populate.

Issue Issue Description After an email send, the number of emails sent is much lower than the number of people that qualified for the sending Smart Campaign or Email Program. Solution Issue Resolution One possible reason you are seeing a different number of emails sent versus the number of people that qualified for that is email is because of communication limits. If a person qualifies for an email, Marketo will try to send it. However, if a lead has already reached their daily or weekly communication limit, Marketo will not send the email (with the exemption of operational emails). To check to see if a lead did not get an email due to communication limits, follow the steps at Email Program Fails to Send Emails.

Issue After adding an IFrame to an email in the Marketo email editor, the IFrame seems to disappear when you view the email in an email client (such as Outlook, Apple Mail, or Gmail). Solution The reason why you can see the IFrame in Marketo but not in your email client is because not all email clients support IFrames. If yours does not support them, the IFrame will be blocked and will not appear in the email. You can try viewing the email in another email client to see the IFrame.

Issue Marketo records are failing to delete. Solution For Marketo records that are synced with Salesforce, if the Delete from CRM is True in the delete process, and the deletion fails in SFDC, then the Marketo record will fail to delete because the entire requested action cannot be completed. (action = delete in Marketo and delete in SFDC) Looking in the Marketo Lead Activity Log will give you a more specific reason as to why the record is failing to delete.

Issue You see the following error when trying to Refresh From Webinar Provider in an Event Program linked to GoToWebinar: "FailedAPI Error: Authentication succeeded, but access to the requested resource is denied." Solution Check LaunchPoint to see if the integration between Marketo and GTW is broken. Go to Admin > LaunchPoint to see the integration between GTW and Marketo. If you see the error "FailedAPI Error: Authentication succeeded, but access to the requested resource is denied," this is a permission issue with GTW. Check with GTW Support to see why requesting resource is being denied. Who This Solution Applies To Customers integrated with GoToWebinar

Issue Issue Description You receive notification that Campaign Failed in trying to update Segmentation for leads. Solution To troubleshoot this issue review the Segmentations for the following: Click on the Segmentation to pop up in a dialog box with the failed Segment(s) If a Segment failed to approve, review the Smart List filters for missing values or errors in the smart list logic of the Segment. When errors have been fixed, approve the Segment, review again if the notification occurs again.

Where can I find the answers I need? Search Product Docs and Knowledgebase Articles The search bar on the front page will search both Product Docs and the Support Knowledgebase. If you need to drill down for a deeper search, you can access the Knowledgebase via the link at the top of the Support Space, or you can go to our Product Documentation site, docs.marketo.com. The Knowledgebase focuses on troubleshooting specific issues, while the Product Docs site contains more feature overviews and how-to's. Support Blog The Support Blog contains posts on product changes, new product features, in-depth discussions on topics such as security and deliverability, and changes and enhancements to the Support portal. How do I contact support? Submit a case Regional Support contact information Chat Support

Marketo Support's Mission is: To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success. Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include: My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code: Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API Our TSEs are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience. Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented. Response Time Our TSEs are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services. We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.

The Marketo system hosting your subscription is currently experiencing an unplanned service interruption affecting Trigger processing. When: Monday April 24 th, 2017 - Current Services affected: During the time of this incident, Trigger Processing is intermittently affected. Customers may experience periodic delays in Triggering events based on an activity. Login to the Marketo application, landing pages, and rest of the platform are not affected. Cause: This service interruption is due to stability issues in our infrastructure, which is utilized for Triggering events. We are actively engaged with our Vendor to stabilize the infrastructure and deliver a permanent resolution. We will provide the next update within 24 hours. A root Cause and/or remediation plan will be shared as soon as we have it from our Vendor. We want to assure you that we take these incidents very seriously, and we are taking steps to prevent similar situations going forward. If you have any questions about service interruption, please contact Marketo Support. Is this article helpful ? YesNo

Dear Valued Customers, This is a Root Cause Analysis for the service issue that occurred on November 20, 2017. Beginning at 12:10 PM, our systems experienced a network server disruption that limited the ability for users to log in to the Marketo platform. All Marketo services have been fully restored, and our analysis has confirmed no data was lost as a result of the disruption. When: Full Disruption: November 20, 2017, 12:10 PM – 2:56 PM PST Partial Disruption: November 20, 2017, 5:15 PM PST – November 21st, 7:59 AM PST Full Disruption Duration: 2 hours 46 minutes Service Impact: During the full disruption window, customers were unable to log in to Marketo. After service was restored on November 20, intermittent errors limiting Marketo functionality for a subset of users persisted through November 21. Cause: The source of the disruption was a network server failure. When our backup systems activated, a component of our secondary server was unable to take over operations due to a synchronization issue. After login access was restored, a buildup of network requests caused the intermittent errors that led to the partial disruption. Resolution: We replaced the servers involved in the issue and reconfigured our network infrastructure for optimal system operation. In addition, we have enhanced our network infrastructure monitoring to better predict and prevent similar disruptions moving forward. We take these incidents very seriously and continue to invest aggressively to enhance system stability and security across the Marketo platform. If you have any questions, please contact our Customer Support team at support.marketo.com. Thank you for your patience as we worked to resolve this issue and for being a loyal Marketo customer. Mohan Achar VP, Customer Support Toll Free US: +1.877.270.6586 Direct +1.650.376.2302 Is this article helpful ? YesNo

Issue An email program with "Send in recipient time zone" was scheduled to sent out an email on Jan 8th, 2019 8:00 PM PST but you see that it was sent out to leads on Jan 8th 12:01 AM PST. Solution From the activity logs of the lead, you can observe the following: 1. Send Email activity happened on Jan 8th 12:01 AM PST. This is when Marketo issued the Send request to the server, which held the request until 8:00 PM PST, per the time zone restrictions. 2. Email Delivered happened on Jan 8th 8:00 PM PST. The MTA (message transfer agent) pushed the held emails to the receiving servers. The send email event is an indication that the lead was qualified at 12:01AM but the actual delivery of the email happened at 8:00 PM. So, the send event means the leads were processed and prepared for email delivery. The delivery event is when the email is actually sent and delivered. You will see this behavior when emails are sent with time zone restrictions. For the complete details on Recipient Time-Zone and it's working , please refer to the following Adobe experience league document :- Schedule Email Programs with Recipient Time Zone

Issue Description A lead was not sent an email by a Smart Campaign Issue Resolution * Check if the lead has reached the daily or weekly communication limit. docs.marketo.com/display/public/DOCS/Enable+Communication+Limits docs.marketo.com/display/public/DOCS/Apply+Communication+Limits+to+Smart+Campaign * Check if the lead has a duplicate lead with the same email address that was sent an email already. * Check if the campaign is set to qualify leads only once. If the lead has ran through the campaign previously when it had different flow steps, then the lead cannot qualify for the campaign again even though the flow steps have changed. docs.marketo.com/display/public/DOCS/Edit+Qualification+Rules+in+a+Smart+Campaign * If all leads in the campaign were not processed, check if there is a campaign restriction. docs.marketo.com/display/public/DOCS/Enable+Person+Restrictions+for+Smart+Campaigns Is this article helpful ? YesNo

Issue Description You want to create a field that will grab the web page the form was filled out on and add this as a token in an alert that goes to sales when a form is filled out. Issue Resolution This can be achieved either through a Smart Campaign or the JS API code. The code is more efficient because it doesn't mean another trigger is active in your instance. Smart campaign: You'll want to create a smart campaign with Smart List - Fills Out Form and Flow - Change Data Value, [your field name], New Attribute is {{trigger.Web Page}} You would need to reference the trigger token in the alert email so the team knows what product page the end user filled out the form on. Code: (Embedded Form) This can be done with a hidden field. MktoForms2.loadForm("//app-**01.marketo.com", "***-***-***", 148, function(form) { form.addHiddenFields({ LastFormURL : document.location.href }) }); The asterisks represent your company's Marketo data (your Munchkin ID and Marketo instance). Your developer will know what to do if s/he is already using the embed code. Code: (Marketo LP) In a Marketo LP, you will have to edit the template and put this at the end, before the </body> tag : <script> MktoForms2.whenReady(function (form) { form.addHiddenFields({ LastFormURL : document.location.href }); }); </script>

Issue Description You sign up for ToutApp and receive a notice that your account is under review or your account is not verified. Issue Resolution If you sign up for ToutApp using a generic email address such as Gmail, Yahoo, Hotmail, Outlook or other email providers your account may require verification by Marketo Support. Please contact Marketo Support with the following information. Company Name: Business Address: URL(s) of your primary Web site(s): What is your average weekly and/or monthly email volume? Do you purchase, or have you ever purchased lists of leads? If yes, which providers have you used and when was your last purchase?

Issue Leads in a GoToWebinar event program have a "registration error" status. Solution If this is affecting all new leads registering for the webinar: This is caused by Marketo losing connection with the GoToWebinar service. To resolve this Go to Admin > Launchpoint. Open the GoToWebinar service. Re-enter your GoToWebinar credentials. Once this is done, you can go back to the webinar program and change the status of the affected leads from "Registration Error" to "Registered." If this is affecting only specific leads registering for the webinar: Check the name, email, company, and job title fields for any special characters. GoToWebinar often doesn't allow special characters and will throw an error.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Editing SFDC Custom Objects in Marketo

Error When Enabling Salesforce Custom Object

Unable to Enable Marketo Sales Insight on SFDC Mobile App

Channel Statuses Are Not Showing

Seeing a Lower Number of Emails Sent Than People That Qualified for a Campaign

IFrame Not Showing in an Email

Marketo Record Failing To Delete

How Many Domains Can Be Added To Marketo Admin > Email > SPF/DKIM?

GoToWebinar (GTW) FailedAPI Error

Campaign Failure: Update Segmentation

Understanding the Support Space in the Community

Marketo Support Policies

Marketo Service Interruption Update

Marketo Service Disruption: Root Cause Analysis

Email Program Appears to Send Emails Early

Smart Campaign did not send an email to a lead

Webhook calls and API limit

How to create a field that grabs the web page the form was filled out on

ToutApp account under review

Registration error status for GoToWebinar