Knowledgebase

  Marketo's Email Delivery & Compliance Team often recommends that our customers send a reconfirmation message to a set of their inactive leads. This process is used as both a proactive strategy to ensure good delivery rates and as a response to blocklisting issues. For more information on this overall strategy search our Resource Articles for Blocklist Remediation. At its most basic a reconfirmation message request a lead takes an action to stay on your mailing list.  If they don't take that action they will be automatically removed from the mailing list. These types of messages don't usually get a high response rate because you are sending the reconfirmation message to people who have already shown to be disengaged from your marketing. However there are instances where some reconfirmation messages get a more enthusiastic response than others so we've put together some tips for making the most out of reconfirmation. Instead of marketing your company itself think of it as though you are marketing ENGAGEMENT with your company. While these ideas are similar, they aren’t quite the same. You want to frame this message with a sense of urgency to click a link. You also want to make it as easy as possible for someone to open the message and just click a link so they continue to stay engaged with your marketing.   Subject Line We recommend that you frame the subject line very clearly with something about “not missing out” or “staying informed”. The subject should create a compelling and specific call to action.  Some senders use an offer in the reconfirmation message to encourage action. Highlight this in the subject line if this is your approach. Examples We’ve Missed You!  Take Action continue receiving our offers! Last Opportunity to Stay Informed (Action Required) Free shipping plus save 15% on next purchase   From Address While you can use any From Address, we recommend that your From: label clearly identifies your company rather than using a lead owner name. A disengaged recipient is more likely to recognize “Your Company” than “Bob Smith”.   Email Content In the body of the message your call to action should be immediate and clear. Put the reconfirmation at the top of the message content. Some usability studies have suggested that two choices may be more successful than a single choice so consider a bolder reconfirmation link at the top and a smaller link or button lower to unsubscribe. The main priority is getting someone to stick around for more of your mailings. You may also wish to make a short value statement about the fantastic information that someone can expect to receive by staying on your list! There are a couple of reasons for these recommendations. The first has to do with making things easy for the blocklist operator. If during the resolution process they can look at the mail received by their spamtraps and immediately tell from the subject line that the message is a reconfirmation pass it will make it much easier for them to consider the data quality issue resolved because their spamtraps will not activate the reconfirmation link. Some of the less automated blocklists will not list a sender for a reconfirmation message that hits their traps so it's important that your cleanup action look like what it is. The second reason behind this advice is that many people just scan their messages and don’t read all the way to the bottom; if someone has to read through a long value proposition before realizing that they must click a link to continue to be subscribed to your email program you may lose more subscribers than intended. The faster and easier it is to click that link the more people you’ll retain! A lot of people scan over marketing offers and think about them for a while before taking an action. You want to interrupt that process and make it clear that action is required now whether or not they’re ready to make a purchase!   Examples of simple reconfirmation email templates More examples can be found in this other Community Resource “A Creative Re-Engagement Email Campaign” Email #1 Subject Line: Action Required to stay subscribed to COMPANY   [First Name]:   You previously expressed interest in receiving valuable information and/or offers from COMPANY that are specific to your field.  We’d like your permission to continue sending you relevant information via email so that you can stay up-to-date on the latest industry trends/topics of interest.   Please click “YES” below to continue receiving research and trends in your area of interest.  COMPANY subscribers receive exclusive benefits, including the latest research briefs, white papers and/or compelling offers or discounts for future purchases.   Please update your Communication Preference by [DATE/TIME] or this could be your last chance to receive any future research.  It only takes a moment to click one of the choices below.   YES, I would like to stay subscribed to the valuable information from COMPANY.   NO, I no longer wish to receive valuable and insightful offers from COMPANY.   Sincerely, COMPANY   ————–   Email #2   Subject Line: Your Subscription to COMPANY Industry Newsletter Expires Soon   [First Name]:   Our records show that you expressed interest in receiving industry information from COMPANY on [INSERT DATE].  Records indicate you have not read an email in [variable time frame], we do not want to bother you with emails you do no wish to receive so we want to confirm that you would like to remain subscribed to the COMPANY email program.   If you wish to be removed, you don’t have to do anything further.  However, if you do want to continue receiving email from COMPANY, please click the link to let us know:   YES, I would like to stay informed and continue receiving email from COMPANY.   Sincerely, COMPANY   ————–   Email #3   Subject Line: Your Subscription to COMPANY Has Expired   [First Name]:   Thank you for your previous interest in receiving valuable content from COMPANY.  Your subscription has now expired and you will no longer receive any future emails.   If in the future you would like to continue to receive email from COMPANY please click the link to sign up:   YES, I would like to receive email from COMPANY.   Sincerely, COMPANY     Other Resources Marketo Community Resource “A Creative Re-Engagement Email Campaign” http://www.spamhaus.org/whitepapers/permissionpass/ http://blog.deliverability.com/2013/07/do-you-know-whats-lurking-in-your-database-know-thy-data.html http://blog.marketo.com/2010/05/key-to-email-deliverability-is-reputation.html http://www.marketo.com/email-deliverability/    

