Knowledgebase

Sort by:
  Full Details of all Marketo Support Offerings:   Support Levels Offered Service Level Response Targets   Global Contact   https://support.marketo.com :            Online Support Portal for Case management and Knowledgebase search support@marketo.com :                     Email to Case Submission supportescalations@marketo.com :   Contact Support management regarding Support services marketocares@marketo.com :            Questions regarding Support or Community access   Regional Contact Information Americas: Hours: M-F, 6am to 6pm Pacific Toll Free US: +1 877 270 6586 Direct: +1 650 376 2303   Languages Supported: English, Spanish Observed Holidays: New Year's Day Independence Day Thanksgiving Day and the Day After Christmas Day New Year's Eve Europe, Middle East, & Africa: Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 242 3030 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holiday: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm AET ANZ: +61 2 8310 7646   Languages Supported: English Observed Holiday: New Year's Day                             ANZAC Day Christmas Day                             Good Friday Easter Monday                             Boxing Day Japan: Hours: M-F, 9am to 6pm JST JP: +81 3 6478 6080   Languages Supported: Japanese Observed Holiday: New Year's Holiday                      Marine Day Coming of Age Day                      Respect for Senior Citizens Day National Founding Day                National Holiday Spring Equinox Day                     Autumnal Equinox Day Day of Showa                              Sports Day Constitution Memorial Day          Culture Day Green Day                                   Labor Thanksgiving Day Children's Day                             Emperor's Birthday Substitute Public Holiday             Year End After-hours Support for Production Down Issues: Online: Enter a Support Portal Case with Priority=P1 Phone: Call Support Line and follow the P1 prompts   Initial Response SLT We ask that you use the following priority definitions when setting your case priority: Priority Description P1 Mission Critical: Core Business function down or potential loss of mission critical data P2 Urgent: Major feature or workflow is not functioning, mission critical workflow and majority of user community is not blocked P3 Important: Normal usability or task completion is impacted but functional or workaround is available P4 Minor: Minor issue requiring a correction, normal workflow is not impacted  
