Knowledgebase

Sort by:
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.  
View full article
Issue How to change the displayed name for your Marketo instance.     Solution Admin users for the Marketo instance can navigate to Admin > My Account > Edit Subscription Information and give the instance a friendly name of their choice. Once that is done, the name on the top left corner will change to what was input in Edit Subscription Information. This is a article attached image
View full article
Adobe Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions. Further details about your Adobe Success Plan can be found HERE. Note: If your Marketo Instance and Users have been migrated to Admin Console, refer to this Admin Console Overview page for managing the Adobe entitlements across your organization and to engage Marketo Support.   Marketo Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form to submit support cases to Marketo Support. The form provides Authorized Support contacts the ability to provide details on the support issue that allows Marketo Support to efficiently and effectively assign your case to the best suited available support engineer. We encourage you to leverage our Best Practices when submitting your case to Marketo Support.   Support Services – Regions, Hours, and Languages Authorized Support contacts can engage Marketo Support by calling one of our Adobe Enterprise Phone Numbers for your region. Live Telephone and Online Technical Support Priority 1 incidents: 24x7x365 via phone or online support case Priority 2-4 incidents: Support available during regional business hours via chat or online support case. Regional Business Hours Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents. If Adobe is contacted for support by someone other than the designated Named Support Contacts, Adobe may request that that the support case be resubmitted by a Named Support Contact. Languages Japanese language support is available during Japanese regional business hours, excluding holidays or Adobe days off. Japanese support is not available for Adobe Commerce. With the above exception, all Support will only be provided in English. Support Access Customer will grant Adobe Support access to applicable customer systems via remote support tools controlled by Adobe for the purpose of troubleshooting and support services. Regional Business Hours for Support Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents.   Americas Europe, Middle East & Africa Asia Pacific Japan 6 am – 5:30 pm 9 am – 5 pm 9 am – 5 pm 9 am – 5 pm  
View full article
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.
View full article
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.
View full article
By default exported reports are limited to 100 rows but it can be changed by navigating to 'User Settings' > “Number of Rows in Excel Export”   The maximum number allowed is 10,000 rows    
View full article
Issue When using the GET Activities API with a specific list Id in the parameter, the response will get all the specified activities from other assets as well. This is the endpoint for this article.     Solution Instead of using list Id (listId) as a parameter, change that to asset Ids (assetId) in the API call. The Asset ID (assetId) is the Id of the primary asset for an activity. Then, the response will narrow down the activities associated to the primary asset by looking up the Id during the call.
View full article
Issue Issue Description Velocity scripted tokens are not displaying the default value in the asset if the information required for the token is not in the database.     Solution Issue Resolution Email Script tokens are not designed to work with the {{my.token:default=Some Value}} syntax, which is for simple tokens. Rather, you must output the default value within the code (using #if/#else, $display.alt or any other conditions) then include just {{my.token}} in the email. Examples can be found here: https://developers.marketo.com/email-scripting/
View full article
Issue Issue Description API user making bulk extract calls is encountering the error "1029, Export daily quota exceeded" but under Admin>Web services> Request in the 7 days shows that you have not reached the "Daily Request limit".     Solution Issue Resolution The "Daily Request Limit" that can be found under Admin>Web Services>API call information is different from the limit that is in place for the bulk extract limit. The API limit is a on the number of calls that can be made, while the bulk extract limit is a limit on the amount of data that can be exported used based on the file size of the bulk extract job. If you notice this behavior, please reach out to your CSM for more information about increasing the Bulk Extract limit.    
View full article
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 Several types of fields in Marketo have requirements for the type of data that can be stored, as well as the limit to how much data can be contained in that field type. The Custom Field Type Glossary can tell you what fields are available, and this article will show you details on the type and maximum limits for those fields.    Field Types & Limits Boolean Can only be set to “true” or “false” (stored in the database as 1 or 0).   Currency Maximum value of 9223370000000000000.  Will be displayed with the currency set in your instance under Admin -> Location.   Date Must be formatted “MM/DD/YYYY”.   Datetime Must be formatted “MM/DD/YYYY HH:MM:SS”.   Email Must be a properly formatted email (user@example.com).   Float Can include decimals up to the hundredths place.  The value will round to the nearest hundredth (eg. 99.999 rounds to 100, 99.985 rounds to 99.99).  Maximum value of 10000000000.   Formula See this guide: Create and Use a Concatenated String (Formula) Field    Integer Values are limited to between -2147483647 to 2147483647.   Percent Must be a full number without decimals.  Maximum value of 9223370000000000000.   Phone Can have letters, numbers, or characters.  Maximum of 2,000 characters.   Score Maximum score of 9223372036854775807.  If the score is increased higher than that, the score will reset to -9223372036854775808.   String Can contain letters, numbers and special characters.  Limit of 255 total characters   Text Area  Can contain letters, numbers and special characters.   Limit of 65,535 bytes.   URL "http://"  will automatically be appended to the value if the value doesn't have that prefix or "https://" already.  Does not have to be formatted any further (Generic top-level domain not required).
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