*Updated in September 2024   Quick points: Spamtraps are addresses owned by antispam organizations Emailing a spamtrap can result in your sending domain or IP to be blocklisted Maintain current, direct opt-in with an active lead database to avoid this Spamtraps are usually functional email addresses that can successfully receive a message.    What is a spam trap or spamtrap?   A spam trap, or spamtrap is an email address secretly owned by an antispam organization that is used to detect spam. Antispam organizations do not sign up for mailing lists, so they consider any email sent to these addresses to be spam. Once an email is sent to the spamtrap, the antispam organization that owns this address can/will blocklist the IP and/or domain that sent the email.   Email administrators purchase subscriptions to the data offered by blocklist providers and may use the lists to block all incoming email from listed IPs or containing listed domains. From the marketer’s perspective, this can mean a high number of bounced emails leading to low lead engagement, and ultimately to weak revenue performance.   There are three types of spamtraps – pristine traps, typo, and repurposed/recycled traps. A pristine trap is an email address that was never used by a person. A repurposed trap is an email address that once belonged to someone but is no longer a valid address; these addresses will bounce as bad addresses for at least six months before an antispam organization will turn them into live traps. A typo trap will contain a misspelled domain.   How can a spamtrap get into my Marketo lead database?   Purchased data Purchased data is unreliable and is high risk for your brand’s sender reputation.  The antispam community does not like the use of purchased data, so antispam administrators have made a concerted effort to get spamtrap addresses into the databases of data vendors. While data vendors may claim they provide opt-in data, you risk inadvertently purchasing spam trap addresses when using a data vendor.  A foundational strategy to maintaining healthy sender reputation is to gather email addresses directly from individuals alongside their consent to be enrolled in bulk email communication.   Sending unsolicited email is prohibited by the Adobe’s Acceptable Use Policy because this practice has a high risk of causing deliverability problems for your brand and the Adobe network.  To avoid spam traps, get direct opt-in before sending email. If you have purchased data in the past, we recommend setting any inactive purchased leads to marketing suspended or simply removing them from your database.   Old data Repurposed traps are email addresses that were once valid but are now owned by an antispam organization. This can happen when a company goes out of business; expired domains are often purchased by antispam organizations. Sometimes a company that has a direct partnership with an antispam organization will allow email addresses of former employees or users to become spamtraps. Because antispam organizations will generally make sure future spam traps return a bounce as bad addresses for at least six months before they become spam traps you can prevent repurposed traps in your database by emailing remaining engaged with everyone in your database at least once every six months.   To safeguard your sender reputation, avoid reengagement campaigns to addresses you have not contacted in more than six months.   Unconfirmed form entries People can unintentionally enter spamtrap addresses into forms either by mistyping their email or by intentionally using a fake email address that happens to be a spamtrap. If you use single opt-in, you risk adding spamtraps to your mailing list. This is more likely to happen if you are a B2C company or through the offer of gated content that requires an email address.   How can I identify spamtrap addresses?   Spamtrap addresses are considered trade secrets by the antispam organizations, and they are obscured by design. They do not share these addresses because their goal is for senders to change their mailing practices rather than to simply remove spamtraps from their mailing lists.   That said, one thing we do know about spamtraps is that they tend to be automated processes and do not engage. Spamtraps do not click links. You can use smart list filters to identify inactive leads in Marketo.   How can I prevent spamtraps in my database?   Maintain active, direct opt-in for all leads Don’t purchase data Email engaged contacts least once every six months Don’t add old data directly to your mailing list Suppress perpetually disengaged contacts Grant access to assets such as free trials and whitepapers as email links to discourage intentional use of fake email addresses on forms Use scripting on your forms to identify potential typos  

