Your Achievements

0% to

Next /

to gain points, level up, and earn exciting badges like the new !

View All Badges

Open Alert Bar

Knowledgebase

Featured article

Included in this article Overview Data you’ll get from Email Bounces Bounce Categories Hard Bounces Soft Bounces Bounce Details Building the Directory 1. Create 6 custom fields 2. Create a Program to house everything 3. Create a Static List 4. Create two Smart Campaigns Smart Campaign One - Logging Email Bounces with Bounce Details Smart Campaign Two - Remove Leads From the List After Successful Deliveries 5. Create Custom List View Showing Bounce Details Overview Bounce activities carry details for why the email was bounced, but it’s housed within the activity log entry, not in a field on the lead record, so it’s difficult to export that data. This article will show you how to extract that information to create a directory of leads bouncing emails and how to make the list automatically update. This will also create counters for bounces and successful re-deliveries after bounces happen. Data you’ll get from Email Bounces Bounce Categories Email bounces come in different types depending on why the email was bounced; Hard Bounces or Soft Bounces. Hard Bounces Hard Bounces come in two types, Category 1 and Category 2. Category 1 bounces are emails that have been marked as spam by the recipient mail server. Many email servers monitor blacklists or spam traps, so after de-listing with them, leads that have had a Category 1 bounce previously may be able to receive emails again. Category 2 bounces occur due to an email address that is invalid or doesn’t exist. Soft Bounces Soft Bounces come in three different types, Categories 3, 4 or 9. Category 3 bounces are usually temporary, caused by full mailboxes, timeouts, or throttling. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 4 bounces are caused by technical problems, Transient Failures, Admin Failures, DNS Failures. Any email with this designation has been retried for up to 24 hours (36 for AOL). Category 9 bounces are unknown, undetermined or gibberish details. Any email with this designation has been retried for up to 24 hours (36 for AOL). Bounce Details When an email is bounced, the recipient mail server includes details of why it was bounced. These are created by the admin of the recipient mail server and vary greatly, but most will give some explanation that can give valuable information. Email Bounce Codes Building the Directory 1. Create 6 custom fields You’ll need 6 custom fields, two DateTime fields, two Score fields, and two String fields Name the DateTime fields “Bounce Date” and “Email Delivered After Bounce”. Name the Score fields “Email Bounces” and “Deliveries After Bounces” Name the String fields “Email Bounce Details” and “Email Bounce Category” Directions for creating Custom Fields can be found here: Create a Custom Field in Marketo 2. Create a Program to house everything Use a default program type and name it "Directory of Leads Bouncing Emails". Info on creating programs can be found here: Create a Program 3. Create a Static List This static list will be your actual directory that contains all of the leads that are currently bouncing emails. Name it "Active Bounce List". Info on creating a static list can be found here: Create a Static List 4. Create two Smart Campaigns These two Smart Campaigns are what will be used to add and remove leads from your active bounce list. Info on creating Smart Campaigns can be found here: Create a New Smart Campaign Smart Campaign One - Logging Email Bounces with Bounce Details Your first Smart Campaign will be used to listen for any email bounces that occur. The campaign will populate the “Bounce Date”, “Email Bounce Category” and “Email Bounce Details” fields. It will then add one point to the “Email Bounces” score field which can be used to count how many bounces have occurred per lead. Lastly, the campaign will add the lead to the static list which will be an active directory of leads who are bouncing emails. Campaign Smart List Use the two triggers of “Email Bounces” and “Email Bounces Soft” in the Smart List. Set both triggers to “is any” so that they will fire whenever any email bounces for any reason. Campaign Flow The Flow of the campaign will have 5 flow steps. The flow will use a System Token and some Trigger Tokens, which can be used to pull details out of the action that activated the trigger. In this case, the Trigger Tokens will be pulling out the details on why the emails were bounced. That info is in the bounce message and is logged in the lead's activity log. Normally you'd have to comb through the activity log one at a time to find these details for each individual lead. This method, however, will pull the details out automatically for all leads. Flow Step 1: Change Data Value Attribute: “Bounce Date” New Value: {{system.dateTime}} Flow Step 2: Change Data Value. Attribute: “Email Bounce Category” New Value: {{trigger.category}} Flow Step 3: Change Data Value Attribute: “Email Bounce Details” New Value: {{trigger.details}} Flow Step 4: Change Score Score Name: “Email Bounces” Change: +1 Flow Step 5: Add to List List Name: “Active Bounce List” Smart Campaign Two - Remove Leads From the List After Successful Deliveries Campaign Smart List The Smart List of the campaign will need a trigger for “Email is Delivered” set to “is any” and also a filter of “Member of List” looking just for leads that belong to your Static List. This way, the campaign will only apply to leads who have had an email bounce but have then had an email successfully delivered afterwards. Campaign Flow The Flow of the campaign will have 3 flow steps to do the following; log when the email was delivered, add a point to the "Deliveries After Bounce" Score Field, and remove the lead from the "Active Bounce List". Flow Step 1: Change Data Value Attribute: “Email Delivered After Bounce” New Value: {{system.dateTime}} Flow Step 2: Change Score Score Name: “Deliveries After Bounces” Change: +1 Flow Step 3: Remove from List List Name: Operational.Active Bounce List 5. Create Custom List View Showing Bounce Details The custom fields you’ve created for email bounce information won’t show automatically in the view of your list. You can create a new view of the list to show just this information so that when it is exported it will give you only the email bounce information you need. Once the list has the necessary details, it can be exported with those columns included so that you can work with it. You can identify emerging trends and issues with your deliverability by looking for common themes among the bounce details. Directions for creating Custom Views can be found here

