Knowledgebase

Sort by:
Issue LinkedIn leads generated through LinkedIn Lead Gen form does not populate Inferred State/City/Country values. Solution Use field mapping between Marketo and LinkedIn to make sure inferred State/City/Country fields are mapped to respective LinkedIn fields so that they are captured in Marketo. Root Cause The inferred State/City/Country is populated via the person tokens and that information is normally captured when a lead fills out a Marketo form. If instead, the form used is a LinkedIn form, then that information is not passed over to the Marketo lead fields. Environment Marketing Activities LinkedIn Lead Gen
View full article
Issue When an A/B test is in scheduled state and you would want to cancel it. On clicking "Unapprove Program", an error message shows up saying 'Cannot unapprove program -<program name> - is in use'. Solution Within the program, go to the trigger campaign which references these assets in their smart list, for example  1. 'Program_1.Email_Asset_1' used in 'Open Emails' trigger step in smart list 2. 'Program_1.Email_Asset_1' used in 'Clicks Link in Email' trigger step in smart list Remove asset references above within the smart list of the campaign, navigate to program and click "Unapprove Program". Root Cause This is due to the program asset being used in trigger campaigns within the program. Environment Marketing Activities A/B Test
View full article
Issue When adding 'Acquisition Program' attribute as part of 'change data value' flow step, ‘New Value’ will not get saved if it is added as a token. As an example, let's say there is a smart campaign within a program and the program has multiple tokens. One of the token is {{program.Name}} whose value is 'Sales Acquisition Campaign'. In the smart campaign, there is a 'change data value' flow step that updates the value of 'Acquisition Program' attribute to a new value. If this new value is added as '{{program.Name}}' in the flow step, and when navigating away from the campaign flow edit page and navigating back again to the same page, the 'Acquisition Program' attribute's new value will be blank. Environment Marketing Activities Change Data Value Acquisition Program Token Solution Use text instead of token to update 'Acquisition Program' value. In the above example, use 'Sales Acquisition Campaign' as the new value in the flow step instead of using token '{{program.Name}}'. Root Cause Marketo does not support use of tokens to update 'Acquisition Program' attribute.
View full article
Summary Smart campaign utilizing the 'Fills Out Facebook Lead Ads Form' trigger does not generate any results for people created as a result of filling out a Facebook Lead Ads form. Issue Smart campaigns utilizing the 'Fills Out Facebook Lead Ads Form' Trigger does not trigger for people created as a result of filling out a Facebook Lead Ads form. Solution If you have Workspaces and Partitions set up on your instance, it is important to remember that people created in the database as a result of filling out Facebook Lead Ads form, will be automatically created in your Default partition per design.  In a scenario where a trigger campaign is hosted under a workspace that does not have the appropriate visibility to your default partition - the person filling out the Facebook Lead Ad form would not be triggering the campaign.    Solution Make sure your trigger campaign lives under workspace which has visibility over the default person partition. To check the workspace configuration go to Admin > Workspaces & Partitions and make sure your default partition is assigned to the workspace where your trigger campaign lives under.  Root Cause New people which are being created in Marketo as a result of filling out a Facebook Lead Ads Form will be created by default in the Default lead partition. Environment Customers who have Workspaces and Partitions set up in their instance. Customers who have set up the Facebook Lead Ads integration and have utilized the  'Fills Out Facebook Lead Ads Form' Trigger
View full article
Issue A/B test in Email Program status is still showing “Running test…” and not all email variants were sent as expected.    Environment A/B Test Email Program  Sample Size Running Test  Solution To ensure the sample size qualified at least a minimum of the total variants of the A/B test.  For example, if you have a total of 6 records, a sample size of 34% will suffice for 2 records (1 for variant A and 1 for variant B).    Root Cause This can occur if the sample size selected is too small. For example, if you have a total of 6 records, a sample size of 1% will not suffice for 1 record.  
View full article
Issue Does applying a permission set to the Marketo Sync User in Salesforce suffice for limiting the number of fields to sync from Salesforce to Marketo? or will the profile need to be updated directly? Solution In order to limit the visibility of fields for the Marketo Sync User in Salesforce, the profile will need to be directly edited (example: Add an Existing Salesforce Field to the Marketo Sync - Marketo Docs - Product Documentation) Root Cause Since the profile has access to a field, the Marketo Sync User will still have access to the field even though a permission set applied to the profile does not have access to the same field. Environment Salesforce Sync Marketo Sync User Permission Set SFDC
View full article
Issue An email link performance report is configured to find people who have clicked in a link in these emails that does not contain 'unsubscribe', however, it still shows links within the email that contains 'unsubscribe'. Solution To exclude certain links from reporting, export the results and remove the links in excel. Root Cause This would be expected as the smart list does not exclude unsubscribe links or specific links from displaying in the report, the unsubscribe links will still appear if any of the people clicked on other links in the emails. Example 1 An email is sent to two leads named Bob and Mary Bob clicks on the unsubscribe link Mary clicks on the unsubscribe link and another link The email link performance report is configured to report on the email and filter people who have clicked on a link in the email that does not contain 'unsubscribe' The email link performance report will show all the links that Mary clicked on as Mary qualified for the smart list. The links that will be displayed include the unsubscribe link as well as the other link. Example 2 An email is sent to two leads named Bob and Mary Bob clicks on the unsubscribe link Mary clicks on another link The email link performance report is configured to report on the email and filter people who have clicked on a link in the email that does not contain 'unsubscribe' The email link performance report will show the link that Mary clicked on as Mary qualified for the smart list. There will be no unsubscribe link displayed in the report as Mary did not click on the unsubscribe link. Environment Email Link Performance Report Analytics Smart List
View full article
Summary duplicate records with the same email across lead partitions can be affected by uploaded custom object activity Issue System not separating lead partitions for custom object imports Uploading custom object activity affects duplicate records across partitions Custom Object activity import writing to the most recently updated record regardless of partition Solution Use the following workaround:  Run an update on the records that should be affected by the custom object activities import. This will make sure they are the most recently updated records among the duplicates Root Cause Normally when you do a list import, it would import into the one partition, whatever partition the list is located in and only impact the record in that one instance.  But when you import a Custom Object, it's able the see ALL the records across ALL the partitions.  If there are duplicate records, it just looks to see which one was updated most recently and grabs that one for the list import. So if you have lead record in A with Add to Custom Object already completed and you re-import again but the lead record in B has been updated more recently and has NOT had the custom object added to it, you get the duplicate "Add to Custom Object" activity. Environment Multiple lead partitions with duplicate records across them Custom Object activity import
View full article
By default – when sending an email via Sales Insight, the “From Email Address” that will be used to send the email will be the user’s email address on their User Profile. As it turns out, there is actually a way to use an alternative email address for Sales Insight!   DISCLAIMER: This doesn’t mean that users can select an email address to be used upon send (best to create an idea in the community!). However, it does allow emails to be sent out with a different From Address if users don’t want to use their default email address. Go to Marketo > Admin > Sales Insight. If you scroll down to the bottom of the module, you will find a Settings section with an ‘Email From Field’ field. By default, the initial and only value will be Salesforce/MSD User Email Address (depending on the native CRM integration used by the customer).   This is a article attached imageThis is a article attached image   In order to select an alternative email, a custom Email Address field should be placed on the User object in the CRM.   To do this in SFDC: 1) Go to SFDC > Setup > Build > Customize > Users > Fields 2) Create a custom field of type Email – refer to the SFDC docs if necessary. (help.salesforce.com/HTViewHelpDoc?id=adding_fields.htm) Have the new field be visible to the Marketo Sync user. In the below example, the custom field is labelled Alternative Email: This is a article attached imageThis is a article attached image   In Marketo: 1) Wait a sync cycle (or two) for the field to sync over to Marketo 2) Go to Admin > Sales Insight > Edit Settings and the custom field is now available   This is a article attached imageThis is a article attached image   Changing this will affect following email sends from Sales Insight.   Remember, this is not a method to select email addresses on send – this will affect all sends from all users after the From Address Field is updated.
View full article
Issue Champion Challenger A/B Test dashboard does not display any data Solution Check that the email was sent from a trigger campaign or an engagement program as "Champion/Challenger emails only work with trigger campaigns and engagement program streams." https://docs.marketo.com/pages/releaseview.action?pageId=2359553 Check that the email sent from the engagement program was added to a stream directly and was not nested within a program that is the asset added in the stream. Reference: https://nation.marketo.com/t5/Knowledgebase/Champion-Challenger-Test-in-Engagement-Programs/ta-p/249176 Check that the email was approved when the email was sent Check that the email has been sent Check the time the Champion Challenger test was created and the time the email was sent   Root Cause The email has not been sent since the A/B test was created or the email was sent before the Champion Challenger test was created. Environment Champion Challenger Engagement Program A/B Test Email Dashboard
View full article
Issue Leads recently imported cannot be found Solution Check if the example leads exist in the partition the workspace has access to. It is possible that the leads cannot be found because the workspace being checked does not have access to the partition the leads exist in. Check if any of the example leads have been deleted: by using the Campaign Inspector to review all of the smart campaigns that contain a Delete Lead flow action. Then check the run history of each smart campaign to see which recently ran and how many people qualified. If there is a significant amount of smart campaigns that contain a delete lead flow action, contact Marketo Support for additional assistance. by checking the delete lead activities via API Check if the example leads' information was changed. For example, if a lead was imported with email address "john@gmail.com" then create a smart list using "Data Value Changed" filter where "previous value" was "john@gmail.com" Root Cause Leads could exist in a partition that has not been searched, the details could have changed, or the leads could have been deleted. Environment Lead Database List Import Workspaces and Partitions Smart Campaign Campaign Inspector
View full article
Issue Interesting moments not appearing for a user in Dynamics. The interesting moments section on a Contact displays: “No Interesting Moments for [Contact Name]” Solution Checked that the user is a contact record synced with a Marketo record that has interesting moments Created a new record with interesting moments and synced to Dynamics, but the user still cannot see the interesting moments Sync is validated  No errors found for example records MSI Sync status is ‘Configured’ in [Admin > Sales Insight] Checked on a system admin users access and were able to see the interesting moments for the example records Found that the Marketo Sales Insight security role was not assigned to the affected user, but after assigning the role, clearing browser cookies and cache, logging out and logging back in, the Interesting Moments for the example records was still not appearing Perform the following update: Go to > Settings > In Marketo API configuration > Form Editor > API secret Key > Details tab > Edit > Disable the field level security Root Cause Marketo Sales Insight role was not assigned to the user and Marketo API Configuration had field-level security enabled Environment Microsoft Dynamics CRM Marketo Sales Insight Interesting Moments
View full article
Summary Estimating the external storage requirements for your Marketo Engage Database Issue I want to extract all of my data from Marketo Engage and store it. How much storage space will I need? Environment Marketo Engage and External Systems Solution Summary There is no repeatable method to accurately estimate the amount of storage you will need to extract and store your Marketo Engage database. Standing in the way of good estimation is data availability, field selection, and storage method. Any accurate estimate will take into account the potential sizes of each type of data and their quantities (known to data scientists as "facts and dimensions"). Determining ranges for these values takes a lot of preparation and may require a high level of skill. IMPORTANT NOTE: Estimating Database size is hard so any estimate used to make business decisions should be made in cooperation with a database or application architect or other qualified professional. Scope Some information won't be extracted. Information about anonymous leads, for example, cannot be extracted. Some of the data that can be extracted may not be needed at all. Selecting the right data for your needs is the best practice as it reduces the required storage and leads to a more efficient extraction process. Field Definitions How the fields are defined in the target system will affect how big the stored data is. Depending on your storage format, padding may play a role in the size of your extracted database. As an example, the "Country" field in Marketo is a string of up to 255 characters. You could chose to store 255 characters for every country value. Or you may choose a format that uses a variable amount of space. You might also know that the longest country name is "the United Kingdom of Great Britain and Northern Ireland" meaning that 199 of those characters will always be extra so you truncate the value from Marketo storing the first 56 characters only. Each choice will have an impact on the size of your extracted database. Estimating 199 unnecessary characters per lead and making similar decisions for other fields will add up to increased storage requirements and slower extraction time. Format Once the desired data is identified, the next step is to extract, transform and load (ETL) the data from Marketo Engage into your storage system. The data returned by Marketo's API is plain old text which is usually formatted as JSON or CSV. For the information to be useful, you will transform it from JSON into the format necessary for your storage system. That format could be an Excel spreadsheet, Microsoft SQL database or a schema-agnostic database like Azure Cosmos DB. How the data is formatted and encoded will make a big difference in the amount of storage needed. Take this simple example: a Microsoft Excel spreadsheet with "Marketo Engage" in cell A1. I saved that same file in four different formats which resulted in files ranging from 1 KB to 25 KB. The format you store you information in may have a bigger impact on your final storage requirement than the data itself. This is a article attached image   To help illustrate the impact of the storage system, take a look at this guide for Microsoft SQL Database size estimation: https://docs.microsoft.com/en-us/sql/relational-databases/databases/estimate-the-size-of-a-database  Functionalization Once you've extracted your data, what are you going to do with it? Archiving your data (simply storing it) is easiest and comes with the fewest contraints. A compressed archive (Zip file) will save dramatically on storage space at the cost of functionality and ease of use. Functionalizing your data (using it in an application) requires more: at least better speed and searchability: typically a relational database. An application will often require additional data and that will need to be accounted for too. Facts and Dimensions: Do the Math It's a lot of work to get to this stage. Once you've determined how your extracted data will be stored, you can set upper and lower bounds on the sizes for each object type extracted (lead, email, activity, etc). These are your facts. Then multiply those values by the number of each type of record. These are your dimensions. Add to that the overhead of your target storage system and its functional requirements to generate your final estimates.    
View full article
  The SFDC is Deleted field can be used to identify a SFDC Lead or Contact which used to be in SFDC but was deleted and now only lives in Marketo. Typically the record is deleted from SFDC for a specific reason and most customers will honor the deletion in SFDC by also setting up a smart campaign to also delete the record from Marketo.    If you decide to keep the deleted record (SFDC Lead or Contact) in Marketo to nurture it, the next time the record flows through the SYNC Person to SFDC flow step Marketo will insert it into SFDC as a new lead record. A strategy should be in place to make sure you're not syncing/inserting records you really don't want.   If you decide to delete a SFDC Lead or Contact in Marketo only you should only do it if you have a custom sync rule set-up. Otherwise the next time the record is updated in SFDC it will sync again to Marketo with a new Marketo ID.    Here are the steps to delete a SFDC record which is syncing to Marketo: Create Smart Campaign Set Smart List Set Flow Change Data Value of the "Sync to Marketo" field to False Wait 1 hour Delete record from Marketo only Schedule Run once     Additional resources for learning about the Marketo integration with SFDC.
