Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

Featured article

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

Issue Description Sometimes there can be a circumstance where a text token should hold null value. Since the token must contain a value, you need to insert a value that will display as empty when the token is rendered. Issue Resolution Adding a HTML comment to the on the Text {{my.token}} side would work.  If you're just plopping the token into your HTML, this will be fine. If you're embedding in JS then you can still check for that specific value, it just won't be "magic": if ( "{{my.token}}" != "" ) { // it's not empty }

Issue Description You may notice that there may be a block in SFDC that stop syncing unsubscribes from Marketo to SFDC. After fixing the block in SFDC the new unsubscribes will sync as expected. How to get all the unsubscribes that happened before this fix to sync into SFDC? Issue Resolution You would need to set up a campaign to reset the field value. Smart list: Unsubscribed = true Flow: Change data value "unsubscribed" -> False Change data value "unsubscribed" -> True That would take everyone who is currently unsubscribed, switch to false and then back to true. That should cause the true value to sync up to SFDC for all of those records. However, make sure you do this at a time when you are absolutely positive there are no email campaigns going out. Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo

Issue Description What is meant by the socially acquired member of a program such as a webinar program? Issue Resolution Leads acquired by the following Social Apps are part of the "Socially Acquired" count - Social Button Youtube video Poll Referrals Sweepstakes If you want to track the number of registrations through social shares, you should consider using the referrals or sweeps app. These apps allow the users to share and also help you track how many registrations each of your referrers bring in.

Issue Description When we delete the static lists from a program after a period of time, will the leads they contain no longer be member of the program? Issue Resolution The individuals should still be a member unless you change their membership status to remove them. Remember lists are simply collections of individuals so you can easily process or associate them, they don't automatically get "membership" unless you had corresponding flow steps that you used when putting them on the list. 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 When a lead fills out the form in Marketo, Marketo sync fails with an error "Duplicates_Detected." Issue Resolution This error, "Failed: DUPLICATES_DETECTED: Use one of these records?" is a message Salesforce is sending back to Marketo, rejecting the attempt to sync the record. This means there's a setting in SFDC preventing duplicates from being created, possibly due to a custom deduplication rule on the SFDC side. Recommended steps : Check the dedupe settings and check for these leads in SFDC based on the things other than the email address like first name, last name etc. You may need to work with your SFDC admin to determine why Salesforce rejecting the record as duplicate. Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo

Issue Description How to identify in which campaign the "Delete Person" flow step is used Issue Resolution You can identify it by going to "Campaign Inspector" in Marketing Activities. From there you can filter down by type of Smart Campaign and search "Delete Person" and the resulting list will be Smart Campaigns containing that flow step. If you do not see the Campaign Inspector, navigate to Admin > Treasure Chest to activate it. Is this article helpful ? YesNo

Issue Description MS Dynamics Sync shows that it is stuck at a certain percentage after a long period of time. Issue Resolution This is usually caused by enabling several Custom Entities at a time. To resolve this issue, you will need to sync the custom entities one by one so that the sync is not bottlenecked. If that does not resolve the issue, check how many fields are enabled for the custom entity. A large amount of fields can cause a bottleneck, try to reduce the amount to have only necessary fields. Who This Solution Applies To Customer with Microsoft Dynamics CRM Is this article helpful ? YesNo

Issue Description Can you remove a CRM from Marketo? Issue Resolution You cannot remove a CRM integration from an instance. Once the CRM of your choice is clicked (Dynamics or Salesforce) the instance is set to use that CRM for the remainder of its life. Once the login and mappings have been setup for a instance, the CRM instance or org cannot be changed as well. If for a reason you do need to change the CRM or the linked instance, you would want to reach out to your Customer Success Manager to get information on provisioning a new Marketo instance.

Issue Description When I navigate to Admin>munchkin, I see option to select workspace. Why is that? Issue Resolution People generally use workspsce either because of their companies geographical location or Business Unit. In each case, the separation is because the marketing assets are completely different. With that said, If you're using Workspaces in your Marketo account, you probably also have separate web presences that correspond to your workspaces. In that case, you can use the Munchkin tracking Javascript to assign your anonymous people to the correct workspace and partition. This is used to differentiate appropriate leads within workspace with the help of appropriate tracking. If you don't use the special workspace Munchkin code, the people will be assigned to the default partition that was created when your account was set up. It's named "Default" initially, but you might have changed that in your own Marketo account. You can only use one Munchkin tracking script for a single partition and workspace on a page. Do not include tracking scripts for multiple partitions/workspaces on your website. I would also like to mention that Landing pages created in Marketo automatically contain tracking code, so you don’t need to put this code on them. Who This Solution Applies To People who use Workspaces and Person Partitions Is this article helpful ? YesNo

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

Issue Description You need to revert a data value change for a field on multiple leads. Issue Resolution There is no way through the UI to "undo" a data value change (unless it was a boolean field, in which case there are only two possible values.) You can certainly use a Smart List to identify whose values have changed, but there no way to go back to the old value (unless it's stored elsewhere in another field or through another data store, along with the API). However, you can use the API to extract the data value change activity from the activity log, which would include the old and new values, extract the original values, then use the API to rewrite the old values back to the lead record. http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadChangesU… Is this article helpful ? YesNo

Issue Description Lead fails sync to SFDC with the error INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST: bad value for restricted pick list field Issue Resolution This happens when the Marketo field has a value that is not available in the list of accepted values on SFDC. We suggest that you check with your SFDC admin to find out the list of accepted values and make necessary changes. Who This Solution Applies To Customers integrated with Salesforce

Issue Description You want to set a field such as "Country" to be required on a list import. Issue Resolution You cannot require a field to be included on a list import. To see any leads imported recently with blank values you can setup a smart list with a subscription Filters -- Lead was created Source Type - Import [Field you are wanting to watch] is Empty You could setup a daily subscription to get the leads who qualify and then correct those leads as needed. Is this article helpful ? YesNo

Issue Description Emails with valid email address get soft bounced with this error: Local address contains control or whitespace Issue Resolution This error means that the email has a space somewhere in the the From email address or there was a comma or extra character in the From line. The email send did not occur due to the error with the address. The emails will need to be resent once after the associated address is corrected with white spaces or extra characters. Is this article helpful ? YesNo

Issue Description Issue in delivering Marketo Email (especially for mimecast users). Email get bounced with Error: 550 Rejected by header based Anti-Spoofing policy Issue Resolution This error can happen if: You have not properly white listed the Marketo IPs You have an ssue with DKIM/SPF set up and configuration Please whitelist the set of Marketo IPs found in the doc below and make sure SPF and DKIM are set up correctly for your email domain https://docs.marketo.com/display/public/DOCS/Configure+Protocols+for+Marketo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Creating a token with a null value

Smart list subscription "Download report"

Sync past unsubscribes into SFDC

Socially acquired member of a program

Remove a list from a program

Smart list that shows leads created in Marketo

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

Error : "Failed: DUPLICATES_DETECTED: Use one of these records?"

How to identify where the "delete person" flow step is used

MS Dynamics Sync Stuck at X% when syncing custom entities

Removing CRM from the Marketo instance

How to set up Wistia in Marketo

Why do I see workspace partition while selecting Munchkin?

Can multiple Marketo forms be used on the same page?

Troubleshooting background image not being rendered on landing page editor

How to revert Data Value Changes

INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST: bad value for restricted pick list field

Setting a field to be required on list import

Soft Bounce: Local address contains control or whitespace

550 Rejected by header based Anti-Spoofing policy