In offering a premium email delivery platform to our customers we carefully monitor our IPs for listings on significant blocklists. When we find that one of our customers was responsible for a blacklisting we contact that customer and request some actions be taken to re-mediate the issue. The goal is to isolate potential spamtrap addresses and remove them. The group of addresses you select should be broad enough to capture those potentially bad addresses but small enough not to suppress a huge portion of your database. Step 1 Build an inactive Smart List using ALL filters Was sent email the day of and day before the spam trap hit (please contact support@marketo.com for the date of the trap hit if you do not have this information already.) Lead “was created” date is at least 6 months ago   Inactivity Filters  Not visited web page is “any”; constraint date of activity “in past 3 months” Not filled out form is “any”, constraint date of activity “in past 6 months” Not clicked link in email is “any”, constraint date of activity “in past 6 months” Not opened email is “any”, constraint date of activity “in past 6 months” If you have custom database fields that would show other forms of activity feel free to add this into your inactive Smart List to exclude active leads.   Step 2 Once you have created a smart list to identify these suspect leads remove them from your database. [Leads Tab > Lead Actions > Flow Actions] You’re Done!      

When trying to sync updates to your salesforce.com instance from Marketo you see the following error in the activity log : "Failed: INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY" This is an error sent to Marketo from salesforce.com. There are a number of reasons why this error could occur but the root cause is always linked to the permissions of the Marketo user that you have set up in salesforce.com. INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY means that the user who is trying to make the update does not have access to a related element that is required for the record to be updated and saved in SFDC. There are a number of specific examples of what might be the cause but these will vary from organisation to organization depending on the configuration of your salesforce.com. If you were to connect to sfdc as the Marketo user and try manually updating the same record that Marketo is trying to update then you will get the same error in the salesforce.com UI. Here are a list of some elements that you should check in SFDC if you see this error: Do you use record types? If so make sure that the the Marketo user has access to all required record types. Are there any look-up or master detail fields on the object in question? If these types of fields are being updated then make sure that the Marketo user has access this object/ these records. Do you use Apex? If so you may have trigger that fire on the the update of a record, you will need to make sure that the Marketo user has profile access to the relevant Apex classes. If you have any workflow rules or assignment rules that send an email when the record is saved then you will need to make sure that the Marketo user has the send email permission and has access to the email folder that contains the mails that are sent rules are triggered. Make sure "Convert Leads" is turned-on within SFDC.  If it is not, you will get this error message when trying to merge leads that exist within Marketo and SFDC. Is this article helpful ? YesNo

  When a new lead enters Marketo from a form fillout or List Import, Marketo automatically searches for a lead with the same email address.  If that lead exists, the existing lead is updated instead of creating a duplicate. However, Marketo does not automatically de-duplicate leads who are already in your database. This is especially a problem for new customers who often have many duplicate leads in their database. Also, if you add a new lead directly into Salesforce (through the Salesforce import process or web-to-lead forms) Salesforce will create a duplicate lead that gets synced into Marketo. When this happens, you can use Marketo to find and fix those duplicates.   How Marketo handles duplicates   The primary consequence of duplicates is that one lead record could have the most relevant information about that lead while your sales rep is looking at the incomplete duplicate.   For example, say that you have a duplicate lead in your database and that lead fills out a form on your website. Marketo generally updates the lead record that was most recently updated. In another case, say you run a campaign to email your lead database and two duplicates are included in your campaign run. Marketo automatically detects the duplicate email address and ensures that only one email is sent to that lead. That Email send and subsequent activity will be attributed to the Lowest Lead ID.   When you merge leads, their entire history is combined, and you can control which fields are kept in the final lead. You won't lose any information or tracking.   Most customers have many duplicates when they start with Marketo. After initially de-duplicating your database, the work to keep your database de-duplicated is usually very small. You should work to stop the sources of duplicate leads and make Marketo your single point of entry for all new leads.   Finding Duplicates   Go to the Lead Database section of the app. Then click on the Possible Duplicates list in the tree. Click the grid header that says Email.  You can sort by email address to see the duplicates next to each other. Selecting multiple leads Select two leads that have matching email addresses.  You can do this by holding the "control" key down while clicking on the two different leads.  (You can merge more than two at a time, but start with two.) Tip: Sometimes clicking too fast will make the grid select incorrectly.  Clicking a little slower usually helps. When you have two rows selected or highlighted, click the Merge Leads button in the toolbar.   The Merge Dialog A dialog will appear showing you all the fields that differ between the two leads.  You need to pick which values to keep in the merged lead.  Not every field is displayed -- just the ones that you need determine appear. By default, the values from the most recently updated lead will be selected (with a check and highlighed yellow). To pick a different value for the merged lead, click the checkbox next to that value. If you want to enter your own values for the merged lead, click the Custom field for that row then type in your own value: When you're done, click Merge.  The winning values will be kept in the merged lead; the other values will be discarded. Important: Clicking merge will instruct Salesforce to merge the records properly.  All Salesforce and Marketo activities are merged into the remaining lead.  Nothing is lost.  Campaign History is also kept.   Duplicate pattern matching You will notice that the Possible Duplicates list has a Smart List tab.  Click on the Smart List and you will see it's using the "Possible Duplicates" filter on the "Email Address" field. You can change this filter to search other fields for duplicates. Click the little green plus in the definition. Note: You should use only one Duplicate Fields filter in your Smart Lists.  If you want to check multiple fields, always use the green plus button to add multiple fields; don't drag in a second filter. When you change the Duplicate Fields filter, you should sort the Leads grid by the column you're checking to put the duplicates next to each other. Marketo Merge Program Marketo offers a service for mass-merging of duplicates.  Please contact your Customer Success Manager to inquire about this service. What happens when I merge two leads in Salesforce? When you merge leads or contacts in Salesforce, Marketo will also merge the matching leads in your lead database. See this article to learn more about how that works: https://docs.marketo.com/display/public/DOCS/Find+and+Merge+Duplicate+People#FindandMergeDuplicatePeople-EffectinSalesforce      

