Knowledgebase

Sort by:
As much as we would like to have all support cases solved with a few quick response from our support team, we know that there are some cases that are going to need to be escalated to our support management team.   If you have submitted a support case and you feel that the case was improperly handled or that the solution being offered does not meet the communicated Marketo support expectations, then we would welcome the opportunity to look deeper at your specific support engagement and work with you on delivering a better resolution.   You can email supportescalations@marketo.com to escalate your issues to our support management team.  Be sure to include your case number and the details of your escalation.   Once your support escalation case has been submitted a Marketo Support Manager will contact you within 24 business hours to address the issue.   Before you send an email to supportescalations@marketo.com you must have a current active support case submitted or a recent support case that has been closed or is pending.  Support Escalations are focused on the handling of current or recent cases.  Brand new technical support issues that are sent to Support Escalations will be re-routed to our general case flow.
View full article
  Marketo Champions are customers who have demonstrated outstanding leadership in the Marketo Community, are experts in Marketo products, are avid contributors in the social world, and are loyal advocates of the Marketo brand. Benefits and perks our Champions receive include:   Access: Meetings with our product and marketing teams to give exclusive feedback Previews: Given early previews to products, features, and releases when available Publicity: Exclusive speaking opportunities at our annual Marketo Summit and other events Networking: Special networking events with Marketo executives and fellow Champions and semi-annual conference calls Ownership: Ownership of content and exclusive activities at our annual Marketo Summit that showcase your expertise and thought leadership Credibility: Special Champion badge on Marketo Community profiles, and profiled on Marketo's corporate website Sweet Swag: Champion-exclusive swag To find out more information and apply, click here. To view a complete list of current Champions, click here. Join the Marketo Elite Today!  
