Knowledgebase

Sort by:
Summary We have identified an issue that occurred during a recent update released on October 26, 2018. This update inadvertently created a condition where landing pages might lose page elements after being re-approved. Free-form landing pages that contain dynamic content may also have missing elements. Frequently Asked Questions Who is affected? This update affected a subset of landing pages across multiple customers that developed their landing pages with the Free-Form Landing Page editor. Landing pages that have been developed using the Guided Landing Page editor are not affected. How does this affect me? Customers need to ensure their live landing pages are not missing any content. This issue is most likely to affect free-form landing pages with dynamic content, and landing pages that have been re-approved since October 26, 2018. However, please keep in mind that it is possible this issue affected other landing pages as well. Which landing pages should I focus on? First, you will want to focus on your landing pages with dynamic content. Landing pages with dynamic content can be reviewed using the Preview Page functionality as shown in the documentation here. Review by each Segment to ensure all content is present in each version of the page. If you notice missing content on the live version of the landing page with dynamic content, you will need to re-add that content to the page in the Landing Page Editor and re-approve the landing page. Second, you will want to look at commonly used and high value landing pages. Open these in Marketo’s editor to check if content is missing and re-add it if necessary. What content is missing? This issue only affects Rich Text Elements. Landing pages have multiple different types of elements (forms, images, snippets, etc.). The only type of landing page element that are impacted Rich Text Elements. Here’s what to look for: Landing Page Elements Impacted – Rich Text Elements Landing Page Elements Not Impacted – All Other Element Types What if I am unsure that any content is missing? Unfortunately, there aren’t many ways to see exactly what content is missing from affected pages. You should be able to see the correct version of landing pages without dynamic content by visiting the live version. If you cannot reach the live version of the landing page, you can try using The Way Back Machine at http://web.archive.org to see older cached versions of the page. While this is a third-party resource not operated by Marketo, it may be helpful in identifying what content was previously on the landing page. Are all my landing pages affected? It is highly unlikely that every landing page is impacted. However, every free-form landing page has the possibility to be impacted. It is recommended to check your active landing pages as well as the pages that have dynamic content to ensure they display as intended. You can utilize a Landing Page Performance Report to see which Landing Pages are active and which ones have the highest traffic so that you can prioritize those first. Free-form landing pages are the only ones affected by this issue. Guided landing pages are not affected at all. Will cloned landing pages be affected? Landing pages that are cloned from an affected landing page after October 26th could also be impacted. You should validate these cloned pages as well. Why doesn’t Marketo rollback the update that caused this issue? We first learned about this issue after other changes occurred to the code base. Unfortunately, we are unable to selectively roll back updates due to unforeseen changes that may occur. Additionally, many customers have made additional changes since this first occurred and there’s no way to identify which version should be restored. Can Marketo Support fix the issue? Marketo Support is not able to determine what content might be missing. Ultimately, you will need to determine if any elements are missing from your landing pages. Landing Page Verification Utility Overview Marketo recognizes that correction of this issue will take investigation. To help you identify pages that could have been impacted, we have built a new Landing Page Verification utility as a resource for you. The Landing Page Verification utility is a new back end utility that was developed specifically for this purpose. Since it is a back-end utility, it is not polished the way that products are inside the Marketo UI. However, it will identify all landing pages in your Marketo instance that could have been impacted by this service issue. Using the Landing Page Verification Utility This resource will allow you to generate a list of potentially affected landing pages, which will then need to be checked. Please note that landing pages not on this list may also be affected. Navigating to the Utility Since this utility is not built into the Marketo UI, access to it is different than accessing any other feature within Marketo. To access the Landing Page Verification utility, you must manually change the URL from within your Marketo instance. Here are the steps for navigating to it: 1. Navigate to your My Marketo page and take note of the URL in the address bar. In the example here, the URL is https://app-xxxx.marketo.com/#MM0A1 NOTE: In your own instance, the “xxxx” will be replaced by a different 4 digits such as ab07 or sj19 as examples. 2. Change the last section of the URL from #MM0A1 to supportTools/landingPageVerification and hit enter. The URL will change From: https://app-xxxx.marketo.com/#MM0A1 To: https://app-xxx.marketo.com/supportTools/landingPageVerification Reading the Results The first screen that the Landing Page Verification utility opens shows you whether you have pages impacted, and if so, how many. Zero Results Returned If the Landing Page Verification utility is unable to find any pages that are likely to be affected, you will see the page below indicating that no pages were impacted. Pages Impacted If the Landing Page Verification utility identifies pages that have been impacted, it will show how many pages there were. To view the full list of landing pages, check the box and click the Submit button. You’ll see a page like the one below that lists all pages that may be affected. Prioritizing Landing Pages While it’s best to assume that all landing pages in the list need to be checked, it’s possible that some were not affected. If there are many pages listed, it will be helpful to know which ones to prioritize to be checked first. Some landing pages are more likely to have been affected. Here are some things to consider when evaluating which pages should be checked first. Landing pages that have dynamic content are the most likely to be impacted and should be checked first Landing pages that have been edited after October 26, 2018 are likely to be impacted Landing Pages that are archived are not visible to your customers and probably don’t need to be checked Checking Your Pages The pages displayed in the Landing Page Verification utility are hyperlinked so that you can click through to those landing pages directly. When you get to the landing page in Marketo, you’ll need to check the live page to see if there are elements missing. The URL for the live page will be found at the bottom, along with a button to navigate directly to the approved page. Due to the nature of the issue, you may find some landing pages where the Landing Page Editor is missing some elements that still appear in the live page. This sometimes occurs when the live pages are cached versions of the landing page. By comparing these to the versions in the Landing Page Editor, you can use these cached versions to help identify which elements of the page need to be recreated. Recreating Landing Page Elements All missing landing page elements must be recreated. Once recreated, approve your landing page and verify that the live landing page has the correct elements in it. Where to Get Help Marketo’s Customer Support is ready to assist. Please contact us at https://support.marketo.com or through any of the methods listed here.
View full article
No, if you have received the blacklist notification, you are not blocked from sending mail.  You can continue to mail while you work through the remediation steps. The only time we will ever block you from sending mail is if you trigger a listing at Spamhaus, the world’s most respected and widely used blacklist. If this happens, you will receive a call or email to let you know what’s going on and we will work with you to resolve the issue. This is a rare occurrence. Additional Resources: Can you give me the spam trap address that triggered the listing? What is a spamtrap, or spam trap, and why does it matter? What is a blacklist? How does Marketo respond to blacklisting and spam notifications? Top blacklists - What you need to know Blacklist Remediation Successful Reconfirmation
View full article
Issue You have a custom sync filter in place between your CRM and Marketo.  You mark a number of records in your CRM as blocked from the sync and go to Marketo, intending to delete them.  However, the records in Marketo have not been updated with the blocked from sync value in the sync filter field.     Solution The Marketo Sync Filter looks at the CRM to verify if a record's updates should sync to Marketo. This means that if the sync filter field is updated to a blocked value on the CRM side, that value will not be pulled into Marketo. If you'd like that field to be updated in Marketo, you can do one following options: Export a list of the new blocked leads with their sync filter field values and use the list import to update those values on the Marketo side. Create a Smart Campaign to update the sync filter field value on the Marketo side. Make the initial update on the Marketo side, since the block will not go into place until the value is pushed up to the CRM by the sync.      
View full article
Issue You want to see how many (and maybe which) records have been sent a specific piece of content by a nurture stream. Solution In the Streams tab of your Engagement Program, change your view from "Content" to "People". You will see numbers below each piece of content indicating how many were last cast this piece of content and how many have been cast it total. Click on one of these numbers to see the specific records which constitute that total. Please note that the last cast is not necessarily the most recent cast of the Engagement Program, it is the last time that piece of content was sent by a cast.  The "Last Cast" of the first piece of content may be from three weeks ago, while the last cast of the third piece of content may be from this week.
View full article
Issue When retrieving result sets from the /rest/v1/activities.json end-point using a Paging Token, the result set returned by the API appears to be less data than what is in the Marketo UI. In this scenario, we're going to explore how and why Paging Tokens work when utilizing them in REST API calls. SCENARIO Say we wanted to grab all 'Send Email' activities (activityType = 6) that have occurred since 2024-04-12T12:00:00Z, and we're planning to pull these activities every two hours, and increment our paging token every two hours prior to making the /activities.json call to obtain the latest data. Current Time Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z What We Want 1. Retrieve all Send Email activities SINCE  Apr 12, 2024, 6:00:00 AM (MST) == 2024-04-12T12:00:00Z We would start by retrieving our Paging Token with the sinceDateTime parameter = 2024-04-12T12:00:00Z: /rest/v1/activities/pagingtoken.json?sinceDatetime=2024-04-12T12:00:00Z Our response would contain the nextPageToken representing the sinceDateTime: { "requestId": "1607c#14884f3e74e", "success": true, "nextPageToken": "RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====" } We would then pass that nextPageToken into our GET /rest/v1/activities.json end-point, as well as our activityTypeId = 6 to target all 'Send Email' activities that have occurred since 2024-04-12T12:00:00Z. /rest/v1/activities.json?nextPageToken=RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====&activityTypeIds=6 After paging through all of the results (now leveraging the returned nextPageToken from the /activities.json end-point to page through all results), we've returned 15,000 Send Email activities.      PROBLEM We know that, from our Marketing team, that we were expecting ~20,000 email sends since 2024-04-12T12:00:00Z. So why does the result set appear to be missing 5,000 records? Let's examine this further. 'Send Email' activities aren't committed to the Marketo database until the message has successfully been sent from our mail servers. Prior to that, the email is queued, awaiting it's launch to it's receiving mail server. This can present a delay from the time the email is sent, to when the activity is recorded to the Marketo database. For example, say there were two campaigns sending 10K emails each: First Campaign Send: 2024-04-12T12:30:00Z (30 minutes after our sinceDateTime token) Second Campaign Send: 2024-04-12T13:45:00Z (110 minutes after our sinceDateTime token, 10 minutes prior to when the call was made) While the first campaign send is most likely accounted for in the database (Send Email activities have been committed), Campaign #2 is still processing and sending out all 10K emails in the background. For this scenario, Marketo has only committed 5K out of 10K email sends to the database at the time the call was made. Without noticing the missing data, you repeat this process two hours from now, incrementing your sinceDateTime token by two hours as well, assuming you'll get all the new Send Email activities for the past two hours. This would now lead to you missing the 5K Send Email activities that were still being processed, but not yet committed to the database. SOLUTION The nextPagingToken returned in the /activities.json end-point is position based, and can only pull data that has been committed to the Marketo database, which inherently changes as records are being processed. If, for instance, you made the original /activities.json call at (Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z), and used the same sinceDateTime token 5-10 minutes later (Apr 12, 2024, 8:10:00 AM (MST)), you would now notice that campaign #2 has fully finished it's processing AND committed the 'Send Email' activities to the Marketo database with dateTime stamps less than Apr 12, 2024, 8:00:00 AM (MST). So, what's the best way to ensure you're retrieving all the data? Solution #1 Increment your sinceDateTime token based on the MAX(created_at) dateTime returned in the latest result set, rather than incrementing it based on an interval (every two hours). This would help ensure you're not missing records that were processing, but not yet committed to the Marketo database. Solution #2 If the data you're retrieving does not need to be live, we would recommend using the Bulk Extract API to pull this data at a lower frequency (such as twice per day 12AM & 12PM). This would greatly decrease the chances of missing records that weren't committed to the database.
View full article
Issue You are unable to archive or delete an asset in Marketo. When you try to do so, you get an error: "The following assets are in use or used by other assets."     Solution To archive or delete the asset, you will need to determine where it is being used. Click the Used By tab for the asset you are trying to delete and see what other assets reference it in some way. For instance, aSmart Campaign may be using it in the Smart List or the Flow Steps, or a report might have it in the Smart List. Once you find where your asset is being used, you can go and remove references to it from the other assets. This should allow you to delete or archive it.
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 The standard unsubscribe footer shown in Admin > Email is not being appended to a particular email. Solution Issue Resolution This can happen when an email contains the system token unsubscribe link:  {{system.unsubscribeLink}} When an email contains this token, Marketo does not automatically append the unsubscribe HTML snippet, found at Admin > Email > Unsubscribe HTML. Check the HTML of the email asset with this behavior. Search the text version of the email. You may find the {{system.unsubscribeLink}} in the template you are using. If you have searched the HTML of the email, and are not seeing the system token, contact Marketo Support.    
View full article
Issue: My landing page is showing the wrong title, why is this and how do I fix it?   Solution: When you clone a landing page, the title of the old page carries over to the new one. In order to update the page title please see Edit Landing Page Title and Metadata for detailed instructions.
View full article
Issue Description Email Insights does not display any data or metrics for specific program when the emails in the program are operational.   Issue Resolution Operational emails are hidden by default, so no data or metrics will be shown in Email Insights unless 'Operational Emails' are included   "Does Email Insights support Operational emails? Yes. By default, Operational emails are hidden from view and querying. However, you may change this setting under the Personal Settings panel." docs.marketo.com/display/public/DOCS/Email+Insights+FAQ   Who This Solution Applies To Customers using Email Insights Is this article helpful ? YesNo
View full article
Issue When you send an email that was cloned from a previous campaign and updated, the sent email shows the old content rather than the new content. Solution This can be caused by Dynamic Content in the email.  If you clone an email with Dynamic Content but only update the default content, then the old content will be sent to leads who are not part of the default segmentation.  Open the email in the editor and see what email elements are displayed in the Dynamic tab.     Check the different segments in the editor and see which ones have the old content. You can update the dynamic content for each segment or simply make the content static, which will make the email use the default content for all leads.    
View full article
Included in this article   Overview The Issue The Explanation   Overview Sometimes you'll see an organization show up as "ISP - Anonymous - Proxy" in your visitors list in RTP.   The Issue RTP is a powerful product with an immense database, but not every ISP can be found.  When we receive a visit from an ISP we can't identify, instead of omitting them from our results, we use the name "ISP - Anonymous - Proxy" and set the location to "United States.     The Explanation Pretty much any free Wifi signal you find like at a library or coffee shop will be listed as an Internet Service Provider (ISP). The admins for that ISP service can configure their network in any way they would like, including whether they allow for identification of their network. If there is no data provided, there's nothing for RTP or any other service to gather. In that case, that's when you'd see the "ISP - Anonymous - Proxy" listing for a visitor in RTP.
View full article
Issue How does Munchkin tracking work when you have one page inside an IFrame on another page?     Solution Munchkin will track page visits for whichever pages include the Munchkin tracking code. If you only have Munchkin on the main page, visits will only be tracked for the main page. If you only have Munchkin on the IFramed page, only the IFramed page will record a page visit. If you have Munchkin tracking on both the main page and the IFramed page, visits to both pages will be recorded in the lead's activity history.   If the main page and the IFramed page are on two different domains, the lead must be a known lead on both domains in order to be tracked on both pages.  Please see this post for more details on Munchkin tracking on multiple domains:  Using Munchkin on Multiple Domains.    
View full article
Included in this Article: Overview The Content Recommendation Engine (CRE) is a powerful tool that can recommend selected content based on a visitor's information in the Marketo database. While you may want the CRE to appear on any page in your website, you may only have certain pages which you do or don't want the CRE to appear. In this article, we will demonstrate two ways of achieving this inclusion or exclusion of the CRE. Edit the CRE Settings First, go to Account Settings In the Domain tab of Account Settings, you will find the options for customizing the appearance of the CRE Enter the URL you wish to include or exclude in the URL Path field You can use wildcards tokens (*), which will match any character or sequence of characters, to match other pages on your website. Edit the HTML If you know how to edit your website's HTML code, you can edit the code to exclude pages. Between the <head> </head> tags on the page you wish to include, insert this CSS code: <style> .insightera-tab-container-bottom{      visibility: hidden !important; } .insightera-bar{        visibility: hidden !important; } </style> If you don't know how to edit your website's HTML, let the developer of your website know you want to have this done.
View full article
Issue Leads were sent the email and clicked on a web page link on the email. However, the web page activities were not associated to these leads.   Solution Issue Resolution Check that the link clicked in the email has tracked link enabled If the web page activities are associated to other records (e.g. duplicates), then: Check who was 'cookied' on the web browser before the visit web page activity was recorded for the other records. This can be checked by looking at the web page activities recorded in the activity log. Check the User Agent details of the Click Link activity of the lead that was sent the email and compare it with the User Agent details of the Web Page Visit activity of the other record. The following tool can be used to help interpret the device details from the User Agent details: developers.whatismybrowser.com/useragents/parse/#parse-useragent In case of a non marketo landing page , check whether the munchkin is enabled correctly over the page without any customization. Reference Doc :- Munchkin Tracking
View full article
Issue The count for the audience of an Email blast program does not match the total members of the Email Program after it has been executed.     Environment This issue is applicable to users who have recently run an Email blast program in Marketo. Solution  The disparity in numbers occurs because the Audience Smart List is evaluated at the moment you access it. As your records evolve, this number can change after the Email Program is run. In contrast, the number of program members, who are the recipients that were emailed through the program during the scheduled run, is fixed at the point the program is executed. 
View full article
Summary When submitting a file for bulk import via the REST API, the uploads appears to stall with no response. Issue Occasionally Bulk Import API calls will "hang" or "stall" never returning a response. This may appear to be a blank or missing response when the API is actually still waiting for the end of the file to be transferred. Solution You can add the following header: 'Transfer-Encoding: chunked' to your API calls and it will fix this issue. Please note that adding this header on the client side will cause cURL to send data in chunks. For more information on chunked file transfer, see Wikipedia: Chunked Transfer Encoding Environment REST API Bulk Import
View full article
Issue Discrepancy between Marketo webinar atttendance and webinar provider attendence report Solution Compare Webex report with Marketo Program members list to determine which leads are involved. Check to see if the leads involved have the same email address but used different names to register/attend. Workaround: Upload Webex final report to a static list and use the list to update the program attendance.   Root Cause Webex issues two reports, a preliminary when the webinar is finished and a final report approx. 12 hours later, which may have updated attendance info.  Marketo Engage uses the preliminary report to set the attended status in the program and does not update when the final report is released. Environment Webex Marketo Event Program synced to Webex webinar Final attendance report from Webex, not preliminary
View full article
Issue Issue Description You have a field (e.g. Most Recent Website Visit) that you want to see previous values for without needing to look through the activity log.     Solution Issue Resolution This can be done using a few custom fields, and one trigger campaign. Make duplicates of the field you want to see most recent values of (e.g. Most Recent Website Visit 1, Most Recent Website Visit 2, etc.) while still keeping the original field. Use the original field as you previously have, but set a trigger campaign to look for data value changes to that field. In the flow of that campaign, set the logic like so:   Change Data Value: Most Recent Website Visit 3 new value: {{lead.Most Recent Website Visit 2}} Change Data Value: Most Recent Website Visit 2 new value: {{lead.Most Recent Website Visit 1}} Change Data Value: Most Recent Website Visit 1 new value: {{lead.Most Recent Website Visit}} Using the above flow, the most recent values for the field can be checked without looking into an activity log. This can be useful in a number of ways, for example this information could be included in an email or alert. Another example, if the primary field (in the above example it is Most Recent Website Visit) is updated to a value that it should not have, then you can setup another campaign to update Most Recent Website Visit using the value in Most Recent Website visit 2 to restore the previous value.   Warning Please Note: The above process can be somewhat resource intensive (particularly if a large number of records trigger the campaign at close to the same time), this should be done with as few fields as possible to assure good instance health overall.
View full article
Issue The format of the landing page is distorted in comparison to the version displayed in the landing page preview.  Environment SSL Certificates Landing Page Domain Landing Page format is different from preview Landing Page contain unsecure content Landing page template has http instead of https   Solution Ensure all the links used in HTML code used in the landing page template is referencing "HTTPS" and not "HTTP". You can follow the steps outlined in the document below on how to edit landing page template.  Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-templates/edit-a-marketo-landing-page-template.html **NOTE: If the landing pages is approved, a draft version of the landing page is created for any landing pages which is using the landing page template. You can mass approve those landing pages via following steps outlined in the document below. Link: https://experienceleague.adobe.com/docs/marketo/using/product-docs/demand-generation/landing-pages/landing-page-actions/approve-multiple-landing-pages-at-once.html?lang=en Root Cause Once you secure your Marketo landing pages to be served over "HTTPS", you should have not links referencing "HTTP" (unsecured) assets or pages. 
View full article