Knowledgebase

Sort by:
Issue Marketo Forms embedded on non-Marketo web page do not show up when using Firefox private browsing.   Solution Marketo forms and Munchkin tracking are inserted into non-Marketo pages via Javascript. If the browser privacy settings block the script from executing, Marketo forms and tracking will not work.  Marketo is not able to override a customer's browser security settings. The alternatives are as follows: Create a non-Marketo form on the web page Use a backend form submission to push the info in the form into Marketo. Instructions for doing so can be found here: http://developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/  
View full article
Issue Description REST API call, Get Lead Activities , is returning 603 error   Issue Resolution Error 603 refers to 'access denied' where authentication is successful but the user doesn’t have sufficient permission to call this API. Additional permissions may need to be assigned to the user role. http://developers.marketo.com/rest-api/error-codes/   Go to Admin > Users and Roles Select API User and identify what role it is assigned to (e.g. API role) Go to Roles and check the permissions assigned to the API role Check to see if the API role does not have 'Read-Only Activity' or 'Read-Write Activity' permission In order to make a Get Lead Activities REST API call with the API user, the API role of the user must be modified to have permissions to  'Read-Only Activity' or 'Read-Write Activity'. If you use Workspaces and Partitions, make sure the API User has the necessary access. Is this article helpful ? YesNo
View full article
Overview GoToWebinar is changing their authentication protocol used for API access. Their legacy protocol, OAuth v1.0, will no longer be used after January 31, 2019, and all services accessing GoToWebinar (Marketo) will be required to use the new authentication protocol, OAuth v2.0. Marketo has already updated our system to utilize the new OAuth v2.0 authentication protocol for new login authentication. All newly initiated service authentications between Marketo and GoToWebinar will use OAuth v2.0. However, all existing GoToWebinar services currently logged in and in use now must be reauthenticated manually. All customers who use GoToWebinar must reauthenticate each of the logins for these services in your Marketo instance by navigating to Admin > LaunchPoint. Any API calls still using OAuth v1.0 after January 31 will fail. This will result in statuses not being shared between Marketo and GoToWebinar and will prevent users from syncing Event programs with a GoToWebinar event. FAQ Why is this change happening? GoToWebinar is strengthening their security protocols for API login access to their services. This requires using an upgraded version of the login protocols, known as OAuth v2.0. Is this a Marketo change or a GoToWebinar change? This change is being implemented by GoToWebinar to strengthen their security protocols. Marketo has upgraded our system to allow a seamless transition, but the protocol change is being made by GoToWebinar. When does this take effect? The new protocol version OAuth v2.0 is active and in place now. GoToWebinar has placed an announcement on their status page stating that the deprecation of the legacy OAuth v1.0 is scheduled for January 31, 2019. All connections between Marketo and GoToWebinar that are still using the legacy OAuth v1.0 protocol will be refused by GoToWebinar after that date. This includes new access requests as well as those currently active and in use. What do I need to do? Reauthenticate your GoToWebinar services with a fresh login from within your Marketo instance before January 31, 2019. Why do I have to do it myself? Marketo has made the changes necessary to utilize OAuth v2.0 for new authentication logins being made moving forward. However, all logins already in use were initiated on the older protocol, OAuth v1.0. Marketo doesn’t know your personal login credentials, so you need to do the reauthentication directly. Is there a different procedure for how to enter the credentials inside the Marketo UI? No. The update Marketo made was on the back end, so there is nothing different to how you enter the info. The UI is the exact same as it was. What happens if I don’t reauthenticate the login before January 31, 2019? All connections between Marketo and your GoToWebinar services will be refused by GoToWebinar on their end. If I miss the deadline and the connection is shut off, how will I know? You’ll find error messages in your Marketo instance where the services are used. See the section below for “Symptoms of a disconnected service” to know what to look for. If I miss the deadline and the connection is shut off, how do I get it working again? Reauthenticate your login credentials in Admin > LaunchPoint. See the “Customer Action Needed” section below for step by step directions. Customer Action Needed All customers who use GoToWebinar must reauthenticate the login credentials for each user. This must be done before January 31, 2019 to avoid experiencing disruption of your services. 1. Navigate to Admin 2. Click LaunchPoint to open the list of Installed Services 3. Click and open the GoToWebinar service to edit it 4. Click the Log into GoToWebinar button. 5. In the GoToWebinar Sign In pop-up window, enter your GoToWebinar email and password and click Sign In. 6. After the window closes, click Save DONE! By reauthenticating the login, you’ve ensured that the service is using the new OAuth v2.0 protocols. Symptoms of Disconnected Service Here is a list of what to expect if the integration with GoToWebinar is disconnected due to the deprecation of OAuth v1.0 on January 31, 2019. 1. The service listing in Admin > LaunchPoint will have a status of Failed along with a few details. A. Reauthenticating your login credentials will resolve these errors. 2. Event programs that have not yet synced with GoToWebinar will be unable to sync and will return errors. A. Reauthenticating your login credentials will resolve these errors. B. For reference, here is the documentation on how to sync an Event Program to GoToWebinar. 3. Existing programs which were synced with GoToWebinar prior to the deprecation will show no difference. However, if anyone is added to the program with a ‘Registered’ status, Marketo will attempt to push this record to GoToWebinar and will fail due to the deprecation of the OAuth v1.0 protocol. This will give the record a status of ‘Registration Error’. If this occurs, this data is not lost. A. Reauthenticate the GoToWebinar service B. Manually refresh the webinar attendance. Navigate to the Event Actions menu of your Event Program and select Refresh from Webinar Provider 4. Records that were already registered with GoToWebinar before the service stopped will still be able to receive the correct {{member.webinar url}} token. That data for the token will already be in Marketo, so reminder emails will still have the right links to the actual webinar even if the service was stopped after they were registered. The attendee report won’t be able to come down from GoToWebinar with the connection cut off, but at least your leads will still have the link to get to the webinar. 5. If the service is no longer active and an existing webinar completes, normally this would record attendance information and sync this back to Marketo and change the status of program members. However, if the service is inactive, this will fail silently, and no status change will occur. Manually refreshing from webinar provider will also silently fail if done while the service is still inactive. The notification will show that there are no updates. A. Reauthenticate the GoToWebinar service B. Manually refresh the webinar attendance. Navigate to the Event Actions menu of your Event Program and select Refresh from Webinar Provider C. Now that the credentials were reauthenticated and the service is back online, the manual refresh will work properly. How to Get Additional Help Feel free to ask questions in the comments section of this documentation. Our Support team will be monitoring the comments to help answer your questions. You can also Contact Marketo Support at any time.
View full article
Leads can be auto unsubscribed due to default Feedback Loop setup with the ISPs listed on this page. You can use the following filters to find leads that have clicked the SPAM button in your emails:     Filter 1: Data Value Changed Attribute: Unsubscribe New Value: True Reason: Contains, Customer Complaint Received from ISP.   (Optional to Specify what Email Domain) Filter 2: Email Address Email Address: Contains, @domain.    
View full article
Marketo has the ability to see and pull data from Salesforce Formula fields, there is however a catch which will be explained in this article.   Everytime the Marketo Sync connects to Salesforce it will scan records and look at the " SytemModStamp " (salesforce system field) for each one of them. It will compare this value with the stored value, which was pulled at the last scheduled sync. If the values match, Marketo will move on to the next record. If the values are different (new value later date than previous value) , then Marketo will do a compare and contrast of all fields on that record in both systems and update the information as needed.   When a normal non-formula field is updated and changed on a Lead/Contact record in SFDC, the SytemModStamp value is updated. This is how on next sync Marketo knows to do a compare/contrast check and pull updates. Formula fields do not behave the same way. A formula field is calculated based on data in fields called upon in the formula; this means that the formula field calculation itself will not update the SytemModStamp in Salesforce.   Chances are you already have existing records in SFDC and Marketo. If you were to create a formula field today in your instance of SFDC and have it sync down into Marketo, the data calculated for the formula field in SFDC will not come into Marketo right away. The reason for this is, the formula field has created data based on already existing data, this does not result in a SytemModStamp change.   Typically formula fields will be a calculation of data from fields which are somehow related to the lead/contact record. This means that moving forward, any change in the normal field, will result in a SytemModStamp change as well as a recalculation of the formula field. In this case, Marketo will see the updated SytemModStamp due to the normal field change. Marketo will do the compare/contrast excercise and find that the formula field also needs updating.   If you create a formula field in SFDC and would like to have all the historical data for the formula field to come into Marketo, you can force an update on the records in SFDC to update the SytemModStamp. This way, on next sync, Marketo will see the formula data and pull it in. Alternatively, you can simply allow for natural SytemModStamp updates in SFDC to occur which should result in a slow trickle of historical data from SFDC into Marketo for the newly created formula field.   You can only use data from a formula field in Marketo to segment data and filter. If you try to do a change data value, Marketo will accept the change, tries to sync it to Salesforce and fails to update there. Eventually the Salesforce calculated value will come back into Marketo. Is this article helpful ? YesNo
View full article
Here are directions for changing a one column form into a multi-column form. Set up your form To create a two column form, first you need to make some changes to the form that you're using.  First, you need to reorder your form fields.  The (visible) fields get divided into two columns by odds and evens -- odds in the first column and evens in the second column. If you want to arrange your fields like this: First Name Company Name Last Name Phone Number Email Address Then you need to order your form like this: First Name Company Name Last Name Phone Number Email Address Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Also while you're on the form, note the values for Label Width, Field Width, and Gutter Width in the Form Properties: Set up your landing page On your landing page, add the form to that page (if you haven't added it already).  Make sure you leave enough space on the page so that the form looks correct once it's laid out in two columns.  The two column form will take half the height and twice the width of the single column form. Next, drag in a Custom HTML box and add the following code.  It does two things: rearranges your form into two columns and (via Javascript) corrects the tab order of the form fields. In the code below, you need to change the column width and form width to match your form.  You'll need the Label Width, Field Width, and Gutter Width from your form which you wrote down earlier: Column width (300px below) must be at least (Label Width + Field Width + Gutter Width + 46) Form width (700px below) must be at least (2 * Column width) <style type='text/css'> form.lpeRegForm li.mktField { float: left; width:300px; clear: none; height: 26px; } form.lpeRegForm ul { width:700px; } #mktFrmButtons { clear: both; } </style> Moving the error messages Depending on how you set up your form, the error messages that appear on each field may be in the wrong position. Use this CSS to move the error messages below the field. You may need to tweak the left or top amounts until it appears correct on your form. <style type="text/css"> span.mktFormMsg { left: 0px !important; top: 15px !important; } </style> Changing the tab order For a vertical tab order (as opposed to horizontal), add this javascript in that same Custom HTML block: <script src="/js/public/jquery-latest.min.js" type="text/javascript"></script> <script type="text/javascript"> var $jQ = jQuery.noConflict(); $jQ(document).ready(function() { // fix the tab order $jQ('.mktInput :input').each(function(i) { if (i % 2) { $jQ(this).attr('tabIndex',30000+i); } else { $jQ(this).attr('tabIndex',i+1); } }); }); </script> That's all!  After you add that code, you should see that the form now is laid out in two columns: Adding section breaks To add multiple sections in your form, you need to know the IDs of the fields immediately before and after the break.  See this article for instructions on getting the field IDs: Setting or Getting a Form Field Value via Javascript on a Landing Page In this case, we'll add a break between email address ("#Email") and company name ("#Company").  Add this inside the $jQ(document).ready() javascript block: $jQ('#Company').parents('li').css('clear','both'); $jQ('#Email').parents('li').css('margin-bottom','20px'); When done, it will look like this. This section break may mess up your tab order.  Delete the javascript block that assigns the tab order ($jQ('.mktInput :input').each(...)) and use jQuery to assign them manually, It tabs in ascending order: $jQ('#FirstName').attr('tabIndex',1); $jQ('#Email').attr('tabIndex',2); $jQ('#LastName').attr('tabIndex',3); ... Download Attachments: Two column forms-JS.txt
View full article
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. If you're trying to use the Munchkin API but not having any success, try these tips:   Include the Munchkin JS   Make sure you include the required lines of Munchkin Javascript on pages with API calls.  You can find the javascript in the Admin section under Munchkin Setup . Check "Enable Munchkin API"   In the Munchkin Setup page, check the box that says Enable Munchkin API , put in a private key (which can be any text), and click Save .   Look for JavaScript errors   Use Firebug on Firefox or enable IE JavaScript debugging to check for JavaScript errors.  Any JavaScript errors that occur -- anywhere on the page -- could prevent Munchkin from working.   Escape special characters   Check and make sure that any quotation marks or other characters that require escaping are properly escaped.  See this document for more.   Call mktoMunchkin first   In your Javascript, you must call mktoMunchkin() before you use any other Munchkin API calls.   Try a proxy program   Use a web traffic capturing program like Firebug (for Firefox) or Fiddler.  The return code from the API call may have useful information to help you diagnose the issue.     Click Link or visit WebPage isn't working   Check to make sure you have only a path listed in the url parameter -- no ", no domain, and no URL parameters.   Associate Lead isn't working   This could be caused by a few issues:   Include an email address   Email address is required when using the associate Lead call.  If you don't use this, the call will always fail.   Check the labels   Marketo expects the labels (like "Email" and "FirstName") in a specific format.  You can get these labels in the Field Management page of the Admin section.  When you get there, click the Export Fields button.  The spreadsheet will have the API names for your fields.   Check the hash value   The hash value is the SHA1 hash (non-HMAC version) of your API Private Key (not your Munchkin ID) concatenated with the lead's email address, as in your-secret-keyemail@address.com .  The hash value must be lowercase.
View full article
Issue You need to obtain data in the fields on a Marketo Custom Object.     Solution Marketo does not have Marketo Custom Object data export option in the UI. Smart Lists will show a list of leads with that specific attribute, and you can see custom object data on an individual Marketo record. However, using API, you or your dev team can query the Marketo database to access all values on these objects. Find out more at Custom Objects.    
View full article
Issue What does the Data Value Change activity with following reasons mean? System flow action sysActionChangeDataValue updateLeadEmailStatus System flow action sysActionChangeDataValue resetLeadEmailStatus Solution Both Data Value Change activity reasons are a result of an automated process known as Durable Unsubscribe https://docs.marketo.com/display/public/DOCS/Durable+Unsubscribe 'updateLeadEmailStatus' refers to durable unsubscribe updating existing records. So when a record's unsubscribe value get's manually changed, the other duplicate record(s) that has the same email address will get updated by the durable unsubscribe and 'updateLeadEmailStatus' will be logged for the updated leads. Whereas, 'resetLeadEmailStatus' refers to durable unsubscribe updating a new record, when its existing duplicate record(s) that has the same email address have 'unsubscribed=true'. So when a new record is created and the other duplicate records have 'unsubscribed=true', the new record will be updated by durable unsubscribe and 'resetLeadEmailStatus' will be logged for the new record. The 'resetLeadEmailStatus' can also occur as follows: Existing lead in Marketo has unsubscribed value set to 'True' Lead that used to exist in Marketo was unsubscribed  Lead is imported into Marketo with unsubscribed value set to 'False'. Momentarily, we can see this reflected in Marketo. Lead's unsubscribed value is changed back to 'True' with reason 'resetLeadEmailStatus'. This is because "When a lead is imported, the unsubscribe flag WILL NOT be overwritten by the import." Durable Unsubscribe
View full article
Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.     Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help   FireFox How to clear the Firefox cache | Firefox Help   Safari Safari for Mac: Manage cookies and website data using Safari   Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer   Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy    
View full article
Issue Description New Marketo person records will not automatically sync to Salesforce to create new Lead records after being created by default. There are other actions required to get these new records into Salesforce.   Issue Resolution 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. Is this article helpful ? YesNo
View full article
Included in this article   Overview Troubleshooting To Try http:// and https:// No Munchkin Tracking Code on Web Page No Visitors to the Web Page Yet Tips for Triggers and Filters Selectors Overview Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error.     You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem.     Troubleshooting To Try There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for.     http:// and https:// Using http:// or https:// in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear.         No Munchkin Tracking Code on Web Page If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs     No Visitors to the Web Page Yet Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page. Check the page for visits. Make sure you have a munchkin installed on the page you are requesting. Create a test lead and visit the targeted page.     Tips for Triggers and Filters Here are a couple of things that may help when using these filters and triggers.   Selectors   "Is" Selector In Triggers and Filters, if you use the selector "Is", (as in "the web page IS xyz.123.com") then the results returned will only be those from an exact URL match. If you want to also find results for the page xyz.123.com/sales, they won't be returned when using the "is" selector.     NOTE : The "is" selector will return results in filters much faster since it is only looking for exact matches.     "Contains" Selector If you use the selector of "contains", (as in "the web page contains xyz.123.com"), then this would return results for all pages that have xyz.123.com. Therefore, xyz.123.com/sales would match. The page xyz.123.com/products would match. All variations of that site xyz.123.com would match up.     NOTE : The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.
View full article
Issue: I am looking for the ID to one of my campaigns for a SOAP API project I am working on. Solution: The ID can be found in the URL of the campaign. 1.1 Log into Marketo, under Marketing Activities , find and select the campaign in question.     1.2 The URL to the campaign will look something like:   The Campaign ID is between "SC" and "A", in the above example it's "1054".    
View full article
Issue Description Embedded Marketo form not visible in Firefox Private Browsing mode. Issue Resolution Firefox's private mode will be enabled by default. When you embed a Marketo form in your own webpages and view it in Firefox's private mode, it will disable the Javascript as part of the tracking protection of this browser. JavaScript is needed for the forms to appear on the landing pages or webpages. The "Content Blocking" in the Firefox browser will need to be deactivated for the form to appear. Here is an article from FireFox regarding the Content Blocking: https://support.mozilla.org/en-US/kb/content-blocking Is this article helpful ? YesNo
View full article
Issue Description You have a record in Marketo that is a Contact in SFDC, and the record fails to sync with the error " INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id." Issue Resolution This error can occur if the Record Type ID field is not updated in Marketo when the SFDC Lead is converted to a Contact.  If the Record Type ID value displayed in Marketo is not valid for Contacts, the sync will fail with the error, " INSUFFICIENT_ACCESS_OR_READONLY: insufficient access rights on object id ." To resolve this, you can update the Record Type ID in Marketo with the correct value from Salesforce, or you can delete the value from Marketo and allow the sync to write the correct value from Salesforce.
View full article
Issue You see email clicks in a lead's activity history but no corresponding web page visits to the Munchkin-tracked page. The clicks happen immediately upon delivery of the email, or sometimes even before the delivery is logged. Solution Issue Resolution This is usually caused by email security software on the receiving email server. The security software tests the links to make sure they are not malicious and this causes Marketo to log a click activity for the email. Because the security software does not actually open the web page in the browser, there is no web page visit logged.   Your emails are more likely to be link tested if your sender reputation is low. For more information on link testing, see the following documents. Understanding a Spike in Click Activity Cracking the Inbox Code: Barracuda    
View full article
No, unfortunately we are unable to tell you what the spam trap address is. We don’t even know it ourselves! Spam trap addresses are proprietary to the blocklists that own them. Anti-spam professionals use spam trap addresses to track unsolicited emails. If a spam trap is known by the offending sender, the sender could simply remove the spam trap address from their lists and never actually address the data problem that caused that spam trap address to be included in their lists to begin with. Instead of asking what the spam trap address is, try to identify the source of the trap address and eliminate bad data sources from your mailing lists. You should be able to identify the email campaign that caused the blocklist issue, so you should start with those lists. To narrow it down and identify the problematic data source, you should consider the following: Have you recently added any new leads or new lead sources? What is the source of these leads? Any purchased or appended email addresses should be removed, because these data sources are often the source of newly introduced spamtraps. In addition, using purchased or appended email addresses for mailing is a violation of Adobe’s Email Use and Anti-Spam Policy. Have you added any older leads that have not been mailed to recently? Some email providers will turn an email address into a spam trap after a year of inactivity. If you have a list of addresses that has not been mailed in a year or more, this list should be removed. Does your system use any custom fields to indicate customer status, event attendance, recent contact with your sales team, or other forms of engagement? If so, take advantage of this and isolate the inactive or non-responsive segments of your database using all of the activity data you have available. Is there anything about this specific mailing that makes it different compared to your previous email campaigns? Did you send any other mail on the same day? If so, you should compare the recipient lists. Think you have narrowed in on the problem? Check out our guide to blocklist remediation to find out what to do with that bad list and complete the remediation program.   Additional Resources: What is a spamtrap, or spam trap, and why does it matter? What is a blocklist? How does Marketo respond to blocklisting and spam notifications? Top blocklists - What you need to know Blocklist Remediation Successful Reconfirmation Blocklist Deep Dive Blocklist FAQ   Is this article helpful ? YesNo  
View full article
What is Marketo’s Marketing Calendar? What are its benefits? What features does Marketing Calendar include? Is it free or do I need to pay for it? How do I get or buy Marketing Calendar? As of our August release: 1 week after our August release How do I know if Marketing Calendar has been turned on? What is the Program Schedule View? Will I need a services package to implement Marketing Calendar? Is this article helpful ? YesNo
View full article
Issue You try to send a sample of an email and receive a notice that the send sample failed.     Solution There are two token-related reasons that Send Sample may fail: You may have an invalid value for a token in your email. If there is an incorrect token value, the send sample will not work. Example: If you have the token for first name written like this {{lead.FirstName:default=Hello}}, when you try to approve the email Marketo will let you know that the token value is incorrect. The correct token value is  {{lead.First Name:default=Hello}}. For this example if you change the token value to {{lead.First Name:default=Hello}}, Marketo will allow you to approve the email and it will allow you to do a send sample. You may have a token in the From or Reply-To line that is not populating with an email address Example: If you have a token in the Reply-To like this one, {{lead.Email Address:default=edit me}}, then the Send Sample using the default will have "edit me" in the Reply-To, which is not an email address.  Marketo cannot send an email without a Reply-To email address, so the Send Sample will fail.   If any of the above does not apply, run the following tests and provide the information to Marketo Support Clone the email in question and test to send as a sample Create a new email and test to send as a sample Send the email via a live campaign or a single flow step to a test lead
View full article
Issue Email get delivered initially but after a while, the email bounces stating 550 error. Solution This is a behavior of a particular type of Bounce called an Out of Band bounce ( OOB). The Send, Delivered and then Bounced sequence tells us that the email was initially accepted, but then due to a variety of reasons (or categories) it was rejected. This type of bounce is not uncommon, but are relatively rare. If you look at the lead record , you'll see that there will be an "Email Delivered" activity right before this bounce message which is what makes it "Out Of Band" . There isn't really any way Marketo can control it--it's entirely up to the recipient mail server. Many times this happens when a recipient mail server takes in emails in through a main server, then dumps them over to a secondary server. The first one that takes in the email gives back the "Email Delivered" message. Then the secondary server evaluates each email based on the spam filters and against known email addresses in their system. If the secondary server gets invalid email addresses or filtered out as spam, they'll then be bounced, causing the bounced message after the delivered message. 
View full article