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 Webinar integration is giving an error "Invalid Username or Password" during setup, even though the username and password are correct. The webinar provider uses your Single Sign-On (SSO) provider for login. Solution Marketo is not able to access the SSO provider and will not be able to log into the service if SSO is used. Use the following workaround for your integration. Disable SSO for the webinar service so that a user with login and password can be used in the Marketo Launchpoint service. Create the integration user in the webinar provider and complete the integration Re-enable SSO for your webinar service after the webinar is over. Who This Solution Applies To Clients leveraging SSO for Launchpoint services

Issue Email filtering can prevent the delivery of the invitation email to the Sales Insight Outlook Plug-in, preventing end users from being able to activate the plug-in. Solution This can be remediated by white-listing the trusted IP range from the following document: https://docs.marketo.com/display/public/DOCS/Setup+Steps#SetupSteps-AskITtoConfigureProtocols The email invitation return path is determined by the Marketo user who is inviting in the instance. So if there is a restriction on the domain that the email can be sent from you can adjust this by creating a dummy user with a username with the a domain that would qualify for IT restrictions. Then log in as the dummy user and send the invitation. It will have the dummy address in the From line.

Issue You see a soft bounce on a lead and in the details you see it show System send failure: Reply-To address parse error (value of the address) Solution Confirm the tokens you are using are for the proper field and that the value for the field is an email address. The parse error occurs when we cannot generate or create a proper email address in the From Email or the Reply To Email fields. The error will show in the parenthesis the value we tried to put in.. For example Service Department is in the parenthesis, this would be an example of a incorrect field being used.

Issue You've been using Marketo for a while and have started noticing that Smart Lists take longer to process than before. There are multiple filters in your Smart List ranging from really specific attributes about a person to really broad geographical information. Solution The best performance will come when you order the smart list filters from most restrictive to least restrictive. Since your entire database is checked against the first filter, if we can narrow down the number of leads which move on to the next, there are fewer and fewer leads who qualify for each of the subsequent filters. Many times, the processing difference will be minimal. However, as your database grows, the penalty on efficiency can grow over time. If you haven't checked it out already, take a peek over at our product documentation for smart list best practices: https://docs.marketo.com/display/public/DOCS/Best+Practices+for+Smart+Lists

Issue You may notice this permission error "You do not have sufficient privileges to perform this action" when previewing an email even though the user role has permission to access the emails. Solution This can happen when the user role didn't have any access to the lead database as shown in the picture. This is a article attached image The user role needs the top-level access to the Lead Database(1 of 15). This is because the email previewer allows one to view the asset as if you were a specific lead, but if you can't see the leads, then the error will trigger. To fix this issue, you would need to provide the user role with top-level access to the lead database.

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

Issue You click on a link in a sample email to test form pre-fill, but when you do, the form is not pre-filled. Solution When sending sample emails, the send sample feature does not generate links which are captured by the web browser, so the form pre-fill information is not passed. The test needs to be performed by sending an email using one the features below: Single Flow Action "Send Email" in a Smart List A Smart Campaign An Email Program Once a live email has been sent and not a sample email, the tracked link which contains the mkt_tok passes the lead info and the form will now pre-fill with that lead's information until the cookies are cleared, a new browser is used or an incognito browser is used.

Issue Issue Description Changes made to an email template are not reflected on the email assets (that are using the template in question) after approving the draft for those emails. Solution Issue Resolution To find out why the changes are not reflected, follow the steps below: Go to the email template in question. Check if the HTML elements that have changed have the class of mktoModule, mktoEditable, mktoContainer, or any other mkto related class name. Disassociate the HTML element(s) in questions from the class above. Note: These steps will require an complete overhaul on the email template's code base, because the relationships between elements would change. This type of change will require assistance from a developer/engineer who is experienced with HTML and CSS.

Issue Why don't some emails appear as an 'Email Filter' option in an Email/Email Link Performance Report? Filter Assets in an Email Report documentation Solution The reason why some emails do not appear as an 'Email Filter' option in an Email/Email Link Performance report is because the emails were used in an A/B test. Similar to the product behaviour illustrated below, when adding an A/B test, the selected email will not be directly selectable or appear as an Email Filter option in an Email/Email Link Performance report. "When adding an A/B test, the selected email will no longer be available for use in any other program." Add An A/B Test In order to report on the A/B test emails that do not appear in the Email Filter option, the parent program can be selected.

Issue You receive the following notification: The user you have authorized for you Facebook Lead Ads Launchpoint Service may have Insufficient Permissions. Solution Visit the Facebook help center to validate that the authorized user has all administrative permissions to both your company page and advertising account. If authorized user has all administrative permissions, please contact Marketo Support for further investigation

