Knowledgebase

Sort by:
Issue Description You recently passed the MCE and want to add the certification to your Community profile.   Issue Resolution Certification updates happen every 2 weeks, and your Community profile has to be filled out completely for the update to work. If you don't see your update within two weeks, please reach out to mktcertf@adobe.com .     Is this article helpful ? YesNo
View full article
Issue How to use the Web Page, Referrer URL, or Query String constraints to specify web page when using one form on multiple pages. Solution Use the appropriate constraint to specify which page the form is on when using a "Fills Out Form" trigger or "Filled Out Form" filter in a Smart List. There are three options: Web Page Referrer URL Query String   Web Page This constraint is designed for Marketo Landing Pages. If you have one form on multiple pages, and were attempting to specify a Marketo Landing Page, then you would use Web Page.  If you use Web Page, your value is the Landing Page asset name, such as "Global Contact Form Page". Or if the page is local to a program, the name format would be [program name].[landing page name]   Referrer URL This constraint is designed for external, non-Marketo pages. If the form you have is embedded on an external page, the value you would enter would be the URL of the page. This constraint is very picky about the values entered. Say the form is on http://www.pages.domain.com/contact-us.html . Only the following 2 options would function: Referrer URL - is - http://www.pages.domain.com/contact-us.html Referrer URL - contains - www.pages.domain.com/contact-us   By using "is", the exact value must match. When using "contains" a smaller portion of the whole can be used. Even "contains" /contact-us would have worked successfully, but the less specific the value is the more other pages could qualify depending on the use case. Generally, "contains" is advised with a unique portion of the URL because there can often be querystrings on URLs that would then not satisfy the "is" constraint.   Querystrings If the form is on a page, and the page has a querystring, such as: http://www.pages.domain.com/contact-us.html?product=new-stuff , then the form submission activity on the Marketo record would have a new field in the Detail called Query Parameters. ( Querystring, Query String, Query Parameters are all the same thing.) If you set up direct links to the Page with unique querystrings, then you would be able to use the Querystring constraint and use values from the querystring in the trigger/filter form fillout campaign.
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 When data is synced to Marketo from lookup fields in Dynamics, the unique record GUID is put in the Marketo field rather than the name of the referenced record.     Solution In Dynamics, the data stored in lookup fields is actually the unique ID of the referenced record. Since the record that is being referenced is also in Dynamics, the UI is able to display the name of the record rather than its unique ID. However, when the data for those fields is pushed to Marketo, it is still the unique IDs that are synced over, so you will see the long string of letters and numbers in the associated Marketo fields, and not the name of the records. A workaround for this behavior is to: Create custom fields in your CRM for each of the lookup fields that you intend to sync. Create a workflow in Dynamics that populates those fields with the name of the  referenced record, and stores it as a string of text. When those fields custom fields are synced to Marketo, the data will be displayed as the text that you want instead of the unique IDs. Who This Solution Applies To Customers integrated with MS Dynamics
View full article
Issue Issue Description A REST API call on the Company API or Opportunity API fails with the error  "1018: CRM Enabled -- The action could not be carried out, because the instance has a native CRM integration enabled."     Solution Issue Resolution Per the documentation on developers.marketo.com, the Company and Opportunity APIs are only available on instances that are not currently synced with a CRM such as Salesforce or MS Dynamics.  If your instance is synced to a CRM, you will need to update Company and Opportunity information through the CRM rather than the API.    Documentation for these APIs can be found here: http://developers.marketo.com/rest-api/lead-database/opportunities/ http://developers.marketo.com/rest-api/lead-database/companies/   Who This Solution Applies To Marketo instances with a CRM sync
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 After updating a Segmentation, a person now qualifies for a different segment than previous, but there is no change segmentation activity in the log for that person. Solution This is expected when the segmentation is recalculated. The process will not write change values as this is seen as initial value in this newly approved segment. Any subsequent changes to the records will write a Change Segment activity
View full article
Issue What does the Data Value Change activity with following reasons mean? System flow action sysActionChangeDataValue updateLeadEmailStatus System flow action sysActionChangeDataValue resetLeadEmailStatus Solution Both Data Value Change activity reasons are a result of an automated process known as Durable Unsubscribe https://docs.marketo.com/display/public/DOCS/Durable+Unsubscribe 'updateLeadEmailStatus' refers to durable unsubscribe updating existing records. So when a record's unsubscribe value get's manually changed, the other duplicate record(s) that has the same email address will get updated by the durable unsubscribe and 'updateLeadEmailStatus' will be logged for the updated leads. Whereas, 'resetLeadEmailStatus' refers to durable unsubscribe updating a new record, when its existing duplicate record(s) that has the same email address have 'unsubscribed=true'. So when a new record is created and the other duplicate records have 'unsubscribed=true', the new record will be updated by durable unsubscribe and 'resetLeadEmailStatus' will be logged for the new record. The 'resetLeadEmailStatus' can also occur as follows: Existing lead in Marketo has unsubscribed value set to 'True' Lead that used to exist in Marketo was unsubscribed  Lead is imported into Marketo with unsubscribed value set to 'False'. Momentarily, we can see this reflected in Marketo. Lead's unsubscribed value is changed back to 'True' with reason 'resetLeadEmailStatus'. This is because "When a lead is imported, the unsubscribe flag WILL NOT be overwritten by the import." Durable Unsubscribe
View full article
Included in this article Overview Sometimes the data you see in your CRM system doesn't match what you see inside of Marketo. This document will show you the common reasons to help troubleshoot where the problem could be coming from. What Causes Data Mismatch The vast majority of data mismatches result from sync backlogs, so much of this doc will go over sync backlogs. However, since there are a number of other ways this can happen, here are the most common ones to watch out for: Sync delays from backlog Incorrect set up of campaigns to add leads to SFDC Campaigns Sync user permissions Field Value Validation Field Type Validation Sync Delays from Backlog Whenever an update is made to a record, it generates a System Modification Time Stamp, referred to as a SysModStamp. The creation of a SysModStamp on a field that is visible to the sync user will queue the record to be resynced. Whether the update is made on the Marketo side or on the CRM side, it will trigger the record to be resynced to update the information on the other end through the regular Marketo to CRM sync cycle. When large numbers of updates are made like from a field value changing, then large numbers of records are altered, causing new SysModStamps on those records. This in turn results in large numbers of lead record updates that need to be resynced between Marketo and your CRM. The sync of leads flows at the rate of approximately 10,000 records per hour. If you've updated 10,000 records at once, you can expect the sync of that data to take roughly an hour to complete. If you've updated 20,000 records at once, you can expect the sync of that data to take roughly two hours to complete, and so on. Thousands of updates are synced over in just one API call as opposed to making a single API call for each individual update. Updates synced between Marketo and your CRM through the sync cycle occur in batches—large groups of updates made all at once to allow the data to be transferred more efficiently. That means 10,000 updates to the Lead Object, 10,000 updates to the Contact Object, then 10,000 updates to the Account Object, all within one sync cycle. The sync cycle won’t let one Object dominate an entire sync cycle with large numbers of updates. Any updates over 10,000 will wait until the next sync cycle. Checking for the backlog Long sync cycles are an indication that there are a lot of updates being made. To check when did the last sync happened 1. Go to Admin 2. Go to integration for your CRM (e.g. Salesforce) in the tree on left 3. Go to the top right corner to see the information of Last Synced. Compare the time shown there to the current time. If it's a long time difference, you've probably got a significant backlog of updates waiting to sync. How do you fix it? Stop making more updates. Once the records are queued up to sync between Marketo and your CRM, there's no way to cut it off and stop it from going through the sync. The data will sync through, but essentially you'll have to just wait for it. If you can stop making continued updates until after the backlog has cleared, you'll be helping it to clear faster. Campaign to add leads to SFDC  Campaign set up incorrectly There can also be cases when you are pushing leads to SFDC Campaigns via Marketo Programs or Smart Campaigns. If you have a flow action where you enter an incorrect campaign name or the corresponding status, the leads flowing through this campaign will have issues while syncing. If you've synced the lead from Marketo to the SFDC Campaign but accidentally synced it to the wrong one, you'll have a data mismatch there. Ensure that you have the campaigns with correct names and statuses Sync user permissions Sometimes a lead won’t sync to CRM because the SFDC sync user doesn’t has permissions enabled to allow the Marketo sync user access to it. Ask your CRM Admin to update the permissions so as to allow Marketo sync user access to the record. Field Value Validation If there’s a validation in your CRM on certain fields, and the field value in Marketo doesn’t qualify for the validation, the lead would not sync.You'll see "FIELD_CUSTOM_VALIDATION_EXCEPTION" error messages, which are your indication that this is where the problems are coming from. For example: Let’s say there’s a validation in Salesforce to accept on “CA” as a value for the field “Country”, and Marketo field has it’s value as “Canada”. The lead would not sync to SFDC. To resolve this, ensure that field value aligns with the validation in SFDC. Field Type Validation Field types must be compatible between Marketo and Salesforce. If the field types are different in Marketo vs CRM, it won't be able to sync properly. For example: If the field in SFDC has the type of “Float” and field in Marketo is “Score”, then they aren't compatible and won’t sync. To resolve, ensure that the fields have similar or compatible types in Marketo and CRM
View full article
Issue Description An Email with only emoji in the subject line is displaying "Subject is empty" error and is not approving, or emoji fail to render elsewhere in the email. Issue Resolution If the subject line only consists of emoji, consider adding text. The Email Editor was not designed to insert emoji. However some have been able to insert emoji from outside sources. Those with the most success are inserting UTF-8 encoded emoticons. This specific encoded emoticon can be inserted (copy/paste) through a 3rd party website, located with a general web search: "UTF-8 emoticons/emoji". If the inserted emoji has a different encoding, it may fail to render in the Email Editor, and it may fail to render upon delivery as well. Rendering upon delivery will be reliant on the recipient server. If the emoji is considered invalid, then the 'diamond with question mark' character may remain. Alternatively, b asic symbols could be used instead of emoji, as they are ASCII characters and not reliant on extra encoding. 3rd party sites, identified with a websearch: "ASCII symbols", can be a resource. Another option can be q-encoding the emoji in UTF-8 format to render a string of code that can be used. This code tells the email client to render the desired emoji. To q-encode, copy and paste the desired emoji through a Unicode to UTF-8 translation tool, such as https://tools.bluestatedigital.com/kb/subject-line-assistant ​and then insert the translated code.
View full article
Question: Will the munchkin tracking code work on different sites? For example, my company has 2 domains DomainA.com DomainB.com. DomainB.com is a separate site for our blog. Will the munchkin code work on the 2nd site? I want to incorporate the 2nd site into my lead scoring measures. Answer: Munchkin CAN pass domains, however what it can not do is bring across information. Thus, if you have a domain of A, when a known lead passes out of domain A and into domain B, its activity will be tracked, however, it will be tracked anonymously. In addition, there will be no way to link the activity of a known lead in Domain A to the anonymous lead in Domain B, even though they're the same lead. The next step to tie the activity to one lead would be to do one or more of the following: Manually merge the separate anonymous leads Nurture the lead under each domain, send emails with tracked links to each domain, the activity will be tied together under that lead and automatically merged.  
View full article
Issue Description The Issue When using the Filter 'Member of SFDC Campaign' in the Smart List and checking the people tab to see which records are qualified, this message occurs: Could not evaluate rule 1 (SFDC Campaign 'Campaign Name' not found)  Note: it may state could not evaluate rule # - # can be any number, if the filter is number 5.  # will equal 5 Issue Resolution The Fix Ensure the that the SFDC Campaign being referenced in the Smart List is an ACTIVE campaign The Why This error occurs due to the SFDC Campaign not being an active campaign in SFDC. You may be wondering "then why can I select the SFDC campaign in the drop down?" This is because the Smart List Filter specifically 'Member of SFDC Campaign' similar to 'Has Opportunity' filter reference a backend table in Marketo. This backend table is updated when a SFDC Campaign is removed or renamed. Therefore, Marketo does not directly perform an API call to check if the campaign is selectable, but rather uses the backend table as reference. One way to check in Marketo if the SFDC Campaign is active is to check the 'Added to SFDC Campaign' Trigger in a Smart Campaign's Smart List as that dropdown will only show active campaigns. Who This Solution Applies To Customers integrated with Salesforce
View full article
Included in this article Overview Do you need to create fields in Salesforce and have them connect to specific fields in Marketo like for Lead Score or Acquisition Program? If so, this document will take you right to the instructions on how to get that done! Step by Step Directions for all Salesforce Editions Adding Custom Marketo Fields to Salesforce Video Overview Here's a video tutorial of the entire process that should make it easy to follow along: Salesforce Connector Setup​ Enjoy!
View full article
With the evolving best practices and awareness around data privacy, Marketo will be upgrading how we handle form pre-fill. What change is being made? Starting April 24, 2019, Marketo will only pre-fill form fields if the URL used to navigate to the Marketo landing page contains a valid mkt_tok URL parameter value (which occurs when users click tracked links in Marketo emails). What that means is, any time a person is viewing a Marketo landing page with a form, the URL being used must contain the mkt_tok token in the query string, otherwise the form on that landing page will not be pre-filled. If the URL in the browser window does have a valid mkt_tok tracking token, then the form within the page will pre-fill as expected with data corresponding to the person record associated with that mkt_tok. Also note that if you are embedding Marketo Landing Pages within other web pages using an <iframe>, the mkt_tok would need to be passed from the parent page to the <iframe> URL if you intend for form prefill to work within the <iframe> ​How did it work before? Previously, Marketo landing pages would rely on Munchkin tracking cookies to identify known person records, and forms would pre-fill based on that cookie. Form pre-fill did not require being linked to a Marketo landing page from a tracked email link. Why is this changing? This upgrade is being made to provide a more consistent and more secure experience with Marketo’s forms. We have identified that, in the past, people have experienced scenarios where data pre-filled into a form didn’t always correspond with the actual person viewing the page. For example, people using a shared computer or those who may have been cookied incorrectly by clicking through a forwarded email, could end up viewing incorrect data associated with a different person. To provide a more consistent customer experience, and as a security enhancement, Marketo is upgrading the conditions under which the form pre-fill will display known customer information. In short, pre-fill will only work when users clickthrough links in Marketo emails, demonstrating that they have ownership of the email address associated with the known person record. Below is a list of different scenarios and how form pre-fill will work moving forward. Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature. Scenario Will the form pre-fill? Notes Clicking a tracked link in a Marketo email to a Marketo landing page with a form which has pre-fill enabled Yes The email link must have mkt_tok enabled. Links that are not tracked or that have mkt_tok disabled will not work. Navigating directly to a Marketo landing page with a form which has pre-fill enabled No A direct link to the landing page will not have the mkt_tok present in the HTTP request. Refreshing a Marketo landing page with a form which has pre-fill enabled No The mkt_tok is stripped from the URL after Marketo Landing Pages load so refreshing the page will not include the mkt_tok in the URL. As a result, pre-fill will not work. Clicking a link in a sample email to a Marketo landing page with a form which has pre-fill enabled No The sample email will not have a valid mkt_tok attached to the link and so will not pre-fill the form. If you wish to test form pre-fill you will need to use a real email from a Marketo campaign. Navigating to a non-Marketo page that includes an embedded Marketo form which has pre-fill enabled No This behavior does not change with the upgrade. Pre-fill has never been supported for Marketo forms that are embedded on non-Marketo pages. Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabled With custom implementation The form within the Marketo Landing Page that is being loaded in the <iframe> will pre-fill if the mkt_tok value from the original HTTP request is passed along to the <iframe> URL Visiting a Marketo page with a mkt_tok that is not associated with the same person record as an existing Marketo Munchkin cookie currently stored on the browser No This will prevent the wrong person’s information from being displayed in cases where a computer is shared, or an email with a mkt_tok tracked link is forwarded to another person that may already be cookied as a known person in your database. Copying a Marketo tracked link from an email and sharing/pasting it externally (email, blog, chat, social media post, etc.) that enables another individual to click the tracked link Yes The tracked link in a Marketo email will redirect to a URL with the mkt_tok included, so anyone clicking this link will reach a page and see pre-fill data associated with the known person record from the “to” line of the email.
View full article
System Uptime and Reliability   Month Uptime May 2021 99.932% April 2021 99.942% March 2021 99.900% February 2021 99.980% January 2021 99.974% December 2020 99.988% November 2020 99.935% October 2020 99.536% September 2020 99.870% August 2020 99.947% July 2020 99.933% June 2020 98.296%     Email Deliverability Score     Trusted IPs All IPs Month Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 Cisco SenderBase Good/Neutral/Poor ReturnPath Sender Score 0 to 100 May 2021 Good 98 Good 97 April 2021 Good 98 Good 96 March 2021 Good 96 Good 97 February 2021 Good 99 Good 98 January 2021 Good 98 Good 98 December 2020 Good 98 Good 98 November 2020 Good 98 Good 98 October 2020 Good 98 Good 98 September 2020 Good 98 Good 98 August 2020 Good 99 Good 98 July 2020 Good 98 Good 98 June 2020 Good 97 Good 98
View full article
Issue Issue Description When trying to approve the Launchpoint connection between Marketo and Webex you receive the following error: FailedWebex API call error: validation: Parsing Error : An invalid XML character (Unicode: 0x1b) was found in the element content of the document.?Line : x? Column : xxx? [Webex exception ID = '999999']   Solution Issue Resolution This error is being produced by Webex.  To resolve, go into Launchpoint and re-enter the login credentials. If error persists, delete and re-add the Launchpoint service as per documentation: https://docs.marketo.com/display/public/DOCS/Add+WebEx+as+a+LaunchPoint+Service Who This Solution Applies To Marketo customers integrated with Webex
View full article
What’s changing? On February 21, 2019, Webkit announced the new release of Safari’s Intelligent Tracking Prevention (ITP), known as ITP 2.1 and ITP 2.2 shortly thereafter. With ITP 2.x, all persistent client-side cookies, i.e., non-session cookies created via JavaScript through document.cookie, are capped to a seven-day or one-day expiry.  Mozilla Firefox and Google Chrome have also announced their intent to conform to these new policies, though no details or dates have been released.   How does this impact Marketo? As a result of these changes to cookie policy, 7 days after their initial tracked visit to your domain, the Munchkin cookies of visitors using Safari (or future affected browser versions) created with the existing versions of Munchkin JavaScript will expire, and on subsequent visits they will be tracked as a new visitor.   How does Munchkin operate? On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser.  All subsequent web activity on that browser is recorded against this anonymous record.  In order to be associated with a known record in Marketo, one of the following methods should be used: The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link. The person may fill out a Marketo Form. REST Associate Lead call must be sent.   Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.   How is Marketo planning to address ITP concerns? Marketo will implement a new web service to allow Munchkin cookies to be set with a Set-Cookie header via HTTP response, so that they may bypass the 7-day expiry cap imposed when setting cookies via JavaScript.   Do I need to do anything to take advantage of these updates? In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following: A Landing Page CNAME Secured Landing Pages (i.e. HTTPS) For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com   What happens if I do nothing? Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.   When will the solution be launched? These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020.   Google Chrome Update (Feb. 2020): Google recently announced that the Chrome browser will block all third-party cookies within two years; however, s ince Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions: https://medium.com/adobetech/an-adobe-perspective-google-chromes-announcement-on-the-future-limits-of-3rd-party-cookies-bbb7bb257fdb
View full article
Issue There are two filters available (Acquisition Program and Acquisition Program Name), but only Acquisition Program Name appears in the lead record and is available as a column in the lead views.  What is the difference between these? Solution Acquisition Program is a system-managed field. It isn't available in many picklists, nor in certain filters. Acquisition Program Name is a field that allows you to use this data more freely as it is not locked by the system. Acquisition Program = Master naming for programs Acquisition Program Name = Friendly usable name    
View full article
Issue Issue Description When there is a notification in Marketo for "Microsoft Dynamics Sync Change", sometimes it may also include "localizedMsg" as one of the fields, despite that field not existing in the Marketo instance.   Solution Issue Resolution The "localizedMsg" is an extra bit of wording that shows up in these error messages sometimes, but it is not relevant to the rest of the notification. Focus on the other field(s) listed there, as that's what the notification message is really talking about. You can ignore the "localizedMsg" bit since that's not an actual field.  Who This Solution Applies To Dynamics Users
View full article
Issue An email program fails to send emails to a large number of leads/people in the Smart List.     Solution Sometimes leads/people in your Email Program's Smart List will be skipped in the email send because they already reached their daily/weekly communication limit. You can confirm if this has occurred by following these steps: Open your Email Program. Change your view to Control Panel. Click on View Results in the top left panel to see a list of all activities attributed to the email program. Click on Filter > Custom. Select the Send Email box. Click the Apply button. Scroll to the bottom of the list. If the leads/people have been skipped due to communication limits, you will see that a large number of leads/people listed as "Skipped Lead already used up Daily/Weekly communication limit."   You can check or adjust your Communication Limits in the Admin panel of your Marketo instance.
View full article