Knowledgebase

Sort by:
Included in this article   Overview Troubleshooting To Try and https:// No Munchkin Tracking Code on Web Page No Visitors to the Web Page Yet Tips for Triggers and Filters Selectors Overview Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error.     You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem.     Troubleshooting To Try There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for.     and Using or in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear.         No Munchkin Tracking Code on Web Page If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs     No Visitors to the Web Page Yet Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page. Check the page for visits. Make sure you have a munchkin installed on the page you are requesting. Create a test lead and visit the targeted page.     Tips for Triggers and Filters Here are a couple of things that may help when using these filters and triggers.   Selectors   "Is" Selector In Triggers and Filters, if you use the selector "Is", (as in "the web page IS xyz.123.com") then the results returned will only be those from an exact URL match. If you want to also find results for the page xyz.123.com/sales, they won't be returned when using the "is" selector.     NOTE: The "is" selector will return results in filters much faster since it is only looking for exact matches.     "Contains" Selector If you use the selector of "contains", (as in "the web page contains xyz.123.com"), then this would return results for all pages that have xyz.123.com. Therefore, xyz.123.com/sales would match. The page xyz.123.com/products would match. All variations of that site xyz.123.com would match up.     NOTE: The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.
View full article
Issue You may experience this error when we create campaigns in SFDC using Marketo Campaign sync through a program.     Solution The error that we are receiving indicates that the User Profile that Marketo uses to log into Salesforce doesn't have permissions inside of SFDC to create campaigns. To test this, log into Salesforce using the Marketo sync credentials and try to create an SFDC campaign.  If you are unable to do so, then Marketo cannot create campaigns via the sync.  You would need to work with your SFDC Admin to grant the Marketo sync user permission to create campaigns in SFDC. If still there is an error, please contact the Salesforce support team, since this error is coming from Salesforce.  
View full article
Issue Description You come across a few leads who failed to sync to SFDC and would like to have the list of leads who faced the same issue. Issue Resolution Unfortunately Marketo doesn't have a specific type of filter to leads who failed to sync to SFDC. However if they are new leads who haven’t synced to SFDC, then you can filter them by using the filters "Person was created" and "SFDC Type" with condition "is empty".     If you want to find the list of leads (previously synced to SFDC) who failed to sync among a particular group of leads, you can filter by following the below steps.   1. Create a new Boolean type field in SFDC namely "Sync Error?" and with the default value as "true". 2. Wait for the filed to sync into Marketo. 3. Create a smart campaign to select those group of records and the flow steps to change the value of the Boolean field "Sync Error?" to ”False" and then "Sync person to SFDC". 4. Once the campaign has finished running, you will be to pull a report on SFDC on the list of leads who have the value "True" for the field "Sync Error?". It means that the value was not updated to SFDC as the record failed to sync. With this list you will be able to select the records and resolve the sync issue.   You can also create a smart list of leads who were never able to sync with the following filters: Lead was synced to SFDC : Assign to : is not empty SFDC Type: is Empty   I would also suggest that you refer the below list of ideas to improve the visibility of sync errors. https://nation.marketo.com/thread/33692-marketo-salesforce-integration-needs-a-serious-overhaul-dont-you-sync   Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo
View full article
Issue You created an Email Performance Report and want to know if the report will show the number of times a person clicked (if they clicked multiple times in an email) or how many people clicked.     Solution The metrics in the report are per person. The report will show the amount of people that clicked a link in the email, not the number of times the email had a link clicked. To see how many times people clicked a specific link in an email, you'll want to use the Email Link Performance Report described here: Email Link Performance Report.
View full article
Issue Issue Description Within a Smart List, there are two filters: 'Person was Created' and 'Created At'; both similarly named but qualifying different records.    Solution Issue Resolution The 'Person was Created' filter is looking for the activity of when the individual record became known, via form fill or list import, etc. Denoted with the New Lead activity type in the Activity Log.  The 'Created At' filter is looking at the date of when the Marketo record was first created. This date is listed under the Info section on the person record.  Some Marketo records have a difference between when the record was initially created and when the individual became a known record.  An individual could visit a Marketo page for the first time and generate an initial web page visit on May 1st tracked on an anonymous record in the database. Then on May 8th the person fills out a form thereby converting their anonymous record to a known record in the database. May 1st is the date used for 'Created At' filter, and May 8th is the date used for 'Person was Created' filter. 
View full article
Issue Description Getting the following error when trying to push leads to Salesforce as members of an SFDC Campaign.   Failed: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: RHX_PRO_NQ.RHX_PRO_CampaignMember: execution of AfterInsert caused by: System.QueryException       Issue Resolution This error is generated from Salesforce when the Marketo Sync User does not have permission to view the members of a particular Campaign in SFDC. In this case, you can try manually adding one of these Leads as a Campaign Member in SFDC while logged in as the Sync User.  Also, check with the Salesforce Admin for the required permission for accessing the associated SFDC campaign.   Who This Solution Applies To Customers integrated with Salesforce Is this article helpful ? YesNo
View full article
Issue Description Lead fails sync to SFDC with the error INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST: bad value for restricted pick list field Issue Resolution This happens when the Marketo field has a value that is not available in the list of accepted values on SFDC. We suggest that you check with your SFDC admin to find out the list of accepted values and make necessary changes. Who This Solution Applies To Customers integrated with Salesforce
View full article
Issue: You have a Salesforce lead field that is not currently in Marketo but you want to have in it Marketo for use.   Solution: Login to Salesforce as a System Administrator user. Identify the Salesforce profile that is being used by the Marketo sync user by clicking on Setup -> Manage Users -> Users Once you have identified the Salesforce profile being used by the Marketo sync user, you will need to make the Salesforce field visible to the Salesforce profile of the Marketo sync user. You do this via "Field-Level Security" setting for the field in Salesforce. In Salesforce:  Click on Your name at the top right of the screen -> Setup -> App Setup -> Customize ->   Click the Salesforce object the field is under. i.e. Leads, Contacts, Accounts, Opportunities -> Fields Click on the Field Label hyperlink Click on the "Set Field-Level security" button -> check the "Visible" checkbox next to the Salesforce profile that is being used by the Marketo sync user.   Only the "Visible" checkbox must be checked. The "Read Only" checkbox must be checked. In the following screenshot below, notice the different checkbox options for the "Backup User" Salesforce field. However, only 1 option combination will work correctly - i.e. the option with only the "Visible" checkbox checked.     Some standard Salesforce fields even though you have correctly followed the instructions above, simply do not sync to Marketo. One example of this is the "Rating" field on the Account object.
View full article
Here's how you can use tokens and URL parameters to automatically assign leads to Salesforce campaigns after filling out a form.  These tokens work in all of the Salesforce campaign flow steps: Add to Salesforce Campaign Change Status in Salesforce Campaign Remove from Salesforce campaign Get the Salesforce campaign ID and status You need two things to begin this process -- the name or ID of the Salesforce campaign you want to sync to and a valid status in that campaign.  You can get the ID for the campaign by opening that campaign in Salesforce and copying the last 15 characters from the URL.  Here's an example campaign URL; the ID is highlighted: naX.salesforce.com/701F00230001Z9z To get the valid statuses, click on "Advanced Setup" on the campaign's page The status should be listed there: Create new fields First, you need to create two new fields -- "SFDC Campaign ID" and "SFDC Campaign Status" -- both of type "string".  You can create these on your lead and contact records in Salesforce, or contact Marketo support to add those custom fields in your Marketo account. Create or edit the form After you create those fields, the next step is to incorporate them into your forms.  Create a new form or edit an existing form, then drag those two fields into your form.  Make them both hidden fields and set them to populate from a URL.  If you're unfamiliar with them, this article on hidden fields has details on how they work. Making a Field Hidden on a Form When setting the values for those fields, use a real Salesforce campaign ID and status as the default value.  Here's how you might edit the settings for those fields: SFDC Campaign ID: Default Value: [a real Salesforce campaign ID or name] Populate from: URL Parameter Parameter name: campaignID SFDC Campaign Status: Default Value: [a real Salesforce campaign status for the campaign you chose] Populate from: URL Parameter Parameter name: status And here's what your form might look like when done: Now you have a form that automatically add leads to the default Salesforce campaign you selected and that you can override with URL parameters. Create a Smart Campaign Next, you need to create a campaign that will add these leads to the selected (or default) Salesforce campaign.  We'll trigger this campaign to launch whenever someone fills out your form: In the flow, first you need to sync the lead to Salesforce so that you can add it to a campaign. Then you can add it to the Salesforce campaign using the values in the SFDC Campaign ID and SFDC Campaign Status fields.  To do this, use the tokens for those fields in your flow step:  {{Lead.SFDC Campaign ID}} for the campaign name and {{Lead.SFDC Campaign Status}} for the status.  If you type "{{" in the fields, the auto-suggest will help you enter that text correctly: Your finished flow should look like this: Finally, in the schedule tab set this campaign to run every time and activate it. Launch your landing page If you modified a form already in use, you can now go to that landing page, fill out the form, and watch as your lead gets synced to the Salesforce campaign you chose.  If this is a new form, create and approve a new landing page which uses that form.  After filling out the form, you should see the lead added to the default Salesforce campaign specified in your form: Use URL parameters to override the default campaign and status.  For our forms, the campaign is set by the "campaignID" URL parameter and the status by the "status" URL parameter.  For example, this URL: offers.marketo.com/offers.html?campaignID=701A00000009K3l&status=Responded will assign the lead to the Salesforce campaign "701A00000009K3l" (the Salesforce internal ID) with the status "Responded."  If either value has spaces or special characters, make sure that you URL encode them before adding them to your URL. Using tokens in other Salesforce campaign flow steps These tokens work in all of the Salesforce campaign flow steps -- Add, Remove, and Change Status in SFDC campaign.  Follow the same directions as above but substitute the appropriate flow step in place of the Add to SFDC Campaign step. Diagnosing errors If your leads are not syncing to your Salesforce campaigns, first go to the Activity Log for that lead and double click the line that has the failed flow step. The information that appears will help you figure out what the problem might be. The most common errors you'll encounter are: Spelling errors in your tokens -- use the autosuggest to help Using an SFDC campaign ID or name that doesn't exist -- check the spelling of the campaign or ID The lead doesn't exist in salesforce -- sync the lead to Salesforce before adding him/her to your campaign Using a status that doesn't exist for that campaign -- change the status to one that does exist for the campaign, or add a new status to the campaign in Salesforce
View full article
Issue Marketo Forms embedded on non-Marketo web page do not show up when using Firefox private browsing.   Solution Marketo forms and Munchkin tracking are inserted into non-Marketo pages via Javascript. If the browser privacy settings block the script from executing, Marketo forms and tracking will not work.  Marketo is not able to override a customer's browser security settings. The alternatives are as follows: Create a non-Marketo form on the web page Use a backend form submission to push the info in the form into Marketo. Instructions for doing so can be found here: developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/  
View full article
Wait steps allow you to “pause” a lead’s progression through a campaign’s flow.  This article will explain how this is accomplished, and help guide you around some common pitfalls when using wait steps.   When a lead encounters a wait step in your campaign’s flow it is “stamped” with the information contained in that step.  Think of it like a rubber stamp marking each lead with the time it should resume its movement through the flow.  The stamp also marks the lead with the next step in the flow, so it knows what to look for when its wait time is up. In the example below, leads will be sent an email from Step #1 then stamped by Flow Step #2 with “Resume on January 30 th at 10 AM.  Look for Step #3” which will then set aside these leads.  They don’t leave the flow, but they’re no longer still in Flow Step #2 either. Next, we’ll look at some situations you might run into when using Wait Steps.  It’s best to think through your flow and make any changes before you initiate your campaign, but here’s what to do if you need to make changes to an active flow.   Keep in mind that in a batch campaign all leads will move through the flow together, so they would all reach the wait step together and would all be stamped with the same information.  In a trigger campaign though, leads are more likely to have triggered the campaign at different times, and will be in different places along the flow. Is this article helpful ? YesNo
View full article
Issue You want to set up a DKIM key on one of your domains or subdomains, but another service has a DKIM key already set up on the selector/domain combo.   Solution Beginning October 2023, Marketo has upgraded it's DKIM feature to allow for a Custom Selector for DKIM Keys.  Most Users will be able to utilize the prior default selector, m1, as their DKIM Key.  However, if another integration is already utilizing the m1 selector, a custom value can be used. Common ones seen are "m2", "a1", "mkto", etc. It can be longer, but shorter is generally better   Afterwards, you'll be able to validate DKIM  as detailed in documentation: docs.marketo.com/display/public/DOCS/Set+up+a+Custom+DKIM+Signature  
View full article
Summary Leads/Forms are not appearing in Marketo but are appearing in Linkedin Issue Troubleshooting LinkedIn Lead Gen Forms issues - Leads/ Forms are not appearing in Marketo but are appearing in LinkedIn Solution Most of the time this issue is caused by insufficient permissions for the user specified in the LaunchPoint Service under "Admin > LaunchPoint." This article mentions what is required for LinkedIn lead gen forms to work on LinkedIn for the user, this is not for Marketo but it makes a great reference. linkedin.com/help/lms/answer/79635  For Marketo, we require full permissions for the integration to work.  - Campaign Manager OR Account Manager (The integration user will only be able to have one of these permissions) - Company Page Admin  - Lead Gen Forms Manager  Ensure that the user has all 3 permissions. If you made some changes to the permission, re-authorize LaunchPoint service and, try again. I would also recommend deleting and re-creating the LaunchPoint service. It is recommended every time you make changes to the permission so that the connection works without any issue. You could see the form in Marketo after this step.   If any one of the permissions is added later, I recommend creating a test lead on the form referring the document - https://www.linkedin.com/help/lms/answer/94217. The leads that fill out the form after this step would be found on Marketo. You could List Import the other leads that filled out the form.  If you are still facing the issue after verifying the above steps, please raise a support ticket with Marketo. We could verify whether the issue is with Marketo or the Integration itself. 
View full article
Issue Note: If you have been migrated to Admin Console, refer to the Admin Console Overview page at https://helpx.adobe.com/enterprise/using/admin-console.html. When I go to the Support area of Nation, my access to the Portal is incorrect.     Solution Our system is particular about how you need to access the Support Portal before we can authorize you to use it.   The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 This is a article attached imageThis is a article attached image Step 2 This is a article attached imageThis is a article attached image   Step 3 This is a article attached imageThis is a article attached image Step 4 This is a article attached imageThis is a article attached image   If you experience issues, please email marketocares@marketo.com
View full article
Issue You are following the SSO setup instructions provided by Azure to configure your IDP (https://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-marketo-tutorial). However, you are getting the error message: " Error processing SAML message. Request was ill-formed in some way. " To troubleshoot that message you are collecting the SAML assertion being passed to Marketo to identify potential issues with it (as described here: https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-saml-debugging ). However, when trying to capture the SAML, you are not able to find any SAML in the network tracer even after arriving at the error message.    Solution Confirm the field "Sign on URL" is empty as it is only intended to be used for service provider initiated single sign-on, which is not supported by Marketo.  Disclaimer: Marketo does not support 3rd party products such as Azure Active Directory and cannot configure your IDP on your behalf. This document is intended to assist Azure users in configuring their IDP, but no guarantees are made that this information is accurate.    
View full article
Issue You try to send a sample of an email and receive a notice that the send sample failed.     Solution There are two token-related reasons that Send Sample may fail: You may have an invalid value for a token in your email. If there is an incorrect token value, the send sample will not work. Example: If you have the token for first name written like this {{lead.FirstName:default=Hello}}, when you try to approve the email Marketo will let you know that the token value is incorrect. The correct token value is  {{lead.First Name:default=Hello}}. For this example if you change the token value to {{lead.First Name:default=Hello}}, Marketo will allow you to approve the email and it will allow you to do a send sample. You may have a token in the From or Reply-To line that is not populating with an email address Example: If you have a token in the Reply-To like this one, {{lead.Email Address:default=edit me}}, then the Send Sample using the default will have "edit me" in the Reply-To, which is not an email address.  Marketo cannot send an email without a Reply-To email address, so the Send Sample will fail.   If any of the above does not apply, run the following tests and provide the information to Marketo Support Clone the email in question and test to send as a sample Create a new email and test to send as a sample Send the email via a live campaign or a single flow step to a test lead
View full article
Issue There is a significant delay of several hours or days between when an update is made to a contact record in Dynamics and when the change shows on that record in Marketo. Solution To determine what may be causing this, follow these steps: Check under Admin > Microsoft Dynamics to make sure your sync is turned on. Take a look at the Admin > Sync Status tab as described here: https://docs.marketo.com/display/public/DOCS/Sync+Status. If there is a backlog of updates or inserts showing here, this is likely what is causing the delay. Check the Sync Errors tab to see if there are any errors indicating issues with your sync. Find an example record that has a sync delay, and locate the GUID of the record in Dynamics. Check the Marketo Log to see if the update to that record was written to it. The logs can be found under Settings > Extensions or under Workplace (this can potentially be customized). Once the logs have been located, you'll want to click on each one individually, and it will show the current view. If not all of the columns are visible, edit the view and include all the column and save/publish that change. Once all of the columns are visible, click on the export option as a static sheet. Once you've exported the Marketo Log, do a search for the GUID in the file. If there is a record of the update on the date-time you made it, that means it was successfully written to the log. In this case, there is likely a backlog of updates to be made, particularly if a large update was made recently, so it may come in later. If there is no record of an update to that record, there is something on the Dynamics side preventing it from being written. You will want to work with Dynamics Support to narrow down the issue in this case.         Who This Solution Applies To Customers using the Microsoft Dynamics CRM integration
View full article
Issue How to work effectively with Marketo Support to quickly resolve your issues. Solution Best Practices:   Be specific about the issue you are experiencing. Describe the expected behavior or appearance of the asset we are troubleshooting - what you believe should be happening Describe the actual behavior or error in the asset we are troubleshooting. Provide links to the assets we need to troubleshoot. Click on the specific asset in the navigation tree and then copy the URL displayed in the address bar of your browser into your case.  This will take us directly to the asset. If we are troubleshooting a specific asset inside a program, such as a Smart Campaign or an email, provide the link to the asset itself rather than to the program containing the asset. Provide examples of the issue: Provide links to specific leads that are examples of the issue you are having. Even if the issue affects multiple leads, we still need to start by looking at specifics. Provide the exact text of any error messages you might be receiving, along with the timestamps. Screenshots can be very useful for this. When troubleshooting API call issues, attach copies of the the request and the response that show the issue you are having. If the issue concerns a non-Marketo asset such as a webpage, please include the URL.   Include screenshots and log files: Since we do not have access to your CRM, if there is information in the CRM we need to see, attach an uncropped screenshot of an example record to your case. When taking the screenshot, log into the CRM using the Marketo sync credentials. This will allow us to see what Marketo sees through the sync. If you are using MS Dynamics, attach the Marketo logs and Marketo error logs to your case. Involve other resources as necessary, even if they aren't Marketo users.  We may need to work with your CRM admin, your IT department, or your web developer.  CC-ing them on the case is a simple way to loop them into the support case so you don't have to run questions back and forth.   Please be aware that Marketo support are not trained as web developers or CRM admins. We are happy to help you troubleshoot issues with your Marketo instance and integrations, but we are not able to troubleshoot custom code or advise you on details of your CRM administration.
View full article
Issue You would like to include the subject lines of your emails in your email performance reporting     Solution In the Email Performance report in Analytics, you cannot not add the subject line to the report. However if your instance has access to Revenue Explorer then you can create a report that includes subject line. Within Revenue Explorer create a new Email Analysis report. Email Subject is listed under Email Attributes, you can either include Email Subject as either a row or a column.  docs.marketo.com/display/public/DOCS/Email+Analysis   Who This Solution Applies To Customers with Revenue Explorer    
View full article
Issue How to use tokens to personalize some of the information displayed in a Marketo form.     Solution It is possible to use Marketo tokens in the following form elements: Field Labels - Edit a Field Label in a Form Hint Text - Add Hint Text to a Form Field Tooltip Instructions - Add Tooltip Instructions to a Form Field Fieldset Text - Add a FieldSet to a Form Rich Text boxes - Add Rich Text to a Form
View full article