Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

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

Issue Embedded Marketo form not visible in Firefox Private Browsing mode. Solution 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 "Tracking Protection" in the Firefox browser will need to be deactivated for the form to appear. Here is an article from FireFox regarding the Tracking Protection: https://support.mozilla.org/en-US/kb/tracking-protection

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 Updating an Email Template is creating a draft for existing emails without the desired changes Solution When changes are made to an Email Template in the Design Studio that is already in use and those changes are approved, it will create a Draft for any existing Email that was created from that Template. If the draft is not reflecting changes you would like to see made, you may have included the changes within a mktEditable or Editable class <div> tag. The content within a mktEditable class element within an email template are ignored from any changes as they are considered to be "default content". Any content within these elements will not see any changes made to them based on changes to the template, and will only be seen when creating a new Email asset. You can update an editable section to remove it's editable status, however this will remove any changes to the content done in any email. You can see which elements can be classified as Editable here: https://docs.marketo.com/display/public/DOCS/Email+Template+Syntax

Issue When forwarding email that was received via Marketo to other people, the email does not render the same in the recipient's email client. Solution This can happen when forwarding emails, as the email rendering capabilities depend upon the email client that recipient uses. HTML and CSS can be interpreted differently by different email clients. As noted in the comment below Some clients' HTML parsers don't understand all types of markup, for example an HTML4-level client will not recognize HTML5 elements. Some HTML elements and CSS rules are deliberately ignored, even if the underlying parser and (in the case of webmail) browser supports them completely The HTML markup is can be changed, sometimes drastically, from the original markup before being displayed for security reasons With that said, you can code against some of these anomalies by adding extra code in CSS to account for the differences. Marketo Support is not set up to assist with troubleshooting custom code as we are not web developers. We would suggest that you consult with an HTML/CSS designer to make these changes. To ensure that the existing email templates are coded to comply with different email clients, it is advisable to consult with a web developer/designer to review the code. Here is a guide that you may find helpful: https://www.campaignmonitor.com/css Furthermore, even if the clients are the same, the act of forwarding an email can itself change the HTML of the email. However, Marketo does have a workaround for this. You would just need to put the ‘Forward to Friend' link directly into an email and when the person forwards the email using this link, there is a reduced possibility of the rendering issue occurring. It also adds the forwarded email address to your Lead Database as an unsubscribed lead. The below article covers adding the ‘Forward to Friend’ link to your emails https://docs.marketo.com/display/DOCS/'Forward+to+a+Friend+Link'+in+Emails

Issue Issue Description You encounter the error "You do not have permissions to do this" in one of the following situations: When you are creating an email template, you click on the Validate HTML button When you are trying to edit an existing email Solution Issue Resolution This error is caused by Javascript in the HTML of the template. Email clients do not often allow <script> and Javascript in their Emails, so even though the email asset may be able to be approved, the email will present this error if attempted to be edited again or if you attempt to validate the HTML. The solution in this situation would be to remove the <script> tag, including all Javascript, from the email HTML. After this, you should be able to edit the email or validate the HTML. If you are unable to actually edit the asset, the workaround is to clone the asset. If you clone the email, it can open in the editor and then you have the ability to remove the script. After this, the email will be good to go.

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 http://labs.actionrocket.co/microsoft-outlook-conditional-statements Outlook 2007/2010/2013/2016 and Word HTML http://www.howto-outlook.com/faq/wordhtml.htm 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 https://litmus.com/blog/a-guide-to-rendering-differences-in-microsoft-outlook-clients Surface Pro 3 and Outlook Email Rendering Redirecting

Issue You have a tracked link in an email. When the email is received, the link breaks and doesn't redirect to the desired page. The link works perfectly when the tracking is disabled. Solution The server hosting the link might not accept parameters, or might limit the number of characters in the parameter, etc. When tracking is enabled, Marketo adds mkt_tok=manymanycharacters. The issue could be either the page does not accept parameters at all, or does not accept such long parameters. You might need to reach out to the developers of that page and investigate this. Our suggestion is to have “track link” checked but not the “Include mkt_tok”. Unchecking just Include mkt_tok will still allow the link to be tracked, but after redirect, the destination URL will not include the mkt_tok query string parameter.

Issue When approving emails, the system shows the following error: "Note: detected the following lines in text version that are longer than 1000 characters: Line 6 and they are not fixed. The email is now approved". Solution This error is an indicator that there is a large line of text in the text-only version of the email that is over 1000 characters. This occurs when there are long links in the email which will not publish correctly in the text version of it. But still the email will be approved and can be sent. Check for excessively long links in the text version of the email and simplify them if possible. You can test it by sending a text version of the email to yourself, or by checking the Text Only version in the Email Editor.

Issue Email asset does not show which template it was built on and shows the word "none" instead of the name of the template that was used to create that asset. Solution Any edit directly to the HTML code of an email will break the connection between the email and the template. Changes made to the template will no longer flow down to the email. After making those change you will see a template name of None instead of the name of a template. When editing the HTML in the email, you will see this warning message: This is a article attached image

