Knowledgebase

Sort by:
Issue You or your customer have a global block on emails sent from servers with the domain "mktomail.com." You would like to keep the global block but allow email from your own Marketo instance to pass through.   Solution The return-path (or envelope_from) in the header of most Marketo emails includes the domain "mktomail.com." Some email servers may have a global block on this domain which prevents delivery of your Marketo emails. There are two options for bypassing this global block. Contact your account manager to see about added the Branded Envelope_From feature to your instance. This will replace the "mktomail.com" domain with a domain of your choice. Have the email admin add a Regex version of your return-path/envelope_from to the Allow List.  Which Regex you use will depend on which datacenter houses your instance. To determine the datacenter, look at the URL for your Marketo instance and see which letters come after the "https://app-". "SJ" is for San Jose, "AB" is Ashburn, "E" is London, "SN" is Sydney The Regex you will use is as follows: San Jose datacenter - "munchkin_id.(\d+.)*\d+@em-sj-77.mktomail.com" London datacenter - "munchkin_id.(\d+.)*\d+@eu-lon-188.mktomail.com" Ashburn datacenter - "munchkin_id.(\d+.)*\d+@potomac1050.mktomail.com" Sydney datacenter - "munchkin_id.(\d+.)*\d+@snsmtp.mktomail.com" Netherlands datacenter - "munchkin_id.(\d+.)*\d+@em-nld1-01.mktomail.com"    Replace "munchkin_id" with the Munchkin ID for your Marketo instance. This operates as the unique identifier to allow only email from your Marketo through the block. Other email from the "mktomail.com" domain will still be blocked.    
View full article
Issue You are trying to add a new stream to an Engagement Program but get an error stating that your program has reached maximum number of streams per program. Solution Due to engineering constraints and as well as to have better user experience, we have limited the number of Engagement Program Streams per program to 25.  When you try to add  26 th stream, you will now get the error message “You have reached the maximum number of streams. Create another program”. So the solution is to create a separate Engagement Program and a Smart Campaign that moves leads from the original Engagement Program to the new one.      
View full article
Issue Description You receive an error in ToutApp - "IMAP access is disabled for your domain. Please contact your domain administrator for questions about this feature. (Failure)" Issue Resolution This due to an invalid Gmail connection For this error message to be resolved, we recommend looping in with your Gmail Administrator regarding the IMAP access of your domain and whether or not it can be enabled. See the link below for additional reference on this for your Gmail Administrator: https://support.google.com/a/answer/105694?hl=en
View full article
Issue You want to add multiple values to a Smart List filter as described here: https://docs.marketo.com/display/public/DOCS/Add+Multiple+Values+to+a+Smart+List+Filter . However, when you go to do so for a field that has a type of "Text" you are not able to add multiple values. Solution This is expected behavior for Marketo Text fields. As a workaround, you can add the same filter to the Smart List multiple times, one for each value you want included.   
View full article
Issue Description How to use a script token to calculate and populate the number of years since a given date Issue Resolution This can be achieved by using a velocity (email script) token: #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/New_York") )  #set( $defaultLocale = $date.getLocale() )  #set( $calNow = $date.getCalendar() )  #set( $ret = $calNow.setTimeZone($defaultTimeZone) )  #set( $calConst = $field.in($calNow) )  #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" )  #set( $ISO8601DateOnly = "yyyy-MM-dd" )  #set( $calJoinDate = $convert.toCalendar(  $convert.parseDate(      $lead.JoinDate,       $ISO8601DateOnly,       $defaultLocale,       $defaultTimeZone     )  ) )  #set( $differenceInYears = $date.difference($calJoinDate,$calNow ).getYears() )  #set( $friendlyLabel = $display.plural($convert.toInteger($differenceInYears),"year") )  You joined us ${differenceInYears} ${friendlyLabel} ago!  Where $lead.JoinDate is the joining date. More at http://blog.teknkl.com/velocity-days-and-weeks/
View full article
Issue Issue Description Unable to create a subscription for static list.     Solution Issue Resolution While Subscriptions are not directly available for static lists and are only for Smart Lists and reports, you can create a Smart List that uses the filter 'Member of List' and then create the subscription on the Smart List instead.
View full article
Issue Attempting to use Champion/Challenger tests in nested programs within engagement programs fails to run test. Solution Champion/Challenger email tests must be inserted directly within the email stream as an asset. The testing functionality is based on being triggered which is the process of a stream content cast. When the email is nested in a smart campaign within a program, this campaign executes as a batch campaign and will see inconsistent behavior for Champion/Challenger testing.  
View full article
Issue: When I try to approve an email I get the following error: Error approving Email Name - Sending IP is empty or not valid This is a article attached image Solution: You likely have multiple dedicated IPs and you did not choose which one to send this email from. 1. Edit Draft of the email in question. 2. Select which IP Address you want this email to sent from and click Save. This is a article attached image 3. Close the email editor and under Email Actions click on Approve.      
View full article
Issue Is there a way to change the order of tags values, to chose the default values that display when you create a new program? Solution Issue Resolution Tags are sorted in alphabetical order, so the default always ends up being the first alphabetical choice. So for a workaround to make a 'default', you could have it start with the letter A. Example: A-Tag Value (default) B-Tag Value C-Tag Value        
View full article
Issue Error when linking/re-authorizing Marketo Launchpoint service with Google AdWords: "Oops.. Something went wrong, please contact Marketo Support" Solution Before attempting to create the Launchpoint service for Google Adwords again, the Marketo App in the Google account must first be uninstalled to avoid receiving the error again. This can be done by going into their Gmail account settings: https://myaccount.google.com/permissions Once the Marketo App is removed from the Google account, please try to recreate the Launchpoint service for Google Adwords in Marketo.        
View full article
Issue Description How do Revenue Cycle Explorer filters operate? Issue Resolution RCE Filters operate in the following ways: Select from a List (Includes, Excludes) -- This filter type within RCE will let you include or exclude preset values Match a specific string (Contains, Does not Contain) -- This filter type will let you enter a free form value such as Contains "We" to find statuses which may have Web in them. The not-contains would filter anyone who did not have "We" in the status. On either filter you can select Multiple Values. Within the Match a Specific String function click on [+] and add another value option and this will then add additional string areas to use. A example would be Status contains: Reg Regis Registered Registered - Web etc.. As you can see you can match to one of many values! Who This Solution Applies To Customers with Revenue Explorer or Email Explorer
View full article
Sometimes you need to give your sales team access to the powerful insight Sales Insight gives into Marketo but would rather some users not be able to take some actions such as sending Marketo Emails or trigger Marketo Campaigns.  You can use SFDC Permission Sets in to give or remove access to the VisualForce pages that power the actions Sales Insight can take. Note: Modifying permissions to Sales Insight components from their documented configuration may cause undesired and unpredictable behavior in your Salesforce instance.  Marketo Support can only support the default documented install configuration MSI for Salesforce - Marketo Docs - Product Docs.  Make these changes at your own risk and fully test any modification in a sandbox environment before deploying to your production environment. Create a new permission set or modify and existing permission set in Salesforce.  Documentation on SFDC Permission Sets can be found here.​ Edit Visualforce Page Access. Remove (if restricting access) or add (if adding access) the desired Sales Insight VisualForce elements.  For example, mkto_si.Send_Marketo_Email - access to the Send Marketo Email feature from an individual Lead/Contact mkto_si.Send_Contact_Marketo_Email - access to the Send Marketo Email feature from a Contact list view mkto_si.Send_Lead_Marketo_Email - access to the Send Marketo Email feature from a Contact list view mkto_si.Marketo_Lead_Detail - access to the View in Marketo feature mkto_si.Add_to_Marketo_Campaign - access to the Add to Marketo Campaign feature from an individual Lead/Contact mkto_si.Add_Contact_to_Marketo_Campaign - access to Add to Marketo Campaign from a Contact list view mkto_si.Add_Lead_to_Marketo_Campaign - access to Add to Marketo Campaign from a Lead list view Assign the Permission Set as desired to your users. SFDC users without permissions to specific Sales Insight features will still be able to choose the associated actions from their drop down menu.  However, they will receive a permissions error after clicking the "Go!" button. Is this article helpful ? YesNo
View full article
Adobe Marketo offers a number of ways to contact Marketo Support directly for assistance from our different support regions. Further details about your Adobe Success Plan can be found HERE. Note: If your Marketo Instance and Users have been migrated to Admin Console, refer to this Admin Console Overview page for managing the Adobe entitlements across your organization and to engage Marketo Support.   Marketo Support Portal (https://support.marketo.com)   The Marketo Support Portal features a web form to submit support cases to Marketo Support. The form provides Authorized Support contacts the ability to provide details on the support issue that allows Marketo Support to efficiently and effectively assign your case to the best suited available support engineer. We encourage you to leverage our Best Practices when submitting your case to Marketo Support.   Support Services – Regions, Hours, and Languages Authorized Support contacts can engage Marketo Support by calling one of our Adobe Enterprise Phone Numbers for your region. Live Telephone and Online Technical Support Priority 1 incidents: 24x7x365 via phone or online support case Priority 2-4 incidents: Support available during regional business hours via chat or online support case. Regional Business Hours Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents. If Adobe is contacted for support by someone other than the designated Named Support Contacts, Adobe may request that that the support case be resubmitted by a Named Support Contact. Languages Japanese language support is available during Japanese regional business hours, excluding holidays or Adobe days off. Japanese support is not available for Adobe Commerce. With the above exception, all Support will only be provided in English. Support Access Customer will grant Adobe Support access to applicable customer systems via remote support tools controlled by Adobe for the purpose of troubleshooting and support services. Regional Business Hours for Support Applicable regional business hours are based on the billing address in the Sales Order or purchasing documents.   Americas Europe, Middle East & Africa Asia Pacific Japan 6 am – 5:30 pm 9 am – 5 pm 9 am – 5 pm 9 am – 5 pm  
View full article
Issue You would like to customize Forward to a Friend emails to add personalized content. Solution You can in fact customize the look and feel of the Forward to Friend form using a combo of Velocity and JavaScript. This article describes how: http://blog.teknkl.com/building-a-better-forward-to-friend-with-velocity/  
View full article
**Nov. 11, 2019 update: In a continued effort to integrate with Adobe's release structure, we are shifting the deprecation of TLS 1.0 and TLS 1.1 to January 13, 2020. To align with Adobe’s world-class standard for security, we will be deprecating support for Transport Layer Security (TLS) 1.0 and 1.1 starting December 13, 2019 January 13,2020.  Systems integrating with Marketo that are not compliant with 1.2 protocol could potentially lose access to Marketo Engage services.  To maintain your Marketo Engage access, please ensure that all client systems are TLS 1.2 compliant before January 13, 2020. For a list of TLS 1.2 compliant browsers and frameworks, see the tables at the bottom of this communication.   What is Transport Layer Security (TLS)?  Transport Layer Security (TLS) is a security protocol that provides privacy and data integrity between two communicating applications. It is deployed widely for web browsers and other applications that require data to be securely exchanged over a network. TLS includes two layers: the TLS Record protocol and the TLS Handshake protocol. The Record protocol provides connection security. The Handshake protocol enables the server and client to authenticate each other and negotiate encryption algorithms and cryptographic keys before data exchange.    Why is Marketo Engage making this change?  Most requests for Marketo Engage web services originate from TLS 1.2 compliant systems, with low traffic from TLS 1.0 and 1.1 systems. TLS 1.0 was first published in 1999, with newer versions 1.1 in 2006, and 1.2 in 2008. As technologies age, security threats evolve, and so must industry standards. To stay aligned and protect our systems from security risks identified with older TLS versions, we are mandating a minimum TLS 1.2 supported connection to ensure secure connections. There have been documented attacks against TLS 1.0 using an older encryption method and the older versions are more vulnerable than TLS 1.2. For more information, see Attacks Against TLS/SSL.   When will this change happen?  TLS 1.0 and TLS 1.1 deprecation will take place on January 13, 2020.  After the date of deprecation, you will not be able to connect to Marketo Engage services using browsers or applications not compatible with TLS 1.2.    Marketo Engage encourages users to quickly abandon older versions of TLS to avoid exposure to security vulnerabilities.      How does TLS affect you?  Marketo Engage services are web-based and can only be engaged through a secure network connection.  TLS helps ensure a secure and reliable connection between your browser or server and Marketo web services, which includes anything that uses Marketo’s API, such as REST, SOAP, Munchkin, RTP, Mobile, and more.   As technology evolves, security standards are upgraded to ensure higher levels of privacy and data integrity.  However, older applications are not updated to include the latest standards.  As the acceptable level of security rises, these older, less secure applications are left behind.    To be able to connect to Marketo Engage services, update your browsers and application frameworks to a version that supports TLS 1.2.    How does TLS affect your customers?  Marketo Engage landing pages will be served to your visitors through TLS 1.2 secured connections.  Any browser updated since late 2013 (except Chrome, updated since 2017) will be TLS 1.2 compliant; further, Apple, Google, Microsoft, and Mozilla have all announced their plan to completely disable TLS 1.0 & 1.1 support by the first half of 2020, so we expect very minimal impact to visitors. If visitors report a loss of connectivity to Marketo Engage hosted landing pages as a result of this change, they will need to update to a compatible browser version.    What error message will return to a non-compliant connection?  The exact error messaging returned depends on the browser or application framework being used to connect to Marketo Engage web services.  Some examples include but are not limited to:  Unable to connect to the service  Service not available  Error in connection  To resolve these errors, the browser or application framework must be updated to a version compatible with TLS 1.2.    TLS 1.2 Compatibility  Desktop Browsers  Desktop Browser  Compatible Versions  Release Date Google Chrome  V30+  March 20, 2017 Mozilla Firefox  V25+  October 29, 2013 Internet Explorer  IE 11  October 17, 2013 Microsoft Edge  All versions    Opera  V17+  October 8, 2013 Apple Safari  V7+  October 22, 2013   Mobile Browsers  Mobile Browser  Compatible Versions  Google Android OS Browser Android 5.0+  Chrome for Android  V30+  Firefox for mobile  V27+  Opera Mobile  V57+  Apple Safari  IOS 5+    Application Frameworks  Java  .NET  OpenSSL  Java 8, or later  .NET 4.6, or later  OpenSSL 1.01, or later  Java 7, with TLS 1.2 enabled in app  .NET 4.5, with TLS 1.2 enabled in app       
View full article
Issue: I need to use a comma in my value list, but Marketo uses the comma as the break between different values. Select One, Not at this time, Yes, within 30 days, Yes, within 60 days Solution: Begin your value list with "\|||\" and use "|||" instead of a comma between each value. \|||\Select One|||Not at this time|||Yes, within 30 days|||Yes, within 60 days Nice work! You can now use commas in the text of your Value List.
View full article
Issue The deep link in a Marketo email does not redirect to the designated App.   Solution By design in Marketo, when tracking is enabled for a link, the link will be wrapped with a tracking link like 'http://test.website.com/[unique sequence of characters]'. So when a tracked link is clicked, the link 'http://test.website.com/[unique sequence of characters]' is first loaded in a browser then redirects to the actual link in the same browser. Therefore, as some deep link configuration can depend on the actual link first loading, a tracked link in Marketo does not redirect to the App. One workaround here is to disable Marketo tracking link so that the deep link will redirect to the App. However, the trade-off of this is that the click link activity will not be recorded in Marketo.
View full article
When a lead fills out a Marketo form, some validation messages are automatically built in. "This field is required." "Please enter a valid email address." "Please  enter a valid phone number." "Please select a value for this field" "Please wait" (appears after the lead submits the form). You may wish to customize these messages either because you are creating a form in a different language or simply because you wish to change the wording. 1. Open up your form for editing. 2. Select the language you wish to use for error messages on your form. If you don't see your language you can Customize the Text of Form Validation Messages. That's it. Leads will now see error messages in the language of your choice.
View full article
Issue Description You would like to export your ToutApp contacts. Issue Resolution Tout doesn't support exporting capabilities at this time.
View full article
1. Go to the Design Studio area. 2. Click on Images and Files, then click next to the file name you want to replace; it will highlight.       Tip You can also Search Uploaded Images or Files.   Is this article helpful ? YesNo  
View full article