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 Leads would be qualifying for a Smart List filter that was set up to only qualify those leads that had a date "on or before mm/dd/yy", leads that have null would also qualify for this filter when they should not. Issue Resolution When the field is left as null, by default Null value is treated as epoch timestamp (i.e, jan 1 1970). In this case it is recommended to change the filter date from "on or before" to "between" in order to exclude those leads that have null in the date field. Is this article helpful ? YesNo

Issue Description You sent an email using a Smart Campaign and the email performance report for the email shows more Sent than there are members in the Smart Campaign Issue Resolution The email may have been sent by more than one campaign. You can determine this by looking at the "Used By" info on the email's summary page, to see which campaigns sent the email. In this case, you can use the Campaign Email Performance Report to view the email's performance within the specific campaign.

Issue 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. Solution 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 it in Javascript then you can still check for that specific value, it just won't be "magic": if ( "{{my.token}}" != "" ) { // it's not empty }

Article Text Included in this Article: Overview The Problem The Solution Rich Media Content Recommendation Engine Info Overview The Content Recommendation Engine (CRE) is a powerful tool that will allow you to promote online content to your visitors based on their behaviors and the performance of the content itself. When the RTP tag is used on multiple domains, it will pull in all available content regardless of which domain it's on. For some marketers, this can be a problem. The Problem With the standard Content Recommendation Engine, this is an expected behavior. You can't limit the the recommendations from one domain to stop showing up on other domains. The content being recommended will show across all domains where the RTP tag is in use. The Solution There are two types of Content Recommendation Engine. The Rich Media Content Recommendation Engine will let you get around this problem. The standard Content Recommendation Engine gives the bar along the bottom of the web page with the content recommendations in it. This recommendation engine is expected to have content extending across all domains where your RTP tag is in use. The Rich Media Content Recommendation Engine will allow you to target which content you want to have in which places by categorizing the content and specifying which categories each web page should pull from. Rich Media Content Recommendation Engine Info For directions on how to utilize the Rich Media Content Recommendation Engine, please see: Enabling the Rich Media Recommendation Engine - Marketo Docs - Product Docs

Issue You need to know if Salesforce Group Edition is compatible with Marketo. Solution Having a look at the comparison between the Group Edition and Professional Edition: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/dev_package_features_pe_ge.htm We can see that a lot of features from the Professional Edition have been stripped in the Group Edition, mainly the removal of Workflows, Campaigns and Custom profiles. These will most likely hinder how the Marketo CRM Connector operates. The minimum would to be to have the Professional edition when syncing a native Salesforce CRM as per our Documentation on Sync Setup. https://docs.marketo.com/display/public/DOCS/Setup

Summary The customer wants to know if a nurture email was not sent to a recipient due to communication limit, then will it be sent in the next cast, or that email will not be sent again? Issue Individual(s) were supposed to get an email from a Nurture (Engagement) Program cast but failed to receive the email due to hitting the communication limits set in the instance. Do you need to manually send the email to the individual(s) via a separate Smart Campaign or will it be sent, automatically, on the subsequent cast for the Nurture Program? Environment Marketing Activities Nurture Programs Engagement Programs Admin Communication Limits Solution You don't need to act on these scenarios as the individual(s) impacted by the Communication Limits will be sent the applicable email in the next cast for the Nurture Program. The only reason that the individual wouldn't be sent the email in the subsequent cast for the Nurture Program would be if the person would hit their Comm Limit again. Should that happen, you might want to review your Communication Limits settings or review the individual(s) impacted and see why they keep hitting the Comm Limits. Reference: How Do Communication Limits Work? - Marketing Nation (marketo.com) Root Cause Communication Limits being hit during Nurture Program cast execution

Summary When renaming a field in a CRM Custom/Entity it does not reflect the change in the constraint of filters/triggers/ Issue I renamed a field in my CRM Custom Entity/Object (MSD/SFDC) and I refreshed the schema. I can see the field name change reflected in the CRM Custom Entity/Object, but when I look for the field in constraint for filter/trigger I only see the old name. Environment Smart List Solution The workaround is that the customer can create a new field on the SFDC side and copy all the values from the old field to the new one. Then, this field can be used in smartlist filters. Old field can be disabled after that. Root Cause We are not propagating field name changes from SDFC to Marketo.

Issue You created a Smart List, but did not define the filters (example: "Member of Smart List" with no Smart List named) and are wondering if this will cause no leads to show up in the results. Solution If you create a Smart List and you do not define any filters, this will cause all leads in your database or leads visible in the partition and workspace to appear in your results. This can create problem if you have nested Smart Lists. For example, if you have a Smart List with the filter "Member of Smart List = Lead not in" with Smart List A selected, and Smart List A has no filter, this logic will cause you exclude all leads in your database.

Issue You sign up for ToutApp and receive a notice that your account is under review or your account is not verified. Solution 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 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.

