Knowledgebase

Sort by:
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. 
View full article
Issue A lead skips the send email flow step, but processes through the other flow steps. In the results tab and in the lead activity log there is no mention of the email step.   Example:     Solution If your lead record is blocked from receiving emails, Marketo will not send an email to that lead. If an email is not sent, there will not be a record in the activity log for the lead record or in the results tab of the smart campaign, but the lead will still go through the other steps as normal.  
View full article
Issue Lead was created but does not appear in the expected Workspace in the Lead Database.   Solution Check if there are any assignment rules that the lead may have qualified for a lead partition associated to another Workspace (e.g. Workspace B) https://docs.marketo.com/display/public/DOCS/Assigning+Person+Partitions+with+Assignment+Rules Check the lead's activity log to see if the lead's partition was changed after it was created to another partition associated to another Workspace (i.e. single flow action or via a smart campaign)  
View full article
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.
View full article
Issue Issue Description "${button-link}" appears on the Email Link Performance report in place of the URL the buttons point to.     Solution Issue Resolution To stop this "${button-link}" from appearing on the reports, edit the text version of the emails to replace the "${button-link}" with the URL the button points to. This occurs because the text version of the email didn't get edited to provide a valid button link. The "${button-link}" value is part of HTML templates and if the setting 'Copy HTML to Text version of email' is checked then those values get copied across. From there, if the text version doesn't get edited or reviewed after that copy over happens, tracked links for "http://${button-link}?mkt_tok=..." will be sent out for those leads that get the text version of the email in place of the URL the button points to. The next question after hearing this solution is often, "If this is just for the text version, who is reading the text version of emails?", and the answer is that it's probably automated link scanners or security software visiting the link and triggering the click to show on reports. 
View full article
Issue You see a large amounts of edits being made by "Unknown" user showing up within the Audit Trail. Solution If you have recently edited a field in Salesforce that utilizes a pick-list field type, the updates to the field will cause updates to propagate to any pages which use a form that uses that field.    
View full article
Summary Some users encounter problems with their Marketo domain not handling URL parameters correctly and resolving URLs. Issue When using URL parameters, some users experience issues where their Marketo domain does not correctly handle and resolve URLs. Cause: The issues can arise due to errors in how the URL parameters are structured, syntax errors, or difficulties in the domain's ability to handle parameters. One common problem is placing the anchor (represented by "#") incorrectly in the URL string, especially before the parameters.     Solution URL parameters are extra pieces of information added to a URL to provide specific data or instructions. E.g., Example Domain?parameter1=value1&parameter2=value2 However, incorrect handling of these parameters by the domain may cause issues in resolving the URL, resulting in broken links or incorrect behavior in your Marketo campaigns. Therefore, it is crucial to ensure that URL parameters are correctly managed to avoid any problems. Below are some recommended guidelines to follow while using URL parameters. Proper use of "?" in URL parameters: Start your URL with "?" if it contains parameters. This correctly initiates the parameters and allows the URL to resolve correctly. Example: www.example.com?parameter=value#anchor   Verify your domain's ability to resolve parameters: It's possible that certain websites may not be set up to accept or process parameters present in URLs automatically. If you're facing such an issue, it's important to inspect your website's domain settings. This can be done by exploring the configuration options offered by your content management system (CMS) or hosting provider. In case your domain isn't equipped to handle parameters, you may need to reach out to your domain provider for further assistance.   Place the anchor correctly: The anchor is typically included at the end of a URL to direct the user to a specific section of a webpage. If you are using parameters in your URL, the anchor must always be placed after the parameters.  Example: Incorrect: www.example.com#anchor?parameter=value Correct: www.example.com?parameter=value#anchor Some examples of different URL constructions. Both of these are valid, correctly constructed URLs: www.example.com?parameter1=value1&parameter2=value2 www.example.com?parameter1=value1#anchor In the examples above, the "?" symbol is used to start the parameters, and the "&" symbol is used to separate multiple parameters. The anchor is placed at the end, after the parameters.  
View full article
Issue You have integrated Marketo and Facebook Lead Ads in Marketo Admin > Launchpoint, and your test form-fills are not appearing in the Marketo Lead Database. Solution Occasionally the integration between Marketo and Facebook needs to be re-authorized. This is one of the primary troubleshooting steps we start with in these situations. The instructions for re-authorizing are as follows: Navigate to Marketo Admin > Launchpoint, and take note of the Facebook User that is used in the Lanchpoint integration, Log into the Facebook Business Account, and navigate to the settings where the Admins are added/removed Remove the User, and save changes Re-add the User back to the Business Account as an Admin, save changes Navigate back to Marketo Admin > Launchpoint, and edit the Facebook Lead Ads integration, Proceed with 'Next' to view the Facebook Account, and click 'Re-Authorize' The final step after this would be to attempt another form-fill on a Facebook form to see if the activities are appearing in Marketo.
View full article
When a customer triggers a blacklisting on Marketo's shared IP range that customer is moved to a set of IPs we call the quarantined IP range.  We do this to protect the health of our shared network and ensure the best deliverability possible for all of our customers on that network.   If you have received a Blacklist Notification from Marketo reporting that you have triggered a blacklisting your Marketo account is now in the quarantined IP range.   While you are in the quarantined range it is possible that you may experience a slight decrease in your deliverability rates. The reason for this is that you are now sending from a range made up of senders that have also caused other blacklist issues. All customers have received a notice of the listing and are in the process of repairing their database.   There are two ways to be removed from the quarantined IP range: Follow the steps outlined in our Blacklist Remediation article.  Be sure to fill out the form referenced in the email alert to indicate that you have taken steps to mitigate the issue. Demonstrate clean sending behavior for 3 months. We remove senders from the quarantined IP range if they have not triggered any new listings in 3 months.   To ensure your best deliverability rates blacklist issues should be addressed right away to prevent further damage to your sending reputation.   Furthermore, if no action is taken to improve list hygiene the issue will likely recur. Marketo's Privacy Team strongly recommend following the Blacklist Remediation steps.   Additional Resources: Blacklist Deep Dive  
View full article
Issue Emails with valid email address get soft bounced with this error:  Local address contains control or whitespace. Solution This error means that the email has a space somewhere in the the From email address or there was a comma or extra character in the From line.  If you do not see a space inside the email address, check the end of the address to see if a space somehow got added at the end. The email send did not occur due to the error with the address. The emails will need to be resent once after the associated address is corrected with white spaces or extra characters. Also, there is the possibility that email address "text" contains Paragraph marks or hidden formatting symbols (https://www.computerhope.com/jargon/f/formmark.htm) and instance users will required to have it reviewed and changed.        
View full article
An email being filtered to a quarantine or bulk mail folder happens after the recipient mail server has accepted message.  Once an email has been accepted by a mail server, it is impossible to tell where it went or what happened to it.  Note that this is true of any mail sent by any system on the Internet.   Every mail server has configurable filters that determine how received mail will be handled.  The mail server administrator should be able to adjust those filters to ensure delivery of emails based on their business standards, or there may even be end-user-configurable controls that can accomplish the same thing.   If test mailings you are sending to yourself or your colleagues are being filtered to a quarantine or bulk mail folder, you should consider asking your email administrator to whitelist Marketo’s IP ranges.  They can be found here.   You can also improve your deliverability in general by setting up SPF and DKIM records, and branding your tracking links.
View full article
Issue Authorized support admin unable to find a contact to add as authorized support contact.   Solution The contact will need to have logged in to the community (nation.marketo.com) at least once for their profile to be created and recognized in the system. "In order to appear on the list of available contacts, the user must have clicked Community (while logged into Marketo) at least once." https://docs.marketo.com/display/public/DOCS/Manage+Authorized+Contacts+in+the+Community Once the contact has logged in to the community, the authorized support admin should be able to see the contact to be added as an authorized support contact.  
View full article
Abuse Report An abuse report is when an email recipient forwards a complaint directly to abuse@marketo.com.  Marketo’s Privacy and Compliance Team processes all complaints to these addresses and will unsubscribe the complainer when possible.   Feedback Loop Complaint A feedback loop complaint is when an ISP forwards the complaints that originate from their users.  For example, when someone clicks the SPAM or JUNK button in their email client. ISPs that offer FBLs expect that subscribers like Marketo will mark the complainer as unsubscribed in the original database.  Marketo does process FBL complaints and marks the email address as unsubscribed.   Additional Information: Feedback Loops (FBL) Abuse Report Deep Dive Finding Leads that are Auto Unsubscribed for Email Spam Complaints / Feedback Loop (FBL)    
View full article
From the Marketo Email Use Policy: "...You may not send any Unsolicited Email by use or means of the Marketo Service. "Unsolicited Email" is defined as email sent to persons other than: persons with whom you have an existing business relationship, OR (ii) persons who have consented to the receipt of such email, including publishing or providing their email address in a manner from which consent to receive email of the type transmitted may be reasonably implied." The full text of the policy is here: https://documents.marketo.com/legal/use-policy/ An abuse report is a report that an individual sends to abuse@marketo.com alleging that a Marketo customer sent unsolicited email. There are a number of reasons why someone might report abuse. Here are a few common reasons people report abuse to us: The person forgot they opted-in to the mailing The person received genuinely unsolicited email The person opted in, but the branding in the email was different than the branding on the opt in form so it was not clear the email they received was connected to their opt-in experience Someone signed up for your list with the wrong address, and the person who actually received your email felt it was abusive   For additional reference - Abuse Report Deep Dive  
View full article
Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.     Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help   FireFox How to clear the Firefox cache | Firefox Help   Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer   Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy    
View full article
Issue You've been using Marketo for a while and have started noticing that Smart Lists take longer to process than before. There are multiple filters in your Smart List ranging from really specific attributes about a person to really broad geographical information. Solution The best performance will come when you order the smart list filters from most restrictive to least restrictive. Since your entire database is checked against the first filter, if we can narrow down the number of leads which move on to the next, there are fewer and fewer leads who qualify for each of the subsequent filters. Many times, the processing difference will be minimal. However, as your database grows, the penalty on efficiency can grow over time. If you haven't checked it out already, take a peek over at our product documentation for smart list best practices: https://docs.marketo.com/display/public/DOCS/Best+Practices+for+Smart+Lists    
View full article
Issue Activity History in Saleforce shows this message: [Email details are being uploaded from Marketo...please check back later] when emails are sent out from the Marketo Outlook Plugin.     Solution This message is created because of insufficient privileges for the Marketo sync user inside of SFDC. There is a permission for “Edit HTML Templates” that needs to be enabled for the sync user in order to prevent this problem from occurring. Background: When you send an email using the Marketo Outlook plugin, it is sent through the user's Exchange server rather than Marketo's email servers. Many users have an email signature that is automatically added to the email. This adds additional HTML to the email, which does not match the template already in Salesforce Sales Insight. Normally, Marketo would create a new template which Salesforce could then display in a link in the Activity History. However, in this case, the Marketo sync user does not have the necessary permissions, so this error results. To fix this, enable the "Edit HTML Templates" permissions to your Marketo Sync User.   Who This Solution Applies To Customer who are using Sales Insight for Salesforce and Outlook    
View full article
Issue Activity History in Saleforce shows this message: [Email details are being uploaded from Marketo...please check back later] when emails are sent out from the Marketo Outlook Plugin.     Solution This message is created because of insufficient privileges for the Marketo sync user inside of SFDC. There is a permission for “Edit HTML Templates” that needs to be enabled for the sync user in order to prevent this problem from occurring. Background: When you send an email using the Marketo Outlook plugin, it is sent through the user's Exchange server rather than Marketo's email servers. Many users have an email signature that is automatically added to the email. This adds additional HTML to the email, which does not match the template already in Salesforce Sales Insight. Normally, Marketo would create a new template which Salesforce could then display in a link in the Activity History. However, in this case, the Marketo sync user does not have the necessary permissions, so this error results. To fix this, enable the "Edit HTML Templates" permissions to your Marketo Sync User.   Who This Solution Applies To Customer who are using Sales Insight for Salesforce and Outlook    
View full article
There are thousands of blacklists out there and all of them operate a little differently and all have varying levels of reputation.  There are only a dozen blacklists that really can impact delivery.   The blacklist that requires the most work from you when you request delisting is Spamhaus. Spamhaus is a trustworthy blacklist and if you are listed at Spamhaus you have made a mistake that will need to be directly addressed before the listing can be removed.   SpamCop is considered a tier one blacklist for B2B marketers but a tier 2 for B2B marketers.  Marketo responds to all SpamCop listings; researching to identify the source so we can work with the customer to educate on best practices and prevent future listings.    Some blacklists require that you pay a fee to be delisted. These blacklists are not favored in the email community because they use this tactic. For the most part, Marketo advises our customers not to mind alerts of being listed on a pay-to-delist blacklist.  These blacklists tend to have minimal impact to your deliverability.   For the most part blacklists are dynamic and resolve themselves in around 24 hours if the issue resolves. If the problematic sending continues, of course, the blacklist will continue to keep you listed until the problematic sending ends.   If you are blacklisted, your main concern at that point should be making sure it doesn't happen again. For steps on how to identify the problematic data source and improve your list hygiene in an effort to avoid blacklist issues, see our blacklist remediation article.
View full article
Issue An Event Program in Marketo connected with ReadyTalk has some members with the status of "Registration Error" and a Status Reason of "Error registering with webinar provider. exception='Ready Talk API call error: ERROR -> HTTP Code ='403". The LaunchPoint connection in the Admin area may also show this error.   Solution This error is an API call that Marketo is getting back from ReadyTalk, and will apply to the individual record that encounters the error but doesn't impact subsequent records that are attempted to be synced. Additionally the LaunchPoint page displays the status of last API call and, if it failed, it displays that information there, but the error will go away when subsequent registrations are successful. This error can be caused by any of the following: Meeting is in a closed state - this can occur when either people try to register after the event is complete, or the date and time of the meeting is changed in ReadyTalk without using the "Refresh from Webinar Provider" feature in Marketo Meeting is cancelled. First name, last name, or email address is missing on the registration form. The format of a registrants email is invalid. (This usually occurs when a registrant enters something like .con instead of .com) The meeting title length is invalid, it must be between 1 and 300 characters. First name field exceeds 125 characters. Last name field exceeds 125 characters. The answer provided in a registration field exceeds 255 characters (i.e. Title, Company, Address, etc). If people are registering after the event is complete, one possible recommendation would be to have the registration landing page redirect to another landing page after the event has either initiated or completed, which provides people the opportunity to register for subsequent events. This way people that attempt to register for the event after it has concluded will not be able to do so, but they will be provided the option to register for future events. This will prevent people from trying to register for an event that has ended and closed, preventing future 403 errors. This doc walks through how you can do this: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/redirect-a-marketo-landing-page-to-another-page.html?lang=en   Who This Solution Applies To ReadyTalk integration users
View full article