Featured article

(Article Updated - August 2024) Overview A blocklist is a database of IP addresses or domains that have been associated with the sending of unsolicited commercial email or spam. Internet Service Providers (ISPs) and business email networks use information from blocklists to filter out unwanted email. As a result there can be a drop to inbox delivery rates if the IPs or domains involved with sending email are listed on a blocklist. Marketo’s Email Delivery and Compliance team monitors blocklist activity on our IPs and domains daily. When an impactful listing occurs, we reach out to the blocklist, attempt to identify the sender that triggered it, and work with the blocklist organization to get the listing resolved. There are thousands of blocklists, most will not have a significant impact on your delivery rates. Below, we have compiled a list of the blocklists that commonly appear across our sender ecosystem. Each blocklist has been grouped into a top tier (Tier I) by most impactful, to the bottom least impactful tier (Tier III). These may have little to no impact across our sender network. Tier I Blocklist Spamhaus (SBL) Impact: Spamhaus is the only blocklist that we categorize as a Tier I for a reason: it has by far the greatest impact on delivery. It is the most well-respected and widely used blocklist in the world. A listing at Spamhaus will have a negative effect on your ability to deliver emails to your customer’s inbox and can cause bounce rates of over 50%. Evidence suggests that most of the top North American ISPs use Spamhaus to inform blocking decisions. How it works: Unlike many blocklists, Spamhaus lists senders manually. This means they are proactively watching sender activity, collecting data, and base listings on a number of variables. Most commonly senders are listed for mailing to spam trap addresses that Spamhaus owns. Sometimes Spamhaus will list senders based on recipient feedback as well. Next Steps: Please note that every Spamhaus email can be quite different depending on the information provided and the nature of the listing . Because Spamhaus has multiple types of listings, the remediation steps are based on which type of blocklisting has occurred. We have listed the most common types to affect Marketo customers, from most to least impactful. Impact can range from a full block of top severity, to a partial block that is less severe (CSS Data, DBL). If remediation isn’t performed and the problem not addressed, these listings can increase in severity and turn into a full blocklisting. Spamhaus Blocklistings Types SBL (full blocklisting) Considered the most impactful. Remediation steps: Our team monitors closely for Spamhaus listings. Once alerted to the listing, we send an email notifying the customer, and reach out to the Spamhaus contact to start the remediation process. Only a Marketo delivery team member should be in direct correspondence with the Spamhaus contact, to speak on behalf of the customer, and to relay their questions and instructions, ensuring quick resolution and reduced impact. Senders that trigger this listing on a shared IP range will be moved to a more isolated, penalty range (IPB), so as not to impact the other shared senders. Those affected on a Dedicated IP, only impact their own sending and will not be moved. However, depending on the severity of the issue, our team may need to revoke a customer’s ability to send any emails until full resolution. The listing will last until Spamhaus is satisfied that the offending sender has taken the appropriate steps to mitigate the problem. SBL CSS Customers are alerted of the listing with an email containing all the information needed to immediately begin the remediation process. This is part of an automated trigger listing, that allows for a customer to delist directly on the Spamhaus website, after they’ve completed remediation. Remediation steps: Customers will go to the Spamhaus IP lookup website, at https://check.spamhaus.org, where they can check on the status of their IP and continue to monitor it in real time, until it is no longer listed there. Follow the remediation and delisting instructions provided, and check for specific details in the blocklist notification email. DBL (Domain blocklisting) Customers will receive an email notification alerting of the company domain being listed. The email will contain specific information to help narrow down and identify which email source likely triggered it within Marketo. It’s important to note that any email sent from outside of Marketo, that contained the company domain, is suspect. This means, if the sender uses multiple IPs and/multiple email platforms, then any of those could be the source. Remediation steps: Follow the detailed instructions in the email, which will also provide a link to the Spamhaus Domain reputation checker webpage, to check the real time listing status of the affected domain. Once the email source is identified and cause addressed, this customer will follow the online instructions to request to be delisted. Tier II Blocklist SpamCop Impact: SpamCop is not used by any of the major North American ISPs to inform blocking decisions, but it makes it to the Tier II list because it can have a significant impact on B2B email campaigns. SpamCop is considered a Tier I one blocklist for B2B marketers but a Tier II for B2C marketers. SpamCop is a dynamic IP blocklist, that can affect a single IP or a subset of IPs Typically, the block will automatically lift within one business day, but can take longer for relisted IPs. To have triggered a SpamCop listing likely means the sender has a list management problem that should be addressed. How it works: SpamCop lists IPs for one of two reasons: Either the email hit SpamCop spam trap addresses OR A SpamCop user has reported the email unwanted. Most of SpamCop’s spam traps are previously valid addresses that have not been active for 12 months or longer. Remediation steps: If you are seeing a significant number of bouncing emails caused by a SpamCop blocked IP but aren’t sure if your email activity triggered the listing, first identify whether you are sending on a shared sender network or not. If sending from a shared IP range when this occurs, you or any other customer sending from the same network may have contributed to the IP block. This IP block will automatically get dropped within a business day. For those on a Dedicated IP that trigger a listing, refer to the above remediation steps and resources, to address the list management issue. Tier III Blocklist (Low/ No impact ) These are considered the lowest tier and therefore cause the least impact across the Marketo sender ecosystem. Some of these blocklists were more impactful at one time, while others are only impactful based on the sender region (Manitu). Others still can suddenly flare up (Lashback). There are also many blocklists that are ignored (0spam), and are not taken seriously because they do not provide any means to delist once on the list (NoSolicitado) or that they charge money to have the listing removed ( UCEPROTECT ). The pay-to-delist model is not well respected in the email industry. When using blocklist tool checkers, such as MXToolBox, many blocklists will appear, but very few are relevant. Here is our selection of Blocklists you may come across that are least impactful: Project Honey Pot SpamAssassin URIBL/SURBL DrMX PSBL 0spam HostKarma Ascams ZapBL Barracuda Trendmicro Inc. Cloudmark Proofpoint Invaluement ISP Blocklists Some ISPs use internal blocklists to make blocking decisions. Examples include AOL, Yahoo, Gmail, Outlook and Hotmail. If your IP is being blocked by one of these networks, and those networks have a large presence in your lists, a block of this kind could have a noticeable negative impact on delivery. Marketo monitors for significant ISP blocks. Those experiencing deliverability issues with emails not making it to the Inbox and bulking in the spam folder may benefit from additional services with our Email Delivery Consultants. Remediation Steps: Email Delivery Compliance Team works to resolve any ISP blocks. ISP blocks are are usually resolved or lifted within less than 24 hours of a delisting request. Customers experiencing significant blocks for Microsoft domains (outlook.com, live.com, microsoft.com), can submit a request to the delivery team to seek mitigation on their behalf. Additional Resources: Blocklist Deep Dive Abuse Report Deep Dive What is a spamtrap, or spam trap, and why does it matter? Blocklist remediation Blocklist resolution flowchart Successful lead reconfirmation What is a blocklist?

