Knowledgebase

Sort by:
Summary Learn how to monitor the synchronization status between Marketo and Salesforce to ensure data consistency and operational efficiency. Issue You want to check the Salesforce sync status to maintain data alignment and workflow effectiveness. Solution Marketo now offers a user-friendly, built-in tool to monitor the Salesforce sync status. To use this tool: Log into Marketo. Go to Admin > Integration > Salesforce. Click on the Sync Status tab.
View full article
Summary Learn how to resolve the issue where Marketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. Issue Marketo only recognizes the first LinkedIn Lead Gen form and does not recognize any additional forms. The problem persists even after disconnecting and reconnecting the LinkedIn account with Marketo. Solution To resolve the issue where Marketo does not recognize multiple LinkedIn Lead Gen forms, follow these steps:   Verify submissions: Ensure that each LinkedIn Lead Gen form has at least one submission. Marketo will not display a form in the dropdown lists for triggers or filters unless it has been filled out at least once.   Preview and test the form: Go to the LinkedIn campaign and use the ad preview feature to fill out the Lead Gen form yourself. This step is necessary for Marketo to recognize and sync the form.   Check for form activity: Once the test submission is complete, check the activity log in Marketo for the test record. Look for the LinkedIn Lead Gen Form Fill activity, which should be present to ensure that the form appears in Marketo dropdowns.   Using Marketo smart list: If you want to check the performance of the form, use a Smart List in Marketo with the filter Filled out LinkedIn Lead Gen Form and set Lead Gen Form Name to any. This will show submissions for all LinkedIn Lead Gen Forms with at least one submission. This filter can also be used in reports to segment people based on form submission activity.   Reauthorize connection: Remember that the authorization for the LinkedIn connection in Marketo is valid for a limited time. To avoid disruptions, set a reminder to re-authorize the connection periodically before it expires.   Additional information: Marketo integrates with LinkedIn Lead Gen forms to capture lead information directly from LinkedIn. Regular monitoring of the LinkedIn connection in Marketo is essential to maintain a seamless integration. By following the above steps, you should be able to resolve issues with Marketo not recognizing multiple LinkedIn Lead Gen forms and ensure all forms are properly synced and can be used within Marketo for lead generation and reporting purposes.  
View full article
  When a new lead enters Marketo from a form fillout or List Import, Marketo automatically searches for a lead with the same email address.  If that lead exists, the existing lead is updated instead of creating a duplicate. However, Marketo does not automatically de-duplicate leads who are already in your database. This is especially a problem for new customers who often have many duplicate leads in their database. Also, if you add a new lead directly into Salesforce (through the Salesforce import process or web-to-lead forms) Salesforce will create a duplicate lead that gets synced into Marketo. When this happens, you can use Marketo to find and fix those duplicates.   How Marketo handles duplicates   The primary consequence of duplicates is that one lead record could have the most relevant information about that lead while your sales rep is looking at the incomplete duplicate.   For example, say that you have a duplicate lead in your database and that lead fills out a form on your website. Marketo generally updates the lead record that was most recently updated. In another case, say you run a campaign to email your lead database and two duplicates are included in your campaign run. Marketo automatically detects the duplicate email address and ensures that only one email is sent to that lead. That Email send and subsequent activity will be attributed to the Lowest Lead ID.   When you merge leads, their entire history is combined, and you can control which fields are kept in the final lead. You won't lose any information or tracking.   Most customers have many duplicates when they start with Marketo. After initially de-duplicating your database, the work to keep your database de-duplicated is usually very small. You should work to stop the sources of duplicate leads and make Marketo your single point of entry for all new leads.   Finding Duplicates   Go to the Lead Database section of the app. Then click on the Possible Duplicates list in the tree. Click the grid header that says Email.  You can sort by email address to see the duplicates next to each other. Selecting multiple leads Select two leads that have matching email addresses.  You can do this by holding the "control" key down while clicking on the two different leads.  (You can merge more than two at a time, but start with two.) Tip: Sometimes clicking too fast will make the grid select incorrectly.  Clicking a little slower usually helps. When you have two rows selected or highlighted, click the Merge Leads button in the toolbar.   The Merge Dialog A dialog will appear showing you all the fields that differ between the two leads.  You need to pick which values to keep in the merged lead.  Not every field is displayed -- just the ones that you need determine appear. By default, the values from the most recently updated lead will be selected (with a check and highlighed yellow). To pick a different value for the merged lead, click the checkbox next to that value. If you want to enter your own values for the merged lead, click the Custom field for that row then type in your own value: When you're done, click Merge.  The winning values will be kept in the merged lead; the other values will be discarded. Important: Clicking merge will instruct Salesforce to merge the records properly.  All Salesforce and Marketo activities are merged into the remaining lead.  Nothing is lost.  Campaign History is also kept.   Duplicate pattern matching You will notice that the Possible Duplicates list has a Smart List tab.  Click on the Smart List and you will see it's using the "Possible Duplicates" filter on the "Email Address" field. You can change this filter to search other fields for duplicates. Click the little green plus in the definition. Note: You should use only one Duplicate Fields filter in your Smart Lists.  If you want to check multiple fields, always use the green plus button to add multiple fields; don't drag in a second filter. When you change the Duplicate Fields filter, you should sort the Leads grid by the column you're checking to put the duplicates next to each other. Marketo Merge Program Marketo offers a service for mass-merging of duplicates.  Please contact your Customer Success Manager to inquire about this service. What happens when I merge two leads in Salesforce? When you merge leads or contacts in Salesforce, Marketo will also merge the matching leads in your lead database. See this article to learn more about how that works: https://docs.marketo.com/display/public/DOCS/Find+and+Merge+Duplicate+People#FindandMergeDuplicatePeople-EffectinSalesforce      
