Product Communities

Issue DescriptionImporting a program from one subscription to another is failing and is returning the following error sent via email:Marketo encountered an error while importing [Program Name]The token "lead.First Name" is not available in the destination subscription. It is either a custom field that you have to create or need to be synced from your CRM system, if you use one.Issue ResolutionCheck if there is any malformed lead.First Name token in emailCheck if there is any malformed lead.First Name token in email template used by the email(s) in the programCheck if there is any malformed lead.First Name token within a program tokenCheck if there is any malformed lead.First Name token within smart campaign flow step(s)This error has been known to occur when the email template had a lead token coded as follows, with a line break between 'First' and 'Name':{{lead. FirstName}}Note: In this scenario, the error message received via email is actually referring to the token in the email temp

Effective March 4, 2019, DTM and Launch will no longer support TLS 1.0 in libraries being hosted by Adobe.  TLS 1.1 will be the minimum allowed version.This change is being made at the request of our customers so that these solutions can be in compliance with certain data security standards required by companies who do credit card processing.Effectively this means browsers that do not support at least TLS 1.1 will no longer be able to retrieve a hosted library over an HTTPS connection - thus anything implemented within the DTM or Launch library will no longer be functional on your site in those browsers.  Browsers that do not support any TLS versions above 1.0 are:Chrome 21 and below (current version is 72)Safari 7 and below (current version is 12)Firefox 23 and below (current version is 65)IE 10 and belowAfter this change, TLS 1.1 will be the minimum supported TLS version.  More info on browser support for specific browser versions can be found here.We expect the impact to be immateri

Issue DescriptionIs there any limit to number of engagement programs that can added to a Marketo instance. If yes, is there a way to increase this limit.Issue Resolution An instance is limited to 100 active engagement programs. Inactive engagement programs are not limited.Deactivate the engagement programs that are not in use under Setup tab of the program.Note: There is a finite resource for active engagement programs, as they inherently take more processing power and storage requirements. We reserve increasing the limit of active Engagement Programs for those use cases that have done all possible preventative steps to ensure that the 100 programs that are in use are properly utilized and necessary. Is this article helpful ?YesNo

Issue DescriptionYou want to create a field that will grab the web page the form was filled out on and add this as a token in an alert that goes to sales when a form is filled out.Issue Resolution This can be achieved either through a Smart Campaign or the JS API code. The code is more efficient because it doesn't mean another trigger is active in your instance.Smart campaign:You'll want to create a smart campaign with Smart List - Fills Out Formand Flow - Change Data Value, [your field name], New Attribute is {{trigger.Web Page}}You would need to reference the trigger token in the alert email so the team knows what product page the end user filled out the form on.Code: (Embedded Form)This can be done with a hidden field.MktoForms2.loadForm("//app-**01.marketo.com", "***-***-***", 148,    function(form)     {        form.addHiddenFields({ LastFormURL : document.location.href })        });The asterisks represent your company's Marketo data (your Munchkin ID and Marketo instance). Your d

You can add a tool tip or instruction to a field on your Marketo form so that users have more information about what you are asking them to input.1. Select a form and click on Edit Form.2. Select the field you want to add an instruction to.3. Under Form Properties, Field Specific, enter the Instructions.Awesome work! Now when a lead hovers the cursor over the form field, the tool tip or instructions will be displayed.Make sure to approve the landing page that this form is on so the changes are live.

OverviewGoToWebinar is changing their authentication protocol used for API access. Their legacy protocol, OAuth v1.0, will no longer be used after January 31, 2019, and all services accessing GoToWebinar (Marketo) will be required to use the new authentication protocol, OAuth v2.0.Marketo has already updated our system to utilize the new OAuth v2.0 authentication protocol for new login authentication. All newly initiated service authentications between Marketo and GoToWebinar will use OAuth v2.0. However, all existing GoToWebinar services currently logged in and in use now must be reauthenticated manually.All customers who use GoToWebinar must reauthenticate each of the logins for these services in your Marketo instance by navigating to Admin > LaunchPoint. Any API calls still using OAuth v1.0 after January 31 will fail. This will result in statuses not being shared between Marketo and GoToWebinar and will prevent users from syncing Event programs with a GoToWebinar event.FAQWhy is

