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 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 Leads are stuck in a smart campaign's Wait Step and have not moved onto next steps, even though the Wait Step has been updated/shortened and the lead should move onto the next step. Solution When a lead enters a Wait Step, it remains in the Wait Step as defined at the moment they entered it. For example, if the lead enters a 1 week Wait Step, it will remain in the step for 1 week. If the Wait Step is updated to be longer or shorter (for example, shortened to 3 days or extended to 2 weeks), the lead that already entered the Wait Step (when it was 1 week) will remain in the Wait Step for the original duration. New leads entering the Wait Step will abide by the new duration.

Issue Customers may run into limitations with Webhook providers or other third party REST services that require their fields are an integer type field. This may present issues with those values being inputted to Marketo (and other systems) accurately if a record has a value outside of the integer value limitation range: -2147483647 to 2147483647 Environment Marketo/Third Party REST/Webhook Providers Solution There is no way to increase/modify the integer value limitations on the Marketo side. This is not a Marketo product limitation, it's the defined constraints of Integer data types. If you're running into issues with values from a third party/webhook provider falling outside of the limitation range, this will present issues with the field value being accurately logged in Marketo. In this scenario, it's worth checking with the third party/webhook provider to see if they have any flexibility around which field types they can allow (for example, String or Float type fields have less limitations and will allow for larger or smaller numbers outside of the -2147483647 to 2147483647 range). For a full overview of Marketo field limitations, you can visit the below article: Marketo Field Limits by Field Type

Issue When cloning an asset from Design Studio into Marketing Activities, there is a box that asks you to select which program to clone the asset into. When clicking into this box, you may see No Results, even though there are programs within Marketing Activities. This is a article attached image Solution Expected Behavior: This happens when there are too many programs in the Marketing Activities tree. To select your desired Marketing Program, begin typing the Program Name, and results will begin to appear in the Program drop-down. This was designed to increase UI performance when cloning assets into Marketing Activities from Design Studio.

Issue When attempting to import a list in the UI, an error appears that states "Invalid encoding" and the import does not complete. Root Cause Marketo requires the import CSV file be encoded with one of the following: UTF-8, UTF-16, Shift-JIS, or EUC-JP. As next steps: Re-save the file, for example in Excel as file format CSV UTF-8, with the correct encoding. Then re-try the import into Marketo. If the error persists, contact Marketo Support.

Summary The customer wants to know if a nurture email was not sent to a recipient due to communication limit, then will it be sent in the next cast, or that email will not be sent again? Issue Individual(s) were supposed to get an email from a Nurture (Engagement) Program cast but failed to receive the email due to hitting the communication limits set in the instance. Do you need to manually send the email to the individual(s) via a separate Smart Campaign or will it be sent, automatically, on the subsequent cast for the Nurture Program? Environment Marketing Activities Nurture Programs Engagement Programs Admin Communication Limits Solution You don't need to act on these scenarios as the individual(s) impacted by the Communication Limits will be sent the applicable email in the next cast for the Nurture Program. The only reason that the individual wouldn't be sent the email in the subsequent cast for the Nurture Program would be if the person would hit their Comm Limit again. Should that happen, you might want to review your Communication Limits settings or review the individual(s) impacted and see why they keep hitting the Comm Limits. Reference: How Do Communication Limits Work? - Marketing Nation (marketo.com) Root Cause Communication Limits being hit during Nurture Program cast execution

Issue You have a Batch Campaign or Email Program setup where the amount of people qualified is more than what's listed under the Smart Campaign Person Restrictions limit (for more context, see Enabling Person Restrictions for Smart Campaigns). Within that same program or campaign, you calculate that between the number of qualified people reduced by how many are blocked from processing puts the total count of records below the Person Restrictions for the instance. Would the campaign or email program still execute and process the appropriate leads that aren't blocked or does Marketo solely look at qualified members to determine if that's more than allowed based on Person Restrictions? Environment Admin Marketing Activities Marketo Scheduling Solution Yes, the campaign will still run as expected. Both Email Programs and Smart Campaigns effectively disqualify non-marketable people before processing records towards the Campaign Processing limit. Example: Your instance is setup to limit campaigns from processing more than 500k records in a given Smart Campaign. If you have 600k qualified for your Smart List (Audience) but 200k of the records are blocked, the campaign will still run as only 400k marketable people qualify to actually get processed through the campaign. Blocked records don't get processed through the campaign execution and, therefore, don't add or contribute to campaign processing limits.