View full article
Summary Sales Insight Email Performance Report grouped by Sales Rep exports file sorted by template rather then by sales rep.  Issue  Sales Insight Email Performance Report grouped by Sales Rep exports file sorted by template rather then by sales rep.  Subscription email displays report grouped by email template as wel  Report within the Marketo UI will show as expected Solution    The current workaround exists for the CSV exported.            1. Export the report to a CSV           2. Format Columns A (Sales Rep) and B (Email Name) to sort A to Z in order to get a view by sales rep. Root Cause This issue is scheduled to be addressed and resolved in the 2021 Q2 release Environment  Sales Insight for Salesforce This issue occurs within the subscription email that gets sent out of the report  This issue occurs when exporting the report to a CSV file
View full article
Summary Creating many-to-many relationships with Marketo custom objects requires an intermediary object with one link to a Lead or Company and another link to a secondary custom object. Here's how to solve the problem of the secondary custom object not showing up to be selected as the linked object. Issue Creating a many-to-many or N:N custom object structure such that a lead or company can be associated with multiple custom objects and a custom object can be associated with multiple leads or companies at the same time. When adding a link to the secondary custom object, that secondary object is not list as an available linked object.     Solution If you find that the custom object you'd like to link to is not list in the "Link Object" list, there are two things two check: The secondary CO must be approved. The secondary CO must not have any link type fields. Since it's not possible to change a link field once a custom object is approved, if you already have link fields, the only solution is discard the secondary custom object and create a new one. Recreate the custom object without link fields. Then, in the intermediary object, the target object will show up as an available link object.  More detail can be found at:  Understanding Marketo Custom Objects Add Marketo Custom Object Link Fields - Create a Link Field for a Many-to-Many Structure Root Cause The secondary custom object type is not approved. - or - The secondary custom object type is approved type and has link fields. Environment Marketo Custom Objects Many to Many Relationship - N:N Link Fields
View full article
Issue -Error editing image in email: “image URL does not exist” or “image URL cannot be found”   Environment -SSL not enabled on Marketo instance -Browser blocks unsecured content Solution Option 1 -Set up SSL for landing pages (Recommended!  SSL should be a baseline configuration for all landing pages and tracking domains). Add SSL to Your Landing Pages | Adobe Marketo Engage Option 2 (Not recommended!   Warning! This is a security risk.) -Allow browser to view unsecured content (can choose to turn this setting back off in the browser after viewing the content) This link below describes how to enable this content in Chrome. https://docs.adobe.com/content/help/en/target/using/experiences/vec/troubleshoot-composer/mixed-content.html This link below describes how to enable this content in Firefox. https://support.mozilla.org/en-US/kb/mixed-content-blocking-firefox Option 3 -Try to use a different browser or try turning off all browser extensions. Root Cause This issue could be caused by SSL not being enabled. If the issue was sudden, and SSL is enabled, it is likely due to the browser needing an update. Check if there are any updates that need to be done.
View full article
Summary Unable to update Person Source as expected for records created with the LinkedIn Lead Gen Forms and Facebook Lead Ads integrations. Issue New records created through LinkedIn Lead Gen forms as well as Facebook Lead Ads results in the records not updating the Person Source field as expected.  Solution Person Source may be set to block updates to the field as noted in the example for Block Updates to a Field - Marketo Docs - Product Documentation.  To resolve the issue ensure the field is not set to block updates for the desired update method.  Alternatively the Person Source values populated by the integrations can be kept and expected values can be updated to include these sources.  Root Cause The LinkedIn Lead Gen Forms and Facebook Lead Ads integrations automatically update the Person Source to preset values when a new record is created in Marketo through the integrations. Blocking field updates to the field may prevent the value from changing to pre-configured values as a value already exist for the integration created records.  Environment LinkedIn Lead Gen Forms Facebook Lead Ads
View full article
Summary Result for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  Issue Result for Smart List using Web Page constraint is greater than the result for the total of conversion on Landing Page Performance Report.  Solution Ensure to append version number to the Landing Page when renaming and ensure each Landing Page has a unique name. Root Cause •             Smart List looks at the information written to the lead’s activity log. •             The Web Page constraint looks at the label and not the ID of the Landing Page. If the Landing Page was renamed, it will show a different result depending what is written to the lead’s activity log. >> Example 1: Lead A filled out the Form when the Landing Page was called LP1. Lead B filled out the Form when the Landing Page was called LP2. Smart List: Filter 1: Filled out Form Form is XXX Web Page is LP2 Result: In this scenario, the result will only display Lead B. >> Example 2: Lead A filled out the Form when the Landing Page was called LPX (ID111) Lead B filled out the Form when the Landing Page was called LPX (ID112) Smart List: Filter 1: Filled out Form Form is XXX Web Page is LPX Result: In this scenario, the result will display Lead A and Lead B. •             Landing Page Performance Report look at data specific to the asset ID. •             Landing Page Performance Report only look at active Landing Pages, therefore data for the deleted Landing Page(s) will not be included. •             If the Landing Page is renamed, it will be reflected on the Landing Page Performance Report (i.e. the Landing Page Performance Report will display the new name going forward).   Environment > Landing Page Performance Report conversion  > Smart List constraint Web Page
View full article
Summary Marketo-only records must be manually synced, become a member of a default-program, encounter a Salesforce flow step in order to sync with Salesforce. Issue Records are in the Marketo database but are not syncing over to Salesforce automatically like I thought they would. Solution The sync between Marketo and Salesforce is bi-directional. However, in order for a record to be synced, one of the following conditions must be met: The record becomes a member of a program which is synced to a Salesforce campaign. This occurs when the background sync is used to keep members of a Salesforce campaign in sync with a Marketo Program status. This can easily be verified by navigating to the program and looking at the summary view. More information on this feature can be found here: https://docs.marketo.com/display/public/DOCS/Sync+an+SFDC+Campaign+with+a+Program https://docs.marketo.com/display/public/DOCS/SFDC+Sync%3A+Campaign+Sync The record encounters an SFDC flow step. Any time a record encounters a Salesforce related flow step in a smart campaign, this will cause the record to sync with Salesforce. Some of these flow steps have other implied actions, which you can read about here: https://docs.marketo.com/display/public/DOCS/Implied+Salesforce+Actions The record is manually synced to Salesforce through a single-flow action. This is an intentional user action. It can only occur when you find the record in your database or in the people tab of a smart list and select the option from the 'Person Actions' menu. More on how to do this can be found in this document: https://docs.marketo.com/display/public/DOCS/Run+a+Single+Flow+Step+from+a+Smart+List Root Cause Records had not encountered SFDC flow steps, become members of a program synced with a Salesforce campaign and hat not been manually synced to Salesforce. Environment Marketo with the built-in integration with Salesforce
View full article