Your Achievements

0% to

Next /

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

View All Badges

Open Alert Bar

Knowledgebase

Featured article

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

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue Issue Description Revenue Explorer (RCE) reports show different stages when comparing Model Performance Analysis and Program Revenue Stage Analysis. Detour stages such as Disqualified, Inactive, Recycled, and Lost do not display as metrics in Revenue Stage Analysis reports. Solution Issue Resolution The Program Revenue Stage Analysis in RCE will not show non-success path Revenue Stages, so detours do not display on the Success Path as viewable metrics. Model Performance Analysis will show non-success path Revenue Stages. For more information on Success Paths, see this related document Who This Solution Applies To clients with Revenue Cycle Explorer and who have an approved Revenue Cycle Model

Issue User cannot add a Field Organizer when the user does not have access to all workspaces. Solution Unless the user has access to all workspaces, they cannot create a field organizer because field organizers are available in all workspaces. However, the user still can access and even delete the field organizers that are created by others. Who This Solution Applies To Instances with workspaces

Dear valued customer, As you may know, on July 25th, 2017, our main web site, Marketo.com, along with other Marketo domain properties, were rendered inaccessible, preventing access to our application from 4:06am – 10:08am PDT. We apologize again for the inconvenience this caused. On the Marketo Trust site, you’ll find current and past Marketo system performance data including System Uptime and Reliability. This is monitored 24x7 and we have consistently maintained greater than 99.9% uptime. This uptime is calculated based on the length of time that the Marketo systems are functioning properly within our servers (“pods”). While the Marketo systems were functioning and available by 10:08am PDT, we realize that due to third-party DNS propagation timing, some customers may have experienced delays in accessing our systems of up to 48 hours, depending on region. All Marketo back-end processes such as Smart Campaigns were still operational during the DNS propagation, however, the propagation reduced accessibility to Marketo for some users. As a result, we believe the normal calculation of system uptime may not accurately reflect everyone’s experience. To address this, we have decided to make a one-time change to our normal calculation for July to more closely track what our customers may have experienced in terms of accessing our systems regardless of whether the problem lay with us or was due to third party systems/processes. After studying the issue, we think the best way to calculate this is based on customer logins to the system. We looked at the first login time for each pod and used login as a proxy to calculate when customers were able to access Marketo. This one-time calculation is a better reflection of the frustration you may have experienced in accessing Marketo. We will return to using our normal calculation for August. For the month of July, our server pod uptime was 99.997%. All back-end systems, such as smart campaigns, were processing normally while the domain was offline, so when calculated in the normal way, our server pod uptime for July was 99.997% When taking into account the 6 hours when the marketo.com domain was not available, the system uptime for the month of July was 99.17% As mentioned, if we add the full extent of the DNS propagation as discussed above, and take an average of the first logins across the entire customer base, the average user accessibility for July would be approximately 97.77%. For additional information please contact Marketo Support and see our FAQ document and this letter from our CEO Steve Lucas.

Issue Description Munchkin activities recording stopped and web page activities were not logged. Since the activities were not immediately registered, any Trigger Campaigns set to initiate when those activities occurred would not have been triggered. Issue Resolution Initial Steps: As soon as you identify an issue with Munchkin Activities recording, contact Marketo Support to ensure that proper steps are taken to prevent any data loss. Once the activity data is back-filled, identify all the Smart Campaigns that were impacted and need to be replayed. If you need assistance to identify which smart campaigns were active during this incident, our Campaign inspector is a great tool to assist you. https://nation.marketo.com/docs/DOC-4470-campaign-inspector-for-triggered-recurring-campaigns. Replay Impacted Smart Campaign: After you have identified the smart campaigns that were impacted, create a new smart campaign using the following smart list filters; For Smart Campaigns triggered by clicking a link on a web page, use the following filters. Select the applicable link and timeframe based off what datacenter your instance is located in. The second filter is to prevent activities that were not impacted from replaying. For Smart Campaigns triggered by a web page visit, use the following filters. Select the applicable web page and timeframe based off what datacenter your instance is located in. The second filter is to prevent activities that were not impacted from replaying. After the Smart List is set up, the flow steps should mirror the flow steps of the original Smart Campaign that you wish to replay. If you experience any issues with replaying the impacted smart campaigns, please contact Marketo support at https://support.marketo.com, or through any of the methods listed here.

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

