Knowledgebase

Sort by:
Issue Description Can Email Insights Quickcharts be shared across users within Email Insights? Issue Resolution At this time Email Insights saved Quickcharts are user-specific and cannot be shared or viewed by other users. You can share the quick chart with anyone by downloading the chart as a PowerPoint or Excel file. Who This Solution Applies To Email Insights Users
View full article
Issue Why does the record in Marketo have an Opportunity when its matching synced Contact in Salesforce does not have an Opportunity? Solution The Contact in Salesforce has an Opportunity Contact Role associated with an Opportunity that belongs to other Contacts. Since "Marketo associates Opportunities and contacts using Opportunity Contact Roles.", Marketo syncs down the Opportunity for the record has it has an Opportunity Contact Role associated with it.experienceleague.adobe.com/docs/marketo/using/product-docs/crm-sync/salesforce-sync/sfdc-sync-details/sfdc-sync-opportunity-sync.html?lang=en If the Opportunity is needed to be removed from the record in Marketo, then: The Opportunity will first need to be deleted in SFDC. The visibility of the role value that is not the primary owner of the Opportunities will need to be removed from the Marketo Sync User. Re-create the Opportunity so that it can be associated to the primary owner.   Who This Solution Applies To Customers who has Salesforce integrated to Marketo
View full article
Summary We have identified an issue that occurred during a recent update released on October 26, 2018. This update inadvertently created a condition where landing pages might lose page elements after being re-approved. Free-form landing pages that contain dynamic content may also have missing elements. Frequently Asked Questions Who is affected? This update affected a subset of landing pages across multiple customers that developed their landing pages with the Free-Form Landing Page editor. Landing pages that have been developed using the Guided Landing Page editor are not affected. How does this affect me? Customers need to ensure their live landing pages are not missing any content. This issue is most likely to affect free-form landing pages with dynamic content, and landing pages that have been re-approved since October 26, 2018. However, please keep in mind that it is possible this issue affected other landing pages as well. Which landing pages should I focus on? First, you will want to focus on your landing pages with dynamic content. Landing pages with dynamic content can be reviewed using the Preview Page functionality as shown in the documentation here. Review by each Segment to ensure all content is present in each version of the page. If you notice missing content on the live version of the landing page with dynamic content, you will need to re-add that content to the page in the Landing Page Editor and re-approve the landing page. Second, you will want to look at commonly used and high value landing pages. Open these in Marketo’s editor to check if content is missing and re-add it if necessary. What content is missing? This issue only affects Rich Text Elements. Landing pages have multiple different types of elements (forms, images, snippets, etc.). The only type of landing page element that are impacted Rich Text Elements. Here’s what to look for: Landing Page Elements Impacted – Rich Text Elements Landing Page Elements Not Impacted – All Other Element Types What if I am unsure that any content is missing? Unfortunately, there aren’t many ways to see exactly what content is missing from affected pages. You should be able to see the correct version of landing pages without dynamic content by visiting the live version. If you cannot reach the live version of the landing page, you can try using The Way Back Machine at http://web.archive.org to see older cached versions of the page. While this is a third-party resource not operated by Marketo, it may be helpful in identifying what content was previously on the landing page. Are all my landing pages affected? It is highly unlikely that every landing page is impacted. However, every free-form landing page has the possibility to be impacted. It is recommended to check your active landing pages as well as the pages that have dynamic content to ensure they display as intended. You can utilize a Landing Page Performance Report to see which Landing Pages are active and which ones have the highest traffic so that you can prioritize those first. Free-form landing pages are the only ones affected by this issue. Guided landing pages are not affected at all. Will cloned landing pages be affected? Landing pages that are cloned from an affected landing page after October 26th could also be impacted. You should validate these cloned pages as well. Why doesn’t Marketo rollback the update that caused this issue? We first learned about this issue after other changes occurred to the code base. Unfortunately, we are unable to selectively roll back updates due to unforeseen changes that may occur. Additionally, many customers have made additional changes since this first occurred and there’s no way to identify which version should be restored. Can Marketo Support fix the issue? Marketo Support is not able to determine what content might be missing. Ultimately, you will need to determine if any elements are missing from your landing pages. Landing Page Verification Utility Overview Marketo recognizes that correction of this issue will take investigation. To help you identify pages that could have been impacted, we have built a new Landing Page Verification utility as a resource for you. The Landing Page Verification utility is a new back end utility that was developed specifically for this purpose. Since it is a back-end utility, it is not polished the way that products are inside the Marketo UI. However, it will identify all landing pages in your Marketo instance that could have been impacted by this service issue. Using the Landing Page Verification Utility This resource will allow you to generate a list of potentially affected landing pages, which will then need to be checked. Please note that landing pages not on this list may also be affected. Navigating to the Utility Since this utility is not built into the Marketo UI, access to it is different than accessing any other feature within Marketo. To access the Landing Page Verification utility, you must manually change the URL from within your Marketo instance. Here are the steps for navigating to it: 1. Navigate to your My Marketo page and take note of the URL in the address bar. In the example here, the URL is https://app-xxxx.marketo.com/#MM0A1 NOTE: In your own instance, the “xxxx” will be replaced by a different 4 digits such as ab07 or sj19 as examples. 2. Change the last section of the URL from #MM0A1 to supportTools/landingPageVerification and hit enter. The URL will change From: https://app-xxxx.marketo.com/#MM0A1 To: https://app-xxx.marketo.com/supportTools/landingPageVerification Reading the Results The first screen that the Landing Page Verification utility opens shows you whether you have pages impacted, and if so, how many. Zero Results Returned If the Landing Page Verification utility is unable to find any pages that are likely to be affected, you will see the page below indicating that no pages were impacted. Pages Impacted If the Landing Page Verification utility identifies pages that have been impacted, it will show how many pages there were. To view the full list of landing pages, check the box and click the Submit button. You’ll see a page like the one below that lists all pages that may be affected. Prioritizing Landing Pages While it’s best to assume that all landing pages in the list need to be checked, it’s possible that some were not affected. If there are many pages listed, it will be helpful to know which ones to prioritize to be checked first. Some landing pages are more likely to have been affected. Here are some things to consider when evaluating which pages should be checked first. Landing pages that have dynamic content are the most likely to be impacted and should be checked first Landing pages that have been edited after October 26, 2018 are likely to be impacted Landing Pages that are archived are not visible to your customers and probably don’t need to be checked Checking Your Pages The pages displayed in the Landing Page Verification utility are hyperlinked so that you can click through to those landing pages directly. When you get to the landing page in Marketo, you’ll need to check the live page to see if there are elements missing. The URL for the live page will be found at the bottom, along with a button to navigate directly to the approved page. Due to the nature of the issue, you may find some landing pages where the Landing Page Editor is missing some elements that still appear in the live page. This sometimes occurs when the live pages are cached versions of the landing page. By comparing these to the versions in the Landing Page Editor, you can use these cached versions to help identify which elements of the page need to be recreated. Recreating Landing Page Elements All missing landing page elements must be recreated. Once recreated, approve your landing page and verify that the live landing page has the correct elements in it. Where to Get Help Marketo’s Customer Support is ready to assist. Please contact us at https://support.marketo.com or through any of the methods listed here.
View full article
Issue Description Naming conventions of email in email performance report Issue Resolution Email reports will use an email's full label including the program it exists in. Although asset names cannot duplicate within Programs, they can be duplicated within the whole Instance and Email Performance Reports have access to emails from an entire instance. For example if you had two newsletter programs, both with an email named "October Newsletter" the full program name can help differentiate between the two. NL-2018-10-Technology Program.October Newsletter NL-2018-10-Industry Program.October Newsletter The email report will always display with the full email name including the program it was created in to avoid this confusion. Even within a specific Program Report, you can access all emails within the Instance.
View full article
Issue Description Example: Person A was sent an email from Marketo, clicked on a tracked link in an Email to a tracked web page, but the web page activity was recorded on Person B Issue Resolution This can happen if Person A and Person B are sharing a computer.  Prior to Person A clicking on the track link in the email to redirect to the tracked web page, Person B was already 'cookied' as a known lead on the same computer and web browser. In Marketo, once a lead becomes known, cookied and tracked on a web browser, any tracked web activities on that browser will be associated to the first cookied lead until the cookie is expired or deleted. Note: to confirm that Person A and Person B are using the same computer and web browser, you can check the details of the most recent web activities and compare if their User Agent and Client IP address is the same.
View full article
Issue How to identify records in Marketo that have not synced to Salesforce. Solution Create a smart list using the filter "SFDC Type is empty", as if the record in Marketo has synced to Salesforce, the SFDC Type will either be 'Lead' or 'Contact.' Be aware that there is also an 'SFDC Type' on the Opportunity object, so make sure you are looking at the Person object and not Opportunity.
View full article
Issue How to change or edit the Display Name of a Launchpoint service. Solution To change the installed service name, follow the below steps: 1. Go to Admin > Launchpoint 2. Select the service Under Installed services. 3. Go to Service Actions and click on "Edit Service" 4. Enter the name you would like to change in the space provided for "Display name" and click Save.
View full article
Issue In the attempt to create or invite a new user with email address "john@mail.com", the message appears "The user id is in use. Choose another email." even though the user was already deleted from the other instance it was being used in. Solution This message can appear as at the time the user "john@mail.com" was being created or invited to another instance, after deleting "john@mail.com" from another instance, the user was not completely deleted from the other instance. At times it can take about 5-15 minutes for a user to be completely deleted from the system, so allow some time before re-creating the user.
View full article
Issue Description Duplicate records were sent an email from an Email Program. Issue Resolution While Marketo prevents sending emails to duplicate records (i.e. same email address) via the same smart campaign, it is possible to send an email to duplicate record when there is A/B test configured for the email program. Specifically, one record can be sent an email from the test sample size while the duplicate record can be sent the email from the winner sample size [see For example, if there are two records for "mary@mail.com" in the audience, Mary can be sent two emails as follows: One record can be sent the email by qualifying for receiving the test from the sample size of the A/B test The other record can be sent the email by qualifying for receiving the winner from the sample size of the A/B test Note: sending the test and sending the winner utilizes individual campaigns which is why the systematic deduplication of emails within a smart campaign does not take effect for this scenario. To prevent this from occurring, exclude the duplicate records from the smart list of the email program.
View full article
Issue In Marketo, is it possible to change the way assets are referenced in Program, Smart Campaigns, Smart Lists, Emails and Reports, or how they are labelled or shown through reporting?     Solution No, it is not possible. The naming convention of assets and how it is used in Marketo is apart of the design of the product. When assets are created within a Program the naming convention is in the format of ProgramName.AssetName This is to identify where the asset resides in which program. Otherwise, multiple assets created with the same name would be causing confusion to the system when referenced in any of our Smart Campaigns, Smart Lists and Reports.
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
Issue You need to know the version of the munchkin script which is used by a particular web-page. Solution Munchkin version can be found by following the below steps: Open up your web browser Open developer console on your browser. Most other browsers use F12 to open developer tools. Visit the page on which the munchkin script is embedded Navigate to the network tab of the Developer console and search for munchkin You should find two attributes named “munchkin.js” and one of them will show a similar request URL as seen below munchkin.marketo.net/154/munchkin.js The numerical value 154 is the munchkin version. NOTE: If you are not able to finds anything over the network tab, we would suggest that you refresh the webpage which has the munchkin script is embedded on it  
View full article
Issue Authorized support contact unable to access the Support Portal Authorized support admin unable to view and manage list of authorized support contacts Authorized support contact unable to create a support case Authorized support contact unable to view list of cases     Solution Issue Resolution Contact marketocares@marketo.com - they are our dedicated team that handles issues with the Support Portal
View full article
Issue You may want to know which Salesforce fields a specific Marketo field is tied to as shown in this document. You will be able to see that the mappings are either not update or a few fields are missing that were created recently. Solution The Field Mapping that you are seeing under Admin -> Salesforce, as well as the mappings included on that export, are a historical log of how the mappings were set when the SFDC integration was originally implemented. Unfortunately, that page does not refresh when new fields are added, or when mappings are changed. We don't have any other tool that would allow us to export all of the field mappings in your instance as they are currently set either, so the best workaround for this is to check each of your fields within Admin -> Field Management. There is an idea in the Marketo Community specifically asking for this feature to be added and we would recommend that you add your vote to that so our product team sees that there is interest in getting this functionality added to Marketo in a future release.    
View full article
Guide for getting 'Email deliverability' set up
View full article
Issue Description You have created a Smart List with a filter for a date type field and you are using the constraints either “before” or “on or before” a particular date. However, records with empty value on those field get qualified. Issue Resolution When you create a Smart List using a date field filter (e.g., Date of Birth, SFDC Created Date) and use the “before” or “on or before” constraints, the Smart List will also include people who have no value in said date field. This is an expected behavior as  by default Null value is treated as a timestamp with a default value (e.g Jan 1 1900). This is similar to a token having default value and this is also mentioned as a caution within our knowledge base document over here. The work around is to use an addition filter or to make sure that the date value is populated for all the records. You can learn the importance of date stamping in this Champion blog post.
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: w3schools.com/tags/ref_urlencode.asp. For example: making this call, " <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
Issue There are a few Smart List configurations that could lead to a campaign failure if you are on Campaign V2. With the change to our new Smart Campaign processing system, some flow step configurations that would run in the old system can lead to campaign failures in the new system. Below are a few examples of configurations that can lead to Smart Campaign failures: Solution Examples: Date field is today Scenario: You have a flow step choice that filters against a Date field. The flow step choice is "<datefield> is TODAY" Solution: Instead of using the condition "IS" use the condition "in timeframe" instead.   Score change to decimal Scenario: The smart campaign has a flow step that changes a score to a number with a decimal eg. 100.12 Solution: Scores are integers, so this value needs to be changed to an integer eg. 100   Empty Choice Scenario: A flow step has multiple choices, one of the choices (not the default choice) is empty, partially filled out, or has no value listed. Solution: Empty or incomplete choices in flow steps are no longer supported, these choices need to either be removed or filled out completely  
View full article
Issue Description When there is a change to a field in your CRM that is mapped to a Marketo score type field, the next time the sync processes the change will be reverted and there will be a "Sync Person Updates" activity logged showing that the original value got pushed back from Marketo to the CRM. Issue Resolution Score type fields are designed to be managed solely by Marketo, since that is a unique field type to our system.  Scoring is intended to be handled by the scoring campaigns that you set up in Marketo, and pushed to the CRM if necessary. If you have a score field that you intend to put processes in place where your CRM will be updating the values, simply make sure that the Marketo field that it is mapped to is an Integer type field. Who This Solution Applies To All instances with a native CRM integration (SFDC or MSD)
View full article
The content of this article has been moved to: https://nation.marketo.com/t5/Support-Blogs/Partner-Support-Submitting-cases-on-behalf-of-your-Customers/ba-p/299853
View full article