Issue Description You want to set a field such as "Country" to be required on a list import. Issue Resolution You cannot require a field to be included on a list import. To see any leads imported recently with blank values you can setup a smart list with a subscription Filters -- Lead was created Source Type - Import [Field you are wanting to watch] is Empty You could setup a daily subscription to get the leads who qualify and then correct those leads as needed. Is this article helpful ? YesNo

A business wouldn’t be able to run successfully without great data. As a data analyst, we understand that you rely on Marketo to make accurate reports for your company. To make sure you’re using Marketo to the best of its ability, here are some trainings we recommend to help get the most out of Marketo’s data and analytics. Instructor-Led Trainings Check out the Using Marketo Analytics and Reporting instructor-led training to get in depth guidance on how to map and measure your customer journey, tie revenue to your marketing campaigns, share progress through reports and easy-to-read dashboards, and focus your investment where it will have the most impact. Core Concepts II Core Concepts II is a great overview of some of Marketo’s more advanced functions, which can be used to enhance your reports. Free Training Videos Our free training videos on reporting and analytics cover performance insights, standard reports, and analytics. These videos are followed by a brief quiz to check your understanding of the material.

What change is being made? Marketo Sales Connect/Toutapp will no longer be supporting our legacy .Net Add-In for Outlook, as of May 19, 2019. Because Marketo made a replacement add-in available in February 2019, we expect minimal impact as there are teams that have already been progressively migrating on to the new add-in. However, it’s important to note that the .Net Add-In will not stop working on May 19, 2019 – it will just stop being supported. If you experience an issue when trying to use the .Net Add-In on or after May 19, 2019, you will be directed to update to the new 0365 Add-In. Screenshot of .Net add-in buttons Why is this changing? In recent updates, the O365 Add-In reached feature parity with the .Net Add-In, making .the Net Add-In a redundant experience. The O365 Add-In takes advantage of Microsoft's advanced API’s and delivers a superior experience that works across Windows and OS operating systems as well as in browsers. With quality and stability being the focus of this change, Marketo wants users to update to the new 0365 Add-In. What action is required? After May 19th, the .Net Add-In will continue to work for any customers who have it already installed. However, Marketo will no longer support troubleshooting this version, and any customers reporting issues will need to upgrade by completing the following steps:The new newly released 0O365 Add-In, released on Feb 26, 2018, has feature parity with the old .Net Add-In and is built on Microsoft's advanced API’s. Individual users will need to complete the following steps to upgrade: NOTE: The O365 Add-in is only supported by Outlook 2013 and higher. Users who are running a version of Outlook 2010 or older will need to upgrade their version of Outlook before installing the O365 Add-In. How to uninstall the .Net Add: http://docs.marketo.com/display/public/DOCS/How+to+Uninstall+or+Reinstall+Sales+Engage+from+Outlook How to install the O365 Add-In: http://docs.marketo.com/display/public/DOCS/Installing+Sales+Engage+for+Office365+Mac+OS%2C+Windows%2C+and+Online