Issue DescriptionAfter running an A/B test, some Lead records appear to have received both Test and Winner. Issue Resolution In an A/B test, the sample size of the audience is sent the variants, and then for the winner: the entire audience minus the test audience is sent the Winning email.  So let's say that you received both Test and Winner. This means you have duplicate records in the database.  Marketo is designed to not send duplicate leads the same email at the same time. So one of the duplicates is qualified for the Test, and then when the Winner is sent, it's the total audience minus the test audience, the Winner is sent to the duplicate record. This above situation can apply to Lead Records as well, because of duplicates with the same email address, but also duplicate records that may have a FWD set up between them (record B emails FWD to Record A email address). Because this is expected from the design decision, the resolution is to deduplicate your database.Is this article he

The Ideas section of the Launch Forum is one of the primary ways that the Launch product team receives feature requests from the community at large and we really appreciate all of our Launch users participating there.To date, we haven't been very organized about how we treated these ideas and how we would respond to them.  We're sorry about that.  And we're going to do better.I'd like to take a few moments to describe the process that we're going to use to review the ideas that are submitted here, what each of the different status labels means, and how they transition from one to the other.Idea Review ProcessWith the current size of the community (and expected future growth), the PM team cannot review every single idea that comes in.  We have established a vote threshold and once an idea exceeds that threshold, the PM team will review the item and begin to move it through the workflow below.  The threshold will increase over time as community engagement grows.At lea

While viewing a published landing page with a form, you can open it up directly in Marketo with this little tool.Note: This tool is not officially supported.     1. To install, go to marketo.com/tools/.     2. Drag Open LP -> MKTO onto your browser bookmarks bar.Tip: To show the browser bookmarks bar: Chrome: View > Always Show Bookmarks Bar Firefox: View > Toolbars > Bookmarks Toolbar      3. That's it. Just click the Open LP -> MKTO bookmark when viewing a published landing page with a form.     4. And you'll be taken to the landing page in Marketo.

OverviewIt can be difficult sometimes to know how many trigger campaigns you have running or where they’re located. Marketo can show you where they all are inside of the Campaign Inspector. This article will show you where to find Campaign Inspector and what to look for when you’re going through it. Turning on Campaign InspectorCampaign Inspector isn’t enabled in all Marketo instances by default, but it can be switched on pretty quickly. To turn on Campaign Inspector:1. Log in to your Marketo instance.2. Click on the Admin link at the top of the window.3. Click on Treasure Chest.4. On the Campaign Inspector section, click EDIT.5. In the dialog window that appears, check the Enabled box and click the Save button.If you have trouble turning on Campaign Inspector, please Contact Marketo Support Finding Campaign InspectorThe Campaign Inspector is a tab located inside of Marketing Activities. Once it’s enabled, you will find it right next to the Marketing Activities tab.What does Campaign I

Issue DescriptionThe "View In Browser" link gives an error "Customer does not belong to any POD" when clicked in the Email Preview or in exported email HTML.Issue Resolution When you Preview an Email you are viewing the layout of the email, but system tokens will not function. This is also true of exported HTML. When you send a Sample Email, you can test the the system tokens {{system.viewAsWebpageLink}} as though you were the customer.

Issue DescriptionYou are receiving this error from your GoToWebinar Launchpoint Service: API Error: Authentication succeeded, but access to the requested resource is denied.This error can occur either in Launchpoint Tab's Service details in Admin or when trying to Refresh an Event Program and selecting the service in the drop down menu.Issue Resolution This error "API Error: Authentication succeeded, but access to the requested resource is denied." is a response from GoToWebinar when Marketo sends an API Call to retrieve the Webinar Meeting details.What is the main cause of this?This is mainly a licensing issue with the Account Credentials specified in the Launchpoint service.The GoToWebinar account does not have a GoToWebinar License and therefore, the account has successfully "Authenticated" and the Requested resource (GoToWebinar Meeting Details) were denied as it does not have access to GoToWebinar features.How to check if you have a license? Login into the home page of GoToWebinar

  *Please Note* these group sessions are discontinued as of Thursday, July 1, 2021.    Offered exclusively to new Marketo Engage launch pack customers, this series of interactive group discussions offer an open forum to learn best practices from a Marketo expert and your peers.    Marketo Group Consulting Webinars are one-hour virtual meetings connecting you with a Marketo expert to expand and improve your knowledge and skills related to marketing strategy and Marketo tactical execution. Each session will include knowledge sharing from Marketo followed by an open Q&A.    

