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 want to recall emails sent from your Marketo instance. Solution Once an email has been sent from Marketo Servers it cannot be recalled or pulled back. You can cancel a program before it sends at its scheduled time using the steps here: https://docs.marketo.com/display/public/DOCS/Abort+Email+Program The above cancellation only works on Email Programs. If you are wanting to cancel a smart campaign follow these instructions: https://docs.marketo.com/display/public/DOCS/Abort+a+Smart+Campaign Note: A smart campaign will only stop what hasn't been run yet. If you already had 100 emails sent by the time you cancel it, those 100 emails cannot be unsent. You may see in your Outlook an option for "Recall Email." This function within Outlook only works with internal sends/private systems where the client can request the server revoke access to other client mailboxes before they're viewed, such as your office email to other users in the same company.

Issue You are trying to edit an existing email template, and it has the status of "Approved with Draft" However the draft is not showing up in menu tree and when you try to edit and save, you get the error "Not Allowed – Template already has a draft." Solution Issue Resolution Refresh the browser or check is the draft is opened in another window. Try logging out and logging back in Try using a different browser to check it further Check if there is a template with the same name that exists elsewhere (Design Studio) Rename the template and check if that is working If the issue persists, please reach out to Marketo Support for further assistance

Issue 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. Solution 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 You need to filter leads who were sent an email by time zone to confirm the Recipient Time Zone feature is working correctly for all leads. Solution The "Was Sent Email" and "Opened Email" filters do include the constraint "Date of Activity" but it is not that granular. You can get granular to the minutes, but you can only select "in past: 5 minutes" for example, not a specific time or date range. One workaround would be to View Results for the Email Program and filter for the "Send Email" activity. You could export the results to a spreadsheet to make sure people are being sent emails at the correct time.

Issue There is a discrepancy for certain emails between Email Insights and Email Performance Report. The data (e.g. sent, delivered, opened and clicked) are significantly lower in Email Insights for the emails as compared to the Email Performance Report for the same emails. Solution There is most likely a discrepancy because at the time Email Insights was first enabled "you’ll have four weeks of historical Email data in addition to all new email activity". There was no request to Marketo support to upload historic data beyond four weeks which would have included data for the emails above. This request relates to the notes below from the article: "We’ll give you a four-week period before you can request Marketo Support to upload your data" The solution is to request that Marketo Support backfill the report data so you have data for Email Insights beyond the four weeks.

Issue You attempt to approve an asset and receive a "Cannot update a stale object" error. Solution This error means that a newer version of the asset exists than the one you started with. This occurs most often with large teams or if you edit an asset in multiple tabs. When you edit an asset, it creates a draft. Another attempt to edit the asset while the previous draft is open would create a new draft, which then causes your first draft to become "stale." Refreshing your screen should resolve this issue and allow you to approve the asset.

Issue Facebook Lead Ads was configured in a Sandbox subscription and then migrated to the Production subscription after testing was completed. After that swap, the Facebook Lead Ads integration is not passing records to the Production subscription. Solution Deleting the Facebook LaunchPoint service does not unregister it from the Facebook Lead Ad pages. To ensure that the Facebook Lead Ad pages is unregistered from the Sandbox subscription and successfully reconnects to the production subscription, perform the following steps: 1. Go into the sandbox and create (or Edit if it still exists) the Facebook LaunchPoint again (just leave the default settings for pages and fields). 2. Once created, go back into the Facebook LaunchPoint and UNSELECT all of the pages that are currently selected (You want to make sure no pages are selected at this point). 3. Save. By doing this you will be unregistering the Marketo endpoint from all the Facebook Lead Ad pages for the sandbox subscription. You can then delete the LaunchPoint if you wish from the Sandbox subscription. 4. Go into the production subscription, since the Facebook LaunchPoint service exists, go back in edit mode and select all the pages you want to leads to come from. 5. Save. This should be able to successfully select the Facebook Lead Ad pages and register them to the production subscription. 6. Test one of the Facebook Lead Ad pages and verify if the data syncs to the Production subscription.

Issue URLs generated by a Velocity script token are not tracking when a person clicks on the link in an email Solution Velocity scripting enforces strict formatting of links in order for them to be tracked: or must be included in the URL. If using a variable, the or must be output outside of the variable. The URL must be part of a fully formed <a> tag. No other type of link tag will work Links must not be outputted from within a for or foreach loop To ensure links are tracked properly, set the entire path inside a variable and then print the variable. Correct: #set($url = "www.example.com/${object.id}") <a href="http://${url}">Link Text</a> Correct: <a href="http://www.example.com/${object.id}">Link Text</a> Incorrect: <a href="${url}">Link Text</a> (missing http/https) <a href="{{my.link}}">Link Text</a> (missing http/htpps, cannot reference an outside my.token) <page xlink:type="simple" xlink:href="https://www.example.com">Click me</page> (must use an <a> tag)

