Knowledgebase

Sort by:
Issue When you go through the "Add to Named Account" or "Remove from Named Account" flow actions, those changes sometimes aren't immediately reflected in the named accounts' dashboards.     Solution ABM runs a recalculation task every 30 minutes to check for any changes in account scores, membership count, opportunity count, and pipeline for all of your existing Named Accounts. When you run a flow action to add or remove people from your named accounts, those changes will be reflected immediately in a smart list for "Member of Named Account". However, ABM can take up to 30 minutes to update, until the changes are captured by the next recalculation. If you are seeing a delay longer than an hour for your dashboards to update, submit a ticket to Marketo Support, and they can force a recalculation and investigate what could be causing the delay.   Who This Solution Applies To All clients with ABM.
View full article
Issue Description The call Webhook flow is successful but the Marketo field mapped is not updated. Issue Resolution Marketo can translate data received by a Webhook to a lead field. If the fields are not getting updated: Check if the Response types are JSON or XML. The correct response type must be selected in order to map properties of the response back to lead fields in Marketo Check if the fields are blocked from Updates in field management. If the response type is XML, all elements in the XML hierarchy must be referenced in the mapping. For example: If the XML is: <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">     <soap:Body>         <GetDealerByPostcodeResponse xmlns="http://webservices.hmca.com.au/DealerLocatorMapService/">             <GetDealerByPostcodeResult>                 <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">                     <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:Locale="">                         <xs:complexType>                             <xs:choice minOccurs="0" maxOccurs="unbounded">                                 <xs:element name="Table">                                     <xs:complexType>                                         <xs:sequence>                                             <xs:element name="dl_tradingName" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_physicalstreetname" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_physicalsuburb" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_physicalstate" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_physicalpostcode" type="xs:string" minOccurs="0" />                                             <xs:element name="pcmaplat" type="xs:float" minOccurs="0" />                                             <xs:element name="pcmaplng" type="xs:float" minOccurs="0" />                                             <xs:element name="maplat" type="xs:float" minOccurs="0" />                                             <xs:element name="maplng" type="xs:float" minOccurs="0" />                                             <xs:element name="distance" type="xs:float" minOccurs="0" />                                             <xs:element name="dl_phonenumber" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_faxnumber" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_emailaddress" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_code" type="xs:string" minOccurs="0" />                                             <xs:element name="pd_postcode" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_webaddress" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_dealershipregion" type="xs:string" minOccurs="0" />                                             <xs:element name="dl_deliverycharge" type="xs:float" minOccurs="0" />                                             <xs:element name="dl_regionstate" type="xs:string" minOccurs="0" />                                             <xs:element name="BkAServiceDesktop" type="xs:string" minOccurs="0" />                                             <xs:element name="NewWinBkAServiceDesktop" type="xs:string" minOccurs="0" />                                             <xs:element name="BkAServiceMobile" type="xs:string" minOccurs="0" />                                             <xs:element name="NewWinBkAServiceMobile" type="xs:string" minOccurs="0" />                                         </xs:sequence>                                     </xs:complexType>                                 </xs:element>                             </xs:choice>                         </xs:complexType>                     </xs:element>                 </xs:schema>                 <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">                     <NewDataSet xmlns="">                         <Table diffgr:id="Table1" msdata:rowOrder="0">                             <dl_tradingName>Wild West Hyundai</dl_tradingName> The Response attribute must be: soap:Envelope.soap:Body.GetDealerByPostcodeResponse.GetDealerByPostcodeResult.diffgr:diffgram.NewDataSet.Table.dl_tradingName All the elements need to be referenced in the top down approach.
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 Description A lead ran through a smart campaign and should have been sent a push notification but there is no activity of this happening even though the lead is a member of the campaign. Issue Resolution Assuming other leads are receiving the push notification (which suggests the app itself is not to blame) the first thing to check is the lead record itself. If the lead is marked as Marketing Suspended or Black Listed, this will prevent the record from receiving a push notification. Mark these fields as "False" and send the record through the campaign again, the lead should now be sent the push notification. Who This Solution Applies To ​Customers using Marketo's mobile app integration
View full article
Issue You would like to reposition the submit button for your Marketo form Solution When editing a Marketo Form, the initial section with the fields displayed will have the submit button at the bottom. You are able to click and drag the button to reposition where you wish the button to be.    
View full article
Issue Is it possible to integrate multiple social media accounts with Marketo for integration with services such as Facebook and Google? Solution There is  only one LaunchPoint service for each, but multiple accounts can be referenced in : Lead gen forms - Linkedln Custom audiences - Facebook    
View full article
Issue When attempting to import a list in the UI, an error appears that states "Invalid encoding" and the import does not complete. Root Cause Marketo requires the import CSV file be encoded with one of the following: UTF-8, UTF-16, Shift-JIS, or EUC-JP. As next steps: Re-save the file, for example in Excel as file format CSV UTF-8, with the correct encoding. Then re-try the import into Marketo. If the error persists, contact Marketo Support.
View full article
Issue New person records are missing data and only contain Email Address. Environment On24 Event Partner Launchpoint Integration Solution When Marketo pulls the Attendance Report, for On24 Events through the On24 Launchpoint Event Partner integration, as documented here: ON24 Event Registration Updates | Adobe Marketo Engage For any net new records to Marketo (people who registered and attended the event outside of Marketo), Marketo will only sync the Email Address and Attendance Status. This will result in records in Marketo that do not have complete data from On24, such as First and Last Name. To avoid this scenario, it is recommended that all records are properly registered for the Event through Marketo, using Marketo Forms and Registration Campaigns as documented here: Create Child Campaigns and Local Assets | Adobe Marketo Engage
View full article
Issue Description When using a velocity scripted my.token, the default value is not being used if the field the velocity script is pointing to is not populated. Issue Resolution The reason for this is because velocity script isn't designed to consider a default value the way that a lead token would. It's designed to execute the code to provide the rendered value. Although the UI specifies to look for a default, that's ignored by design since the code itself is only looking for the value for those leads. If the goal is for it to evaluate and provide a known value, otherwise then render a specified default, that needs to be built into the velocity script code itself. Who This Solution Applies To
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 Description When selecting an image to display on a landing page, the image shows as a featureless grey box. There are also spaces in the image's file name. Issue Resolution Ensure that there are no spaces in the image's file name in Marketo. If there are, remove the spaces from the file name and re-upload. 
View full article
When a deactivated record is reactivated Microsoft Dynamics CRM, the following behavior occurs in Marketo: If the record was initially deactivated because of a merge or a conversion, we will create a new record in Marketo when the record is deactivated. If any other record is reactivated, Marketo will change the “Microsoft is Deleted” flag of the associated record in Marketo is set to false.
View full article
Issue You need to set Marketo passwords to expire in accordance with your security policies. Solution You can absolutely set the passwords to expire! Simply go to Admin > Login Settings. You can then click edit on Security Settings and change the Expiration from Never to the option that fits your needs.    
View full article
Summary When attempting to approve snippet error Access Token is Invalid appears. Have the customer sign out and sign back in. Seems maybe they got logged out somehow. Issue When attempting to approve a snippet you receive  "Access Token Is Invalid" error. Solution The error can occur when your internet browser logs you out of Marketo in the background. To resolve, sign back in to Marketo and retry the approval. 
View full article
When the owner of a record is changed in Dynamics, this action will be mirrored in Marketo in the next sync cycle.
View full article
Issue You need to revert a data value change for a field on multiple leads. Solution There is no way through the UI to "undo" a data value change (unless it was a boolean field, in which case there are only two possible values.)  You can certainly use a Smart List to identify whose values have changed, but there no way to go back to the old value (unless it's stored elsewhere in another field or through another data store, along with the API). However, you can use the API to extract the data value change activity from the activity log, which would include the old and new values, extract the original values, then use the API to rewrite the old values back to the lead record. http://developers.marketo.com/rest-api/lead-database/activities/#data_value_changes      
View full article
Issue An anonymous lead triggers a Smart Campaign that includes a Change Program Status flow step.  Instead of adding the anonymous lead to the program, you get an error, "Cannot add an anonymous lead to a program."     Solution Anonymous leads can not be added to programs, but they can trigger Smart Campaigns that include a Visits Web Page trigger.  If you want to capture these anonymous leads and add them to the program once they become known, add the following to your campaign. A "Lead is Created" trigger - this trigger will fire when the anonymous lead becomes known. A "Visited Web Page" filter with the specific page you are looking for. You may wish to add a Date of Activity constrain to the "Visited Web Page" filter if you do not want leads that visited the page too long ago to be added to the program.    
View full article
As you know, Marketo issued a security patch on 4/6/16 in order to strengthen token encryption within email links. At Marketo, security is a top priority and we will continue to invest in changes that make the platform more robust. In reference to this patch, Marketo Support has been answering several common questions that are documented here for your reference. Please find this information below and, as always, contact Marketo Support if you still have any unanswered questions. Are all email links impacted by this patch? No, the vast majority of links within emails are not impacted in any way. By default, Marketo converts all email links to shortened tracking links. These links were not impacted by this patch. These links should continue to function as expected, regardless of when your email was sent. Note: This also applies to any links that contain the “mktNoTrack” or “mktNoTok” class. These links were also not impacted by this patch. Which links were impacted? The only links that were impacted were links that contain pre-generated mkt_tok values. There are three ways these type of links can be present in your email: 1.  You use one of the following system tokens in your email: {{system.viewAsWebpageLink}} {{system.unsubscribeLink}} {{system.forwardToFriendLink}} 2.  You use the “Include View as Web Page” option in the Email Editor and your Admin > Email defaults for “View as Web Page Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## 3.  You use Marketo’s default functionality to auto-insert “Unsubscribe” footers at the bottom your emails and your Admin > Email defaults for “Unsubscribe Text” explicitly includes an mkt_tok value like this:  mkt_tok=##MKT_TOK## How will behavior change for these links? 1.  System Tokens For emails sent out prior to 4/6/16: {{system.viewAsWebpageLink}} - Any pre-patch emails that contain {{system.viewAsWebpageLink}} links will now direct users to a page indicating that the lead-specific email cannot be rendered. Users will, however, have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). {{system.forwardToFriendLink}} - Any pre-patch emails that contain the {{system.forwardToFriendLink}} link will no longer function. Currently, users will see an error message on click. {{system.unsubscribeLink}} – Any pre-patch emails that contain the {{system.unsubscribeLink}} link will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: For all of the above system tokens, any emails sent out post-patch are not impacted. 2.  “View as Webpage” - If you implement a “View as Webpage” experience in your emails by using Marketo defaults, selecting “Include View as Web Page” from the Email Editor, then you will see the following behavior: “View as Webpage" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “View as Webpage" links inserted into TEXT side will behave similarly to {{system.viewAsWebpageLink}}. For emails that were sent prior to 4/6/16, these links will direct users to a page indicating that the lead-specific email cannot be rendered. Users will have the option to instead see a generic view of the email (no lead tokens, dynamic content, etc.). Note: any emails sent out post-patch are not impacted. 3.  “Unsubscribe” - If you implement an “Unsubscribe” experience in your emails by using Marketo’s defaults, then you still see the following behavior: “Unsubscribe" links inserted into the HTML side of emails are not impacted. These links should continue to function as expected, regardless of when your email was sent. “Unsubscribe" links inserted into TEXT side will behave similarly to {{system.unsubscribeLink}}. For emails that were sent prior to 4/6/16, these links will continue to function and point users to your unsubscribe page. However, the unsubscribe form will not support prefill for this visit. Note: any emails sent out post-patch are not impact
View full article
Issue Can the {{system.unsubscribeLink}} be customized to point to a different page, such as a preference center?     Solution Issue Resolution The system token unsubscribe link will always behave the same way, and it cannot be customized. The {{system.unsubscribeLink}} will always bring you to: sub.domain/UnsubscribePage.html. If your Landing Pages are not branded, this system token will still behave the same way and take the lead to your out-of-the-box Marketo Unsubscribe Page (ending in /UnsubscribePage.html). If you want the link to go to a different page, the easiest workaround is to create a redirect rule that sends visitors to UnsubscribePage.html to your custom page instead.
View full article
Issue You are considering archiving or deleting old programs, and you are wondering how that will affect reporting on membership of leads.     Solution If you delete a Marketo Program, the membership data will be lost. Technically, in the Lead record Activity Log, there will not be an activity for "no longer in program," but any and all reporting will not be able to report from deleted programs.  Keep in mind that Marketo Support cannot restore deleted programs. Archiving Programs keeps program membership data. This means that Analytics reporting, including Revenue Explorer, will be able to see archived programs and the related data. However, smart lists will no longer be able to reference the archived program. For example, say the smart list was: "Member of Program, program is [name]". In this situation, the smart list wouldn't be able to locate the program.    
View full article