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 511 9556 UK: 0800 151 3030   Languages Supported: English, French, German, Portuguese Observed Holidays: New Year's Day Easter Monday Christmas Day St. Stephen's Day Australia Hours: M-F, 9am to 6pm AET ANZ: +61 2 8031 8188   Languages Supported: English Observed Holidays: New Year's Day                            ANZAC Day Christmas Day                             Good Friday Easter Monday                             Boxing Day Japan: Hours: M-F, 9am to 6pm JST JP: +81.03.4233.9014   Languages Supported: Japanese Observed Holidays: 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 Critical Business Impact:  ​ Customer's production business functions are down  or have significant data loss or service degradation  and immediate attention is required to restore  functionality and usability. P2 Major Business Impact : ​ Customer's business functions  have major service degradation or potential data  loss, or a major feature is impacted. P3 Minimal Business Impact :  ​ Customer's business functions  have minor service degradation but  there exists a solution/workaround allowing  business functions to continue normally.   P4 No business impact : ​ General question regarding current product  functionality or an enhancement request.
View full article
Congratulations on being the Support Admin for your company.  It's a very important role for your organization and with the new Marketing Nation, the support admin role is expanding even more.  Let's go over some of key things you can do as the Support Admin.   You can submit support cases to Marketo Support This is one of your key abilities.  Submit cases on behalf of your company to our Marketo Support Team for assistance.   Manage your list of authorized contacts You have the ability to add and remove contacts from your list of authorized support contacts.  This becomes important if people leave your company or if teams switch out your main Marketo users.  If someone needs the ability to contact Marketo Support, you're the one to make that happen for them.   Invite people to your account space (NEW) That's right,. You own the guest list to your Account space.  You get to invite people from your company to this space.  You can remove them from this space and you can also ban them from ever entering this space if you wanted to.  This is a newly added feature within the Marketing Nation.   Manage your Company Space (NEW) You're not just the Support Admin, you are the admin of this space.  Adjust this space as you need it,  If there are different types of content widgets or text boxes you want to add to this space, you can do it.  This is a space for your company's use and benefit, so do with it as you need it.   Our team is on hand to assist you with any questions you have to manage this space.  You can contact us by sending an email to supportfeedback@marketo.com . Is this article helpful ? YesNo
View full article
Marketo users can configure Marketo to manage, nurture, and measure leads that are created from Google AdWords. We offer 2 options, depending on what type of web page is linked to your Google AdWords ad. Option 1: Link Google Adwords Ad to a Marketo Landing Page with a Form   This solution does not require custom coding This solution does not require any additional cost Option 2: Link a Google Adwords Ad to Any Page on your Website This solution does require custom coding so that you can capture the PPC (pay per click) information when the lead comes back 'later' to fill out a form on your page Depending on whether you have resources internally to do the custom coding, this solution may or may not require additional cost Reporting Available (for both Option 1 and 2) Number of new leads acquired by Google Adwords Program Cost per new lead acquired by Google Adwords Program Number of leads acquired by keyword/search phrase Top 10 keywords/search phrases which acquired new leads Top 10 AdWords CampaignID which acquired new leads Number of Opportunities by keyword/search phrase Number of Opportunities by CampaignID Additional Reporting Available if you have Revenue Cycle Analytics/Explorer Conversion ratio of your Google Adwords Return to investment for your Google Adwords Top 10 keywords by month report which shows Average days to convert to opportunity Number of leads converted to opportunity Top 10 CampaignID’s by month report which shows Average days to convert to opportunity Number of leads converted to opportunity Program Channel report >> Google Adwords (custom channel) metrics by quarter New names, cost per new name Opportunity units, Pipeline generated, revenue, revenue to investment     Learn more:   Linking a Google Adwords Ad to a Marketo Landing Page with a Form Linking a Google Adwords Ad to Any Page on Your Website Google Adwords and Marketo FAQs  
View full article
NOTE: As of late-2019, a Secured Domains 'base' offering is now automatically included in all new customer subscriptions, and existing customers upon next renewal. This secures your first landing page domain and first tracking link domain. To make any domain changes, or purchase coverage for additional domains, please contact your Marketo Engage Customer Success Manager (CSM) for more information.   Marketo’s Secured Domains for Landing Pages secures any and all landing page domains defined in your instance to be served via HTTPS. Serving your pages securely assures that you’re providing critical security and data integrity for both your pages and your visitors’ personal information.   Below you’ll find the 5-step process to secure your Marketo landing pages with Marketo’s Secure Domains for Landing Pages. Please note, there is an automated support case that gets created on your behalf when the purchase of Secured Domains for Landing Pages is completed.     Step 1. Verify your Landing Page Domain, CNAMEs and any Domain Aliases are setup Before you can secure your landing page domains and any domain aliases (subdomains), you must first set these up in Marketo. If you are a new Marketo customer working through your implementation, please work with your implementation consultant on the landing page domain(s) setup and timing to cut over to HTTPS. If you’re securing your landing page domains for a previously implemented instance, please verify that your domains and domain aliases (subdomains) are set up in your instance. Below are some links to help: Edit Landing Page Settings – to set you Landing Page Domain Customize Your Landing Page URLs with a CNAME – to understand and set up CNAMEs (subdomains) Add Additional Landing Page CNAMEs – to set up multiple CNAMEs in your instance (subdomains) Be sure your redirect rules and domain aliases are updated to use https://  instead of http://    Step 2. Edit and update the HTML code of your existing landing page templates to HTTPS Next, you'll need to review and update your Marketo landing pages to ready them to be served securely. Please complete the following two actions in order before moving on to Step 3: If you purchased Marketo before January 2016, please un-approve and immediately re-approve all landing pages last updated before January 2016. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages for un-approve/re-approve via the “Landing Page Actions” menu. We recommend completing this step in batches of a maximum of 10-20 pages at a time. Instructions for doing so can be found here: Approve Multiple Landing Pages at Once - Marketo Docs - Product Documentation. You can see the "Last Updated" timestamp in the Landing Pages section of Design Studio. Open the HTML code for each landing page template. C hange all URLs listed in the HTML currently formatted as "http ://" to instead read "https://" TIP: Ctrl+F "http" to automatically highlight all URLs that must be updated: Simply add "s" after each http reference until ALL have been updated to https Missing even one URL's http reference will cause the "Mixed Content" browser warning:   vs.  SAVE THE PAGE AS A DRAFT Do  not approve the draft. You will approve the drafts after Support activates SSL in Step 4. NOTE: Once you secure your Marketo landing pages to be served over HTTPS, you should not link to HTTP (unsecured) assets or pages from your secured landing pages.   For more detailed guidance, please see our recorded instructions below         Step 3. Respond to the TSE via the existing support case The TSE will then begin the process on our end to generate certificates to cover all the domains and subdomains configured in your instance. Once notified, please allow 3 business days for Marketo to create your secure server endpoint. Marketo's Support team will contact you when this is complete. We appreciate your patience during this 3-day setup process.   Step 4. Marketo Support Will Activate Your Secured Domains for Landing Pages Once we've generated and issued the necessary SSL certificates for your domains, we'll notify you that it is done and activate SSL for your Landing Pages. NOTE: There will be a brief "cut-over" period between when HTTPS is enabled by the TSE and when you are able to complete Step 5 below. During this time, landing pages may show up to customers with a mixed-content warning; however, all links and emails will continue to work properly without disruption, and your customers are not at any risk. Be ready to complete Step 5 quickly once instructed to minimize this period. Step 5. Re-approve your landing pages and verify success Once your Support Engineer has activated the switch to HTTPS for your instance, y ou must immediately take the following actions: Approve all draft pages that you edited from Step 2 above. This can be done in bulk in the Landing Pages section of Design Studio by selecting a group of pages to approve via the “Landing Page Actions” menu. If you include a Marketo landing page on a secure website using an iframe, you will need update the HTML to load the secure version of the landing page, otherwise the end user will get a security warning. Verify your pages are loading and rendering as expected. Contact Marketo Support with any issues you may encounter.     Questions & More Information For more detailed information, please see the Secured Domains Technical FAQ.     Is this article helpful ? YesNo
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
Technically, you cannot move records backwards in a progression status.  The only so called “backward” status that you can change the record to is a progression status of “Not In Program”; however, doing this removes them from the membership of the program.  If you do this procedure, this will allow you to re-add them with a different status.   We mentioned technically this cannot be done but logically, there is another method that allows you to juggle the record’s progression status but in a more lateral movement with what appears to be in a “backward” state.  This is all dependent on how you have your channel steps configured.  To access your channel steps, please do the following:   Choose Admin Choose Tags Click the + next to Channel Locate the channel you wish to configure and highlight it Click the drop-down menu towards the top of Tag Actions, and select Edit   You should now see a pop-up window that allows you to configure the status steps for that channel like the following example:       If you configure statuses that have the same step number, this will allow you to move the record in a lateral movement which, in a sense, is somewhat like a backward progression but it really isn't .  With the example screen capture, I can do a change in progression status of “Invited” to “Attended Show” and vice-versa because the step is with an identical number. If I wanted to change in progression status of “Invited” to “Engaged” and back, it will not work because the step value is not identical. You can reference more information about this in the Marketo Admin: Customize, Create, & Manage Channels article.
View full article
Issue You need to locate the Munchkin ID for a specific Marketo instance. Solution What is a Munchkin ID? Marketo's custom JavaScript tracking code, called Munchkin, tracks all individuals who visit your website so you can react to their visits with automated marketing campaigns. Even anonymous visitors are tracked along with their IP addresses and other information. The Munchkin ID is the unique identifier for a specific Marketo instance and insures tracked activity goes to the correct instance. How to find your Munchkin ID 1. Log into the specific Marketo Instance you need the Munchkin ID for. You can verify the instance name by checking the listing in the top left of your browser.   2. Go to Admin and click Munchkin in the tree on the left in the Integration section.     3. The Munchkin Account ID will be the first thing listed in the Tracking Code box.  
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
Issue Description You would like to change the displayed name for your Marketo instance.   Issue Resolution 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. Is this article helpful ? YesNo
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
    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 90 days, 25 months, or 37 if you have purchased the premium data retention option. The official Marketo Data Retention Policy can be found here:  Marketo Activities Data Retention Policy   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
  This is a article attached image 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