Issue You have been receiving form submissions that appear to have bogus/nonsensical data in the fields, such as "kjsag@sm4.to" for email address, or "111-111-1111" for phone number, or in a Comment field other random nonsensical text.     Solution Currently, there are no default settings in Marketo that prohibit a form submission if the required fields are filled out. A great workaround for addressing these bogus form submissions in Marketo is to implement a 'honeypot' field on the form. To do this, you will need to create a custom Marketo field, string type, and name it something distinctive (such as "spam" or "honeypot"). After creating this field in Marketo Admin > Field Management, place this new field on the form as a hidden field. Real live end-users do not see hidden fields, but spam bots will see them and fill out all available fields. So now when we see form fills with this honeypot field "not empty," we know that it was a bot fillout.   Setting up the Honeypot Field Say that you have a Trigger Campaign that's having some issue with these spam/bogus form fills. In the flow of this campaign, you can add a flow step at the top: Remove from Flow, with a Choice.   Choice: If Honeypot field Is not empty, then remove from flow Default: do nothing   This way, the lead record is removed from the flow. You can also have other campaigns to handle these bogus form fills, such as a daily recurring batch to delete the record.   Other Options Another method of dealing with bot fillouts is to enable a reCaptcha. In fact, a very prolific Marketo user has written custom code that you feasibly could use to enable a reCaptcha on the form! Check this out: https://codepen.io/figureone/pen/meybqN?editors=0110    

  So you’ve now used the previous document (Getting Started With Guided Landing Pages:) to download a template from our library and set it up in your Marketo instance, you have even used it to make a landing page or two and you’ve customized those landing pages, AND you’ve even gone the extra mile and customized your template and modified some elements! (Editing Marketo Guided Landing Page Templates, Pt. 1 - Elements:) All of which is fantastic news! Good job!   But if you recall from the article that showed you how to edit Elements on the template, I skipped right over the section on Variables. This is the piece that this document is designed to tackle.   So what is a variable? If you edit a Guided Landing Page you will see a panel on the right hand side that displays both Elements and Variables. In this instance, the variables do everything from assigning a gradient color, to deciding if you want to display or hide different sections of the landing page.   Modifying a variable in the landing page editor is designed to be really simple, just click the variable you want to change and give it a new value. Here I changed the Primary Gradient 1 and 2 from 1DA083 and 0F3450 to A00E35 and F2F2F2 respectively and the landing page changes:   At its easiest to understand, a variable works a lot like a token in an email. It’s a placeholder for actual code to be used later. So if I create an email that starts with “Hello, {{lead.firstname:default=Friend}}!” you can tell right away what that’s going to do. Pull the first name from the lead record, if none exists use the word “Friend”.   Think of a Variable as a token that you get to define as well as use. The first step is to define it and the second step is to actually call back to the variable you defined.   While it’s easy for a non-technical user to use a variable (as it should be!), setting one up in the template does require a fair amount of HTML knowledge. As stated before, if you are not comfortable editing HTML and do not have a resource available to you, please reach out to services@marketo.com, they are able to assist with any sort of coding needs.   So as before, let’s dive into the template, this time we’re going straight for the Variable code.       <!-- Marketo Variable Definitions -->     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   So right at the start of the template, we’re off to the races defining variables. As you can see with the Gradient 1 and Gradient 2, these are both marked with a class of “mktoColor”.   As with the Elements, the full list of Variable types can be found here: https://docs.marketo.com/display/public/DOCS/Create+a+Guided+Landing+Page+Template        class : "mktoString"      class : "mktoColor"      class : "mktoBoolean"   A string is a variable that contains a value, Color should be obvious what that does and Boolean is a yes or no choice.   In addition to the class, each variable has to have a unique ID. This is critical and used when the variable is called later on down the page. When you call a variable it’s always with the syntax of ${id name}. So in this case ${gradient1} and ${gradient2}. As you can see it looks a LOT like a token but it’s a token you can name whatever you want.   The mktoName is how it displays the variable in the Landing Page editor.   The default value is what it starts out with.   So let’s take a look and see how these Gradients are applied now that they’re defined at the top of the template.   Color is typically used in the CSS portion of the header. As defined in the previous document, CSS stands for “Cascading Style Sheets” and is a way of formatting the same thing over and over again, kind of like setting a font in a word processor.       /* Header Gradient */     #is {         top: 0;         width: 100%;         min-height: 620px;         position: relative;         z-index: 1;         color: #fff; padding-top: 10%;                 background-image: linear-gradient(${gradient1},${gradient2});     }   Now normally in CSS, the linear-gradient option would have two colors listed, the top color and the bottom color and it provides a gradual transition from one to the other.   We could just as easily change this in the template to        background-image: linear-gradient(red,white);   But the problem doing that is that an end user, who is only using the Landing Page Editor, would not be able to change it. The gradient would be defined in the template and inaccessible to the Editor.   Changing these values to the variables defined before allows the user to change the first and second colors in the Landing Page editor interface.   In Summary:   The Meta Tags define what the variables mean:     <meta class="mktoColor" id="gradient1" mktoName="Primary Gradient 1" default="#1da083">     <meta class="mktoColor" id="gradient2" mktoName="Primary Gradient 2" default="#0f3450">   The ID= is then used to call the variable and put it into action:       background-image: linear-gradient(${gradient1},${gradient2});   The other benefit to doing it this way is you can re-use the same variable over and over again. Look at this piece of CSS:   body {                 background: ${gradient2};         margin: 0;         color: #696E74;     }   That’s the same ID as the gradient we used before, only applied to a different section. This ensures that the bottom color of the gradient and the background of this section will always be the same color.   Any item in the CSS that contains a text value, a color value or a yes/no choice can be converted to a Variable.   Here’s another common usage:   You’re using a form on your landing page, but you want the end user to be able to change the text on the submit button.   As before you define the variable:        <meta class="mktoString" id="section4ButtonLabel" mktoName="Sec. 4 Button Label" default="More Questions?">   Then farther down the page where the button appears you call the variable you defined before:        <div class="centered mtb">           <a href="${section4ButtonLink}"><button class="btn btn-lg btn-green mt">           ${section4ButtonLabel}</button></a>      </div>   The <a href= is pulling a http link that the user can define in the editor, the button class is setting up a green button as defined in the CSS, and there is our Variable to display the label which reads “More Questions?” Here’s what it looks like in the editor:   So this is great, and it makes sense because you can see this was all set up and defined by a professional. What if you wanted to add your own? Is that even possible?   Naturally it is!   First, figure out what you want to convert to a Variable. Is it a piece of text like a button name or a link? Is it a color? Is it a yes/no choice?   Let’s say we want to add a variable that controls the color of the buttons. We have two, both using the same color green, and we want whoever is running the landing page editor to change that without having to go to the template:   Step 1: Define your variable:        <meta class="mktoColor" id="ButtonColor" mktoName="Button Color" default="#1DA083">   We’re talking about colors so the class will be “mktoColor”. The ID can be anything we want it to be as can be the mktoName. The default is the same lovely green shade as was used before.   Now we need to call this color.  Looking at the CSS, we can see the .btn-green is defined as this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: #1da083;           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   The background is the color we want to change to a Variable so it can be edited without having to access the template.   Change the code to this:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor};           -webkit-transition: none;           -moz-transition: none;           transition: none;      }     Approve the template and check out the landing page in the editor:     Well that’s fantastic, but there’s a separate color for the border, we could just as easily add a variable for it as well:        border: 4px solid #1da083;   We don’t want to HAVE to add another new variable for just the border. We could change the border at the same time as the button. By changing #1da083; to ${ButtonColor};   The trick now becomes what if you change your mind? What if you have a variable in the template that is no longer desired? How do you get rid of it?   Remember each variable is two pieces, the definition and the call. You have to remove BOTH pieces. Technically removing the call would be enough to prevent the change from being made on the page, but the definition is what makes the variable appear in the Landing Page Editor, if you only removed the call then there would be a non-functional Variable in the landing page editor.   So in the case of our button color:   Step 1 would be to strip out the meta tag containing the definition:     Step 2 would be changing the variable name where it’s being used to some fixed value:        .btn-green {           border: 4px solid #1da083;           border-radius: 60px;           color: #fff;           background: ${ButtonColor}; -> change this to some other fixed color. #00FF33; or the original #1da083;.           -webkit-transition: none;           -moz-transition: none;           transition: none;      }   Doing both pieces will prevent the Variable from being listed in the Landing Page Editor and prevent it from having any effect on the page.  

  Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate    