Issue Field values updated in Marketo do not sync to SFDC when the record exists as a Contact. Environment Marketo - CRM Native contact Sync Solution The issue is caused by the interaction of the Block Field Updates with the conflict resolution rules for Contacts described here. The Block Field Updates will prevent Marketo from writing values from Salesforce into Marketo, but it does not prevent the sync from attempting to sync those values. If a field has Block Field Updates enabled to prevent updates from SFDC and that fields gets updated in both Marketo and Salesforce at the same time, Marketo will attempt to use our conflict resolutions rules to allow the update from SFDC to override the Marketo updated. The Block Field Update prevents this from occurring which leaves the records stuck unable to update the value in either system. To resolve the issue for the specific records, the Block Field Updates setting must be removed for the specific values to allow the values from Salesforce to sync down. Then the feature can be re-enabled. To prevent recurrences of the issue in the future, Users and processes in Salesforce must be prevented from editing those values to prevent a conflict from occurring.

Summary Marketo Form Does Not Appear on a Landing Page Issue Marketo Form embedded on a Landing Page and the Form does not load. Environment Marketo Solution If you are able to reproduce the behavior in a Private Browsing window using Firefox, then issue is most likely caused by the embed being used. Examine the embed code on the page and ensure that the Form is loading using your instance's Landing Page Domain. For example you may see your embed code formatted as <script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script> It instead it should look like <script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script> <form id="mktoForm_1"></form> <script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script> Once the embed code has been updated, load the page again and the Form should now appear. Root Cause Firefox released a privacy update that blocks loading of certain elements directly from the marketo.com domain. This prevents Marketo Forms from loading when they point to a source of marketo.com. Updated the embed code to use your Landing Page Domain allows the form to load correctly.

Summary Adding Webinars from Additional Users Issue After setting up the Marketo/Zoom integration and attempting to connect a Webinar to an Event Program, you may see the message "This Account has no Webinars" or certain webinars may be missing as an option. Environment Zoom/Marketo Solution When setting up the Marketo/Zoom integration an Admin user must be connected to the Launchpoint integration. By default, only webinars created directly by this Zoom user will appear as options. If other users have shared webinars with this admin, additional steps must be taken to make them visible in Marketo. In this article you will find the steps to add additional Zoom users to the Marketo integration configuration. Once those users have been added, webinars they own will be available as options in Marketo. Webinars owned by users not added with the instructions above will not be available in Marketo.

Issue When using the [mktorest.com/rest/asset/v1/emailTemplates.json] end-point to pull all Email templates, the COUNT is much less than what is shown in Marketo's Design Studio Global Search. Solution This is the expected behavior. When viewing the total count of Email templates in the Design Studio UI, it will count EACH shared template that is shared across other workspaces, counting the same template multiple times depending on how many workspaces it's shared to. However, when retrieving the Email Templates from the REST API, it will only return DISTINCT Email Template ID's from the originating shared workspace where the template resides. It will not return the templates from the shared workspaces. Root Cause REST API Expected Behavior

Issue When using the Merge Lead(s) REST API end-point and merging multiple leads, which field values would be copied to the winning record? In the below example, the winning lead record has a blank value for Job Title. When merging all 4 leads, which field value will get copied to the winning record from the list of losing records? This is a article attached image Solution The field values that will be injected to the winning lead record are directly impacted by the order of leadID's in the Lead array parameter of the call, where the FIRST leadID listed in the parameter array will be the winning value IF the field on the winning Lead record is blank. URL Example {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=2232,1323,1455 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = 'electrician'. URL Example #2 {{baseUrl}}/rest/v1/leads/4231/merge.json?leadIds=1323,1455,2232 RESULT Based on the above excel chart, LeadID 4231 (Winner) would have their Job Title field updated = blank/empty. Root Cause This is the expected behavior when merging multiple leads via the REST API Merge Leads end-point.

Summary When renaming a field in a CRM Custom/Entity it does not reflect the change in the constraint of filters/triggers/ Issue I renamed a field in my CRM Custom Entity/Object (MSD/SFDC) and I refreshed the schema. I can see the field name change reflected in the CRM Custom Entity/Object, but when I look for the field in constraint for filter/trigger I only see the old name. Environment Smart List Solution The workaround is that the customer can create a new field on the SFDC side and copy all the values from the old field to the new one. Then, this field can be used in smartlist filters. Old field can be disabled after that. Root Cause We are not propagating field name changes from SDFC to Marketo.