Issue Issue Description A smart list in the Marketo database generates an amount of records for a specific Created Date and a report in Revenue Explorer reports a different number of records for the same Created Date. Solution Issue Resolution Revenue Explorer (RCE) will report counts of records by Create Date by which ever is earlier: the Marketo Create Date or the CRM create Date. If the record was created in Marketo on May 1st, and then synced and created in CRM on May 5th, RCE will report that record's Create Date as May 1st. If the record was created in CRM on February 13th, and then synced and created in Marketo on March 20th, RCE will report that record's Create Date as Feb 13th. Additional example: If a person was cookied for the first time via a web page visit on April 3rd creating an anonymous record in Marketo, and then filled out a form on April 5th converting the anonymous record to a known person and synced to CRM on April 7, RCE will report that record's Create Date as April 3rd because that's when the anonymous record was created in the database. If a smart list is generated to compare with Revenue Explorer to identify records by Create Date, there can be differences in count due to the following possibilities: 1) RCE Sync - the sync to RCE delays data by about 24 hours. If a net new record was just imported into Marketo, RCE would be able to report on it approximately 24 hours later. 2) Differences in defining measures/filters - as stated above, RCE will report based on the record's Create Date (visible on the Marketo Record's Info tab), and the Smart List could be based on different filters. See this related document about smart list filters (LINK TBD). The Smart List could be looking at a date when records became known, or could be looking at when the record was created in Marketo; RCE and the Smart List could be looking at different dates. 3) Time zone difference - RCE will always report on Central Time, and Smart Lists will report on the instance's local time. Who This Solution Applies To Customers with Revenue Explorer

