Knowledgebase

Sort by:
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 How to see all the historical Support cases created for Marketo Issue How to see all the Marketo Support cases, attachments, and comments related to your historical support cases Environment Support Portal Solution Authorized Contacts can see the cases that they personally created/own, and the Support Admins can access the all cases on the entitlement from within the Support portal. Below is a community article with additional information and instructions: Managing your Support Cases  
View full article
Issue You receive the error message of "exceeded limit" for Program Member Custom Fields (the documented limit is 20), but you don't see 20 fields listed in the Admin > Field Management > Program Program Member Info area.   Root Cause There may be Program Member Custom Fields in your Marketo instance that are hidden. These hidden fields still count toward your limit of 20.  As next steps, in Admin > Field Management, review the Hidden Fields area to find the hidden Program Member Custom Fields, and un-hide them. After un-hiding them, they will appear under Admin > Field Management > Program Program Member Info. To resolve the "exceeded limit" error, unused fields should be deleted. Reach out to Marketo Support to delete Program Member Custom Fields.
View full article
Summary Learn how to troubleshoot the REST API Error: read ECONNRESET. Issue You are getting the following HTTP error when attempting to call the associated REST API.  REST API Error: read ECONNRESET Cause This error might occur because of issues on the local network or HTTP client config. Here are some possible causes of this error. HTTP Client Configuration Issues: The error may occur due to incorrect, incomplete, or incompatible settings in your HTTP client. To align your HTTP client settings with the Marketo REST API requirements, you should review and update your HTTP client settings. Proxy Server or Configuration Problems: If you use a proxy server, its configuration may result in an HTTP error. Verify your proxy server settings and consult your network administrator for accurate configuration if necessary. Faulty Network Equipment: Issues with hardware such as switches and routers, particularly if they are malfunctioning or improperly configured, can cause the problem. You should investigate the status and settings of your networking devices to determine if this is the issue.     Solution To resolve this issue: Review and adjust your HTTP client's configuration to match the Marketo REST API specifications. Check your proxy server settings and consult your network administrator if needed. Examine network equipment for faults or incorrect configurations.
View full article
Issue You added yourself to the Send Alert To portion of the List Import process and continue to receive unwanted Alert Emails every time a list is imported.         Solution During the next List Import process to the problem Static List in Marketo, you'll want to select the Edit Send Notification from the window that pops up in the top right section of your screen after the import process is started. Selecting the Edit Send Notification will cause a new window to open up that shows all of the email addresses who will be sent an Alert Email once the import completes.     If you no longer want to receive the Alert Emails for this static list going forward, deleteyour email address and click save.    
View full article
All the Recommendation Bar customization options are available within the RTP account settings page:   Colors: Link Color: select the color from the dropdown choices. Background Color:select the color from the dropdown choices.   Font:   Font Size: type in the size in the 'Font Size' field (must be in pixels - px) Font Family: type in the 'Font Family' field Arrow Icon Color: select the color from the dropdown choices. Icon Font: select the icon style Icon Opacity: define the opacity level for the arrows     Advanced customization There is additional customization can be done by the support team: Horizontal Bar Position: bottom (default) /top Vertical Bar Position: right (default) / left  
View full article
Article Text If you're finding that boxes in your Facebook Lead Ads setup are not staying checked, the issue may be related to your sandbox. This fix applies only if you have ever previously set up the same pages in your sandbox.   In this situation, you began by going to Admin > Integration > LaunchPoint and adding Facebook Lead Ads. During initial setup, you checked the boxes for the Facebook pages you want to connect to Marketo. It appeared to be set up correctly.     However, you later discovered that one or more of them actually fail to work. The next time you looked at it, some of the boxes were mysteriously un-checked.     The issue here is that the page/s you selected were previously used in a sandbox (for instance, to test them out before setting them up in production). Once you decided to move them to production, your natural assumption was that you needed to delete the sandbox integration and re-create it in production.   However, deleting the integration from the sandbox does not break the connection with Facebook. As far as Marketo is concerned, that page is still in use by the sandbox, even if the integration is deleted.   To resolve this issue, you will need to clear the page from use on the old instance and allow it to be used on the new instance. Follow these steps: Log into the instance where the Facebook page was previously used. Create a new FB Lead Ads integration (with the user who has admin rights on the page that unchecked itself). Uncheck the page and click Next. Ignore mapping and click Save.   Note: It isn't possible for Marketo Support to tell you which instance the Facebook page was used on.
View full article
Article Text FAQs included in this article   How long does it take to see RTP data in Google Analytics? Should I develop any custom code to send the RTP data to Google Analytics? Are the data events sent to Google Universal Analytics marked as non-interation? What needs to be configured in Google Tag Manager to enable to GA integration Important note about getting help from Marketo Support: Overview RTP has great a integration built in with Google Analytics that will pass data through for you. This doc will answer some of the most frequently asked questions about this integration.   How long does it take to see RTP data in Google Analytics? Custom Variables (classic Google Analytics version) or Dimensions (Google Universal Analytics version) should show up after up to 24 hours. Custom Events show up in Real-Time   Real-Time Data details: About Real-Time - Analytics Help Real-Time Data is available in all Google Analytics accounts. No changes to the tracking code are necessary. To see Real-Time data: Sign in to your Google Analytics account. Navigate to your view. Select the Reporting tab. Select Real-Time.     Should I develop any custom code to send the RTP data to Google Analytics? No, all data is sent automatically by RTP to Google Analytics behind the scenes.   Here are the related pieces of documentation to get the Google Analytics integration set up successfully: Integrate RTP with Google Analytics - Marketo Docs - Product Docs Integrate RTP with Google Universal Analytics - Marketo Docs - Product Docs     Are the data events sent to Google Universal Analytics marked as non-interation? Yes. The RTP script sends data events to Google Analytics (both Classic and Universal) as non-interation, so it has no affect on bounce rate and pageview metrics. Google Universal Analytics version:      ga('send', 'event', 'RTP-Segments', 'segmentName', 'organizationName', null,   {'nonInteraction': 1}  ) Classic Google Analytics version:      _gaq.push(['RTP-Segments', 'segmentName', 'organizationName', null, true]);     What needs to be configured in Google Tag Manager to enable to GA integration Nothing. Everything is done automatically by the RTP tag and behind the scenes once the integration is set up correctly.   Here are the related pieces of documentation to get the Google Analytics integration set up successfully: Integrate RTP with Google Analytics - Marketo Docs - Product Docs Integrate RTP with Google Universal Analytics - Marketo Docs - Product Docs     Important note about getting help from Marketo Support:  
View full article
Any emails being sent as part of 'Forward to Friend' will create that user as a new lead (provided that the lead does not already exist in Marketo). When leads are created in Marketo via the 'Forward to Friend' feature, Marketo automatically unsubscribes the lead records in order to protect our global customers from anti-spam laws. This is because a lead being sent a forwarded email doesn't qualify as opting in to a mailing list and also prevents them from getting any other emails by accident.    
View full article
Issue When a Marketo field is synced to a SFDC field with a picklist, that picklist will be synced to Marketo when the field is added to a Marketo form. The values section of the field in the form will show the values from SFDC. However this does not occur with the standard state field in Marketo. Solution The state field's form picklist is not updated because it is automatically populated with the 50 US states.  To get around this, you can either manually update the values in the picklist in the form, or you can use a custom Marketo field. This field can be remapped to the state field in salesforce with assistance from support.
View full article
Issue Issue Description Marketo allows you to upload any file type to your instance (100MB or less) but these files don't always download automatically or open in a new browser tab or window consistently between users.   Solution Issue Resolution Marketo's servers are not configured to force a download, so any desired effect is up to the user and/or utilizing custom code to achieve that effect. How a file is handled or displayed is largely up to the browser and you will need to test whether your specific desired outcome is possible. Keep in mind, this may vary by file type and file size and may not be feasible.  
View full article
Issue Issue Description Importing a program from one subscription to another is failing and is returning the following error sent via email:   Marketo encountered an error while importing [Program Name] The token "lead.First Name" is not available in the destination subscription. It is either a custom field that you have to create or need to be synced from your CRM system, if you use one. This is a article attached image   Solution Issue Resolution Check if there is any malformed lead.First Name token in email Check if there is any malformed lead.First Name token in email template used by the email(s) in the program Check if there is any malformed lead.First Name token within a program token Check if there is any malformed lead.First Name token within smart campaign flow step(s) This error has been known to occur when the email template had a lead token coded as follows, with a line break between 'First' and 'Name': {{lead. First Name}} Note: In this scenario, the error message received via email is actually referring to the token in the email template that contains a line break between 'First' and 'Name' but is stripped out on the message when HTML is rendered.  
View full article
Issue Duplicate records were sent an email from an Email Program. Solution While Marketo prevents sending emails to duplicate records (i.e. same email address) via the same Smart Campaign, it is possible to send an email to duplicate record when there is A/B test configured for the Email Program. Specifically, one record can be sent an email from the test send while the duplicate record can be sent the email from the winner send. For example, if there are two records for "mary@mail.com" in the audience, Mary can be sent two emails as follows: One record can be sent the email by qualifying for receiving the test from the sample size of the A/B test The other record can be sent the email by qualifying for receiving the winner from the sample size of the A/B test   Note: sending the test and sending the winner utilizes individual campaigns which is why the systematic deduplication of emails within a smart campaign does not take effect for this scenario. To prevent this from occurring, exclude the duplicate records from the smart list of the email program.
View full article
Issue You created a batch A/B test with a sample size of 100%.  Even though all the leads should have been sent the test email, some leads still receive the winner.     Solution Email Batch Programs are built in such a way that the test is sent with an background 'exploration' Smart Campaign, and the winner is sent with a background 'exploitation' campaign.  The exploitation campaign will send the "winner" email to the following Smart List: Member of Program Not Sent Test Email There are two situation where the exploration campaign may not send to all the leads in the program, even when the sample size for the test is 100%. If there are duplicate leads in the program, the program will not send the email to the same address twice.  It will send the test email to the first lead and skip all following leads with the same email address.  Those skipped leads will then qualify for the "winner"/exploitation campaign and will receive the winner. If there are leads in the program who hit their Communication Limits while the "test"/exploration is running, they will be skipped.  When the "winner"/exploitation campaign runs, if those leads are not at their Communication Limits at that time, they will be sent the winner email because they were not sent the test email.  
View full article
Issue What will happen to leads currently in flow steps if you deactivate a trigger campaign?     Solution If you deactivate a trigger campaign, all leads that are currently in the flow will still be processed. Deactivating a trigger campaign will only prevent any new leads from qualifying for the campaign and going through the flow steps.   To stop people from continuing through the campaign flow steps, you have 2 options: Remove people from flow steps. (Recommended option) Note: You may want to add that flow step after every flow step, to target all areas where people may still be in and processing. Delete all flow steps. As people complete any flow step, they will no longer have a next option.
View full article
Issue When a piece of predictive content is approved the following error appears: "Action failed. Please contact support. Error code:24 Error message: Invalid email title Error message: internal error, reported to support." Solution Change the title of the content to less than 48 characters. This error indicates that the title for the content is too long. The maximum number of characters for a title in content AI is 48 characters.      
View full article
Issue After running an A/B test, some records appear to have received both Test and Winner.     Solution In an A/B test, the sample size of the audience is sent the variants, and then for the winner: the entire audience minus the test audience is sent the Winning email. So let's say that you received both Test and Winner. This means you have duplicate records in the database. Marketo is designed to not send duplicate leads the same email at the same time. So one of the duplicates is qualified for the Test, and then when the Winner is sent, it's the total audience minus the test audience, the Winner is sent to the duplicate record. This above situation can apply to Lead Records as well, because of duplicates with the same email address, but also duplicate records that may have a FWD set up between them (record B emails FWD to Record A email address). To reduce the chances of this happening, you may wish to run a de-duplication pass on your database.    
View full article
Issue A Change Data Value activity gets recorded on a person record but the Updated At field for the record doesn't get changed to reflect it.   Solution The "Updated At" field in Marketo is a system managed field that gets refreshed any time that there is a data value change to a person field, but not when the field is on the company object instead.  To confirm what object the field in question is on, search for it in Field Management and check what folder it is located in.  The folder Info (or Lead Info) contains person fields while company fields are contained within the Company Info folder.
View full article
Issue You have a Marketo form embedded on a non-Marketo page.  When you open developer tools in your browser you see: "Error loading form: Object error: true errorCode: 400 message: "Subscriber <Your Munchkin ID> is not valid" "   Solution The form embed code you are using is looking for your instance in the wrong place. Check the URL when you first log in to Marketo, make sure the sub domain in that URL matches what is in your embed code. For example: If you see https://app-sjst.marketo.com/ then make sure you have that same "app-sjst" in your embed code. Please note: This may vary between your sandbox and production instances.        
View full article
Issue Are Smart List filters that accept text values case-sensitive (e.g. First Name, Last Name)?   Solution Smart list filters are NOT case-sensitive. For example: If you use the smart list filter 'First Name is John', it will return leads with First Name 'John' or 'john' with a lower case 'j' Vice versa: If you use the smart list filter 'First Name is john', it will return leads with First Name 'john' or 'John' with an upper case 'j'  
View full article