Summary Learn how to troubleshoot the REST API Error: read ECONNRESET. Issue You are getting the following HTTP error when attempting to call the associated REST API. REST API Error: read ECONNRESET Cause This error might occur because of issues on the local network or HTTP client config. Here are some possible causes of this error. HTTP Client Configuration Issues: The error may occur due to incorrect, incomplete, or incompatible settings in your HTTP client. To align your HTTP client settings with the Marketo REST API requirements, you should review and update your HTTP client settings. Proxy Server or Configuration Problems: If you use a proxy server, its configuration may result in an HTTP error. Verify your proxy server settings and consult your network administrator for accurate configuration if necessary. Faulty Network Equipment: Issues with hardware such as switches and routers, particularly if they are malfunctioning or improperly configured, can cause the problem. You should investigate the status and settings of your networking devices to determine if this is the issue. Solution To resolve this issue: Review and adjust your HTTP client's configuration to match the Marketo REST API specifications. Check your proxy server settings and consult your network administrator if needed. Examine network equipment for faults or incorrect configurations.

Summary New checkbox for query parameters available when adding new content or editing current content. Issue You were previously unable to specify query parameters for predictive content, and query parameters were not used when adding new content, editing current content, and reporting on URL clicks. Autodiscovery works by adding a new URL to the DB, and later on, clicking counts are accumulated against the newly found asset. The asset is determined based on the URL (and there, it previously didn't account for anything that followed the ? in the URL. The same was used as a validation when a user added new content. The rule to determine this part of the URL, minus the query parameters, was a requirement back then and was taken into account during design. Solution As you add predictive content from the predictive content page, you need to have the checkbox on this page to allow the user to decide whether they want to include/exclude the query parameters while adding it. The same thing should be followed for editing predictive content as well. Engineering built a nuanced approach that provided flexibility to include or exclude query patterns in determining a unique URL and added a feature to include query parameters when manually creating a piece of content. It should rightly identify the right asset to record clicks/views against as well.

Summary Learn how to resolve issues with uploading SVG files to Marketo. Issue You are not able to upload Scalable Vector Graphics (SVG) files to Marketo. You are encountering errors during the upload process or facing issues with improper display in browsers after uploading. Cause: The root cause behind such issues is often Marketo's security checks, which may reject certain properties of SVG files. This can lead to conflicts between what Marketo accepts and what browsers can display. Solution To address SVG files not being accepted or displayed correctly in Marketo, try the following steps: 1. Change File Extension to .xml: Instead of saving the file with a .svg extension, save it as a .xml file. This will change the server MIME type and allow it to be uploaded to Marketo. Example: If your file is named "example.svg," rename it to "example.xml" before uploading it to Marketo. 2. Remove Unwanted Properties: If the SVG file contains additional properties or namespaces causing rejection by Marketo, removing them can resolve the issue. For instance, the xlink namespace, if present at the top of the SVG file, may lead to rejection by Marketo. Exercise caution not to remove essential properties, as this could result in errors when attempting to display the file in a browser. Example: If your SVG file has the following line: xml xmlns:xlink="http://www.w3.org/1999/xlink" Remove this line from the SVG file's code using a text editor. When saving SVG files from applications like Adobe Illustrator, changing the file extension or manually editing the code may be challenging. However, using any file explorer, you can easily change the file extension to .xml. Code editing can be performed using a text editor to manually remove unwanted properties. Always back up the original SVG file before making any changes to prevent permanent data loss. By following these steps, you should be able to successfully upload SVG files to Marketo and ensure proper display in browsers.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Does Marketo reuse or recycle old deleted lead IDs

Error exceeded limit for Program Member Custom Fields

MyToken used in Email not reflecting correctly

SFDC Error Unable to process due to no XML response from Salesforce

Leads stuck in Wait Step after Wait Step Change

Can Marketo Increase The Max Integer Value Limit of 2147483647?

No Programs To Select When Cloning Assets From Design Studio To Marketing Activities

List Import Error: "Invalid Encoding"

Nurture Program Email Blocked Due To Communication Limits

Smart Campaign Limits And Blocked Records

Block Field Updates not syncing marketo field values to SFDC

Lead cannot see unsubscribe form

Webinars Missing from Zoom Integration

Marketo Sales Insight is Disabled

Email Template Count Different in UI When Compared to REST API Count

What Field Values Are Copied to Winning Records When Merging Multiple Records From REST API

When I rename a field in my CRM Custom Entity/Object why is the change not reflecting in the constraint of a filter/trigger?

Troubleshooting REST API Error: read ECONNRESET

Predictive Content Query Parameters

Troubleshooting SVG Upload and Display Issues in Marketo