View full article
Issue Our organization understands that Marketo has a durable unsubscribe field. Is that the only field that is durable or are other fields like block listed, marketing suspended, etc... durable? The scenario here is if someone is deleted, then later comes back in via SFDC for example -- are other fields durable and thus, carry over to a newly created record with the same email address? Solution The durable unsubscribe is the only field that will persist if the lead re-enters Marketo. This is because we host that data in a separate database, whereas fields such as 'Block Listed' are hosted in your local database. (When the lead is deleted, then all data is wiped for that lead in the local database.)  
View full article
Issue An attempt is made to add an API user to a 2nd instance and we get the error "This userid is in use. Choose another email." Solution API Users are unique to an instance and cannot make use of the Universal ID feature. 
View full article
Issue Marketo Azure integration is not functioning despite having the correct configuration. Solution One suggestion is to remove the relay state in Microsoft Azure Single Sign-on settings. This field is not required in setting up SSO with Marketo.
View full article
Summary Disable Require PKCE for syncing with SFDC via OAuth 2.0 Issue If attempting to connect Marketo to Salesforce via OAuth 2.0, no authentication window is presented by Salesforce allowing for credentials to be entered, only showing "Redirect Failure" Environment Marketo is not compatible with the "Proof Key for Code Exchange" authentication with Salesforce, "Require PKCE" in Salesforce Configurations Solution Disable the "Require PKCE" checkbox in the Connected App during configuration of OAuth 2.0, prior to connecting Marketo via the Native SFDC Integration. Root Cause PKCE not supported by Marketo's sync solution with Salesforce. This is documented in Adobe Experience League: Log in Using OAuth 2.0 | Adobe Marketo Engage
View full article
Issue You want to re-map a synced SFDC field to a different field in Marketo. Solution Yes, it is possible to re-map Salesforce - Marketo fields after initial sync. For this you need to Contact Marketo support with a request for your current field mapping and your desired field mapping. You will need to provide the Marketo Field(s) and the Salesforce API Name(s), then format your request similar to the example below.   Important Note Before initiating the re-mapping, please export the records and their field values from Marketo and import the values into their Salesforce or create a smart campaign to write the data from one field into the other. This is important so that there is no data loss after the remapping work has been performed. Marketo will not automatically push these values to SFDC, after the mapping is complete.   Example Request Current Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead)   Field Label: [Marketo Field Name 2] CRM Field Map: fieldName__c (SFDC Contact) Desired Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead) fieldName__c (SFDC Contact)   Field Label: [Marketo Field Name 2] CRM Field Map:   Limitations - Fields need to be of the same type (String/String, Date/Date, etc) - Fields can only have one of each object type (eg: A Marketo Field could be mapped to a SFDC_1 (Lead) field and a SFDC_1(Contact) field, but can not be mapped to both SFDC_1 (Lead) and SFDC_2 (Lead). - Fields can be mapped to a maximum of 2 SFDC fields - SFDC fields can only be mapped to one field in Marketo   Please note that there may be additional limitations in certain circumstances. The Marketo Support agent that handles your request will provide any further details should such a situation arise.  
View full article
Issue After creating an Email Program with an A/B test, you create smart lists (or smart campaigns) and would like to use filters such as "Opened Email" for the A/B test email. When starting to type the A/B test email name into the smart list filter, the A/B test email name does not show as available to select (it may show a red squiggly line). Solution The Email Program (with the A/B test) needs to be in "Approved" status before the A/B test email assets can be entered into a smart list filter.
View full article
Issue The SFDC sync error "Unable to process due to no XML response from Salesforce" or "No XML Document Error" appears. Root Cause This error means Marketo received an invalid XML response returned by SFDC. Most often, this is a transient error from SFDC and resolves on its own in the next sync cycles.  If the error persists or is continually blocking your sync, please reach out to Marketo Support.
View full article
Summary Your global form validation rule is setup/active in Admin, and the rule is enabled on the form, but the rule isn't working. Issue Your global form validation rule is setup/active in Admin, and the rule is enabled on the form, but the rule isn't working (emails that should be blocked can still submit) Environment Admin Solution Check the rule in Admin > Global Form Validation Rules and confirm that there is no '@' prepended to the email domains. The domains should look like the below: 'gmail.com, outlook.com, acme.org...' Instead of: '@gmail.com, @outlook.com, @acme.org..." Root Cause '@' referenced in the domain name within the validation rule.
View full article
Issue An email using a Velocity Script Token fails to send. Environment Marketing Activities Solution There is a 40 custom field token limit per email. If you have Velocity script tokens present in the email and those tokens more than 40 fields, the email will fail to send. To resolve, ensure that velocity script tokens have less than 40 custom fields referenced. Root Cause The Velocity Script Token in the email exceeds the limit of 40 Custom Fields. 
View full article
Issue You encounter the error "XSRF Protection Mismatch: User does not have access" when trying to access a Marketo instance, or when using the instance switcher to change from 1 instance to another. Root Cause This error can happen when you have multiple Marketo tabs open or can be due to session cookies, and the resolution is to clear cookies and re-try. If the error persists after clearing cookies, please reach out to Support.
View full article
Issue My SFDC production instance is undergoing Instance Refresh Maintenance in SFDC. Will this impact the SFDC and Marketo sync? Salesforce Article: Help And Training Community Solution Provided the org ID of your SFDC environment stays the same, it will remain connected to your Marketo instance. As best practice, double check with your SFDC team that all of your SFDC records will retain their unique IDs after the refresh. After the refresh occurs, double check that the Marketo connection in Marketo (under Admin > Salesforce) is intact.  
View full article
Issue When trying to reset a user's password under Marketo > Admin > Users & Roles, a popup error appears stating "Single id enabled users cannot have their passwords reset". Solution Admins cannot reset passwords for universal ID enabled users under Marketo > Admin > Users & Roles. The universal ID user should reset their own password themselves, by clicking on "Forgot Password" in the Marketo login page.
View full article
Issue You encounter a "Couldn't connect to host" SFDC sync error. Environment Salesforce Solution This is a message returned by Salesforce to Marketo indicating that for some time, Salesforce couldn't be accessed because the SFDC servers were temporarily down. This could be caused by transient SFDC Server issues/outages but is most commonly caused due to scheduled Salesforce database maintenance. When these errors occur, Marketo will continue to sync to SFDC where it last left off once the Salesforce servers are back up and running - however, this only applies to records already syncing with SFDC. If any records affected by this sync error were attempting to initially sync (through "Sync person to SFDC" flow steps, for example), then the flow steps need to be run again to push any of those records to SFDC for the first time. The global background sync works on its own and will automatically retry to sync any recently updated records (that were already previously syncing with SFDC) after the Salesforce server outage has been resolved. Root Cause Server outage or scheduled maintenance on SFDC servers  
View full article
Summary Admin unsubscribe HTML is overriding unsubscribe language hard-coded into an email template Issue You are trying to add unique unsubscribe text to a specific email asset template's code (for example: unsubscribe text in another language), but the Admin Unsubscribe HTML found in Admin > Email > Settings is overriding it.    Environment Design Studio/Admin Solution To implement dynamic unsubscribe text by language into an email asset, we recommend using the Segmentations and snippets, placing the {{system.unsubscribeLink}} directly into the email asset via the snippet as the presence of this system token in the email asset should override the Admin unsubscribe HTML. Make Your Unsubscribe Message Dynamic for Languages | Adobe Marketo Engage  
View full article
Issue You notice that new records in Marketo have the 'Website' and 'Company Name' fields populated with the domain of their email address.     Solution This will happened when a new lead is created by a form fill-out. If the new record is imported or created manually then this would not apply. This design decision has been a part of the code for many years where the domain of the email is used for the company name and website fields on the lead record. This feature cannot be disabled.    
View full article
Issue Issue in delivering Marketo Email (especially for mimecast users). Email get bounced with Error: 550 Rejected by header based Anti-Spoofing policy Solution This error can happen if: You have not properly white listed the Marketo IPs You have an issue with DKIM/SPF set up and configuration Please whitelist the set of Marketo IPs found in the doc below and make sure SPF and DKIM are set up correctly for your email domain https://experienceleague.adobe.com/docs/marketo/using/getting-started-with-marketo/setup/configure-protocols-for-marketo.html?lang=en#step-allowlist-marketo-ips
View full article
Issue How page views and form fills are counted in the statistics section of a Marketo Landing Page asset. Solution How they're calculated When viewing the Landing Page asset in either Design Studio or Marketing Activities, the statistics section provides information regarding page views and form fill outs, if the page has a form located on it.  The page views are a cumulative total indicating how many times the page was loaded, regardless if the visitor was a known record in the database. This means anonymous people can record a view here, due to Munchkin tracking on the page. This section provides a total number of views, not unique visits. This means that a person can load this page multiple times and each visit will be tallied in this section. The form fills section (x Filled out Form (x%)), indicates how many times a visitor filled the form out on the page, if it has one. This total is also counted in the same way the views section is, meaning it's a total number of submissions. Therefore, if a record in your database fills out the form more than once on a page, it will be counted toward the total.   Difference between calculations The difference between these two metrics is that the page views will keep a historical record of visits to the page. This means the total will not change if you happen to delete a bunch of records that visited the page in question - the total persists regardless if the record is no longer in the database. With that said, the forms section does not. This area is tied specifically to the existence of that known record in your database. This means that, once a record who filled the form out is removed from your database, the submissions they performed will be subtracted from the total.
View full article