Issue Sometimes, you may notice that editing the text version also affects the HTML version of the email. Is there a way to edit the text version without the same edits occurring to the HTML version? Solution Changes to TEXT never apply to the HTML version. It's likely because when you "save" an element, it will add the "root block element" to the HTML side if one isn't present. So, your HTML is probably not handling it correctly. You can change the "root block element" to none in the Admin > Email > Editor Settings dialog. https://docs.marketo.com/display/public/DOCS/Using+the+Rich+Text+Editor

Issue You have developed a Marketo landing page and enabled Personalized URLs (PURLs) for your records but when people visit the PURL, form pre-fill does not take place. Solution When a person visits a PURL landing page, the form pre-fill checks their Munchkin tracking cookie to identify what values to populate for the form fields. If that person has a Munchkin tracking cookie associated to a known record in the database, it will pull and populate the information from that record. However, if this is the first time this person has visited a Munchkin tracked page or their browser is tied to an anonymous record, the pre-fill will not populate any information into the form. The customer/prospect will need to fill out a form or click on a tracked link in an email sent from Marketo. This will allow future PURLs that people visit going forward will have pre-fill populate as their cookie will be tied to a known record in the database. The web page visit will be associated back to the know record for the PURL. Additionally, you can also use Person related tokens on the landing page and those will resolve. For examples having the token in the text that states {{lead.First Name:default=Default}} within the body of the landing page will populate with the expected persons first name for the PURL they visited. This is because the token generation goes through a different path on the back end for PURLs.

Issue You have noticed that in some Asset URLs the 9-digit Munchkin ID displays, and you would rather have something else display. Solution It is possible to alter the URL and replace Munchkin ID with the Account String for your Marketo instance located in Marketo Admin > Landing Pages. The following can only be done when inserting the URL into your email or landing page HTML. There is no global setting to change this permanently. For example say you have an image asset at the URL: https://na-sjst.marketo.com/rs/164-CZO-458/images/android.jpg When you insert this link in an email or landing page, you can replace the Munchkin ID with the account string of for your instance: https://na-sjst.marketo.com/rs/mktosupportmybaben/images/android.jpg This link will still resolve correctly and the Munchkin ID will not be displayed.

Issue Is there a way to make a landing page only accessible through a form? In other words, if someone gets to the thank you page and then forwards that URL along, you don't want the next person to be able to access it without filling out the form first. Solution Marketo does not currently have functionality that can support this Use Case. If a Landing Page is approved, it's published on the web and if anyone has the URL then they can visit the page. That being said, perhaps there is some custom implementation that you can have a developer create. Here are two possible approaches: Custom coding that would look at the previous page of the visit; when accessing the Thank You page, if the Referrer is not the page with the form, then reject access or redirect it to display the page with the form Have the page submission pass along some kind indicator (URL Parameter) so that a reroute logic (on the thank you page) would run on that page all the time except when that indicator is present Marketo Support would not be able to assist in custom implementations. However if you were interested in a Professional Service Engagement we can explore the option of Marketo building this out for you.

Issue Issue Description When you update fields for the sales owner in SFDC, the information is not updated in Marketo. You are also blocking updates from SFDC for the affected fields. Solution Issue Resolution Due to how the SFDC User object is mapped in Marketo, if a field is blocked from updating from SFDC, this will also prevent Sales Owner info from syncing over. You'll need to remove the "Block Updates From" logic for that field.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Webinar Integration Gives Invalid Username or Password Error When Using SSO

Email Filtering Blocking Sales Insight Outlook Plug-In Invitations

Soft Bounce “System Send Failure Reply-To Address Parse Error”

Does the Order of Smart List Filters Matter?

Permission Error When Previewing Email

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

Adding Multiple Social Media Accounts with Marketo

Form Pre-fill Is Not Working on When Tested from Sample Emails

How to Roll Out Changes from Email Template Edits

Reporting on A/B Tests Emails in Email Reports

Facebook Lead Ad Error: Insufficient Permissions

Edit Text Version of the Email without Affecting HTML

Personalized URLs Are Not Working for Form Pre-fill

Email server used when sending Tout Emails from Salesforce

Removing Munchkin IDs from Image and File Asset URLs

Set Marketo Passwords to Expire

Block Landing Page Access for Leads That Have Not Filled Out A Form

“Change Score” Flow Step activity is not recorded or missing

SFDC Sales Owner Information Updates Not Showing in Marketo

Image on Landing Page shows as grey box