Issue Form in Design Studio will not convert the time format upon language selection. English form with date format dd/mm/yyyy This is a article attached image Below is a form using settings with form language selecting German. The date format remains the same "dd/mm/yyyy" when the expected value should be "tt/mm/jjjj" as per language date format This is a article attached image Environment Marketo forms and common web browsers such as Chrome, Opera, Firefox. Root Cause This behaviour is related to the browser language settings. It automatically translates the date in the format of the selected language in the browser. Example of the same form with different browser language selected, the date format is changed by the browser This is a article attached image This is a article attached image

Issue Sometimes, you may receive an auto response from an email that has been sent through a batch campaign. The auto response email will not show the lead's email address instead it does contain the HTML of the email along with the Marketo decorated link. Is there a way to decipher this to determine which lead record this corresponds to? Solution You could try opening a new browser window and either clear your cookies first or use the browser's private browsing feature (makes a cookie sandbox) so you don't confuse Marketo and tie that person's lead to you by accident. Anyways, in your cookie-free browser, click the link and then go to a form that Marketo prefills for you and you may see the email address that was originally targeted.

Issue You want to delete an Email Template but that template was used to create existing emails in your instance. Solution It is not possible to delete an Email Template that is in use by emails in your Marketo instance, even if those emails are not approved. If you wish to delete the template, you will need to first delete the emails that use it. You can find these in the Used By tab in the template's information. Alternately, you can break the connection between the email and the template, which would allow you to keep the email but delete the template.

Issue You receive the "Subject is empty" error when attempting to approve an email which contains an emoji character in the subject line, and elsewhere in the email, emojis may fail to render. Solution Marketo can render any Unicode character up to 5.2 and any ASCII character, but this does not encompass emojis. The Marketo email editor will strip out any unsupported symbols. This is because we cannot guarantee the consistency of their appearance across platforms, as not all clients can render all emoji. Marketo only supports the text symbols that are generally then converted into emoji's by the recipient client or operating system. The basic symbols in a list such as https://www.copypastecharacter.com/symbols should work, as they are ASCII characters and not reliant on extra encoding. These are a set of accepted text symbols that will universally work on all clients and many will convert them to emoji. Just highlight the symbol from https://www.copypastecharacter.com/symbols, copy and paste it into your email. Alternately, you can work around this by q-encoding the emoji in UTF-8 format, which will render a string of code to add to your subject line. This code tells the email client to render the desired emoji. All you need to do is copy your desired emoji and run it through a Unicode to UTF-8 translation tool, such as https://onlinetools.com/unicode/convert-unicode-to-utf8. As an example, say you want to send a Happy Birthday email to a lead. You could copy the (birthday cake) emoji and run it through a translator to yield the code "=?utf-8?Q?=F0=9F=8E=82?=" Entering this code in your subject line without the quotation marks will render the emoji on the client's end, and render it in the design most compatible with their device/browser. With any email design, it's always important to test before a live send to confirm it appears the way that you expect it to.

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 Issue Description Marketo allows you to upload any file type to your instance (100MB or less) but these files don't always download automatically or open in a new browser tab or window consistently between users. Solution Issue Resolution Marketo's servers are not configured to force a download, so any desired effect is up to the user and/or utilizing custom code to achieve that effect. How a file is handled or displayed is largely up to the browser and you will need to test whether your specific desired outcome is possible. Keep in mind, this may vary by file type and file size and may not be feasible.

Issue Sometimes, you may notice that editing the text version also affects the HTML version of the email. Is there a way to edit the text version without the same edits occurring to the HTML version? Solution Changes to TEXT never apply to the HTML version. It's likely because when you "save" an element, it will add the "root block element" to the HTML side if one isn't present. So, your HTML is probably not handling it correctly. You can change the "root block element" to none in the Admin > Email > Editor Settings dialog. https://docs.marketo.com/display/public/DOCS/Using+the+Rich+Text+Editor

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Embedded Form No Longer Showing on Your Webpage

Embedded Marketo Form Not Visible in Firefox Private Browsing Mode

Embedded Forms Load Slowly on External Web Pages

Email Template Updates Not Reflected in Existing Emails

Email Rendering Issue in Forwarded Emails

Email Permission Error When Validating or Editing Email

Email Looks Different on Various Versions of the Same Email Client

Email Link Breaks When Tracking Is Enabled

Email Error : Lines in the text version that are longer than 1000 characters

Email Asset Shows Template “None” Instead of an Actual Name

Editing the Email Header

Translation of date format in Marketo form

Determine Lead Record Using a Decorated Email Link

Deleting an Email Template That Is Used by Emails in Your Instance

Customizing Forward to a Friend Emails

Using Emojis in Marketo Emails

Deep Links in Emails Do Not Take Lead to App

CSV Files Hosted in Marketo’s Images and Files Don’t Always Download Automatically

Edit Text Version of the Email without Affecting HTML

Adding a Marketo Form to an Email