Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

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?

Marketo can send key employees notifications of any errors that occur during the Salesforce sync. Follow the steps below to get started. 1. Click Notifications. 2. Click Subscribe. 3. Open the Notification type drop-down, and select CRM Sync. 4. Enter the email addresses to subscribe, separated by commas, then click SUBSCRIBE. That's it! Those emails will now receive important notifications about any problems with the Salesforce Sync.

Issue Lead conversion/qualification through workflows in Microsoft Dynamics CRM resulting to duplicates (i.e. Lead and Contact) in Marketo Environment Microsoft Dynamics CRM Lead conversion Sync Solution While lead qualification through workflows is currently not supported, one approach that we saw implemented by a customer that did not result in duplicates is by redeveloping the lead qualification workflow using the msdyncrmWorkflowTools (1.0.54.0): QualifyLead step. Dynamics-365-Workflow-Tools/Qualify Lead.md at master · demianrasko/Dynamics-365-Workflow-Tools This was verified to result in no duplicates as the workflow writes the "Create [Qualify Lead]' operation type to the Marketo Log which is like the standard qualify button. Should there be any further assistance needed in developing the lead conversion workflow, it's recommended to engage with our Professional Services / Consulting team Root Cause Marketo's integration with Microsoft Dynamics CRM currently does not support custom qualify workflows.

Issue Issue Description After an email send, the number of emails sent is much lower than the number of people that qualified for the sending Smart Campaign or Email Program. Solution Issue Resolution One possible reason you are seeing a different number of emails sent versus the number of people that qualified for that is email is because of communication limits. If a person qualifies for an email, Marketo will try to send it. However, if a lead has already reached their daily or weekly communication limit, Marketo will not send the email (with the exemption of operational emails). To check to see if a lead did not get an email due to communication limits, follow the steps at Email Program Fails to Send Emails.

Question: How are the Original Search Engine and Original Search Phrase fields populated? Answer: Both fields are intended to be populated if the very first webpage visit is due to the lead clicking on a link from a search engine. If the lead logs their very first webpage visit to your website via directly typing in the URL or clicking an email link then the Original Search Engine / Search Phrase will not be populated. Due to security and privacy concerns, current search engines no longer pass this informations, but we retain the fields so that leads who had values populated for them previously can retain that information. .