Issue How is syndication ID set up while setting up a referral offer? Solution For a referrer to be given credit they must have a Marketo Syndication ID assigned. This can be done manually (directly on the lead record) or via the social campaigns' Offer Details > Fulfillment Goal > should be set to Referred Sign-Ups. Once you set that up, the referrer will get issued a "syndication id" and be part of that social campaign's participant's list.

Issue You come across a few leads who failed to sync to SFDC and would like to have the list of leads who faced the same issue. Solution Unfortunately Marketo doesn't have a specific type of filter to leads who failed to sync to SFDC. However if they are new leads who haven’t synced to SFDC, then you can filter them by using the filters "Person was created" and "SFDC Type" with condition "is empty". If you want to find the list of leads (previously synced to SFDC) who failed to sync among a particular group of leads, you can filter by following the below steps. 1. Create a new Boolean type field in SFDC namely "Sync Error?" and with the default value as "true". 2. Wait for the field to sync into Marketo. 3. Create a Smart Campaign to select those group of records and the flow steps to change the value of the Boolean field "Sync Error?" to ”False" and then "Sync person to SFDC". 4. Once the campaign has finished running, you will be to pull a report on SFDC on the list of leads who have the value "True" for the field "Sync Error?". It means that the value was not updated to SFDC as the record failed to sync. With this list you will be able to select the records and resolve the sync issue. You can also create a smart list of leads who were never able to sync with the following filters: Lead was synced to SFDC : Assign to : is not empty SFDC Type: is Empty

Issue When you navigate to Admin>Munchkin, you see option to select Workspace. Why is that? This is a article attached image Solution 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.

Issue How to copy the data from one field to another field using tokens. Solution It’s very easy and it can be achieved through a Smart Campaign. Create a Smart Campaign and set up the Smart List to target the specific leads you want. In the Flow, use the Change Data Value step. You would need to choose the field you are copying to as the Attribute, and the new value as token {{lead.fieldYouAreCopyingFrom}}. When you run the campaign, the values will be copied across. Be careful when doing this as the process cannot be reversed and any existing data in the field you are copying to will be destroyed. Note: Use appropriate tokens for the field, if the field is available under lead use lead tokens otherwise company tokens.

Issue You would like to have a new lead created in SFDC after every form submission regardless of whether the contact/lead already exists. Solution When you use the "sync lead", assign the person to lead queue explicitly, that will create a new lead since contacts cannot be assigned to queues. However, this is going to create a lot of duplicates in your database unless your salespeople are converting/merging these leads correctly. Furthermore, these new leads will have no campaign history, no interesting moments, no score. It's better to use an "Inbound sales rep campaign" in SFDC and attach the person to it using an "add to SFDC campaign" flow step. Campaigns can contain leads and contacts and can have workflows assigned to them.

Issue How to use a script token to calculate and populate the number of years since a given date. Solution This can be achieved by using a velocity (email script) token: #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/New_York") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) #set( $calJoinDate = $convert.toCalendar( $convert.parseDate( $lead.JoinDate, $ISO8601DateOnly, $defaultLocale, $defaultTimeZone ) ) ) #set( $differenceInYears = $date.difference($calJoinDate,$calNow ).getYears() ) #set( $friendlyLabel = $display.plural($convert.toInteger($differenceInYears),"year") ) You joined us ${differenceInYears} ${friendlyLabel} ago! Where $lead.JoinDate is the joining date. More at http://blog.teknkl.com/velocity-days-and-weeks/

Issue Calls made to the REST API return response code 611 "System Error". Solution Submit a Customer Support ticket with the following information The full body of the REST API call including the endpoint being called The full body of the REST API response The date and time that the call was made Customer Support will work to diagnose the root cause of the error and the reason a more identifiable error code is not being returned instead.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Trigger Not Capturing Change: SFDC Is Deleted

Can Multiple Marketo Forms Be Used on the Same Page?

Can an Email Be Recalled?

Email Template Has a Draft That Is Not Showing Up in the Navigation Tree

How to Create a Field That Grabs the Web Page the Form Was Filled Out On

Can You Sync Multiple Marketo Programs to a Single Salesforce Campaign?

Checking Email Send Times for Recipient Time Zone Sends

System.DateTime Token Timezone

Discrepancy Between Email Insights and Email Performance Report

Using Tokens in Email 2.0 Pre-headers

“Cannot Update a Stale Object” Error When Editing an Asset

Facebook Lead Ads Not Syncing into Production Subscription after Connected to Sandbox Subscription

URLs in Email Script Token Not Tracking

Setting Up a Syndication ID for a Social Campaigns

Filter Out the List of Leads Who Failed to Sync to SFDC

Why Do I See Workspace Partition While Selecting Munchkin?

Copying Data from One Field to Another

Creating a New SFDC Lead with Every Form Submission

Use Email Script Token to Calculate Number of Years Based on a Date Field

REST API Returning 611 Errors