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

(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?

If you sent an email from the Lead Database (as a Single Flow Action), as part of a campaign, or as a test email but didn't receive it, here are some tips. Check the "From:" address When sending a test message, make sure to check the "From:" address setting on your message. To do this, go to the Email Settings tab of the email editor. In the "From:" field, make sure that you either have a single valid email address, or a valid email address as the default, if you are using a token. Many people want to send their messages from the lead owner. When you use the send test feature, the email address you are sending to doesn't have a full lead record, and so it doesn't have a lead owner. Since Marketo cannot send an email with no "From:" address, test messages without a valid email address in the "From:" field will not send. Send as a Lead If you have verified that the email had a valid From: address and you still aren't getting it, make sure to create yourself as a lead and send using a flow action. See if the mail was sent If you sent the email as part of a campaign or Single Flow Action, check the campaign's Results tab or your lead detail page to see if that mail was already sent to you. If it hasn't been sent yet, try waiting a little while longer. Check your Junk Mail In your email client, check your Junk Mail or Spam folder to see if the mail landed there. If it did, you should change the content of your email. Check your corporate spam filter Your corporate mail server may have blocked emails from Marketo; you should contact your IT department to see if this is the case. Please see our instructions for whitelisting Marketo's email servers: Add Marketo to Your Corporate Email Whitelist Try sending to a different recipient If you sent the original mail to your corporate account, try sending to a personal account on Yahoo or Gmail. If you sent it to a personal account, try your corporate mail account. Use Marketo's Email Deliverability product The Email Deliverability PowerPack, with Design Informant and Inbox Informant, can warn you when your mail is being rejected because of its content and help you identify junk mail pitfalls. Also, using Domain Keys and SPF improve the chances of your email landing in your leads' inboxes. Contact Marketo If you still can't figure out what happened contact Marketo to see if we can help.

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

Included in this article: Overview Limitations Error Handling and Troubleshooting Overview No-Draft for Snippets allows you to distribute snippet changes without drafting approved assets using it. All assets using the edited snippet get the updates and maintain their respective status: Approved assets get the snippet updates and stay approved Drafts get the snippet updates and stay in draft mode No-Draft is automatically enabled for all Administrator roles. An admin can then enable this feature for any additional role. While No-Draft Snippets are very useful, they do have some limitations and issues that tend to arise. This article will show you what those limitations are and how to troubleshoot issues that can come up. Limitations This feature is designed to save time with the snippet approval workflow. There are a few limitations to be aware of: No-Draft will not work if you replace one segmentation with another one in the same snippet. However, No-Draft will work if you change, add, or delete a segment within a segmentation that is referenced in the snippet No-Draft will not work if you add/remove a segmentation to a previously approved snippet By design, No-Draft will fail if you make a dynamic snippet static, or a static snippet dynamic. If your use case requires this scenario, then we recommend you create a new snippet to be used across your assets. If you must update the existing snippet, then you will need to approve it using the Create Draft option, then re-approve the assets using the snippet (in other words, the old behavior) No-Draft does not auto-approve drafts Users without the No-Draft permission can still approve a snippet, however it will generate drafts of approved assets No-Draft works only when approving one snippet at a time Assets using the snippet are locked for approval until No-Draft is done processing Snippet updates made to approved assets cannot be rolled back No-Draft applies only to snippets Error Handling and Troubleshooting If something goes wrong, an error message is delivered to the Notification section of Marketo. You can subscribe to this notification and receive email alerts in their inbox. Users must subscribe to No-Draft in each workspace with the permission enabled. If an error does occur, chances are that the update process was not completed. Some assets may have the updated snippet content and others may not. To resolve, redraft the snippet and re-approve. 1. Select the snippet and click Edit Draft. 2. Make a small edit in the snippet editor to create a draft (such as pressing the keyboard’s spacebar). 3. Click Approve Snippet. 4. In the dialog box, select Update all to start over. This should fix the issue. Contact Marketo Support if the problem persists.

Issue You have a custom landing page template and are able to see that landing page is not rendering perfectly on the editor but works as expected when published. Solution As you are facing the issue on a custom template, we suggest you to follow the below steps. Download a template form the URL- experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/guided-landing-page-template-list.html In Marketo, navigate to the Design Studio Click Landing Pages in the left-hand tree, then select Templates. In the menu bar, click Import Template. Choose the downloaded file, enter a template name, then click Import (make sure to pick a descriptive name and indicate that editing mode is Guided). Create a new Landing page with the recently downloaded template without making any changes. If the default background image works on this landing page as expected, it confirms that the issue lies with the custom coding that was added to the template. Marketo Support is not set up to assist with troubleshooting custom code. The best point of contact will be your web developer who should be able to resolve the issue for you. Please be aware that the landing page editor may not load all external resources in the editor or previewer, which can cause them to look different than the published version. If the background image doesn’t render on this newly downloaded template as well, contact support and we will assist in troubleshooting your issue.

Issue Issue Description After submitting a form on a landing page, the Thank-you page fails to load, or it loads the wrong page. Solution Issue Resolution The Thank-you page used by the form can be defined in two places, at the Form level and at the Landing Page level. If these two are in conflict, the setting on the Landing Page wins. To troubleshoot this issue, compare the two Thank-you options and make sure the Landing Page is either set to the correct page, or that it allows the Thank-you to be form-defined.

Issue You put a variable inside an email token and when the email was sent, the variable rendered as text rather than as a link: Example: ${queryParameters} Should expand to: {{my.CertainURLHREF}}?utm_source=${utm-source}&utm_content=${utm-content}&utm_medium=${utm-medium}&utm_campaign=${utm-campaign}&ajs_uid={{lead.Email Address}}&ajs_event=Email%20Clicked With the various tokens populated Instead it expands to this: app.fakewebsite.biz/profile/55555555?utm_source=$%7Butm-source%7D&utm_content=$%7Butm-content%7D&utm_medium=$%7Butm-medium%7D&utm_campaign=$%7Butm-campaign%7D&ajs_uid=adam.tow+test@voxmedia.com&ajs_event=Email%20Clicked Solution Essentially, email template variables are used at design time to make building out an email easier. Tokens are used at send time to make data variable per program without having to edit the asset or lead. Putting email template variables inside tokens won't work for this reason. It is just how the current design works and you will not be able to put email template tokens inside my tokens or lead tokens. Unwrapping variables before you put them within the token will allow them to function properly. This removes the simplicity of the variable, but retains the functionality.

Issue Links sent to a customer using AppleMail are not rendering properly. Solution This issue is cause when there is no protocol assigned to a link so AppleMail appends applewebdata:// to the beginning of the url instead of or The work-around for this is to include the protocol in the link. If there's no protocol (e.g. ) then the rendering engine will insert applewebdata:// as the protocol for any links.

Issue The deep link in a Marketo email does not redirect to the designated App. Solution By design in Marketo, when tracking is enabled for a link, the link will be wrapped with a tracking link like 'http://test.website.com/[unique sequence of characters]'. So when a tracked link is clicked, the link 'http://test.website.com/[unique sequence of characters]' is first loaded in a browser then redirects to the actual link in the same browser. Therefore, as some deep link configuration can depend on the actual link first loading, a tracked link in Marketo does not redirect to the App. One workaround here is to disable Marketo tracking link so that the deep link will redirect to the App. However, the trade-off of this is that the click link activity will not be recorded in Marketo.

Issue Marketo forms that are embedded on external web pages see loading errors. Examples of this could be that the fields load with delay, or once submitted the form lags before moving to a follow up page. Solution Two things to check: Is there custom CSS in your form? Is the embed code on your form customized? Isolate the cause You can isolate the root of the lag by testing your form on a Marketo Landing Page 1. Locate the embedded form with in your instance 2. Build a landing page to test the form: Landing Page with a Form 3. Place your form on the new testing landing page, approve the page and close it. 4. Load the Landing Page using the URL If the form loads with no delay, the issue lies with the embed code used to push the form onto the external page. Please work with your custom developer to find a resolution. If the form is loading with a delay (and there is custom CSS): 1. Clone your form 2. Remove any custom CSS from with in the form 3. Build a landing page to test the form: Landing Page with a Form 4. Place your form on the new testing landing page, approve the page and close it. 5. Load the Landing Page using the URL If you are not seeing any loading errors, the issue lies with in the custom CSS of your form. Please work with your custom coder to improve the loading speed of your form. Note: Occasionally, incorporating the form embed script into containers (custom coding) and utilizing custom JavaScript may lead to delays in form functionality. In such instances, it is recommended to collaborate with your developer to identify a solution, as Marketo Support does not troubleshoot issues specifically related to custom coding. If you are still seeing lag errors on your form loading on the Marketo Page, please submit a ticket with support@marketo.com

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: developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/

Issue You want to have one email address in the From field ( abc@test.com) a different email address in the Reply-To (all@test.com)? Solution Yes, you can use different email addresses in the From and Reply-To. If the Reply-To is an email alias that sends to a group, you should confirm that email is working and able to receive email. Please note: Automatic replies, such as out-of-office notifications will be sent to the From address, not the Reply-To. Reply-To is only used when the person who received the email clicks the Reply button in their email client. Note :- The SMTP envelope sender typically appears as <uniqueidentifier>@*.mktomail.com. You will only receive responses of this nature if you have configured a branded sender for your subscription. While this serves as the correct destination for auto-responses, regrettably, it is frequently overlooked.

Issue The same email looks different in different email clients, and does not match what is shown in the Email Previewer. Solution Different browsers and email clients render HTML and CSS differently. While there are standards set forth by W3C, there is room for flexibility. At a high level, it is expected for emails to look different, even within the same platform such as Outlook 2013 vs Outlook 2010. With that said, you can code against some of these anomalies by adding extra code in CSS to account for the differences. You should consult with an HTML/CSS designer to make these changes. In all likelihood, the issue is related to how Outlook(or any other email client) is rendering the email and reviewing the Outlook settings as well as email and template code should resolve any issues customers are experiencing as when we send test emails to both outlook and gmail both are generally rendered differently (gmail seems a bit fine though). FAQs Where should I start trying to determine whether this is a Marketo or Outlook issue? In most cases if the email is loading within another email client without issue then Outlook would be the best location to review. Is there a way for me to see if it is a template problem? Yes, does the issue occur when an email is created and sent with another template? What are the steps to troubleshoot? In general, to provide the most accurate troubleshooting steps, a bit more information will be helpful. I have provided a few general tips below which may be helpful. As a rule of thumb, Outlook sometimes requires custom coding to appear as it does in other email clients since they use their own word engine to render the html. If the images when they are downloaded are not displaying as expected, we would typically recommend reviewing any code in the email since Outlook uses its word engine to render html and additional code may be needed for Outlook specifically as a result. A developer may be required to implement any custom code required to display the emails as expected. You may consider reaching out to the Community to understand what other users have done to overcome similar obstacles. I have provided a few links below which may be relevant. Is there any reference Documentation ? https://nation.marketo.com/docs/DOC-4765-why-does-my-email-looks-different-on-various-version-of-the-same-platform-like-outlook HTML Email Display in Outlook Marketo emails don't render properly in MS Outlook app for iOS Re: Help - My Emails Look Terrible in Outlook 2016 Here are a few resources that may help with Outlook rendering issues: It’s Not You, It’s Outlook – The Complete Guide for Email Marketers http://www.verticalresponse.com/blog/its-not-you-its-outlook-the-complete-guide-for-email-marketers/ Gallery of Common Outlook Rendering Issues Gallery of Common Outlook Rendering Issues MICROSOFT OUTLOOK CONDITIONAL STATEMENTS labs.actionrocket.co/microsoft-outlook-conditional-statements Outlook 2007/2010/2013/2016 and Word HTML Outlook 2013 / 2016 / 2019 / 365 and Word HTML - HowTo-Outlook 12 Techniques for Excellent Emails in Outlook.com How to Create Excellent Emails for Outlook.com A Guide to Rendering Differences in Microsoft Outlook Clients Outlook Email Rendering Issues and How to Solve Them - Litmus Surface Pro 3 and Outlook Email Rendering Redirecting

What is the Email API? What is the Email API used for? What is Email 2.0? Does the Email API Work on Email 2.0 Assets? Will the Email API Break when Enabling Email Experience 2.0? How Are 1.0 Assets Upgraded to 2.0 Assets? What to Do When an Email Was Accidentally Converted to Email 2.0 format? What is the Email API? API stands for Application Programming Interface and the Email API allows an automated process to create and edit emails in Marketo. There are also other API calls that involve emails, such as Approve Snippet (assuming the Snippet is used in an Email) and Clone Program (assuming the Program contains Emails). There are also API calls to create and update Email Templates. Essentially, the API can do many things that you can also do through the Marketo user interface, but then in an automated fashion. What is the Email API used for? There are many scenarios: an external system could create Emails in Marketo using data that lives outside of Marketo. A translation service provider could clone a master Email, translate it to many languages, then save them back into Marketo as localized Emails. A reporting system could extract Emails from Marketo to use in reports that are generated outside of Marketo. An external system could Clone a Program that contains Emails, then populate the Program Tokens and schedule the Email to be sent out at a specific time. There could be an external email template creation system that creates new Email templates in Marketo through the API. What is Email 2.0? “Email Experience 2.0” is the new Marketo product feature with the enhanced email editor, documented here: docs.marketo.com/display/public/DOCS/Email+Editor+v2.0+Overview. It can be switched on in Admin > Email > Edit Email Editor Settings. All Emails and Email Templates also have a version number, either 1.0 (the old version) or 2.0 (the new version). If we refer to “Email 2.0 asset” we mean an email or email template in the new upgraded 2.0 format. Does the Email API Work on Email 2.0 Assets? Yes. Will the Email API Break when Enabling Email Experience 2.0? No. Enabling Email 2.0 will not automatically upgrade Emails or Email Templates to the new 2.0 format. The Email API can still create new Emails and Email Templates in the 1.0 format. However – after enabling Email 2.0 – any Email or Email Template that is created or edited and approved through the Marketo User Interface will automatically be upgraded to the 2.0 format. How Are 1.0 Assets Upgraded to 2.0 Assets? If you edit an “Approved" or “Approved with Draft” 1.0 Email with Email 2.0 enabled, the draft is converted to the 2.0 format. You can still discard the draft to go back to the approved 1.0 format. Once you approve the email and it becomes 2.0, the Email cannot be converted back to 1.0. If you edit a “Draft” 1.0 Email (never been approved), this will automatically be converted to 2.0 with no option to revert back to the 1.0 format. The same applies to Email Templates. What to Do When an Email Was Accidentally Converted to Email 2.0 format? If an Email or Email Template was accidentally converted to the 2.0 format, you’d have to copy the asset contents to a text editor, disable Email 2.0, then create a new 1.0 asset using the content that you copied.

If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution. Caution: If the item you're looking to escalate is related to a Production Down incident, please call the support line for your region to receive immediate assistance. Support Manager escalations are only handled during normal business hours. The phone numbers for each region are listed below, follow the prompts for P1: Americas: +1.877.270.6586, Direct: +1.650.376.2303 Europe, Middle East, & Africa: +353 (0)1 242 3030, UK: 0800 151 3030 Asia Pacific: +61 2 8031 8188 Japan: +81.03.4233.9014 How to Escalate: Step 1. Navigate to the "Case Management" area of the support portal either by mousing over the Support tab and selecting "Case Management" or clicking the Support tab and click on the “My Case Management” button. NOTE: You will need an open or recently closed case in order to escalate to support leadership. This is a article attached image Step 2. From here you will need to click on either an open or a recently closed* case: This is a article attached image *Support Cases that have been closed for longer than 10 days are no longer eligible to be re-opened and we ask that you open a new support ticket for your current issue prior to escalating to a Support Manager. We ask that you have an open support ticket for a Support Manager to be able to address specific issues. Step 3. After selecting a case, click on the Escalate to Manager button: This is a article attached image Step 4. A pop up will display and you will need to the purpose for the escalation and click on the “Escalate” button. This is a article attached image Once your support escalation case has been submitted a Marketo Support Leader will contact you within 1 business day of your support region's support hours to address the issue.

Issue Clicking "Automatically copy over from HTML" or "Copy from HTML" in the Email Editor fails to copy the contents over to the Text Only version of the email. Solution This can occur if there are no editable sections in the email asset. By default, Marketo automatically copies the text content of any Rich Text element that’s in your email over to the Text version. Marketo defines a Rich Text element inside of an email template as a section using either mktEditable or mktoText classes. If the email's HTML does not contain either class, then no content would automatically be copied over. Here is additional documentation related to Email Text Versions: https://experienceleague.adobe.com/docs/marketo/using/product-docs/email-marketing/general/creating-an-email/edit-the-text-version-of-an-email.html?lang=en A quick workaround would be to manually copy and paste the content you wish in the Text Version, and in the future build/use templates to make emails with editable sections.

Summary Your global form validation rule is setup/active in Admin, and the rule is enabled on the form, but the rule isn't working. Issue Your global form validation rule is setup/active in Admin, and the rule is enabled on the form, but the rule isn't working (emails that should be blocked can still submit) Environment Admin Solution Check the rule in Admin > Global Form Validation Rules and confirm that there is no '@' prepended to the email domains. The domains should look like the below: 'gmail.com, outlook.com, acme.org...' Instead of: '@gmail.com, @outlook.com, @acme.org..." Root Cause '@' referenced in the domain name within the validation rule.

Issue How page views and form fills are counted in the statistics section of a Marketo Landing Page asset. Solution How they're calculated When viewing the Landing Page asset in either Design Studio or Marketing Activities, the statistics section provides information regarding page views and form fill outs, if the page has a form located on it. The page views are a cumulative total indicating how many times the page was loaded, regardless if the visitor was a known record in the database. This means anonymous people can record a view here, due to Munchkin tracking on the page. This section provides a total number of views, not unique visits. This means that a person can load this page multiple times and each visit will be tallied in this section. The form fills section (x Filled out Form (x%)), indicates how many times a visitor filled the form out on the page, if it has one. This total is also counted in the same way the views section is, meaning it's a total number of submissions. Therefore, if a record in your database fills out the form more than once on a page, it will be counted toward the total. Difference between calculations The difference between these two metrics is that the page views will keep a historical record of visits to the page. This means the total will not change if you happen to delete a bunch of records that visited the page in question - the total persists regardless if the record is no longer in the database. With that said, the forms section does not. This area is tied specifically to the existence of that known record in your database. This means that, once a record who filled the form out is removed from your database, the submissions they performed will be subtracted from the total.

Issue The subject line for an email sent out to leads did not match what was set for an approved email. Solution The email may have Dynamic Subject Lines enabled. Dynamic Subject Lines allow you to set dynamic content for the subject line based on the Segmentation of your leads. Visit our Documentation for further information about segments and dynamic content. Segments: Create a segmentation Dynamic Content: Using Dynamic Content in an email The issue can be resolved by converting the subject line to a Static Subject Line. A Static Subject Line is a single line of content that will send out to any recipient of your email, regardless of their segmentation. You can do so by doing the following: Click on the Subject Line to bring up the Subject Line edit buttons. Click the Make Static button

Issue You're receiving an error that states 'Not Allowed - Error approving <asset-name> - {{token-name}} : Token key not found' when trying to approve an email asset. Solution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}' Check that the field name of the token does not have any incorrect spelling (e.g. Email Address) If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.

Issue Issue Description Getting 'Communication Failure' error popup repeatedly when doing normal operations within the application. Solution Issue Resolution: - Disable all browser extensions especially any dealing with ad blockers as they seem to be the primary cause of this issue ("Ghostery" is an example of extension known for blocking multiple Marketo operations/ tasks). - Try to repeat same operations after you have cleaned cache and cookies - (If above option does not work) Try to repeat same operations while using a incognito browser window.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

I Didn't Receive a Sample Email that I Sent

Dealing with Spam or Bot Form Fillouts

No-Draft Snippet Limitations and Troubleshooting

Troubleshooting Background Image Not Being Rendered on Landing Page Editor

Correct Thank-You Page Does Not Load After Form Submission

Email Script Token Containing Variables Renders Incorrectly

Recipients using Apple Mail Getting Broken Links

Deep Links in Emails Do Not Take Lead to App

Embedded Forms Load Slowly on External Web Pages

Marketo Forms Not Showing Up in Firefox Private Browsing

Different Email Addresses in the From and Reply-To Lines

Email Looks Different on Various Versions of the Same Email Client

Email 2.0 and Email API FAQ's

Escalating a Support Issue

HTML Email Not Copying Over to Text Only Version in Editor

Global form validation rule not working

Statistics section on a Marketo Landing Page asset

Subject Line for Sent Emails Different than What Was Approved

Error Approving Email - Token Key Not Found

Getting Repeated 'Communication Failure' Errors