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 An email you previously had in Marketo under a program in Marketing Activities no longer exists and you believe it was deleted. However, you do not see that deletion in the Audit trail. Solution If an email was deleted directly, by un-approving the asset and then deleting it from the program, this activity will be seen in the Audit Trail. However, if the program containing the email is deleted, the individual email's deletion will not show in the audit trail. Only the program deletion will be displayed.

Issue Running a Revenue Cycle Explorer report on Opportunities shows programs from long ago are being credited for those Opportunities through Multi-Touch (MT) Attribution measures. Solution When using Multi-Touch measures, past programs will also be credited if a contact on the Opportunity achieved success in the program. A possible workaround could be to utilize Filters in the RCE report to try to narrow the results.

Issue Description Can a Default program in a nurture stream be changed to the Nurture Channel for reporting purposes? Issue Resolution Program Channels can only be applied to one type of Program. Nurture Channel will only be usable on a Engagement type program. You can however have multiple channels avaliable for a specific type of program! So you can have one program type with multiple channel options, but you cannot have one channel used for multiple program types.

Issue User cannot add a Field Organizer when the user does not have access to all workspaces. Solution Unless the user has access to all workspaces, they cannot create a field organizer because field organizers are available in all workspaces. However, the user still can access and even delete the field organizers that are created by others. Who This Solution Applies To Instances with workspaces

Dear valued customer, As you may know, on July 25th, 2017, our main web site, Marketo.com, along with other Marketo domain properties, were rendered inaccessible, preventing access to our application from 4:06am – 10:08am PDT. We apologize again for the inconvenience this caused. On the Marketo Trust site, you’ll find current and past Marketo system performance data including System Uptime and Reliability. This is monitored 24x7 and we have consistently maintained greater than 99.9% uptime. This uptime is calculated based on the length of time that the Marketo systems are functioning properly within our servers (“pods”). While the Marketo systems were functioning and available by 10:08am PDT, we realize that due to third-party DNS propagation timing, some customers may have experienced delays in accessing our systems of up to 48 hours, depending on region. All Marketo back-end processes such as Smart Campaigns were still operational during the DNS propagation, however, the propagation reduced accessibility to Marketo for some users. As a result, we believe the normal calculation of system uptime may not accurately reflect everyone’s experience. To address this, we have decided to make a one-time change to our normal calculation for July to more closely track what our customers may have experienced in terms of accessing our systems regardless of whether the problem lay with us or was due to third party systems/processes. After studying the issue, we think the best way to calculate this is based on customer logins to the system. We looked at the first login time for each pod and used login as a proxy to calculate when customers were able to access Marketo. This one-time calculation is a better reflection of the frustration you may have experienced in accessing Marketo. We will return to using our normal calculation for August. For the month of July, our server pod uptime was 99.997%. All back-end systems, such as smart campaigns, were processing normally while the domain was offline, so when calculated in the normal way, our server pod uptime for July was 99.997% When taking into account the 6 hours when the marketo.com domain was not available, the system uptime for the month of July was 99.17% As mentioned, if we add the full extent of the DNS propagation as discussed above, and take an average of the first logins across the entire customer base, the average user accessibility for July would be approximately 97.77%. For additional information please contact Marketo Support and see our FAQ document and this letter from our CEO Steve Lucas.

Note: Please ensure that you have access to an experienced JavaScript developer, because Marketo Technical Support is not set up to assist with troubleshooting custom JavaScript. Is this article helpful ? YesNo The default subscription management records the email address through hidden fields when users click the unsubscribe link in emails. A simple JavaScript can capture the email parameter and pre-populate a visible field. Drag and Drop a "Custom HTML" object into the top of the unsubscribe landing page. Add the following code: <script language="Javascript" src="/js/public/jquery-latest.min.js" type="text/javascript"></script> <script src="/js/public/jQueryString-2.0.2-Min.js" type="text/javascript" ></script> <script> // to set cookies. Uses noConflict just in case var $jQ = jQuery.noConflict(); var pEmail = $jQ.getQueryString({ ID: "Email" }); document.getElementById("Email").setAttribute("value", pEmail); </script>