Issue Trigger Tokens in a Batch Campaign Flow are not functioning as expected, or result in an error. Solution Issue Resolution Trigger Tokens can only be used in a Trigger Campaign Flow and will not work in batch campaigns. While originally intended for Interesting Moments, Trigger Tokens will also work in Change Data Value flow steps. The associated Trigger Tokens will only function with the corresponding Triggers denoted by the green check-marks in the chart here.

Issue Issue Description Possible disadvantages of maintaining Engagement/Nurture Program emails in Design Studio. Solution Issue Resolution Housing all of your emails for email nurture content in Design Studio could cause the following issues: 1. Reporting: Reports can specify Emails in Design Studio, however they will show results for any send of the individual email and will not be constricted to the program they were sent from. 2. Asset re-use in Engagement Programs: When using an engagement program, an asset is scanned for its ID. If that asset has been previously sent to a record via any other send, the engagement program will skip that send for that record. This could become a problem when reusing email assets housed in design studio in different engagement programs. 3. My Tokens: my.tokens will not properly render as they are based on a program folder. The assets that reference them need to be in the folder as well. In my testing, assets in design studio do not have a frame of reference for mytokens. Emails will not populate mytokens if they are housed outside of the program that owns the tokens. With all of this noted, our recommendation is to utilize detailed templates in design studio and continue to clone your engagement programs and alter them as necessary. Although this presents some busy work in the short term, it pays off dividends in the long term when it comes to reporting, the use of my.tokens, and guaranteeing that records are sent the assets you are specifying in your programs.

Issue Description Munchkin activities recording stopped and web page activities were not logged. Since the activities were not immediately registered, any Trigger Campaigns set to initiate when those activities occurred would not have been triggered. Issue Resolution Initial Steps: As soon as you identify an issue with Munchkin Activities recording, contact Marketo Support to ensure that proper steps are taken to prevent any data loss. Once the activity data is back-filled, identify all the Smart Campaigns that were impacted and need to be replayed. If you need assistance to identify which smart campaigns were active during this incident, our Campaign inspector is a great tool to assist you. https://nation.marketo.com/docs/DOC-4470-campaign-inspector-for-triggered-recurring-campaigns. Replay Impacted Smart Campaign: After you have identified the smart campaigns that were impacted, create a new smart campaign using the following smart list filters; For Smart Campaigns triggered by clicking a link on a web page, use the following filters. Select the applicable link and timeframe based off what datacenter your instance is located in. The second filter is to prevent activities that were not impacted from replaying. For Smart Campaigns triggered by a web page visit, use the following filters. Select the applicable web page and timeframe based off what datacenter your instance is located in. The second filter is to prevent activities that were not impacted from replaying. After the Smart List is set up, the flow steps should mirror the flow steps of the original Smart Campaign that you wish to replay. If you experience any issues with replaying the impacted smart campaigns, please contact Marketo support at https://support.marketo.com, or through any of the methods listed here.