View full article
Issue You receive a Web Services Error 612 on a REST API call. Solution The 612 error code denotes that there was an invalid Content Type in the REST API call. If you see this error, add a content type header specifying JSON format to your request. For example, try using "content type: application/json". Since this error is in the formatting of the REST API call that is being made to the Marketo instance, we recommend working with a developer to update the API call to resolve the error message. Here is a Link to StackOverflow that helps to discuss this kind of error message further: ( http://stackoverflow.com/questions/28181325/why-invalid-content-type ).      
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 Persons do not trigger Smart Campaigns as expected when using the REST API 'Push Leads to Marketo' endpoint.     Solution Issue Resolution Marketo utilizes a special trigger for persons pushed to Marketo using REST API. The 'Person is Pushed to Marketo' trigger will qualify persons upserted by the 'Push to Marketo' endpoint.    
View full article
Issue Does Marketo have an SLA for REST API? Solution No, Marketo does not have an SLA for REST API. Our REST API Responses time out after 30 seconds. Unless written within the subscription contract, there is not a commitment for Marketo to provide an SLA for REST API Responses. As mentioned in our API License document: http://developers.marketo.com/api-license/ in section 6 B: "B. No Support. Unless otherwise agreed to in writing, Marketo shall not be responsible for providing any support, maintenance, or other services (or level of service) to You or a user of the Software Application for the Marketo APIs."    
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
Using the Marketo SOAP API, you can check whether or not your website visitors have filled out a form and present them content accordingly. The following code below is unsupported and is intended to help you develop your own solution. In the resources section of the Marketo website, we use this method for our premium content. For leads who have already registered, their links go directly to the resource. Leads who haven't registered are given links to a landing page. In both cases, the link appears the same. Behind the scenes, a cookie is used to store whether or not this lead has registered: If the user has the premium registration cookie, the premium links are shown. If the user does not have that cookie, the lead's record is retrieved via the SOAP API. Based on the lead's record: If the lead has a valid email address, the premium content links are shown and the premium registration cookie is set. If not, the premium content links are not shown. Instead, they take leads to a landing page to fill out a form. First, you'll need to develop a SOAP API connection to Marketo. The attached ZIP file has a sample connection PHP file. You'll need to make the following changes in this file: ... $this->access_key = 'Your API Access Key Goes Here'; $this->secret_key = 'Your Secret API Key Goes Here'; // // The endpoint is in the "SOAP API Setup" page in the Marketo Admin section // ex. $soap_end_point = 'https://xx-1.marketo.com/soap/mktows/'; // $soap_end_point = 'Your SOAP API End Point URL Goes Here'; // // Errors are sent to this email address. Your web server // must be configured to send email for this to work correctly. // // ex. $this->error_email_address = 'example@example.com'; // $this->error_email_address = 'Put your debug email address here'; ... After creating your SOAP API connection, the next step is to implement the logic that determines which content to show if the user is logged in or not. The get_premium_url_status() function returns true if the lead has the premium cookie or if they've filled out a form. Otherwise, it returns false. You can use that result to determine what content the lead should see. The attached ZIP file has a PHP file that contains an example of this check.
View full article
Issue You have exported the fields under the Field Management section as mentioned in this document to view the API name of the Marketo fields  You see there are few fields missing and would like to know their API names. Solution Here's a list of the Marketo Standard fields that are available via API. If there are fields which are not available in the list export, it means they likely do not have an API name or not accessible through API calls.    
View full article
Note: Please ensure that you have access to an experienced Web developer. Marketo Technical Support is not set up to assist with troubleshooting code. The listOperation SOAP API call allows for the ability to interact with static lists (My Lists) in the Lead Database. The supported operations are adding a lead to list (ADDTOLIST), checking if a lead is a member of the list (ISMEMBEROFLIST), and removing a lead from a list (REMOVEFROMLIST) Note, there is no operation to create a new list (or delete) via the SOAP API. The list must be created beforehand in the Lead Database. In the examples, the list is named "Static List". Example 1 - Request: Adding multiple leads into the list <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "http://www.marketo.com/mktows/">     <soapenv:Header>         <mkt:AuthenticationHeader>          <mktowsUserId>[User Id]</mktowsUserId>          <requestSignature>[Signature]</requestSignature>          <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp>         </mkt:AuthenticationHeader>     </soapenv:Header>     <soapenv:Body>         <mkt:paramsListOperation>             <listOperation>ADDTOLIST</listOperation>             <listKey>                 <keyType>MKTOLISTNAME</keyType>                 <keyValue>Static List</keyValue>             </listKey>             <listMemberList>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>213</keyValue>                 </leadKey>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>215</keyValue>                 </leadKey>             </listMemberList>         </mkt:paramsListOperation>     </soapenv:Body> </soapenv:Envelope> Example 1 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.marketo.com/mktows/">    <SOAP-ENV:Body>       <ns1:successListOperation>          <result>             <success>true</success>             <statusList xsi:nil="true"/>          </result>       </ns1:successListOperation>    </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 2 - Request: Check to see if leads are a part of list. One lead (Lead ID #213) is and the other (Lead ID #70) is not  <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "http://www.marketo.com/mktows/">     <soapenv:Header>         <mkt:AuthenticationHeader>          <mktowsUserId>[User Id]</mktowsUserId>          <requestSignature>[Signature]</requestSignature>          <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp>         </mkt:AuthenticationHeader>     </soapenv:Header>     <soapenv:Body>         <mkt:paramsListOperation>             <listOperation>ISMEMBEROFLIST</listOperation>             <listKey>                 <keyType>MKTOLISTNAME</keyType>                 <keyValue>Static List</keyValue>             </listKey>             <listMemberList>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>213</keyValue>                 </leadKey>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>70</keyValue>                 </leadKey>             </listMemberList>         </mkt:paramsListOperation>     </soapenv:Body> </soapenv:Envelope> Example 2 - Response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.marketo.com/mktows/">    <SOAP-ENV:Body>       <ns1:successListOperation>          <result>             <success>false</success>             <statusList>                <leadStatus>                   <leadKey>                      <keyType>IDNUM</keyType>                      <keyValue>213</keyValue>                   </leadKey>                   <status>true</status>                </leadStatus>                <leadStatus>                   <leadKey>                      <keyType>IDNUM</keyType>                      <keyValue>70</keyValue>                   </leadKey>                   <status>false</status>                </leadStatus>             </statusList>          </result>       </ns1:successListOperation>    </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 3 - Request: Similar to Example 2, but all leads are valid  <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "http://www.marketo.com/mktows/">     <soapenv:Header>         <mkt:AuthenticationHeader>          <mktowsUserId>[User Id]</mktowsUserId>          <requestSignature>[Signature]</requestSignature>          <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp>         </mkt:AuthenticationHeader>     </soapenv:Header>     <soapenv:Body>         <mkt:paramsListOperation>             <listOperation>ISMEMBEROFLIST</listOperation>             <listKey>                 <keyType>MKTOLISTNAME</keyType>                 <keyValue>Static List</keyValue>             </listKey>             <listMemberList>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>213</keyValue>                 </leadKey>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>215</keyValue>                 </leadKey>             </listMemberList>         </mkt:paramsListOperation>     </soapenv:Body> </soapenv:Envelope> Example 3 - Response:  <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.marketo.com/mktows/">    <SOAP-ENV:Body>       <ns1:successListOperation>          <result>             <success>true</success>             <statusList xsi:nil="true"/>          </result>       </ns1:successListOperation>    </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 4 - Request: Remove leads from the list. One lead (Lead ID #213) is a member of the list, the other (Lead ID #70) is not  <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "http://www.marketo.com/mktows/">     <soapenv:Header>         <mkt:AuthenticationHeader>          <mktowsUserId>[User Id]</mktowsUserId>          <requestSignature>[Signature]</requestSignature>          <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp>         </mkt:AuthenticationHeader>     </soapenv:Header>     <soapenv:Body>         <mkt:paramsListOperation>             <listOperation>REMOVEFROMLIST</listOperation>             <listKey>                 <keyType>MKTOLISTNAME</keyType>                 <keyValue>Static List</keyValue>             </listKey>             <listMemberList>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>213</keyValue>                 </leadKey>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>70</keyValue>                 </leadKey>             </listMemberList>         </mkt:paramsListOperation>     </soapenv:Body> </soapenv:Envelope> Request 4 - Response:  <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.marketo.com/mktows/">    <SOAP-ENV:Body>       <ns1:successListOperation>          <result>             <success>false</success>             <statusList>                <leadStatus>                   <leadKey>                      <keyType>IDNUM</keyType>                      <keyValue>213</keyValue>                   </leadKey>                   <status>true</status>                </leadStatus>                <leadStatus>                   <leadKey>                      <keyType>IDNUM</keyType>                      <keyValue>70</keyValue>                   </leadKey>                   <status>false</status>                </leadStatus>             </statusList>          </result>       </ns1:successListOperation>    </SOAP-ENV:Body> </SOAP-ENV:Envelope> Example 5 - Request: Similar to Example 4, but all leads are valid  <soapenv:Envelope xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns:mkt = "http://www.marketo.com/mktows/">     <soapenv:Header>         <mkt:AuthenticationHeader>          <mktowsUserId>[User Id]</mktowsUserId>          <requestSignature>[Signature]</requestSignature>          <requestTimestamp>[yyyy-mm-ddThh:mm:ss-00:00]</requestTimestamp>         </mkt:AuthenticationHeader>     </soapenv:Header>     <soapenv:Body>         <mkt:paramsListOperation>             <listOperation>REMOVEFROMLIST</listOperation>             <listKey>                 <keyType>MKTOLISTNAME</keyType>                 <keyValue>Static List</keyValue>             </listKey>             <listMemberList>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>213</keyValue>                 </leadKey>                 <leadKey>                     <keyType>IDNUM</keyType>                     <keyValue>215</keyValue>                 </leadKey>             </listMemberList>         </mkt:paramsListOperation>     </soapenv:Body> </soapenv:Envelope> Example 5 - Response:  <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://www.marketo.com/mktows/">    <SOAP-ENV:Body>       <ns1:successListOperation>          <result>             <success>true</success>             <statusList xsi:nil="true"/>          </result>       </ns1:successListOperation>    </SOAP-ENV:Body> </SOAP-ENV:Envelope> Related Learning Resources Marketo SOAP API Reference
View full article
Issue Users for your Marketo instance are unable to log into the instance. Solution Check your landing page URLs and email links. If these are also unavailable, your Marketo instance may have been shut off. Marketo Support can confirm whether your instance has been deactivated, but are not able to reactivate it.  In this situation , please contact your Marketo Account Representative to discuss the status of the instance and regaining access.        
View full article
!!EASTER EGG!! The ball with the Marketo logo in the upper-left corner of the screen is your Superball.  Here's a quick trick to make it bounce like it did when you first got into your Marketo instance: Hold down Ctrl (Command for Macs) + Shift, then hit the 's' key. Happy bouncing!    
View full article
Issue You want to use a non-standard character as a value (or part of a value) in an API call (e.g. é), but when you put it in, the call does not work (either failing with an error or not posting the expected character).     Solution Encode the extended characters using ASCII URL encoding for UTF-8. There are sites that will perform this encoding for you, here is one: https://www.w3schools.com/tags/ref_urlencode.asp . For example: making this call, " https:// <munchkinid>.mktorest.com/rest/asset/v1/folder/{folder id}/tokens.json?access_token=<accesstoken>&name=TestName&value=Hello+%C3%A9marketo&type=text&folderType=Folder " will create a token called "TestName" with a value of "Hello émarketo"      
View full article
Attached to this article is a ASP.NET C# implementation of Marketo's SOAP API. This is just a sample, but it may be useful for providing a starting point for building your own SOAP API client. Learn more: Marketo SOAP API Note: You will need access to experienced developers This is not supported development by Marketo Support. Our support engineers are not able to provide assistance in building or troubleshooting SOAP API's.
View full article
Issue You are pulling the folder ID from the UI, but it is not working in your API calls.   Solution Retrieve the Folder ID from an API query call (GET Folder byName), and use the ID given from that call to make additional calls.    
View full article
Issue Issue Description You want to use the /rest/v1/leads/delete.json API endpoint to delete multiple lead from your instance in one call.     Solution Issue Resolution You can include up to 300 lead IDs in the body of the call and delete them at once. To delete more leads than that you will need to make multiple calls with batches of 300 leads or less.   Who This Solution Applies To Customers using the REST API
View full article
Issue Issue Description Occasionally Bulk Import API calls will return a blank response.   Solution Issue Resolution You can add the following header: 'Transfer-Encoding: chunked' to your API calls and it will fix this issue. Please note that adding this header on the client side will cause cURL to send data in chunks.  
View full article
Issue Description When a lead is created through an API call, the Reason and Source attributes say "Web Service API" with no further detail. Issue Resolution As described in the doc here, https://docs.marketo.com/display/DOCS/Understanding+System+Managed+Fields, "Source" and "Reason" fields are managed by Marketo: 1. Web Service API for Original Source Type means Person was discovered by a web service API. 2. For Registration Source Type, it states that Person was created via SOAP/REST API When a lead is created via API, no additional "Source" or "Reason" is provided to Marketo. A possible workaround is to create a custom field and populate it as needed through the API.
View full article
Issue Would a requested campaign via API show in activity log if filtered? Ex: You request a campaign, and the lead does not qualify due to a filter. Will the activity log show the request occurring?     Solution Yes, the request will show no matter if the lead runs through the flow or not. The request campaign action will be recorded, but the lead will not go through the flow steps if they do not meet the requested campaign's Smart List requirements.  
View full article
Summary Handling 606 rate limiting, 607 daily quota, and 615 concurrency errors. Issue An API user is receiving rate (606), quota (607), or concurrency (615) errors when connecting to the Marketo Engage REST API. The errors will be evident in the responses to the requests creating them and in admin notifications as a web services error notification.    Solution The Marketo Engage REST API is protected by 3 limitations on the number of requests made: daily quota, request rate, and the number of simultaneous/concurrent requests. The errors generated when on of these limits is exceeded are recoverable by waiting the appropriate amount of time before retrying the request. Daily Quota: Error Code 607 This error indicates that the number of requests made since 12:00AM CST has exceeded the daily quota. The daily quota varies and can be found in your Admin->Web Services menu.  Contact your account manager if you require increased daily quota. Rate Limit: Error Code 606 and Concurrency Limit: Error Code 615 Handling concurrency and rate limiting errors is similar. In each case, the request should be tried again after a waiting period. At most 10 requests can be processed by any Marketo Engage instance at a time. Error code 615 will be returned if there are already 10 open HTTP connections to the instance's REST API and an attempt is made to create an 11th connection. At most, 100 requests can be processed by any Marketo Engage instance in any rolling 20 second window of time. Error code 606 will be returned if there have already been 100 requests in the last 20 seconds. In both cases, an exponential backoff retry strategy will allow your application to eventually make a successful request. All popular web development languages have libraries available which implement exponential backoff: using an existing library is highly recommended. Unlike daily quota which an be increased through your account manager, rate and  concurrency limits cannot be changed. Further Reading For information on implementing your own exponential backoff algorithm, see Devopedia's article on Binary Exponential Backoff. For more best practices to apply when using the Marketo Engage REST API, see this page.
View full article