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 When using the Merge Lead(s) REST API end-point and merging multiple leads, which field values would be copied to the winning record? In the below example, the winning lead record has a blank value for Job Title. When merging all 4 leads, which field value will get copied to the winning record from the list of losing records? This is a article attached image Solution The field values that will be injected to the winning lead record are directly impacted by the order of leadID's in the Lead array parameter of the call, where the FIRST leadID listed in the parameter array will be the winning value IF the field on the winning Lead record is blank. URL Example {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=2232,1323,1455 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = 'electrician'. URL Example #2 {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=1323,1455,2232 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = blank/empty. Root Cause This is the expected behavior when merging multiple leads via the REST API Merge Leads end-point.

Issue Tokens in form-triggered emails are not populating values when a new lead comes in through form fill out. Solution For the token to populate, the associated Marketo field shouldn't be empty and it must hold a value that will be passed to the token. It takes a small amount of time for the form to write the value to the lead record and it my not write all the info before the triggered email is sent. In case of new leads, using a wait step as the first flow step (before send email flow step) will be helpful. This will leave some time for the fields get their value filled from the form fillout. Once the fields have the value, the associated token will populate correctly during the email send.

Issue When attempting to publish a landing page to Facebook, you get the error "Error when calling Social Campaign API. Warnings: Error while creating facebook tab." Solution If you haven't purchased Ad Targeting add-on for your instance, you could face this issue. You can contact your Customer Success Manager to include this add-on in your Marketo subscription. If you are facing the issue in spite of having ad targeting add on to your subscription, we would suggest that you contact Marketo support and we will be able to troubleshoot it for you.

Issue What happens when you enable "Send all Tout emails in my team through this server connection" within the SMTP Server settings on ToutApp.com. Solution When you select "Send all Tout emails in my team through this server connection" within the Tout admin panel, this will provide the option to all standard users to either choose to use the ToutApp Email Servers or your company's own Email servers. If you decide to share the SMTP Settings with the team, t is recommended that you have your IT team setup a dedicated STMP/Email account to use as the Custom SMTP Credentials. Note: Each user can choose to either use the Tout servers or the configured & shared SMTP server. It is not applied automatically to all users.

Article Text Included in this article Overview The Background The Problem The Solution Overview RTP gives a dashboard that provides lots of valuable information about your RTP instance and how everything is performing. One of the widgets in this dashboard is Top Industries. This widget is designed to give you a breakdown of the top performing industries, but sometimes the industry widget is empty: The Background When a segment is saved in RTP, it is automatically assigned a type. If the segment contains only the Industry filter, then it is assigned the 'Industry' type and is included in the Industry widget on the dashboard. So, this widget only contains information on Industry segments. If it is not an Industry segment, it will not be included here. The Problem You can obviously add more filters to the segment other than Industry. However, if the segment contains other filters, then it is assigned the 'Complex' type and is not included in the Industry widget. The only information that will display in the Industry widget is what comes from segments that use only the Industry filter and that alone. The Solution If you'd like a particular segment to display in the Industry widget, there are two options: 1. Remove the other filters other than Industry. 2. Create different additional Industry-only segments.

Issue After the campaign is run for deleting leads, the result tab shows as "No activities found". Solution Whenever a lead is deleted using a Smart Campaign, the results tab will not show the list of leads that got deleted as they are not available in the database anymore. However, with the help of "Run History" tab you will be able to see the number of the leads that got deleted. Once the campaign is run and the "Delete Person" flow step is executed, the lead will be deleted immediately from the Marketo database.

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 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 You receive an error in ToutApp - "IMAP access is disabled for your domain. Please contact your domain administrator for questions about this feature. (Failure)" Solution This due to an invalid Gmail connection For this error message to be resolved, we recommend looping in with your Gmail Administrator regarding the IMAP access of your domain and whether or not it can be enabled. See the link below for additional reference on this for your Gmail Administrator: https://support.google.com/a/answer/105694?hl=en

Issue You have recently added a new field to a SFDC Custom Object which is synced to Marketo, but you do not see that new field available on the object in Marketo. Solution To have the new fields pulled over to Marketo, disable your SFDC global sync within Marketo and then refresh schema for custom objects. This should pull over the new fields on that custom object to Marketo. Once the schema is refreshed, please make sure that the global sync is turned back on. We would also suggest that you refer the below document which will guide you on the above steps. However, the below document is meant for first custom object sync. The same steps need to follow up for the existing object sync as well. SFDC Sync: Custom Object Sync

New Features: Audit Trail - An enterprise-class feature that gives organizations full visibility into user activity. Chronological activity log viewable at each level of the hierarchy (from the home tab hierarchy to the detailed line item level). Search, filter, sort, and export detailed audit data. 90-day historical view (with the ability to request data past this period). Access via the >> arrows at any level of the Home or Budget tab hierarchy. Available to Owners and Admins only. Advanced Searchable Drop-downs - Making our product easier to use for end users. No more scrolling through large lists! Just type to filter the list to your desired value and hit enter. Enhancements: Improved Import Budget Feedback for Multi-Select Fields - error messages now include the: Exact row and column where the data needs to be adjusted. Exact issue with the data. ***For budget imports with multi-select fields only. HTML User interface Update - The Details, Roll-up and Budget Panels as well as Import Schedules have been transitioned to HTML5. The new HTML panels include the following usability enhancements: Navigation - The ability to tab through fields and select values using your keyboard. Saving - Faster and less intrusive saving (with a saving.../saved notification giving you immediate feedback). Layout - See everything in view-only mode first for a cleaner interface. Identify what cells are editable with a pencil icon on hover and a single click to edit.

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/

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.

Issue "Currency" type fields are rounding off their value. For example, if you enter the value as 8092384905, Marketo is automatically rounding it to 809239000. Solution This is an expected behavior. TThe currency field type in MySQL is considered to be a Float field and MySQL will automatically round the values in our current database structure. As a work around for this, change the field type to "string" . Since standard fields type cannot be changed, we suggest that you create a new custom field of type "String" to use instead of the standard field..

Issue Change Lead Owner reason shows "Synched from salesforce.com - fixup Lead Owner." Solution The "synched from salesforce.com fixup lead owner" activity means the lead owner was switched within SFDC, often times through auto-assignment rules. The phrase "fixup Lead Owner" is what Marketo records when it is taking the Owner ID being passed from Salesforce and translating it into the Lead Owner values (First Name, Last Name, Email Address, etc) to populate into Marketo.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

What Field Values Are Copied to Winning Records When Merging Multiple Records From REST API

Do I need a dedicated Microsoft Dynamics CRM user for the integration?

Email mailto: Link Not Working

Tokens in Form-Triggered Emails Are Not Populating for New Leads

Error Publishing Marketo Landing Page to Facebook

Syncing with SFDC Big Objects

ToutApp Custom SMTP Team Settings and How They Work

Troubleshooting Web Personalization (RTP) -- The Industry widget in the Dashboard is empty

Delete Leads Smart Campaign Showing No Results

Head Start feature Q&A

FORMS 1.0 - Change Your Form Label Layout

Creating a New SFDC Lead with Every Form Submission

ToutApp Error: IMAP Access Is Disabled for Your Domain

New Fields Created on SFDC Custom Object Not Found in Marketo

Marketo Financial Management Release Notes 05/14/14

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

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

Currency Type Field Is Rounding Off Its Value

Change Lead Owner Activity Shows Reason Synched from salesforce.com - fixup Lead Owner

Edit schedule email in ToutApp