*Updated in September 2024   What is a feedback loop (FBL)? An FBL is an arrangement between an email sender, such as Marketo, and an Internet Service Providers (ISPs) or email hosting service.  The FBL allows the email sender to be automatically notified when the user who receives an email marks it as spam.   When a lead who uses one of these ISPs clicks the spam button for an email, the ISP sends an automated notice to Marketo. Marketo automatically unsubscribes the lead with the unsubscribe cause, "Customer Complaint Received from ISP".  Marketo's Email Compliance Team also logs these complaints for internal compliance monitoring.     What FBLs is Marketo enrolled in? By default, all emails sent by Marketo are covered by an FBL with the following email providers: Bluetie/Excite Comcast Fastmail Gandi.net Italiaonline Lapost.net Liberomail Liberty Global Locaweb Mail.ru* QQ.com* OpenSRS/Tucows Rackspace Seznam.cz SFR SilverSky Swisscom Synacor Telenet Telenor Telstra Terra TIM Unitymedia UPC United Online/Juno/Netzero Virgilio Virgin Yahoo! Ziggo Zoho.com   *The FBLs for Mail.ru and QQ.com can only be set up for customers on dedicated IPs.  Please reach out to Support if these Russian and Chinese ISPs respectively are targets for your email program.   Notably, Gmail does not offer a traditional FBL. They have a similar offering that Marketo has evaluated and determined does not meet the needs of our clients at this time.  Google does offer Postmaster Tools that allow senders to monitor their complaint rate and other reputation information.  Senders can sign up here:  https://gmail.com/postmaster/   