Issue Interesting Moments for a specific Marketo record are not showing up in SFDC Sales Insight for the record with the same email. Solution The most common cause for this is that the record in SFDC is not the same record as the one in Marketo. This can happen if there are duplicate records in Salesforce with the same email address. To check if the record in Salesforce matches the record in Marketo, compare the SFDC ID. On the Marketo side, this can be found in a field on the Lead Database record. The SFDC ID for a record in Salesforce can be obtained from the URL. It is generally the the 15 alphanumerical characters near the end of the URL (e.g. 012300000012BYN) - here is an article in Salesforce for more information: help.salesforce.com/articleView?id=000004383&type=1

Issue How to check what version of the Marketo Solution you have installed in your Microsoft Dynamics CRM environment. Solution Navigate to the Settings section of Dynamics, and then to the 'Solutions' menu. Under the 'Solutions' menu there is a list of all installed solutions called 'All Solutions', and once you have located the Marketo Solution in there, its version number will be listed in a column beside its name. Who This Solution Applies To Users with Microsoft Dynamics integrations.

Issue Issue Description An email with inserted bold/italic font in email subject line is not approving, with an error of "Cannot Update Stale Object," or does approve but the special font text disappears upon approval. Solution Issue Resolution The subject line in an email is intended to be plain text. Some have found success inserting basic symbols, or even emoji with specific encoding, though the rendering of these characters is dependent on the receiving server. Related: Using Emojis in Marketo Emails

Issue Issue Description You would like to have an RTP domain in your Account Settings in Web Personalization removed Solution Issue Resolution We cannot delete domains from accounts unless the tag for this domain has never been implemented on your website. To check that, log-in and verify that (by navigating to the visitors page and filtering the data by this domain and see that there is no data showing up). If there is no data under this domain - go ahead and submit a support ticket to delete the irrelevant domain from you Web Personalization Account. Who This Solution Applies To Web Personalization Customers

Issue Issue Description You are attempting to send a list to Google via your Google Customer Match integration, but when you open the dropdown to select the destination list, none of the lists you have prepared are visible. Solution Issue Resolution For Marketo to see a list and present it as an option, the user that was used to set up the Customer Match Launchpoint service needs to have visibility of that list. Only lists that this user can see will be available. It is not possible to check which user was used for this setup from Marketo's Launchpoint menu, however you can alter which user is being used to connect to Google by opening the associated Launchpoint service and selecting 'Re-authorize', and then follow steps 6 and onwards from the following article: Add Google Customer Match as a LaunchPoint Service Who This Solution Applies To Users making use of Google Customer Match

Issue Issue Description After following the set up directions for a domain alias for a new landing page domain, the new domain redirects to a Marketo 404 page. The instance has SSL for Landing Pages. Solution Issue Resolution Contact Marketo Support and request that the new domain be added to your SSL certificate. If this has been done, they will be able to help you troubleshoot further. Who This Solution Applies To SSL for Landing Pages