Summary This method can be used when moving a CNAME from an old instance to a new instance. Often at times, when changing to a new instance, this question can come around, and ones would wonder how to do it or a solution on how to do it. This steps will show you the two phases which I will explain below. (Note: This would need to be done before the old instance deactivated) Issue A CNAME needs to be moved from an old instance to a new instance Solution NOTE: You cannot have the same CNAME in two different instances (Pointing to two instances, e.g. cname1.company.com pointing to instance1.mktoweb.com and instance2.mktoweb.com) Key terms: CNAME 1 = Initial cname in the old instance CNAME 2 = Additional cname created in the old instance INSTANCE1 = Old instance (Instance Name) INSTANCE2 = New instance (Instance Name) Phase 1: --------------- 1. Create an additional CNAME (a replacement CNAME) which you would want to swap as the default in the second step. CNAME 1 > INSTANCE1 (Default) <Existing CNAME in the Marketo Admin > Landing Pages section> CNAME 2 > INSTANCE1 This would be the additional CNAME created for the replacement. 2. Swap the default with the replacement CNAME you just created in step 1 and set this CNAME1 as a domain alias in the old instance. CNAME 1 > INSTANCE1 A domain alias in the old instance. CNAME 2 > INSTANCE1 (Default) ————————————————————————————————————————————————————————————————— Phase 2: --------------- ** Transition might not be smooth during the cutover. 🙂 (The Landing page links might get some interruption during the cutover) During the Cutover (Before the old instance deactivated) : 1. [Your Action] - To remove the CNAME1 which is a domain alias in the old instance (INSTANCE1) 2. [Your Action (IT Team)] - To create CNAME1 as a domain alias in the new instance (INSTANCE2). (During this time the link to old landing pages will be broken) 3. [You need to raise a support ticket to enable SSL for CNAME1 for the new instance (INSTANCE2). If you have any questions, please contact Marketo Engage Support at https://support.marketo.com. Environment Production/Sandbox

Issue An embedded Marketo form on your company website showed up in the past, but is now not showing on the page. Solution Embedded forms may not show if you have mixed content on your website (meaning that your website is using HTTPS, but the embedded form from Marketo is using HTTP). To resolve this, you need to ensure the content from Marketo is also using a secure connection. You can purchase an SSL certificate to use for your Marketo forms by contacting your Customer Success Manager/Sales Account Manager.

Included in this Article: Overview In the Web Personalization platform, you defined a campaign that included certain pages, but you are seeing the campaign appear on pages that you didn't intend them to appear on. Below, we will describe what might be the issue and how to solve it. Why This Happens When defining a segment using the "Specific Pages" parameter, every visitor that views this page will be matched to that segment. Once this happens, the "sticky" campaign will be triggered and will be displayed on every page that includes this Zone id parameter. After the visitor is matched to the segment and the campaign is triggered, the segment is not taken into consideration anymore, so this visitor will keep seeing the campaign every time the Zone id exists on the page. Two Ways to Fix this Problem Set the campaign as "Not Sticky" This will make the campaign show up only once per session, and only when visitors are viewing the specific pages defined in the segment. Go to the Campaigns page Edit the existing campaign Uncheck the box for "Sticky" Use a dedicated Zone id that exists only on the page(s) to include in the campaign In Zone campaigns are displayed in a particular zone in a website, designated by the Zone id. Find "Zone id" in the campaign editor Then, give the campaign a Zone id corresponding to a unique div ID tag on the desired site(s). This will ensure that once a visitor matches the segment and visited this page once, they will keep seeing the Call To Action (CTA) on this page.

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

Issue Description 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. Issue Resolution 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" Supplement: Email Insights Launch Process - Marketo Docs - Product Documentation The solution is to request that Marketo Support backfill the report data so you have data for Email Insights beyond the four weeks. Who This Solution Applies To Customers using Email Insight

Marketo has built-in spam lead filtering for leads who fill out Marketo forms on your landing pages. However, junk leads may still get into your Lead Database. You can use a Smart List to find these junk leads or other leads who you might not want in your database. Here are some examples of leads you might not want: missing company name or last name email address bounced has a personal email address (like yahoo.com) Say you want to find all leads who use a personal email address. You could build a Smart List that checks by using the Email Address and looks for leads whose email address contains a non-commercial domain: Common personal email domains gmail.com hotmail.com live.com msn.com rocketmail.com yahoo.com ymail.com sbcglobal.com comcast.com aol.com netzero.com Is this article helpful ? YesNo After that, it's up to you how you want to handle those leads. You could: ask them to provide a commercial email address (with an email, landing page, and form) stop their emails with Marketing Suspended or Blacklisted (using Change Data Value) delete those leads (using Delete Lead) You can build similar Smart Lists to find potential junk leads such as: undeliverable email addresses -- filter on Email Invalid is true missing a company name -- filter on Company Name is empty

Issue Issue Description A Champion/Challenger A/B test contained in a nested program within an Engagement Program stream only sent the Champion email. Solution Issue Resolution Per the Product Documentation Champion/Challenger tests can be used within Nurture Engagement Programs, however, the email asset with the Champion/Challenger test must be within the stream. Having a nested program in the stream with a local email asset with the Champion/Challenger test will not function; only the Champion Variant will be sent, similar to what happens in other batch sends.

Issue How days are calculated in Wait flow steps and Smart List time-frames. Solution Marketo considers a "day" in a Wait step or a Smart List timeframe to be 24 hours, not a calendar day. So if a Smart Campaign hits a 1-day Wait flow step at 9:30am, it will wait until 9:30am the following day. If a Smart List filter has a look-back timeframe of 7 days, it is specifically looking back seven 24-hour periods.

Due to the way Excel handles CSV files with unicode data, you may need to follow these steps for importing the file into Marketo as UTF-8 data: Set up your Excel spreadsheet properly for your import (for example, removing unnecessary columns) Select all the data in the spreadsheet. Copy it to the clipboard (control-c in Windows, command-c in OS X) Paste the data into a text editor -- Notepad in Windows, TextEdit in OS XSave the file. In the "Save As" dialog, pick the UTF-8 option in the Encoding section at the bottom of the dialog In TextEdit, set the file to text only using Format -> Make Plain Text before pasting Save the file. In the "Save As" dialog, pick the UTF-8 option in the Encoding section at the bottom of the dialog Import the file into Marketo as a "Tab-separated values" file Your unicode characters should import correctly.

Uncover powerful, yet simple-to-use features of Design Studio. Join Don Mayberry, Marketo Support expert, as he reveals the lesser known treasures in Design Studio that will help you hone your craft. In this session, you will learn: Key features of the Email Editor and Landing Page Editor to craft the email and landing page to your needs. How to manipulate content on your landing page. Watch the recorded webinar Useful resources: CampaignMonitor.com specifically; Guide to CSS Support for Email Clients Design Guidelines Top HTML Email Coding Mistakes from Mailchimp.com Tools for FireFox Colorzilla Firebug Download Attachments: Master-Design-Studio-1-2011.pdf

Issue Description In sent emails, if the system token {{system.viewAsWebpageLink}} is used, the link will load successfully on web browsers. However on the same browser session, after refreshing the page once, the link will return an error "Cannot get email content- Customer does not belong to any POD". Issue Resolution After Marketo's 2019 Q1 release, a security enhancement has been set for Marketo emails. When loaded on a browser, a View as Webpage Link will include the recipients' unique mkt_tok parameter. If recipients of the Marketo emails were sharing these links, this would mean that they are also sharing their unique/private mkt_tok with third parties. With this enhancement, the view as webpage link is only expected to load once and the mkt_tok value which is contained in the link will disappear after the page has loaded. With the removal of the mkt_token value on the link, hitting refresh will send a request to Marketo that does not contain the recipient's lead and email information, so there is no data for the link to return.

Issue By default, new Marketo person records will not automatically sync to Salesforce to create new Lead records. There are other actions required to get these new records into Salesforce. Solution In order for new Marketo person records to sync over to create new Salesforce Lead records, they will need to be run through a Sync Person to SFDC flow step or be given a member status in a Program that is synced to a Salesforce Campagin. Sync Person to SFDC flow action: You can sync a new Marketo person record to Salesforce using this flow action as either a single step flow action or as a flow step in a smart campaign. Single-Step Flow Action: In Lead Database, select the Marketo person records you want to sync, click Person Actions > Salesforce > Sync Person to SFDC Flow Step: Creating a smart campaign that utilizes the Sync Person to SFDC flow step will sync the Marketo person record to Salesforce. Note: Other SFDC flow steps, such as Change Lead Owner, or Change SFDC Campaign status, will also sync the record to Salesforce, since the record must be in Saleforce in order for these steps to execute. Program Member Status Sync: Giving a new Marketo person record a member status in a Program that is synced to a Salesforce Campaign will sync that new person record to Salesforce during the next scheduled Salesforce sync.

Problem/Issue: You created a new custom field in Salesforce and see that Marketo synced to it successfully the first time. You later decide to change the name and/or type in Salesforce. After making the change, you checked Marketo to confirm the change, but can no longer find the custom field; or, you find that the field name and type did not change. Resolution: Once a new field name and type is picked up by Marketo during the first sync, Marketo keeps the original properties. A manual change is required in Marketo in order to properly sync to the right field/type.

Issue Description You see a soft bounce on a lead and in the details you see it show System send failure: Reply-To address parse error (value of the address) Issue Resolution Confirm the tokens you are using are for the proper field and that the value for the field is an email address. The parse error occurs when we cannot generate or create a proper email address in the From Email or the Reply To Email fields. The error will show in the parenthesis the value we tried to put in.. For example Service Department is in the parenthesis, this would be an example of a incorrect field being used. Is this article helpful ? YesNo

Abuse Report An abuse report is when an email recipient forwards a complaint directly to abuse@marketo.com. Marketo’s Privacy and Compliance Team processes all complaints to these addresses and will unsubscribe the complainer when possible. Feedback Loop Complaint A feedback loop complaint is when an ISP forwards the complaints that originate from their users. For example, when someone clicks the SPAM or JUNK button in their email client. ISPs that offer FBLs expect that subscribers like Marketo will mark the complainer as unsubscribed in the original database. Marketo does process FBL complaints and marks the email address as unsubscribed. Additional Information: Feedback Loops (FBL) Abuse Report Deep Dive Finding Leads that are Auto Unsubscribed for Email Spam Complaints / Feedback Loop (FBL) Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Subscribe to Salesforce Notifications

Duplicate leads after lead conversion in Microsoft Dynamics CRM

Seeing a Lower Number of Emails Sent Than People That Qualified for a Campaign

How are the Original Search Phrase and Original Search Engine fields populated?

Moving A CNAME From An Old Instance To A New Instance

Embedded Form No Longer Showing on Your Webpage

Troubleshooting Web Personalization (RTP) – Campaigns Appearing on the Wrong Pages

Why do I see workspace partition while selecting Munchkin?

Discrepancy between Email Insights and Email Performance Report

How Acquisition Date is Populated

Finding Junk Leads

Champion/Challenger Test in Engagement Program Only Sending Champion Variant

How Days Are Calculated in Wait Flow Steps and Smart List Time-frames

Importing Unicode Data into Marketo

Mastering the Elements of Design Studio (Legacy UI)

Email Viewed as Webpage Returning an Error after Refreshing Browser - "Customer does not belong to any POD"

How to Sync New Marketo Person Records to Salesforce

Marketo is unable to sync to the new field name and type after it was changed in Salesforce

Soft bounce "System Send Failure Reply-To address parse error"

What’s the difference between an Abuse Report and a Feedback Loop Complaint?