Issue Values for a person were changed while they were in a wait step and you want to know if this will affect the values they see in an email they are set to receive after they come out of the wait step. Solution When a lead enters a wait step, they are put on hold until the specified time. The logic is simply to wait until the specified time, then move on to whatever the next step is. The next step can even be changed while people are waiting, and they will go on to the new step. No content is generated in preparation of them exiting the step. When the wait step ends, the person moves on to the next step in the flow. Any information that was updated while they were waiting will be reflected in that next step. Thus, if values were changed while they were in the wait step, those new values will appear in the email they are sent after the wait step.

Marketo recommends keeping the FT (First Touch) and MT (Multi-Touch) in separate reports . Though they are attribution metrics, FT and MT use different measures to derive pipeline and revenue attribution. One should not try to compare FT and MT metrics and having them in the same reports may cause confusion. Step 1: In RCE, Program Opportunity Analysis, identify the Program and Opportunity of interest. If verifying FT, pull in relevant FT metrics. Ditto for MT. Also pull in Opportunity Closed and Opportunity Stage. The combination will tell you if the status of opportunity (open, won, lost) - which does affect attribution. Step 2: For the opportunity, find out the lead(s) associated to that opportunity and opportunity create/close date, status information. One way is to get this information is to do so in SFDC. In SFDC, search for that Opportunity and scroll down to the Contact Role section to identify the associated leads (contact). Other opportunity information should also be available. Another way is in RCE, Opportunity Analysis area. Filter Opportunity Name to the opportunity of interest. Pull in # of Opportunities and Lead Name. You can also find out oppty create/closed date, status in this area. Step 3: Find out acquisition and success status/dates for the leads in the program In Marketing Activities, go to the program and click on Member. Search for the lead by name. The column Acquired By and Success will tell you if the lead is acquired by the program and/or achieved success, respectively. If the lead is acquired, to get Acquisition Date for this lead, in the lead grid, choose column Acquisition Date If the lead achieved success, to get Success date: Go to Lead details, click on Activity Log tab Search for program name and filter on activity type 'Change Status in Progression' Locate the FIRST success activity when a lead changed to a successful status. RCA only counts the first success. The activity date is the success date. Step 4: Evaluate if program is qualified for attribution for the program The combination of Acquisition program/date, success status/date, opportunity create/close dates and opportunity status will help determine FT/MT attribution. The rules of attributions is documented in Product Docs. With all the information gathered, you can now determine if the program is qualified for attribution for this opportunity. Again, this technique is to verify if the program should get some attribution and doesn't necessarily give you the exact units and dollars.

Issue How deleting or archiving programs will affect the Lead field: Acquisition Program. Solution If you delete a Marketo Program, the field will append a "deleted" at the end of the Program Name. For example, if the Program Name was "July 2016 newsletter" for Acquisition Program, after deleting the Program, the field value would change to: "July 2016 newsletter - deleted (####)". The numbers represent an activity ID on the backend. Note: Archiving Programs does not affect the Acquisition Program.

Issue Person/Lead Source is empty. Why isn't it populating? Solution Marketo does not automatically assign Person Source. We do populate Original Source Type. Assigning credit for a Lead can only be determined by someone with intimate knowledge of a company's marketing strategies. If someone fills out a form, Marketo doesn't know if they were brought to that form by an email blast, TV commercial, talked to a salesperson, or any number of other reasons. If they came in through a List Import, they could have attended a Tradeshow and signed up there, they could have been exported by a CRM and are being imported, or any number of other ways. There are many discussions on best practices for handling Lead Source attribution in the Community. If you need assistance setting up Smart Campaign to update the Lead Source based on your specific business criteria, please contact Marketo Support.