Marketo campaign queues work like a mall parking lot.  We accommodate average and even above average loads.  But if it's Christmas, you may have to wait a while for a spot.   The campaign execution queue When a flow is launched, Marketo assigns it a priority then queues it for execution.  This priority is based on how the campaign was launched (batch, trigger, resume from Wait) and what's in the flow: Priority level Priority criteria High Send email (triggered) Send alert Medium Request Campaign Interesting Moment Create Task Convert / Delete Lead Add to / Remove from List Change Sales Owner / Progression Status / Revenue Stage / Field in Program Change Member of / Add to / Remove from Sync to SFDC Change Status in SFDC Campaign Low Change data value Change score Wait steps with a wait time > 5 minutes Web hooks Marketo then executes campaigns based on priorities.  High priority campaigns run first in the order they were added to the queue.  Once those are finished, the next highest priority campaigns are executed in time order and so on down until all have completed. If the queue contains only low priority campaigns and a new high priority campaign comes in, the high priority campaign will jump to the head of the line and run next. Batch campaigns and trigger campaigns are run and processed in separate queues.   "Why is my campaign running slow?" Several factors determine how fast and when your campaign will run.  In general, campaign execution time depends on: The campaign's priority The complexity of the smart list filters being used - See Best Practices for Smart Lists The number of records that qualify for the campaign The number of flow steps used in the campaign The complexity of Choices in the flow steps   Even though Marketo can execute many campaigns simultaneously, there are only so many resources available to process smart campaigns. Also, certain campaign flow steps take longer to process, than others.  The flow steps below take longer than most, and you may notice that difference when executing your campaigns: Send Email Delete Lead Sync Lead to Sales Add Lead to SFDC Campaign Call Webhook   Speeding up your campaigns Here are some tips to speed up how and when your campaigns are executed: Do essential flow steps first If this is an auto-response or notification campaign, put the Send Email or Send Alert flow step first.  Absolutely do this if you're using two slow steps in a row (Send Email followed by Sync Lead to Sales) so that the email goes out with the highest priority. Don't start with a "Wait" step If you need to delay the launch of your batch campaign, use the batch campaign scheduler.  Re-think any triggered campaigns that start with a "Wait" step because it will be prioritized lower; you probably don't need to include it anyway. If you have a wait step of longer then 5 minutes this will cause all flows below it have a low priority.

  What is a Blocklist? Can I Still Send My Emails, or Are You Blocking Me from Sending? What Is a Spamtrap and Why Do They Matter? Can You Give Me the Spam Trap Address That Triggered the Blocklist So I Can Remove It from My Database? Can You Give Me More Information regarding the Blocklist Issue? What Is the Quarantined IP Range? I Sent This Email Campaign a While Ago. Why Am I Only Getting Notification of the Blocklist Issue Now, and Am I Still Blocklisted? The Blocklist Notification Went to the Wrong Email Address. Why Was It Sent to That Address? Which blocklists should I be concerned about? - Top Blocklists – What You Need to Know How do blocklist issues get resolved? What steps do I need to take to resolve the blacklist issue? - Blocklist Remediation