Issue The issue appears when a custom view is created in MSI that contains dependant fields. The error message: "The dependent picklist '<dependant field name>' requires its controlling field '<parent field>' to be present on the page." will be displayed when you are trying to add the dependant field. For example: "The dependent picklist 'Sub-Classification' requires its controlling field 'Classification' to be present on the page." Environment Salesforce MSI Solution Need to omit the dependant field in the custom view. Root Cause We curently do not support creating a view in SFDC MSI with a dependant field.

Marketo recommends keeping the FT (First Touch) and MT (Multi-Touch) in separate reports . Though they are attribution metrics, FT and MT use different measures to derive pipeline and revenue attribution. One should not try to compare FT and MT metrics and having them in the same reports may cause confusion. Step 1: In RCE, Program Opportunity Analysis, identify the Program and Opportunity of interest. If verifying FT, pull in relevant FT metrics. Ditto for MT. Also pull in Opportunity Closed and Opportunity Stage. The combination will tell you if the status of opportunity (open, won, lost) - which does affect attribution. Step 2: For the opportunity, find out the lead(s) associated to that opportunity and opportunity create/close date, status information. One way is to get this information is to do so in SFDC. In SFDC, search for that Opportunity and scroll down to the Contact Role section to identify the associated leads (contact). Other opportunity information should also be available. Another way is in RCE, Opportunity Analysis area. Filter Opportunity Name to the opportunity of interest. Pull in # of Opportunities and Lead Name. You can also find out oppty create/closed date, status in this area. Step 3: Find out acquisition and success status/dates for the leads in the program In Marketing Activities, go to the program and click on Member. Search for the lead by name. The column Acquired By and Success will tell you if the lead is acquired by the program and/or achieved success, respectively. If the lead is acquired, to get Acquisition Date for this lead, in the lead grid, choose column Acquisition Date If the lead achieved success, to get Success date: Go to Lead details, click on Activity Log tab Search for program name and filter on activity type 'Change Status in Progression' Locate the FIRST success activity when a lead changed to a successful status. RCA only counts the first success. The activity date is the success date. Step 4: Evaluate if program is qualified for attribution for the program The combination of Acquisition program/date, success status/date, opportunity create/close dates and opportunity status will help determine FT/MT attribution. The rules of attributions is documented in Product Docs. With all the information gathered, you can now determine if the program is qualified for attribution for this opportunity. Again, this technique is to verify if the program should get some attribution and doesn't necessarily give you the exact units and dollars.

Issue A/B test in Email Program status is still showing “Running test…” and not all email variants were sent as expected. Environment A/B Test Email Program Sample Size Running Test Solution To ensure the sample size qualified at least a minimum of the total variants of the A/B test. For example, if you have a total of 6 records, a sample size of 34% will suffice for 2 records (1 for variant A and 1 for variant B). Root Cause This can occur if the sample size selected is too small. For example, if you have a total of 6 records, a sample size of 1% will not suffice for 1 record.

Issue When looking at Email Insight it is only showing the first email activity (Send, Delivered, Click or Open), even though the email has been sent several times in the past few days/weeks/months. Environment Email Insight Solution Use different Smart Campaign to send the email if you want to track statistics of the email. Root Cause Email insights will only track the first email activity associated with the email if using the same campaign. this is the same as Email Performance report in terms of this note. Multiple sends from the same campaign to the same person are counted only once.

The reason why the Sales Insight Anonymous Web Activity report differs from the Lead Management Anonymous Web Activity report is because the Sales Insight report does not show anonymous leads whose company name is either blank or is an ISP while the Lead Management report shows everything. The Sales Insight tool is geared towards Sales, and visitors with blank or ISP company names could be misleading to the Sales person. You can see this by looking at the Lead Management report. Notice that the visitors whose company name is bolded are the ones that are displayed in Sales Insight. When the company name is bolded, that means that the visitors company name has been verified using a reverse DNS lookup. Conversely, if the company name for the visitor is not bolded (or is missing), the reverse DNS lookup just shows us the ISP (or nothing if the reverse DNS lookup yields nothing). If you want to remove anonymous leads who do not have company information from your web activity report, follow these instructions: Hide anonymous leads without an inferred company in web activity reports