Issue The URL for the landing page shows as "https" even though you do not have SSL set up on your Marketo instance, causing the browser to display a "Not Secure" warning.   Solution This can happen if the primary domain and DNS are SSL secure, but Marketo is not.  For instance, if your primary domain is " https://www.mycompany.com " (SSL secure) then the DNS, which is also SSL secure, will push down the "https" transfer protocol down to all the CNAMEs on that DNS.  This will force the Marketo landing page using the CNAME to use "https" in the URL, even though it is not secure. There are two ways to resolve this: Work with your IT department to see if there is a non-SSL option for your DNS Purchase SSL for your Marketo instance so that both your primary domain and your Marketo pages are SSL secure. If you would like to add SSL to your Marketo instance, please contact your Account Manager to see about adding that to your subscription.     
View full article
Issue After going through a modification of a text field type from 'Text' to 'String', the field is no longer available as a filter for smartlists. Don't worry, the field is not gone - it is just temporarly unavailable. Solution Changing the field type from one type to another is a database intensive operation and in some cases where the field values are widely populated across your database records, this can cause the filter to be unavailable until the operation is completed in full. The time it takes for the field filter to become available may vary and it can take up to ~30 hours sometimes until the field filter is available again after the type of the field has been changed.  
View full article
Issue Executing a GET API call to retrieve a list of available activity types in the target instance using the '/rest/v1/activities/types.json' endpoint, resolves with an unexpected attribute name for a field with the display name ID in the context of Marketo Custom Objects. An example of that may be a Marketo Custom Object with the following name: '3 to be', as can be shown in the image below: One of the '3 to be' Marketo custom object fields name is 'ID'. (highlighted in red). When performing a GET API call using the '/rest/v1/activities/types.json' endpoint, you will be getting a list of available activity types in the target instance, along with associated metadata of each type, however for a Marketo custom object with an ID field name, you may see it returns back with a slightly different name, in this case, it would be returning the following output for my test Marketo Custom Object activity: { "id": 100019, "name": "Add to 3 to be", "primaryAttribute": { "name": "3 to be ObjRef", "dataType": "integer" }, "attributes": [ { "name": "3 To Be Person Id", "dataType": "integer" }, { "name": "ID (3)", "dataType": "string" }, { "name": "Linkfield4", "dataType": "string" } ] } ], Here's an image of what it may look like when making the call using POSTMAN: In fact, the character in the brackets next to the ID field represents the very first character of your Marketo Custom Object name.    Environment Customers who have Marketo Custom Objects where one of the custom object fields is named 'ID'. Solution If this is interrupting your business, you may want to select a different name for the ID field under your Marketo Custom Object. (ie. ID number, Transaction ID etc.) Root Cause This behavior is expected and is a result of the 'ID' field being a unique field in the context of Marketo custom objects world and while it may be possible to create a Marketo Custom Object field with the name 'ID', it may be better to give it a distinct name that will be better describing what kind of ID field it is.   
View full article
Issue When changing Program Status in Admin > Tags > Channel for "Event" result in this error, "Failed: no more information".  Environment Changing Program Status  Failed: no more information Solution "System mapping for Registered, Waitlisted, and Attended statuses is required." Therefore, ensure the status is mapped to Registered, Waitlisted, and Attended.   Root Cause One or more of these statuses "Registered, Waitlisted, and/or Attended" were not mapped as required. 
View full article
Issue When editing the expiration date for a user in Admin by completely removing the expiration date set to null and clicking save. The change is not saved, and the expiration date remain. Environment Expired Date for user Expiration Date Changing the expire date to never in Admin   Solution There are two options: 1. Change the expiration date to a date in the future.  2. Delete the user in Admin and recreate the user again and set the expiration to never.  *Please note that if option 2 is selected, the history of the user is will be lost and this cannot be retrieved. Root Cause This is a design limitation as it is expected for the user with an expiration date to be deleted from the Marketo Instance after the expiration date has been reached. 
View full article
Issue Error 603 'Access Denied' is returned for when an API user with the default Admin role attempts to make an API call http://developers.marketo.com/rest-api/error-codes/   Environment REST API Users and Roles Permissions Solution To avoid this error, create a new role: Create, Delete, Edit and Change a User Role | Adobe Marketo Root Cause It is expected that when the default 'Admin' role is used for an API user, attempting to make API calls will return error 603.
View full article
Issue Per our developer page: https://developers.marketo.com/rest-api/assets/programs/#update, it is possible to update tags on your existing program When updating a program tag within an existing program, you may encounter an error below given the tag and its values are correct.  {"code": "709","message": "Required tags are mandatory"}]} Environment Any API clients when performing the Web Service API Solution The workaround is to have the tag updated via the UI. Root Cause "Updating tags is a destructive operation." Any attempt to update the tags of a program must include valid values for all of the required tags for a program. Unless the 'specific' tag type you are working on is the only required tag type in the instance, then that is possible to update it using the API. Otherwise, you'll encounter the error above as it is a system behaviour.
View full article
Issue When adding new IP Address to the IP Restrictions list on Admin > Login Settings > IP Restrictions, you receive this error message: "Your current IP address (XXX.XXX.XXX.XXX) cannot be blocked."   Environment Admin IP Restrictions Login Solution Ensure that you have Admin Access to the Marketo instance and that you have logged into the Marketo instance via one of the IP Addresses listed on the IP Restrictions list.  Root Cause User logging into the instance with an IP Address not on the IP Restrictions list. 
View full article