Issue Can Interesting Moments and Web Activity be written on the Account object in SalesForce? Solution Marketo does not have permissions or capabilities to write to the account object. Marketo can only write data to the Contact or Lead Object in SalesForce. If you want to have that data recorded on the Account object, you would be able to setup a custom SalesForce work flow to add that data to a field or as an activity in SalesForce. This data will not be usable or recognized by sales insight however.

I'm trying to find out who had a lead score change from a specific smart campaign - would I use data value changed with a reason or some other filter? The Data Value Change trigger/filter with the Reason constraint is appropriate for finding leads that had their Lead Score changed by something such as a manual edit or Smart Campaign. This is a article attached image This is a article attached image This screen shot shows examples of how you might set this up. The list below shows a few of the values you may see in the Reason field. If you know the exact phrase you are looking for, use the "is" operator. For example, "Changed by Smart Campaign Contact Us." If you don't know the exact value, try using the operator "starts with" or "contains." Synched from salesforce.com Changed by Smart Campaign System flow action System action reset Form fill-out SOAP API Manual lead edit Munchkin API Import/merge into list The Reason filter constraint is available in these filters: Data Value Changed Lead Partition Changed Progression Status was Changed Revenue Stage was Changed Not Data Value Changed Not Lead Partition Changed Not Progression Status was Changed Not Revenue Stage was Changed

Issue When comparing the Engagement Score on the Engagement Dashboard, the scores do not match with the Email Insight Engagement Scores. Environment Engagement Program Email Insight Solution The Engagement Score from the Engagement Dashbaord will hold the most accurate information as this is direct information, rather than for example with RCA/RCE and Email insights where the data source is different. If you want to see Engagement Score over a period of time more accurately, use the Engagement Stream performance report: Engagement Stream Performance Report | Adobe Marketo Root Cause The Engagement Score on the Engagement Dashbaord only calculates the last 3 casest, it is also important to remember that the engagement score only includes emails that were cast more than 72 hours ago. As per this documentation: The Engagement Dashboard | Adobe Marketo In comparison, the Email Insight Engagement Score is calculated over a period of time that is set by the user but the data can still be mismatching, this is due to the fact that the data source is not the same from the Engagement Dashboard.

Issue New user gets message that the password link is expired when attempting to login for the first time. Solution If the invite isn't accepted within 24hrs of the first invite email being sent, it expires and there is no way to re-send it. You will need to delete the user and create a new one with the same email address. After you delete a user, it take a few minutes to clear out of the backend, so if you get a message that the user is already in use, just wait a few minutes and try again.

Issue After creating an Email Program with an A/B test, you create smart lists (or smart campaigns) and would like to use filters such as "Opened Email" for the A/B test email. When starting to type the A/B test email name into the smart list filter, the A/B test email name does not show as available to select (it may show a red squiggly line). Solution The Email Program (with the A/B test) needs to be in "Approved" status before the A/B test email assets can be entered into a smart list filter.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Cannot See Deleted Email in Audit Trail

Past Programs Credited With Current Opportunities

Can a Default program be changed to a Nurture campaign channel?

User Cannot Add a Field Organizer Without Access to All Workspaces

I have a Marketo instance currently synced to salesforce.com, can I now change the integration to sync with a Microsoft Dynamics CRM integration?

Marketo System Uptime - July 2017

Pre-populating email address in subscription forms through visible fields

Values Changed While a Person Is in a Flow Step

Landing Page Test Group Rerouting To Fallback Page

How To to Identify a Unique Relationships between Opportunities and Programs

Keep the "Clear" form button on the same line as the "Submit" button

Program Acquisition When Deleting and Archiving Programs

Person/Lead Source is Empty

Interesting Moments and Web Activity on the Account Object in SalesForce

Using the Reason Constraint on the Data Value Changed Filter

Why is my Engagement Score not matching with the Engagement Score in Email Insights?

Expired User Invite Email

ToutApp: Unable to delete Template categories

Is it possible to use universal ID for API user

Unable to reference AB test email in smart list or campaign