Issue Issue Description Users are unable to reference a static list that is in a shared folder. Solution Issue Resolution Depending on how you're attempting to reference a static list located in a shared folder, you may be unable to do so. If you are using a 'Member of List' filter you will be able to see the static list. However if you're using the 'Was Added to List' filter or the 'Is Added to List/Is Removed from List' triggers you will not be able to see the same list. The reason for this is because the 'Member of List' filter is only looking at membership of the asset whereas 'Was Added to List' and the 'Is Added to List/Is Removed from List' triggers actually need to look at the activities of records. This would cause problems if the workspace where we are referencing the static list does not have access to the same partitions as the workspace that the static list lives in. So looking at only membership and not these activities makes for a much more consistent experience.

Issue Issue Description A Champion/Challenger A/B test contained in a nested program within an Engagement Program stream only sent the Champion email. Solution Issue Resolution Per the Product Documentation Champion/Challenger tests can be used within Nurture Engagement Programs, however, the email asset with the Champion/Challenger test must be within the stream. Having a nested program in the stream with a local email asset with the Champion/Challenger test will not function; only the Champion Variant will be sent, similar to what happens in other batch sends.

Issue Issue Description Account records were merged in Salesforce and there is concern if this merge will sync to Marketo. Solution Issue Resolution If you would like this change to be reflected on the affected Contact records that are synced to Marketo, then you will need to update the Contact records so that their System Modstamp field is updated (this can be done by updating a field on the Contact record). This will then cause the updated Account information to sync to Marketo. Please remember that updates to formula fields will not cause an update to the System Modstamp.

Issue Description When using a velocity scripted my.token, the default value is not being used if the field the velocity script is pointing to is not populated. Issue Resolution The reason for this is because velocity script isn't designed to consider a default value the way that a lead token would. It's designed to execute the code to provide the rendered value. Although the UI specifies to look for a default, that's ignored by design since the code itself is only looking for the value for those leads. If the goal is for it to evaluate and provide a known value, otherwise then render a specified default, that needs to be built into the velocity script code itself. Who This Solution Applies To

Issue Issue Description After several failed login attempts you are locked out of your Account. You get the message "Account locked due to too many failed login attempts. Reset password and login again." This is a article attached image Solution Issue Resolution Marketo Locks a user automatically after 5 failed login attempts. You can either reset the password or have Marketo Support unlock your user from the backend if you know your password.

Issue Issue Description When trying to reference a Custom Object in a Smart List with a Filter, there are no filters for the Custom Object. Yet, when checking within a Smart Campaign, there are Triggers for the Custom Object. Solution Issue Resolution Filters are not included in the original design of the Marketo Custom Object setups that act as an intermediary/bridge between two other objects. Check the object setup within Marketo Admin > Marketo Custom Objects - how many linked objects are there? If there are two linked objects, that means the selected Custom Object is an intermediary/bridge between the two linked objects. For these, there will not be any Filters, however there will be Triggers for these objects. Who This Solution Applies To Clients with Marketo Custom Objects

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Setting a field to be required on list import

Education Resources for Marketo Data Analysts

End of Life - Outlook .NET Add-In for Toutapp/Marketo Sales Connect

'Created Date' Differences Between Marketo Smart Lists And Revenue Explorer

Trigger Tokens in Flow Steps Render Incorrectly

Housing Email Nurture Content in Design Studio

Replay Trigger Campaigns That Failed Due To Munchkin Activities Recording Issues

Interesting Moments Not Showing in SFDC Sales Insight

Check the version of your installed Marketo Solution in Microsoft Dynamics (MSD)

Bold/Italic Font in Email Subject Line Gives Error or Does Not Render

Removing Web Personalization (RTP) Domain

Google Customer Match Audiences Aren't Available For Selection

New Landing Page Domain Shows Marketo 404 Page

Unable to Reference Static Lists in Folders Shared Across Workspaces

Champion/Challenger Test in Engagement Program Only Sending Champion Variant

Champion/Challenger Test Email Notification Shows Unexpected Results

Merging Account Records in SFDC - Does This Sync to Marketo?

Velocity scripted tokens not using default values

User Locked Out after Failed Login Attempts

Marketo Custom Object Filters Missing