Issue DescriptionYou try to approve a segmentation and get the error message of "No possible draft" even when there is a draft in place.Issue ResolutionThis error message can be a little misleading, as there usually is a draft in place.Check to make sure that segments in the draft have smart list filters in place and that there are no empty values in the smart lists. An example of an empty value would be "First Name is ____" instead of "First Name is Joe."

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

SummaryWe 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 QuestionsWho 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 fo

SummaryA service issue has been identified that can potentially cause duplicate leads to be generated in Marketo for customers using Microsoft Dynamics (MSD) CRM. This issue only applies to customers using MSD 2016, and only when upgrading to MSD version 9. Who is ImpactedAll customers using the native CRM Sync between Marketo and MSD 2016  Already Impacted: Customers using MSD  2016 Version 9 with Marketo Lead Management (MLM) solution version 4.0.0.23 or lower Potentially Impacted: Customers using MSD 2016 version 8 or lower who plan to upgrade to version 9The issue of duplicate leads being created occurs when the MSD instance is upgraded to version 9All customers who have already upgraded to MSD v9 are already impactedIf you have MSD but have not yet upgraded to v9, you are not yet impacted, but could be by upgrading to MSD v9Who is Not ImpactedCustomers using MSD On Premises CRM instances Customers using Dynamics 2011, Dynamics 2013, or Dynamics 2015Customers with Salesfo

Issue DescriptionNaming conventions of email in email performance reportIssue 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 NewsletterNL-2018-10-Industry Program.October NewsletterThe 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.

Issue DescriptionDuplicate 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 testThe other record can be sent the email by qualifying for receiving the winner from the sample size of the A/B testNote: 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 p

Issue DescriptionExample: 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 BIssue ResolutionThis 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.

Issue DescriptionYou 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.

We're testing a new behavior with the way that rules execute in the browser.This post will cover the problem we're solving, the solution that we'd like help testing, and the things you should watch out for as you test.  We'll then provide instructions for testing the behavior in your own browser as well as rolling it out to a portion (or all) of your audience.1) The ProblemCurrently, when a rule is triggered, Launch will execute the rule actions in order, but it does not wait for one to finish before the next one starts.This can create problems when the rule action actually does something asynchronous.  This is most common in the case of custom code where the network retrieval of the custom code is done asynchronously, so subsequent actions are often completed before the custom code is retrieved and executed.2) Solution in TestingTurbine is Launch's client-side rules engine.  Turbine is currently shipping with a hidden behavior that you can enable.  Once enabled, rule conditions and ru

Issue DescriptionCustomers based in our Sydney datacenter experienced a service issue which caused an intermittent disruption in email sends beginning 10:30 AM AEST local time on November 12, 2018. This issue was resolved at 1:00 pm AEST and all emails are now sending normally. No customers outside of the Sydney datacenter were impacted.During the impacted time frame, some email sends were lost and will not be delivered. The issue occurred intermittently during the affected time, so some emails were sent successfully, while others were not.This documentation provides details on how to identify the impacted lead records.Identifying Affected LeadsSymptomsAll lead records that were sent emails during the impacted time will show an "Email Sent" activity (as per normal behavior)Leads that were not impacted and successfully had emails sent will show the corresponding "Email Delivered" or "Email Bounced" activities (as per normal behavior)However, the impacted leads that emails did not send t

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

Issue DescriptionIn an attempt to approve an email, a 'Not Allowed' error message is being displayed with the following details:{{lead.Email Address}} : Token key not foundIssue Resolution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}'Check that the field name of the token does not have any incorrect spelling (e.g. Email Address)If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.