Knowledgebase

Sort by:
Issue Will custom settings, such as Launchpoint integrations, API configurations and SFDC sync settings, remain in place when doing an instance copy, or will they be overwritten?     Environment Non-Microsoft Dynamics integrated Instance Solution All permanent configuration settings which can be done to a Marketo instance are reset to the default values or settings in the destination instance. Everything is copied except for the below list: Lead Database and activity history are not copied CRM configuration is reset on the destination instance. Users are not copied. CRM Field Mappings are removed in the destination instance except for standard mappings, and must be set during the Field Mapping Stage of CRM sync initialization. RCA information is not copied. Program subscriptions are not copied. Campaign History is not Copied. CNAMES for Email links and LPs are not copied. All Account-string based properties are modified accordingly. Munchkin ID of the destination instance is preserved. Sales Insight Admin Configuration is Reset. Outlook licenses are not copied. All pre-existing data on the destination instance will be destroyed. Asset IDs for emails, landing pages, and programs will match Launchpoint and API integrations are not copied   If data may exist on the destination instance prior to the copy process, this may require that you work with your Success Manager to obtain a replacement instance for the copy to be completed. NOTE* This process is not applicable to customers utilizing the native Microsoft Dynamics integration.
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 technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include:   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 TSEs 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 TSEs 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 After declaring a champion for your Champion/Challenger test, you notice that the test (ex: "Whole Emails" test) in the Marketing Activities asset tree under your Email Asset is missing.   Root Cause When you declare a champion, you select a Declare Date. Once this date/time is reached, only the new champion will be sent. After the test is over, it is expected behavior that the test (ex: "Whole Emails" test) will no longer be shown in the tree. This is because the test is no longer active. If you would like to retain your test data, it is recommended that you save this outside of Marketo.
View full article
Issue An email was expected to sent out on a specific cast of Nurture Program but a specific lead or couple of records did not receive it.   Environment Marketo>Engagement Program Solution There are a number of steps to begin troubleshooting this query and here is a flowchart how to proceed. 1). Check if engagement program is turned on from its setup up. Also check if at the time of email cast, the program status was on (this can be checked from Admin>Audit Trial) 2). Check if the email asset which was expected to send was present in the Nurture Stream at the time of cast. Also check if that email asset was activated (having green arrow). Both of these can be checked from Audit trail where you will find the log of "Add Email" and "Activate Email" along with its date/time. 3). Check if the lead is present in that specific stream using the smart list filter "Member of Engagement Program > Stream = <required stream>" 4). In the same smart list, use filter of "Engagement Program Cadence Changed" and set "New Value = Paused" and see if that lead qualifies it or not. A paused cadence would mean the lead has been temporarily restricted to move in the flow of nurture stream and hence will not received any email content. 5). Most important step- Go to the activity log of lead and search for the engagement program's name in the quick find bar. Look for all logs along with their dates when the lead performed any activity related to that engagement program like added to program, changed cadence, removed from program, etc. 6). In continuation of step 5, check in the activity log if the lead was added to engagement program in less than 25 hours before the next cast by looking at the time of log "Added to Engagement Program". This is because as per the doc, the lead must be added atleast 25 hours before the cast to abide by the recipient  time zones otherwise it will skip that current cast and will qualify for the next cast. Schedule Engagement Programs with Recipient Time Zone | Adobe Marketo 7). In continuation to step 5, check if the lead was moved to a different stream via getting qualified into transition rules. Transition rules are present in stream of those engagement programs that have more than one stream and are used to move leads from one stream to another. Transition People Between Engagement Streams | Adobe Marketo 8). Check if the lead is unsubscribed, email invalid, email suspended (this one is only valid for 24 hours), marketing suspended or block listed because any of these 5 conditions would block the lead from receiving any communication from any of the Marketo's program or campaign. 9). Check if the record has hit the communication limit. Go to Admin>Communication limit and see what we currently have setup. If limit is 2 emails per day, then create smart list "Was sent email>Email Is ANY> Minimum Number of times 2" and see if lead qualifies in it. Alternatively you can go into lead's activity log and manually count number of "Send Email" logs in last 24 hours and in last 7 days and match it with the communication limit of Admin tab. Using programs as stream content: We can also use programs (default and event) in nurture stream instead of direct email assets. 10). In case of using a program, the email can be sent out to the required audience only if that program have a smart campaign with filter "Member of Engagement Program>Name of Program" and flowstep of "Send Email". So make sure the smart campaign has these configurations. (Make sure the campaign has to be a batch campaign and not trigger) 11). If above pointer is true still record is not present in the result tab of the campaign, then check all steps from step 1- step 9. If nothing is found then check if smart list has more than just "Member of Engagement Program" filter and if the lead is failing to qualify any of the other filter. 12). Check in the schedule tab if qualification rules says "Each Lead can qualify only once". If yes then go to campaign member tab and search if lead is already a member, if yes then lead will not qualify again and this is why email was not sent. 13). Check if flowstep has a wait step and the lead is stuck there because wait step does not create any log in the results tab. People in waitstep can be checked from dashboard of the smart campaign. 14). For any other possible reason why the lead did not qualify the smart campaign, you can look for the knowledge base "Lead not qualifying smart campaign- Universal Checklist" under heading of Batch Campaign: marketo.my.salesforce.com/articles/en_US/Article/Lead-not-qualiying-smart-campaign-Universal-Checklist?popup=true 15). If all above pointers have been checked still unable to figure out why the email was not sent on a specific cast, escalate the case to Tier 2.
View full article
It's one of the most common calls we get in Support - "This lead should have qualified for this campaign, but it didn't. Why?"  Here's how we go about answering this question, and you can do it too.   Did the lead actually qualify? Sometimes the leads do qualify for the campaign but don't go through the flow.  One quick way to check this is to look at the campaign membership.  If the lead qualified, it will become a member of the Smart Campaign, even if it doesn't go through the flow. Has the lead gone through the flow before?  We can check this in the campaign results. If it has, we need to see if the campaign allows the leads to go through the flow more than once. If the campaign is set up to allow leads to run through the flow multiple times, then we need to proceed with troubleshooting. But if it is not, we have our answer - the lead didn't go through the campaign because it had done so previously and couldn't go through again.   Did the trigger have constraints? If it didn't, we move along, but if it did, we need to check and see if the lead met the requirements of the constraints at the time the lead hit the trigger. This is very important.  If, for instance, there was a constraint that required a value in a field, and that field was not populated before the trigger went off, then the lead wouldn't qualify.  The timestamps in the activity log for the trigger activity and the value change might be the same, but if the value change for the field happened even a fraction of a second after the trigger event, it's still too late. The lead will not qualify.  Looking at the lead now, it looks like it qualifies, but at the moment the campaign was triggered, the lead had different information, so check to see when the required values were written to the lead.   Did the Smart List have filters in addition to the trigger? Just like the constraints, we need to confirm the lead satisfied the filter requirements before the trigger fired.  This can get complicated if one of your filter requirements is "Member of Smart List" because you are going to have to go into the referenced Smart List and confirm the lead met all those requirements, and if that Smart List also contains a "Member of Smart List" filter, then will have to check that one as well and, well, you will see why we in Support recommend against nesting Smart Lists.   Has the campaign been changed since the lead hit the trigger? We tend to assume that the campaign we are looking at today is the same as it was when the lead hit the trigger, but this is often not the case.  Check through the Audit Trail to see if there have been any changes.  Maybe a constraint was added, removed, or changed.  Maybe the filter logic was changed from AND to OR.  Maybe it used to only let leads go through the flow once.  If the campaign was changed, you will need to go through the troubleshooting steps above all over again, checking against what the campaign used to have, rather than what it has now.  If you have nested Smart Lists, it may be that the campaign didn't change at all, but a filter criteria in a the secondary Smart List did.  This is another reason why nested Smart Lists should be avoided if possible.   If you go through these steps and still can't figure it out, open a case in Support and include the results of the troubleshooting above so we can look into it further.
View full article
Issue Issue Description If a page is not loading in your browser for Marketo, this can sometimes be due to network related issues. We can help troubleshoot by using a HAR file from the browser to see network traffic.   Solution Issue Resolution Instructions to generate a HAR file broken down by browser version: Chrome In Chrome, go to the page within Marketo where you are experiencing trouble. At the top-right of your browser window, click the Chrome menu ( ⋮ ). Select Tools > Developer Tools . The Developer Tools window opens as a docked panel at the side or bottom of Chrome. Click the Network tab. Select Preserve log. You will see a red circle at the top left of the Network tab. This means the capture has started. If the circle is black, click the black circle to start recording activity in your browser. Refresh the page and reproduce the problem while the capture is running. After you successfully reproduce the issue, right click on any row of the activity pane in the Network and click Save as HAR with Content. Save the HAR file. Select the Console tab. Right-click anywhere in the console and select "Save as...". Name the log file Chrome-console.log. Send both files as shared links in a reply to your case. Firefox In Firefox, go to the page within Marketo where you are experiencing trouble. Click the Firefox menu (Three horizontal parallel lines) at the top-right of your browser window. Select Web Developer > Network. The Developer Tools window opens as a docked panel at the side or bottom of Firefox. Click the Network tab. Select Persist logs. After you successfully reproduce the issue, right-click any row and select Save all as HAR. Firefox typically takes a few seconds to prepare the download. A slight delay on this step is normal. Select the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Safari In Safari, go to the page within Marketo where you are experiencing trouble. In the menu bar at the top, click Develop and select Show Web Inspector. Click Preserve Log. Click the Console tab and select Preserve Log. Go back to the Network tab. Refresh the page and reproduce the problem while the capture is running. Once you have reproduced the issue, select Export. Save the HAR file. Click the Console tab. Right-click any row and select Select all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case. Internet Explorer 11 (IE 11) In Internet Explorer, go to the page within Marketo where you are experiencing trouble. Click the gear icon in the top right. Select F12 Developer Tools. Click the Network tab Clear the Clear entries on navigate option, which is selected by default. The icon looks like blue arrow with a red X. The green play button (Start Profiling Session), should be selected by default. This means the capture function is running. Refresh the the page and reproduce the problem while the capture function is running. Once you have reproduced the issue, click the Export as HAR icon. The icon looks like a floppy disk. Click the Console tab. Right-click any row and select Copy all. Paste the content in a text file and name it console-log.txt. Send both files as shared links in a reply to your case.
View full article
Issue Clicking a tracked link in an email either leads to a 404 page or the fallback page. Environment Tracked links Tokens Specific Characters: "#", "$", unbalanced brackets "{" or "}" Solution Do not use the following characters "#", "$", unbalanced brackets "{" or "}" in a link that is tracked when using a token as well. For example: www.google.com/ebook-download.html?ebook={{lead.ebook}}# This will not work and will either direct to a 404 page or redirect to fallback page. When hovering over the link you will see that it is not a normal tokenized link, it will contain something along the lines of: $mktEncrypt.encrypt($mkturl2)/<random characters> Root Cause When using tokens in the url of a tracked link, the email is processed and the tokens are substituted and populated with the correct information. The engine that assembles this information have some characters reserved for use such as #.
View full article
Issue When comparing the Engagement Score on the Engagement Dashboard, the scores do not match with the Email Insight Engagement Scores. Environment Engagement Program Email Insight Solution The Engagement Score from the Engagement Dashbaord will hold the most accurate information as this is direct information, rather than for example with RCA/RCE and Email insights where the data source is different. If you want to see Engagement Score over a period of time more accurately, use the Engagement Stream performance report: Engagement Stream Performance Report | Adobe Marketo Root Cause The Engagement Score on the Engagement Dashbaord only calculates the last 3 casest, it is also important to remember that the engagement score only includes emails that were cast more than 72 hours ago. As per this documentation: The Engagement Dashboard | Adobe Marketo In comparison, the Email Insight Engagement Score is calculated over a period of time that is set by the user but the data can still be mismatching, this is due to the fact that the data source is not the same from the Engagement Dashboard.
View full article
Issue New program status created in CRM did not sync to Marketo.  Environment Program status did not sync to Marketo New Program status is missing in Marketo Solution Create the corresponding status in Marketo by navigating to Admin > Tags > Channel > Select the corresponding channel > Add new status > Save.  Create a Program Channel | Adobe Marketo Root Cause This is an expected behaviour as program statuses created in CRM do not sync to Marketo. 
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
To enable Marketo to meet the performance demands of its customers, Marketo has a standardized Data Retention Policy used across the platform. This policy applies to the activities stored in the activity logs of people in your database.   Activities and Data Retention There are three components to our data retention policy: a retention period of 14 days for one activity, 90 days for twelve high-volume activities; and a retention period of 25 months for other lead activities. Activity with Retention Period of 14 days Activities Retained for 14 Days       Delete Lead   Activities with Retention Period of 90 days The high-volume activities listed below will be retained for 90-days. After 90-days, these activities will be permanently deleted. Activities Retained for 90 Days Add to List Change Score Change Data Value Visit Webpage Click Link on Webpage Sync Lead to SFDC Sync Lead to Microsoft Sync Lead Updates to SFDC Update Opportunity Request Campaign Email Delivered* Send Email*   * Email Delivered and Send Email activities change from 25 months to 90 days effective August 31st, 2020.  More information here .   Activities with Retention Period of 25 Months The activities listed below will be retained for 25 months. After 25 months, all such lead activities will be permanently deleted. The only exception is the New Lead activity, which will always be displayed in the activity log. All other activities will be deleted, but the New Lead activity will not, giving you a permanent record of when the lead was created and how. Category Activities Retained for 25 Months Web Click Predictive Content Click RTP Call to Action Fill Out Form Smart Campaign Add to Engagement Program Call Webhook Change Lead Partition Change Engagement Program Cadence Change Engagement Program Stream Change Program Success Change Revenue Stage Change Revenue Stage Manually Change Program Status Compute Data Value Enrich with Data.com Execute Campaign Interesting Moment Merge Leads Remove from List Resolve Ruleset Reward Test Group Variant Schedule Test Variants Send Alert Engagement Program Cast Push Lead to Marketo Social Click Shared Link Share Content Vote in Poll Email Click Email Email Bounced Email Bounced Soft Open Email Received Forward to Friend Email Sent Forward to Friend Email Unsubscribe Email CRM - Salesforce Add to Opportunity Add to SFDC Campaign Change Owner Change Status in SFDC Campaign Click Sales Email Convert Lead Delete Lead from SFDC Lead Assigned New SFDC Opportunity Open Sales Email Receive Sales Email Remove from Opportunity Remove from SFDC Campaign Resolve Conflicts SFDC Activity Sales Email Bounced Send Sales Email SFDC Activity Updated SFDC Merge Leads Add to Case Add to SFDC Custom Object Test (Contact) CRM - Microsoft Dynamics Add to Opportunity (Contact) Add to Opportunity (Account) Remove from Opportunity (Contact) Remove from Opportunity (Account) Update Opportunity (Contact) Update Opportunity (Account) Delete Lead from Microsoft Segmentation Add to Segment Change Segment     Retaining Data Marketo’s data retention policy gives you a rolling 90-day view of certain high-volume activities and a rolling 25-month view of other lead activity data. To help prevent any actual data loss, Marketo has developed a Bulk Extract API that enables you to export this data directly if desired. Once exported, you will be able to host this information locally and utilize it in any way you deem necessary. Premium Data Retention Option Marketo offers a premium Extended Data Retention subscription option that will allow activity data to be stored for 37 months instead of the standard retention period of 25 months. The high-volume activities, however, will only be retained for 90 days even with the premium option. For more information, contact your Customer Success Manager.  
View full article
Issue When searching or grouping a list of leads based on email address filter ‘Contains’ @ sign, you may encountered the different numbers in the ‘People’ tab (result). Environment This behaviour is specific to the email filter as it uses two main indexes; we’ll call them Index 1 and Index 2 when using the contains/not contains operator. Index 1 searches for the entire email address value from beginning to end. This Index is used when the @ character is not included in the list of values. Index 2 searches only for the domain half of the address, which comes after the @ symbol. This Index is used when the @ character is included in the list of values. Solution A suggestion is to create a smart list with two Email Address filters wherein you will have all the ones that do not have the '@' symbol, and for the other, you will include the '@' symbol for the email address and use the logic as 'Any'. That would give you the preferred number of leads in your smart list. Root Cause Marketo database searches for email domains in a way that when using the 'contains' keyword in the 'Email Address' filter, you must make sure that if you are using the '@' symbol in your list of domains that all email domains contain this. If you want to filter for email domains that do not include the '@' symbol, you must make sure that no email domains in your list use the '@' symbol. This behaviour happens when the indexing of the database and the rules that apply to the contains operator.
View full article
Issue When working on an event program, Marketo Engage users are unable to select a webinar provider in the event partner selection. Environment Event program Webinar provider (ON24, Zoom, Cvent) Solution The members need to be removed before setting up the event partner. You can remove members from a program by changing their status to "Not in Program". Root Cause Marketo does not allow selecting an event partner in a Marketo event program with members.
View full article
Once you have submitted a case to Marketo support, we provide a simple way of staying connected to your case and the cases submitted from your company through the Marketo Support Portal. You can access the support portal through your Marketo instance by selecting Community in the top right corner: You can also access the support portal directly at https://support.marketo.com and login with your Marketo credentials (login and password). This will not work for users with SSO.   Once you are in the support portal you can Create a Case for Marketo Support or you can also review any cases that are open and being worked on by support or review your case history. Navigate to My Case management: From the My Cases navigation y ou can access the following case views: My Recent Cases* - Cases that you have opened in the past 30 days All Company Recent Cases* - Cases that any authorized support contact has opened in the past 30 days My Open Cases – Cases created by you that are being triaged by Support and pending Support’s response and are more than 30 days old My Closed Cases – Cases that were created by you and are now closed My Awaiting Fix Cases – Cases that were created by you where Marketo is developing a fix which will be implemented at a later date All Company Closed Cases – Cases that were created by you or your colleagues that are now closed All Company Open Cases - All open cases submitted for the account Company Awaiting Fix Cases – Cases that were created by you or your colleagues where Marketo is developing a fix which will be implemented at a later date Management Escalations - Escalations opened by you or your colleagues  Survey Cases - Surveys that are available for you to fill out after a case is closed *Cases that have been opened for more than 30 days will move from Recent cases to Open cases   To view specific case details, click a case number. From the Case Details, you can perform the following: Close your Case - Select the "My Case is Resolved" button to close your case Add Comments - Provide additional comments to support or respond to a Support question Add Attachment - Provide any screenshots or documents that will help illustrate the issue you are reporting   If your case has been closed there are two options available to you.   Reopen - You can reopen your case if you are not satisfied with the case resolution by adding a comment in the case. Case Survey - Once your case has closed, please consider offering feedback on the level of Support you received.
View full article
Issue You would like to pull a report of all the non-marketable records that you have in Marketo. Solution You can do this via a Smart List: Use the Any filter in the Smart List. Filters: Black Listed = true Unsubscribed = true Marketing Suspended = true Email Invalid = true Email Address is empty This Smart List will pull all the people that fall into the blocked leads list.    
View full article
Issue You made an A/B Test within an Email Program, and now when you are in a Smart List or Smart Campaign and are attempting to set up a filter (such as Opened Email), you are unable to locate the A/B test email asset in order to select it. Solution When an A/B test is made in an Email Program, the Program must be approved in order for the email to be located by other assets (Smart Lists/Smart Campaigns.) When the Program is approved, the email asset name will be changed to whatever kind of A/B test is used, and will be available for reference in other assets. For example: [program name].Subject Line Test; or [program name].Whole Email Test
View full article
Issue Smart campaign email tab's count for soft bounced and delivered activities does not match the number of soft bounced and delivered activities in smart campaign results tab Example: Email tab shows 5 soft bounces, whereas, results show 6 soft bounce activities Email tab shows 10 delivered, whereas, results show 13 delivered activities Solution The email tab on a smart campaign is an Email Performance Report so it is calculated based on documented rules at Email Performance Report | Adobe Marketo   Root Cause There was one lead that opened the email, so the lead was not counted as soft bounced on the email performance report and was counted as email opened based on email performance report rule #4 "If the email is Opened, bounces are ignored." There were three leads that had soft bounce activity also had a delivered email activity. Based on email performance report rule #1 "Each email activity record is set to one, and only one, of the following: Delivered, Hard Bounced, Soft Bounced, or Pending." - in this case, soft bounce takes precedence over delivered email activity so the three leads were not counted as delivered on the report but were counted as soft bounce. Environment Smart campaign Email tab Smart campaign results Email performance report
View full article
Issue Best practices for trigger campaigns. Solution Trigger campaigns in Marketo look for ANY activity that could be related even if there is a filter or constraint. If you have 10 Clicked Email Campaigns active, and 100 Leads click on an email. Each lead has 10 evaluations to determine if that trigger qualifies. They will still evaluate even if they will not qualify due to constraints or filters. Here are some best practices to assure your trigger evaluation step is as quick as possible: -Turn off any trigger campaigns that are no longer needed. (This will reduce the # of active monitors that will cause evaluations to fire off for a trigger event)       -Note: Once a quarter, Marketo will find smart campaigns that have sat dormant (no people trigger it) for 6 months or more and deactivate them automatically. However you can manually deactivate campaigns on your own.   - Convert Trigger campaigns to Batch if they are not needed for immediate response (for activities or campaigns that can run nightly). Batch campaigns run on a separate component of Marketo's processors which doesn't affect the Trigger qualifier speeds. Each instance's situation can be unique. Our support team would be glad to go over best practices for your instance and also review how you can self-maintain the campaign deactivation through the Campaign Inspector.   
View full article
Issue If a record which is in a Marketo Campaign Wait Step and is merged into another record, does the winner of the merge continue through the flow?    Solution Winner of the merge will continue through the Campaign flow and complete the remaining steps. To prevent this behavior, remove the record from Campaign using the 'Remove From Flow' step. Environment Records merged in Marketo  Records merged in SFDC
View full article
Issue Single Flow Step to send an email to x number of leads failed  Solution Create a smart campaign and override the person restriction to send an email to a number of people that is greater than the campaign restriction Root Cause The number of people selected to send an email from a single flow action exceeds the campaign person restriction/limit. The campaign restrictions apply to the single flow action because a background campaign is generally created to process the single flow action. Environment Single Flow Action Send Email Campaign Restrictions Smart List
View full article