Issue You receive a Marketo email and an email address in the text is blue and underlined, which does not match your desired styling for the email. Solution When an email address is simply included in the email text, the email client's default behavior may automatically convert it to a link with blue text and an underline. In order to override this default email client behavior, use the following HTML: <a href="mailto:[email address]" style="[custom styling]">[email address]</a> When the email address link is inside the anchor tag <a>, the email client will not override this custom styling that you wish to use. This can be used for tokens as well: <a href="mailto:{{lead.Email Address}}" style="[custom styling]">{{lead.Email Address}}</a>

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 You receive the error message of "exceeded limit" for Program Member Custom Fields (the documented limit is 20), but you don't see 20 fields listed in the Admin > Field Management > Program Program Member Info area. Root Cause There may be Program Member Custom Fields in your Marketo instance that are hidden. These hidden fields still count toward your limit of 20. As next steps, in Admin > Field Management, review the Hidden Fields area to find the hidden Program Member Custom Fields, and un-hide them. After un-hiding them, they will appear under Admin > Field Management > Program Program Member Info. To resolve the "exceeded limit" error, unused fields should be deleted. Reach out to Marketo Support to delete Program Member Custom Fields.

Issue You added yourself to the Send Alert To portion of the List Import process and continue to receive unwanted Alert Emails every time a list is imported. Solution During the next List Import process to the problem Static List in Marketo, you'll want to select the Edit Send Notification from the window that pops up in the top right section of your screen after the import process is started. Selecting the Edit Send Notification will cause a new window to open up that shows all of the email addresses who will be sent an Alert Email once the import completes. If you no longer want to receive the Alert Emails for this static list going forward, deleteyour email address and click save.

Issue Issue Description In a Smart Campaign Results section, there are activities showing that are not campaign flow steps. Solution Issue Resolution Marketo will display any related activities that were a result of the campaign flow steps in the Results For example, if a campaign syncs a record to the CRM, any associated 'change data value' activities from the sync will be written in the Campaign Results.

When you ask Marketo to add a Salesforce contact to a lead queue, Marketo creates a duplicate lead in Salesforce and adds that to the queue instead. The reason why Marketo creates a duplicate is because Salesforce queues can only have leads in them, not contacts. If you try to add a contact to a queue, Marketo can either do nothing or create a duplicate lead and add that to the queue. We opted for the duplicate. If you want to prevent this behavior in your campaigns, use a filter on "SFDC Type is Lead" to limit the action to only leads

Issue Error "API is not enabled for this Organization or Partner" occurs during Marketo - Salesforce integration. Solution This is a Salesforce generated error and indicates that API access is not available in your SFDC instance. For more information, see this Salesforce documentation: http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_concepts_core_data_objects.htm . To resolve this, contact Salesforce to enable API access.

Sometimes you may see a link in your email that isn't decorated when you mouse over it. That same link isn't tracked when you click it. Check that there is a link The most common solution is to add a link to the email. Many email clients will automatically add links to when the text looks like a URL. For example, here's a link as it was typed in an email: But Outlook renders that text as a link: To fix this, edit the email and add a link to the URL by highlighting the text and clicking the link icon in the HTML editor: Check the <a> tag If you edited the HTML, check to make sure it's correct. Check if the: href is enclosed with quotes <a> is opened and closed correctly Check for class="mktNoTrack" If you edited the link with class="mktNoTrack", the link will not be decorated by Marketo. You'll have to remove that class from the email template or email body, depending on where it is. Validate your email HTML As an additional check, you might want to run the HTML through a validator; HTML errors can cause links to break among other problems. Download the HTML for your email with the Download HTML button in the HTML Tools menu. Then run the HTML through HTML Tidy. You should address the issues it discovers as they may be responsible for the bad link.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Revenue Explorer Program Revenue Stage Analysis Does Not Show Non-Success Path Revenue Stages

User Cannot Add a Field Organizer Without Access to All Workspaces

Marketo System Uptime - July 2017

Replay Trigger Campaigns That Failed Due To Munchkin Activities Recording Issues

Engagement Program Failed to Send Email in Stream

Soft Bounce “System Send Failure Reply-To Address Parse Error”

Keep the "Clear" form button on the same line as the "Submit" button

Unable to create custom view in SFDC MSI with dependant field

How To to Identify a Unique Relationships between Opportunities and Programs

Status: “Running test…” A/B Test

Why are emails sent from the same campaign to the same person only showing up once in Email Insight?

Why are the Anonymous Web Activity reports different between Lead Management's Analytics report and Sales Insight?

Received Mail Has Email Addresses Underlined and Blue

Email Permission Error When Validating or Editing Email

Error exceeded limit for Program Member Custom Fields

Removing Yourself from a List Import Alert Email.

Non-Campaign Activities Shown in Campaign Results

Adding a Contact to a Salesforce Queue Creates a Duplicate Lead

SFDC Integration Error: API Is Not Enabled for This Organization or Partner

An Email Link Is Missing Decoration