View full article
Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions.   Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form submission to submit support cases to Marketo Support.  The form gives 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.   Email to Case Submission Authorized Support Contacts can email their cases to: support@marketo.com Reminder: Cases submitted by email are all submitted with a P3 Priority   Regional Phone Contact Information Marketo does feature the tried and true means of contact support, by the phone.  Authorized Support contacts with any support entitlement of Business level or higher can contact Marketo Support by calling one of the regional phone numbers listed below.   Region Contact Details Observed Holidays North America Hours: M-F, 6am to 6pm Pacific Toll Free US: +1.877.270.6586 Direct: +1.650.376.2303 Languages Supported: English, Spanish New Year's Eve and Day Independence Day Thanksgiving Day and the Day After Christmas Eve and Day Europe, Middle East, Africa Hours: M-F, 8am to 5pm GMT Europe: +353 (0)1 242 3030 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese New Year's Eve and Day Easter Monday Christmas Eve and Day St. Stephen's Day Asia Pacific Hours: M-F, 9am to 6pm AUS EST ANZ: +61 2 8310 7646 Language Supported: English New Year's Day Good Friday Easter (following Monday) ANZAC Day Christmas Day Boxing Day Japan Hours: M-F, 9am to 6pm JST JPN: +81 3 6478 6080 Language Supported: Japanese New Year's Day Coming of Age Day National Foundation Day Emperor's Birthday Spring Equinox Showa Day Constitution Memorial Day Greenery Day Children's Day Marine Day Health and Sports Day Respect for the Aged day Fall Equinox Labor Thanksgiving Day
View full article
Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate  
View full article
Upon signing a contract with Marketo you are provisioned a Marketo instance and a Support Service. There are four different types of Support Services which are available to meet different customer support needs: Online (Legacy) Business  or PREMIER SUPPORT BUSINESS (Legacy) Premier or PREMIER SUPPORT ENTERPRISE (Legacy) Elite or PREMIER SUPPORT ELITE Each Support Service has a different Service Level Target (SLT). An SLT is the amount of time Marketo Support targets to make first contact with you after a support case has been submitted. SLTs differ for each Support Service and priority level. Priority levels range from Priority P1 to Priority P4. Here are the SLTs and priority levels for each Support Service:   Priority Online (Legacy) Business PREMIER SUPPORT BUSINESS (Legacy) Premier PREMIER SUPPORT ENTERPRISE (Legacy) Elite PREMIER SUPPORT ELITE P1 1 hour 1 hour 1 hour 30 minutes 30 minutes 30 minutes 15 minutes P2 4 hours 3 hours 2 hours 2 hours 1 hour 2 hours 30 minutes P3 6 hours 5 hours 4 hours 4 hours 2 hours 2 hours 1 hour P4 3 days 1 day 1 day 1 day 1 day 1 day 1 day   Here are the descriptions for each priority level: Priority Description P1 Mission Critical:  Core business function down or potential loss of mission critical data P2 Urgent:  Major feature or workflow is not functioning. Mission critical workflow and majority of user community is not blocked P3 Important:  Normal usability or task completion is impacted but functional, or workaround is available P4 Minor:  Minor issue requiring a correction. Normal workflow is not impacted   Find more information About Support here!
View full article
Note: Please ensure that you have access to an experienced JavaScript developer, because Marketo Technical Support is not set up to assist with troubleshooting custom JavaScript. If you're trying to use the Munchkin API but not having any success, try these tips:   Include the Munchkin JS   Make sure you include the required lines of Munchkin Javascript on pages with API calls.  You can find the javascript in the Admin section under Munchkin Setup . Check "Enable Munchkin API"   In the Munchkin Setup page, check the box that says Enable Munchkin API , put in a private key (which can be any text), and click Save .   Look for JavaScript errors   Use Firebug on Firefox or enable IE JavaScript debugging to check for JavaScript errors.  Any JavaScript errors that occur -- anywhere on the page -- could prevent Munchkin from working.   Escape special characters   Check and make sure that any quotation marks or other characters that require escaping are properly escaped.  See this document for more.   Call mktoMunchkin first   In your Javascript, you must call mktoMunchkin() before you use any other Munchkin API calls.   Try a proxy program   Use a web traffic capturing program like Firebug (for Firefox) or Fiddler.  The return code from the API call may have useful information to help you diagnose the issue.     Click Link or visit WebPage isn't working   Check to make sure you have only a path listed in the url parameter -- no ", no domain, and no URL parameters.   Associate Lead isn't working   This could be caused by a few issues:   Include an email address   Email address is required when using the associate Lead call.  If you don't use this, the call will always fail.   Check the labels   Marketo expects the labels (like "Email" and "FirstName") in a specific format.  You can get these labels in the Field Management page of the Admin section.  When you get there, click the Export Fields button.  The spreadsheet will have the API names for your fields.   Check the hash value   The hash value is the SHA1 hash (non-HMAC version) of your API Private Key (not your Munchkin ID) concatenated with the lead's email address, as in your-secret-keyemail@address.com .  The hash value must be lowercase.
View full article
  What is the Email API? What is the Email API used for? What is Email 2.0? Does the Email API Work on Email 2.0 Assets? Will the Email API Break when Enabling Email Experience 2.0? How Are 1.0 Assets Upgraded to 2.0 Assets? What to Do When an Email Was Accidentally Converted to Email 2.0 format?     What is the Email API? API stands for Application Programming Interface and the Email API allows an automated process to create and edit emails in Marketo. There are also other API calls that involve emails, such as Approve Snippet (assuming the Snippet is used in an Email) and Clone Program (assuming the Program contains Emails). There are also API calls to create and update Email Templates. Essentially, the API can do many things that you can also do through the Marketo user interface, but then in an automated fashion.     What is the Email API used for? There are many scenarios: an external system could create Emails in Marketo using data that lives outside of Marketo. A translation service provider could clone a master Email, translate it to many languages, then save them back into Marketo as localized Emails. A reporting system could extract Emails from Marketo to use in reports that are generated outside of Marketo. An external system could Clone a Program that contains Emails, then populate the Program Tokens and schedule the Email to be sent out at a specific time. There could be an external email template creation system that creates new Email templates in Marketo through the API.     What is Email 2.0? “Email Experience 2.0” is the new Marketo product feature with the enhanced email editor, documented here: https://docs.marketo.com/display/public/DOCS/Email+Editor+v2.0+Overview. It can be switched on in Admin > Email > Edit Email Editor Settings. All Emails and Email Templates also have a version number, either 1.0 (the old version) or 2.0 (the new version). If we refer to “Email 2.0 asset” we mean an email or email template in the new upgraded 2.0 format.     Does the Email API Work on Email 2.0 Assets? Yes.     Will the Email API Break when Enabling Email Experience 2.0? No. Enabling Email 2.0 will not automatically upgrade Emails or Email Templates to the new 2.0 format. The Email API can still create new Emails and Email Templates in the 1.0 format.  However – after enabling Email 2.0 – any Email or Email Template that is created or edited and approved through the Marketo User Interface will automatically be upgraded to the 2.0 format.     How Are 1.0 Assets Upgraded to 2.0 Assets? If you edit an “Approved" or “Approved with Draft” 1.0 Email with Email 2.0 enabled, the draft is converted to the 2.0 format. You can still discard the draft to go back to the approved 1.0 format. Once you approve the email and it becomes 2.0, the Email cannot be converted back to 1.0. If you edit a “Draft” 1.0 Email (never been approved), this will automatically be converted to 2.0 with no option to revert back to the 1.0 format. The same applies to Email Templates.     What to Do When an Email Was Accidentally Converted to Email 2.0 format? If an Email or Email Template was accidentally converted to the 2.0 format, you’d have to copy the asset contents to a text editor, disable Email 2.0, then create a new 1.0 asset using the content that you copied.
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   Safari Safari for Mac: Manage cookies and website data using Safari   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 want to view your current usage of the Marketo API.     Solution Current usage of both REST and SOAP API can be found by following these steps: Go to Admin > Web Services Look at the API Call Information section. In the API Call Information section, you will see a line that says "Requests in the Last 7 Days:". The number next to that is the number of calls made to this instance in that time frame. The number is also a hyper-link that will allow you to break this down by API user. Each individual REST user will be its own row, while the SOAP requests will be in one line, using the given SOAP User ID within the SOAP API section just below.
View full article
Issue: I am looking for the ID to one of my campaigns for a SOAP API project I am working on. Solution: The ID can be found in the URL of the campaign. 1.1 Log into Marketo, under Marketing Activities , find and select the campaign in question.     1.2 The URL to the campaign will look something like:   The Campaign ID is between "SC" and "A", in the above example it's "1054".    
View full article
Issue Description REST API call, Get Lead Activities , is returning 603 error   Issue Resolution Error 603 refers to 'access denied' where authentication is successful but the user doesn’t have sufficient permission to call this API. Additional permissions may need to be assigned to the user role. http://developers.marketo.com/rest-api/error-codes/   Go to Admin > Users and Roles Select API User and identify what role it is assigned to (e.g. API role) Go to Roles and check the permissions assigned to the API role Check to see if the API role does not have 'Read-Only Activity' or 'Read-Write Activity' permission In order to make a Get Lead Activities REST API call with the API user, the API role of the user must be modified to have permissions to  'Read-Only Activity' or 'Read-Write Activity'. If you use Workspaces and Partitions, make sure the API User has the necessary access. Is this article helpful ? YesNo
View full article
Issue You make a REST API call and receive an error code 1006 "Field '****' not found." Solution This error lets you know you are referencing a field by the wrong API name. The ****  will let you know which field you are referencing incorrectly. To resolve this Export a list of API names for the fields in your instance. Locate the desired field and its API name in the list Update your REST API call with the correct API field name   Who This Solution Applies To Customers using REST API    
View full article
Issue Description You need to revert a data value change for a field on multiple leads. Issue Resolution There is no way through the UI to "undo" a data value change (unless it was a boolean field, in which case there are only two possible values.) You can certainly use a Smart List to identify whose values have changed, but there no way to go back to the old value (unless it's stored elsewhere in another field or through another data store, along with the API). However, you can use the API to extract the data value change activity from the activity log, which would include the old and new values, extract the original values, then use the API to rewrite the old values back to the lead record. http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadChangesU… Is this article helpful ? YesNo
View full article
  Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 25 months, or 37 if you have purchased the premium data retention option. The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.         Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List     4. Add these two Flow Steps to the Campaign Flow: Flow Step 1 : “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2 : “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing       This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing.       Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.      
View full article
Issue Issue Description A REST API call on the Company API or Opportunity API fails with the error  "1018: CRM Enabled -- The action could not be carried out, because the instance has a native CRM integration enabled."     Solution Issue Resolution Per the documentation on developers.marketo.com, the Company and Opportunity APIs are only available on instances that are not currently synced with a CRM such as Salesforce or MS Dynamics.  If your instance is synced to a CRM, you will need to update Company and Opportunity information through the CRM rather than the API.    Documentation for these APIs can be found here: http://developers.marketo.com/rest-api/lead-database/opportunities/ http://developers.marketo.com/rest-api/lead-database/companies/   Who This Solution Applies To Marketo instances with a CRM sync
View full article
Issue You are experiencing slow processing of campaigns, smart lists, and reports.     Solution There are three key components that can slow down an instance: Number of trigger campaigns : Trigger campaigns are always on, always listening.  If there are 50 campaigns triggering at the same time, all the 50 triggers will be in queue, slowing down your processing and routing inside Marketo. Solution: Reduce the number of Triggers. Convert some of the triggers to batches: Batches also run all the flow steps for every lead at once, instead of serially, which reduces total processing time.   Complexity of smart lists : The more complex a smart list, the harder it is for the system to figure it out, which increases backend processing and even creates campaign failures from timeouts. Solution: Reduce the number of nested smart lists called in a smart list. Whenever you ask Marketo to call another Smart List, it has to wait until all of the other smart lists finish, before putting together the final counts. Instead of Marketo looking for the list and running it, just put the filters in the trigger itself.   Volume of Leads: With regular cleaning and good systems design, it is fairly easy to keep your system running fast. Reduce the number of leads that can flow through with filters. Clean up the inactive leads at regular intervals.    
View full article
  Marketo Support's Mission is:   "To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success."   Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any questions or concerns. TSEs are responsible for troubleshoot issues within your Marketo instance. Common areas within a Marketo instances which TSEs will assist with are:   My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community   Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code:    Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API   Our technical support engineers are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.   Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.   Response Time   Our Technical Support Engineers are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services.  We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.
View full article
Issue Description The Get Lead Activities REST API is not returning any activities even though t he lead referenced definitely has multiple activities of the type being called.   REQUEST: https://[munchkinID].mktorest.com/rest/v1/activities.json?access_token=x&leadIds=123&nextPageToken=ABC&activityTypeIds=46   RESPONSE: { "requestId": "xyz123", "success": true, "nextPageToken": "ABC", "moreResult": true }   Issue Resolution The Get Lead Activity REST API are reliant on timestamps for their nextPageToken. Each Get Lead Activity call will go through 300 activities of ALL types from the timestamp placed on the nextPageToken. This is supported by the article http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities/getLeadActivitiesUsingGET   "By default, the endpoints mentioned in this section will return 300 activity items at a time.  If the moreResult attribute is true, this means that more results are available. Continue to call the endpoint until the moreResult attribute returns false, which means that there are no more results available."   Based on that, the reason why the API call does not return any activities is that it does not find any activities of type 46 in the 300 activities it checks from the timestamp placed on the nextPageToken   So when making a Get Lead Activity call for a specific activity type, ensure that nextPageToken is as close as to the timestamp of the specific activities Is this article helpful ? YesNo
View full article
Issue What to do if you've exceeded your daily limit of API calls.     Solution If you go Admin > Web Services in Marketo, you will see a section called API Call Information. The number next to "Enforced Daily Request Limit" lets you know how many API calls you can make daily. If you need this number to be increased, the best option is to contact your Custom Success Manager; they can help you start the process of increasing your limit.    
View full article
Issue You changed the Label name of the field and want the API name to match.     Solution I Outside applications rely on API names and changes to these names can make your Marketo instance unstable. For this reason, it is not possible to change API names of fields. Instead, we suggest creating new field with the correct API name. 
View full article
Included in this article Note: This post will be updated to reflect changes made to activity records returned by the API due to migration to new infrastructure. Overview With the rollout of Marketo’s next-generation Activity Service beginning in May 2017, we will be unable to enforce the uniqueness or presence of the integer “id” field in activities, data value changes, or lead deletion records returned by Marketo’s APIs.  This change will begin rolling out to all subscriptions over the remaining first half of 2017. To avoid service disruptions for integrations which retrieve activity records, the id field should be treated as optional.  Cutover of this change will begin to affect subscriptions with the September (Q3) 2017 release. This change will affect the following endpoints: REST API Get Lead Activities​ Get Lead Changes​ Get Deleted Leads​ Add Custom Activities​ SOAP API getLeadActivity​ getLeadChanges​ The affected SOAP types are ActivityRecord and LeadChangeRecord. Examples The following examples show record types which will be affected.  In both examples, the effected field is called “id.” Example REST Field: id ​ Example SOAP Field: id ​ FAQs Do I need to update my WSDL version if I'm using SOAP integration? Yes. The marketoGUID field will only be returned in activities when using the WSDL version 3.1 or later.  The new URI will follow this pattern: https:// {munchkinId}.mktoapi.com/soap/mktows/3_1  It may also be obtained through the Admin->Web Services menu in your subscription When can I expect to see each change? Beginning with our Q1 Minor Release on April 7th, activity records retrieved via Marketo’s SOAP or REST APIs will include a new field called “marketoGUID”.  The value of this field will match the value of the “id” field, but will be a string type field.  Some time after the Q2 release beginning May 17th 2017, the “id” field will stop being returned as part of these records, and the value of marketoGUID will become a 128-bit string. What do I need to do? If you are responsible for code that deals with Marketo activities, you should determine whether your code relies on the presence or uniqueness of “id” field for Marketo activities, and then remove that requirement.  In an upcoming release, an additional string field called “marketoGUID” will be added.  “marketoGUID” should be considered the unique ID for retrieved activities when it becomes available.  If you are not, you should consult with your team and relay this message to the appropriate stakeholders. Who will this change affect? This change should only affect client and partner integrations which retrieve activity records from Marketo, and only if the integrations rely on either the presence and/or type of the “id” field in the response, or rely on the uniqueness of the field.  After the rollout of Orion AS, and the disabling of activity writes to MySQL, the “id” field will no longer be available and will be supplanted by a unique string id field. Check out our documentation on the Marketo Developers Site here: https://developers.marketo.com/blog/important-change-activity-records-marketo-apis/
View full article