Article Text Included in this article Overview Editing Labels Deleting Labels Overview RTP will allow you to add labels to your Segments and Campaigns. Here are the directions on how to do so: Label Your Segment - Marketo Docs - Product Docs Label Your Campaigns - Marketo Docs - Product Docs Sometimes Labels need to be changed or removed. Editing Labels Currently it is not possible to edit labels Deleting Labels You can delete labels using following process: 1. Filter the the page by the label you want to remove. 2. For each segment or campaign displayed, click the select box and then click Set Label 3. In the Set Label list, uncheck the label you want to delete. When the label is removed from all segments/campaigns, it will be removed automatically

Article Text Included in this article Overview Troubleshooting Steps Verify Global Settings Check for CRE Excluded URLs Verify Content Being Recommended Make Sure the Page Has the RTP Tag Running Clear Your Browser's Cache and Cookies Overview The Content Recommendation Engine allows content assets to be promoted to visitors on your website. But what happens if it stops working? This doc will show you the common things to check and troubleshooting steps to try to get it working again. Troubleshooting Steps Verify Global Settings The CRE can be switched on or off for your entire RTP instance whenever you want. It's possible that another user may have switched it off and not turned it back on again (it happens more often than you'd think). To enable or disable the CRE globally, go to the Account Settings page and look for the Recommendation toggle switch. Full directions can be found here. Check for CRE Excluded URLs You have the ability to prevent the CRE from being added onto specific pages. If you have URLs excluded from allowing the CRE to be displayed, that would cause the CRE to no longer display on those pages. Many times the exclusion can be set and then forgotten, or set by a different user on accident. Directions on how to set up the exclusions can be found here Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages Verify Content Being Recommended Content assets can be switched on or off to designate whether that content should be included in the CRE recommendations or not. Each piece of content can be enabled or disabled individually, but if you don't have any enabled at all, there's nothing for the CRE bar to recommend, so it won't even show up on the page. To check whether content is enabled, from the menu, select Recommendations In the Content Recommendations page, look for the Recommendations column. This will list out all pieces of content you have in RTP and display whether they are enabled or disabled. The Red box means it is turned Off and is disabled. The Green circle means it is turned On and is enabled. Make Sure the Page Has the RTP Tag Running The CRE is a feature of RTP, so if the RTP script tag isn't running on the page, there's no way for the CRE to work. The RTP tag can be implemented in many different ways besides by having it directly in the page's HTML, like having it in a tag manager. These other implementation methods can cause problems so be sure to follow the directions in the documentation here when setting it up: RTP Tag Implementation - Marketo Docs - Product Docs If you know for sure that the RTP tag is on the page, here's documentation on how to troubleshoot what could be keeping it from loading properly: Troubleshooting Web Personalization (RTP) - RTP Tag Clear Your Browser's Cache and Cookies Web browsers store cached data from websites, which can frequently cause old versions of webpages to continue showing even if a different newer version of the page should be loading instead. Try clearing both cache and cookies in your browser and then testing the page again. You can also test using a different browser.

If the user makes changes to the my tokens, snippets, etc during the processing of the an email that is using head start, will those changes be reflected—No If someone unsubscribes during the processing of the an email that is using head start, will they receive the email—Yes Can you cancel a head start program once the processing of the an email that is using head start has begun—Yes What happens to the processing data when someone cancels a program during the processing of the an email that is using head start—It is deleted (I.e. Program membership, etc.)

Issue My token is not displayed correctly in view as webpage version of email. Environment If customers manually type a {{my.token}} and use uppercase M such as {{My.token}}, then the view as webpage version of email may not render that token as expected. The feature to HTML encode lead tokens (source of external data) for security reasons, applies to my tokens that incorrectly use uppercase M. HTML Encode Tokens Solution Use the token picker to pick the correct lowercase {{my.token}}.

Summary Email previews by list can only view the first 25 people. Issue When previewing an email and viewing people by 'List', you are only able to generate a preview for the first 25 people on that list. Environment This occurs in email previews. Root Cause This is the expected behaviour for email previews. The intention of email previews is to allow for a quick confirmation that the email is compiling as expected, rather than to confirm it is correct for every recipient.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Lead qualifies for Smartlist filter utilizing "on or before" date filter when lead has no date in the corresponding date field

How to Add an Additional Domain for Predictive Content

Using Campaign Email Performance Report to Troubleshoot an Email Performance Report

Creating a MyToken with a Null Value

Troubleshooting Web Personalization (RTP) Content Recommendations Appearing Across Domains

Salesforce Group Edition Compatibility

Nurture Program Email Blocked Due To Communication Limits

When I rename a field in my CRM Custom Entity/Object why is the change not reflecting in the constraint of a filter/trigger?

Smart Lists With No Filters Defined

ToutApp Account under Review

Disable Niko from ToutApp Extension

Setting Up a Syndication ID for a Social Campaigns

Web Personalization (RTP) - Can I Delete or Edit Lables?

Troubleshooting - Web Personalization (RTP) Content Recommendation Engine Not Working

Head Start feature Q&A

My token not displayed correctly in view as webpage version of email.

Edit Schedule Email in ToutApp

Email Previews By List Are Limited To 25 People