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

(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 You are unable to abort a triggered Smart Campaign currently in progress. Solution The "Abort Campaign" function only works for batch campaigns. To stop leads from going through the flow of a triggered campaign, do the following: Deactivate the trigger campaign in the Schedule tab. This will prevent new leads from entering the campaign flow steps. It will not stop leads that have already entered from continuing through the flow. Use a "Remove from Flow" step to remove existing campaign members from the flow. This can be done a few different ways. View Campaign Members > Select All > Lead Actions > Special > Remove from Flow If the leads are in a Wait Step, you can add a Remove From Flow step after the Wait Step in the trigger campaign Create a small batch campaign with a "Member of Smart Campaign" Smart List filter and a "Remove from Flow" flow step that specifies the trigger campaign you want to remove them from.

Issue The Engagement Program has no engagement score more than 72 hours after the Engagement Program cast. Solution First, make sure that is has been more than 72 hours since the Engagement Program cast, since it takes some time for the engagement score to update. If you are using child programs in the Engagement Program stream, check the individual programs to see if leads have achieved a Success status in those programs. When programs are used as content in streams, the engagement score is based on program membership and success status, not email interaction (clicks, opens, unsubscribes). Also, if there are any campaigns in the child program that contain wait steps, the Engagement Score will not populate until the campaign is complete. docs.marketo.com/display/public/DOCS/Understanding+the+Engagement+Score

Issue You want to set up a DKIM key on one of your domains or subdomains, but another service has a DKIM key already set up on the selector/domain combo. Solution Beginning October 2023, Marketo has upgraded it's DKIM feature to allow for a Custom Selector for DKIM Keys. Most Users will be able to utilize the prior default selector, m1, as their DKIM Key. However, if another integration is already utilizing the m1 selector, a custom value can be used. Common ones seen are "m2", "a1", "mkto", etc. It can be longer, but shorter is generally better Afterwards, you'll be able to validate DKIM as detailed in documentation: docs.marketo.com/display/public/DOCS/Set+up+a+Custom+DKIM+Signature

Issue Marketo Forms embedded on non-Marketo web page do not show up when using Firefox private browsing. Solution Marketo forms and Munchkin tracking are inserted into non-Marketo pages via Javascript. If the browser privacy settings block the script from executing, Marketo forms and tracking will not work. Marketo is not able to override a customer's browser security settings. The alternatives are as follows: Create a non-Marketo form on the web page Use a backend form submission to push the info in the form into Marketo. Instructions for doing so can be found here: developers.marketo.com/blog/make-a-marketo-form-submission-in-the-background/

Issue You receive a notification that the Marketo/SFDC sync has failed due to " Invalid username, password, security token; or user locked out." On the Salesforce side, you see the error "Salesforce setCredential failed with code: {LOGIN_DURING_RESTRICTED_DOMAIN} and message: {cannot log in from current domain}" Solution Take the following steps to troubleshoot this issue: Confirm that the username and password are correct by using them to log into Salesforce. Check to make sure the Marketo IPs are on the Salesforce general whitelist. Check the Marketo sync user's profile in Salesforce and make sure the "Login IPs" include the IPs for your Marketo instance. The complete list of IP ranges is: 199.15.212.0/23 199.15.214.0/23 192.28.144.0/23 192.28.146.0/23 192.28.148.0/23 192.28.150.0/23 192.28.152.0/21 192.28.160.0/19 185.28.196.0/22 103.237.104.0/23 103.237.106.0/23 Who This Solution Applies To Customers integrated with Salesforce using IP restrictions

Issue You have noticed that in some Asset URLs the 9-digit Munchkin ID displays, and you would rather have something else display. Solution It is possible to alter the URL and replace Munchkin ID with the Account String for your Marketo instance located in Marketo Admin > Landing Pages. The following can only be done when inserting the URL into your email or landing page HTML. There is no global setting to change this permanently. For example say you have an image asset at the URL: na-sjst.marketo.com/rs/164-CZO-458/images/android.jpg When you insert this link in an email or landing page, you can replace the Munchkin ID with the account string of for your instance: na-sjst.marketo.com/rs/mktosupportmybaben/images/android.jpg This link will still resolve correctly and the Munchkin ID will not be displayed.

Issue You are unable to add members to a secondary instance using a secondary login. You receive an error that the email is already in use. Solution This solution applies in the following scenario: You have two or more Marketo instances. The instances are set up so you are allowed to specify the login email address separate from the email address used to notify/invite the users. For example, something like this: Login: login.user@domain.com Email: user@domain.com You have a user in the second instance whose email address exists in the first instance, using a different login but the same email address, like this: Login: login2.user@domain.com Email: user@domain.com When you try to do invite the user to the second instance using Universal ID, you will get an error stating that the email is already in use. To resolve this, you will need to delete the existing login for the user in the second instance (login2.user@domain.com) and instead invite their primary login (login.user@domain.com) to the instance. This will allow the user to access both instances from a single login For more information on Universal ID: Using a Universal ID for Subscription Login - Marketo Docs - Product Docs Who This Solution Applies To Subscriptions with Universal ID active

Issue You want to have one email address in the From field ( abc@test.com) a different email address in the Reply-To (all@test.com)? Solution Yes, you can use different email addresses in the From and Reply-To. If the Reply-To is an email alias that sends to a group, you should confirm that email is working and able to receive email. Please note: Automatic replies, such as out-of-office notifications will be sent to the From address, not the Reply-To. Reply-To is only used when the person who received the email clicks the Reply button in their email client. Note :- The SMTP envelope sender typically appears as <uniqueidentifier>@*.mktomail.com. You will only receive responses of this nature if you have configured a branded sender for your subscription. While this serves as the correct destination for auto-responses, regrettably, it is frequently overlooked.

Issue You would like to include the subject lines of your emails in your email performance reporting Solution In the Email Performance report in Analytics, you cannot not add the subject line to the report. However if your instance has access to Revenue Explorer then you can create a report that includes subject line. Within Revenue Explorer create a new Email Analysis report. Email Subject is listed under Email Attributes, you can either include Email Subject as either a row or a column. docs.marketo.com/display/public/DOCS/Email+Analysis Who This Solution Applies To Customers with Revenue Explorer

Issue The same email looks different in different email clients, and does not match what is shown in the Email Previewer. Solution Different browsers and email clients render HTML and CSS differently. While there are standards set forth by W3C, there is room for flexibility. At a high level, it is expected for emails to look different, even within the same platform such as Outlook 2013 vs Outlook 2010. With that said, you can code against some of these anomalies by adding extra code in CSS to account for the differences. You should consult with an HTML/CSS designer to make these changes. In all likelihood, the issue is related to how Outlook(or any other email client) is rendering the email and reviewing the Outlook settings as well as email and template code should resolve any issues customers are experiencing as when we send test emails to both outlook and gmail both are generally rendered differently (gmail seems a bit fine though). FAQs Where should I start trying to determine whether this is a Marketo or Outlook issue? In most cases if the email is loading within another email client without issue then Outlook would be the best location to review. Is there a way for me to see if it is a template problem? Yes, does the issue occur when an email is created and sent with another template? What are the steps to troubleshoot? In general, to provide the most accurate troubleshooting steps, a bit more information will be helpful. I have provided a few general tips below which may be helpful. As a rule of thumb, Outlook sometimes requires custom coding to appear as it does in other email clients since they use their own word engine to render the html. If the images when they are downloaded are not displaying as expected, we would typically recommend reviewing any code in the email since Outlook uses its word engine to render html and additional code may be needed for Outlook specifically as a result. A developer may be required to implement any custom code required to display the emails as expected. You may consider reaching out to the Community to understand what other users have done to overcome similar obstacles. I have provided a few links below which may be relevant. Is there any reference Documentation ? https://nation.marketo.com/docs/DOC-4765-why-does-my-email-looks-different-on-various-version-of-the-same-platform-like-outlook HTML Email Display in Outlook Marketo emails don't render properly in MS Outlook app for iOS Re: Help - My Emails Look Terrible in Outlook 2016 Here are a few resources that may help with Outlook rendering issues: It’s Not You, It’s Outlook – The Complete Guide for Email Marketers http://www.verticalresponse.com/blog/its-not-you-its-outlook-the-complete-guide-for-email-marketers/ Gallery of Common Outlook Rendering Issues Gallery of Common Outlook Rendering Issues MICROSOFT OUTLOOK CONDITIONAL STATEMENTS labs.actionrocket.co/microsoft-outlook-conditional-statements Outlook 2007/2010/2013/2016 and Word HTML Outlook 2013 / 2016 / 2019 / 365 and Word HTML - HowTo-Outlook 12 Techniques for Excellent Emails in Outlook.com How to Create Excellent Emails for Outlook.com A Guide to Rendering Differences in Microsoft Outlook Clients Outlook Email Rendering Issues and How to Solve Them - Litmus Surface Pro 3 and Outlook Email Rendering Redirecting

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 www.pages.domain.com/contact-us.html. Only the following 2 options would function: Referrer URL - is - 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: 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.

Using URL parameters are an important way to organize your web analytics and tracking. With Marketo Web Personalization, when a web visitor clicks on a personalized Web Campaign we add a parameter to the URL. This parameter is "?iesrc=ctr". Having this parameter allows you to report on your web analytics to see and compare all the clicks on Web Personalization campaigns and overall performance of your personalization strategy. The Marketo Predictive Content application also includes a URL parameter every time a visitor clicks on predictive content (from the bar, rich media or email). The URL parameter used here is "?iesrc=rcmd". You can also add your own UTM parameters to the URL link you have in your Web Personalization Campaign or your Predictive Content piece. The most common URL parameter tools we see customers using is the Google Analytics tool. In their words "This tool allows you to easily add campaign parameters to URLs so you can track Custom Campaigns in Google Analytics. See: Campaign URL Builder — Google Analytics Demos & Tools". Make sure to follow the best practices: Best Practices for creating Custom Campaigns - Analytics Help

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

Issue When looking at a lead's email activity, you see that they clicked a link in an email, but there is no open activity recorded for that same email. Solution It is technically possible for a person to click a link in an email without opening it. An Open Email event is only logged when a single pixel tracking image is downloaded from the Marketo server, but many email clients, such as Outlook, don't download images by default. So someone could open the email, read and click it without choosing to download the images, resulting in a Click Email without a corresponding Open. Email performance reports have an additional logic in them that backfills the Opens. They know that to click an email you must open it. Smart Lists don't have this backfill, so the Opens in a Smart List will often be different than the Opens in a report.

Issue You are trying to add a hyperlink for your calendar event token to text in an email, but when you click on the link in a sent email, you are not getting an ICS file. Solution When you add the calendar token to an email, it displays as a "My token." Once the email is generated, that token will then appear as a link in your email. However, if you try to hyperlink the token, the token cannot resolve. To get the calendar file token to work properly, you need to add the token to the email by following the steps in this document: Include a Calendar Event in an Email. Note that you should add the token using the Insert Token button, rather than the Insert/Edit link button.

This is a article attached image Image: Step Flow for Predictive Content for Web and Email What is Auto Content Discovery? This post explains the first part of the flow image above: discovering, mapping, and tracking your content assets. Content Discovery is used in the Predictive Content app to auto-discover all the content assets (videos, pdfs, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you can see how your content is performing and decide which pieces of content should be prepared, approved, and enabled for the Predictive Content outcomes on web (either in the recommendation bar or rich media) and email. Setting up Predictive Content and Content Discovery See Set Up Docs: docs.marketo.com/display/public/DOCS/Getting+Started+with+Predictive+Content Steps RTP Javascript tag is installed on all your web pages (Note: RTP is now called Web Personalization) Set Asset Discovery to On Asset Discovery auto-discovers extensions (PDFs, PPT, MP4, OFF, WEBM) and a click/view on embedded videos (Youtube, Vimeo, Wistia) Create URL Patterns Setting URL patterns auto-discovers content when a web visitor clicks on the HTML web page relevant to the content pattern. The URL syntax pattern determines your ability to use this feature optimally (e.g., to create a pattern for press releases, your press releases should all be stored on a page identified as www.yoursite.com/press-releases/*). How is content auto-discovered? The content discovery technology uses an event listener that runs on every web page (where the RTP Javascript tag is installed) and waits for a web visitor to click on a URL link or arrive directly on that web page in a browser. If that link includes an extension (PDF, ppt, embedded video) or matches the URL pattern defined, then it will be discovered and added to the All Content page in the Predictive Content app. Only content pieces that a web visitor interacted with (clicked on or viewed) once the RTP Javascript tag has been installed are discovered via Content Discovery. If the content is already discovered, it will add to the tracking and views of those discovered pieces. You can also manually add new content to be listed and tracked in the All Content page. This is a article attached image Image: All Content Page in the Predictive Content app displaying and tracking all discovered content What data is discovered? Visitor Data (Used for Analytics + Predictive Algorithm) Pages Viewed - number of page views by the user in the session Visit Count for Web Visitor Last Content URL Seen Last 5 Content Assets clicked via Predictive Content that this visitor has seen in the last 90 days Last Web Campaigns Seen - 10 last campaigns per session (within the last 5 sessions) Inferred Organization Inferred, Industry, Size, Revenue Inferred Country, State, City Search Term Content Data Extensions Video (Youtube, Vimeo, Wistia) Video Name Video URL Video Image URL PDF PDF Name PDF URL URL Patterns (HTML pages) Found via metadata of the HTML page Content Name Content URL Content Image URL Content Description What data is auto-populated during the auto-discovery phase? Based on the content data we discover, the aim is to populate as much of the Predictive Content as possible, making it quicker, easier and involves less prep work for you. However, you still need to review the discovered content and then approve and enable it for the Predictive Source (Email, Rich Media, Recommendation Bar). Assuming we discover an HTML page defined in URL patterns, this HTML content piece will be populated in the following fields in Predictive Content: Predictive Content Fields Auto-Populated Value Notes Content Name (Content Name) Unique Value Content URL (Content URL) The URL is consistent for all sources (email, bar, rich media) Categories Video OR Category Name from URL Pattern If Video is discovered, the category is populated as Video. Category populated from defined URL Pattern. e.g., Marketo.com/blog = Blog all discovered content based on this URL would receive Blog as a category Category is consistent for all sources (email, bar, rich media) Content Title (Content Name) Email Title (Content Name) Email URL (Content URL) Email Image URL (Content Image URL) Email Button Label Read More Not Auto-populated. Default is "Read More." Rich Media Title (Content Name) Rich Media URL (Content URL) Rich Media Image URL (Content Image URL) Rich Media Description (Content Description) Bar Title (Content Name) Bar URL (Content URL) This is a article attached image Image: Example of Populating Metadata for HTML content into Predictive Content

Image: Step Flow for Predictive Content for Web and Email What are Content URL Patterns? This post explains the first part of the flow image above: the discovery and tracking of content for the Predictive Content app. During the setup phase, the marketer defines their content URL patterns (See Create Content Patterns for more information), in order for Marketo to discover HTML content (e.g., blog posts, press release, news articles) across a domain. Setting URL patterns allows Marketo to auto-discover content when a web visitor clicks on the HTML web page within the content pattern. This content is then added to the All Content page in Predictive Content. Setting up URL Patterns Go to User Profile > Content Settings > URL Patterns. (For more information, see the Getting Started doc: Getting Started with Predictive Content) Image: URL Patterns Page Rules for Content URL Patterns Use of a wildcard (*) is permitted throughout the expression. e.g., domain.com/* or domain.com/*blog* It's recommended to use /* at end of the expression to continue pattern discovery. e.g., domain.com/blog/* to discover all your blog posts in the blog folder Content Patterns are not case sensitive. URL Pattern: "domain.com/Blog/*" will discover all HTML pages on "domain.com/Blog" and "domain.com/blog" Parameters in URLs are not discovered. Auto-content discovery removes the URL parameters in order to avoid discovering the same content URL multiple time with different parameters. Examples of Content URL Patterns Domain URL Pattern Type Result domain.com blog/* Pattern Discovers all your content that matches the pattern domain.com/blog/. Example: domain.com/blog/5-top-tricks domain.com/blog/2017/new-year-solutions domain.com/Blog/3-best-recipes domain.com article/2017/* Pattern Discovers all your content that matches the pattern domain.com/article/2017/ Example: domain.com/article/2017/5-top-tricks domain.com *datasheets* Contains Discovers any URL that contains the word "datasheets" Example: domain.com/datasheets/5-top-tricks domain.com/blog/5-top-datasheets domain.com press-release Exact Only one HTML page is discovered: Example: domain.com/press-release domain.com Exact If the domain is selected and the URL expression left empty, the URL pattern will discover only the home page Example: domain.com sub.domain.com blog/* Pattern Discovers all your html pages in the folder blog only on the sub domain sub.domain.com

Issue Issue Description After an email send, the number of emails sent is much lower than the number of people that qualified for the sending Smart Campaign or Email Program. Solution Issue Resolution One possible reason you are seeing a different number of emails sent versus the number of people that qualified for that is email is because of communication limits. If a person qualifies for an email, Marketo will try to send it. However, if a lead has already reached their daily or weekly communication limit, Marketo will not send the email (with the exemption of operational emails). To check to see if a lead did not get an email due to communication limits, follow the steps at Email Program Fails to Send Emails.

If you have a large database, use Firefox to access Marketo, and often get "band-aid errors" when trying to accomplish basic tasks (such as edit an email or look at a program), it may be an issue with the Firefox browser. In some cases, the 32-bit version of Firefox is unable to accommodate a very large/complex Marketo instance. If this is the problem, installing the 64-bit version of Firefox should resolve the problem. To check what version of Firefox you're using, follow the steps at Find what version of Firefox you are using. To switch to the 64-bit version of Firefox, follow the steps at How to switch from 32-bit to 64-bit Firefox.

Included in this Article: Overview Creating Custom Fields Dynamic Updates Set Up Custom Fields in RTP Filter by Custom Fields Overview Unfortunately RTP does not support the option to use Lead Database segmentations as segments in RTP. However, it is still possible with a bit of a workaround. Essentially, you will want to create custom fields for each segmentation, dynamically update them using smart campaigns, and filter by these custom fields in RTP. Below we will describe the steps you will need to take to implement this. Creating Custom Fields To start off, you will have to make a custom field in My Marketo for each segmentation you wish to use in RTP. Follow the steps in this article to get the custom fields set up in My Marketo. Make sure to select Boolean in the Type field. Dynamic Updates Next, you will need to assign these custom fields to those matching their respective segmentations. To do so, we will create a smart campaign, which will also update the list as more leads begin to match the segmentation. In My Marketo, visit the Marketing Activities page and create a new Smart Campaign This is a article attached image In the Smart List tab, choose the filter for your desired segmentation, and the Segment Changes trigger for the same segmentation This is a article attached image The filter will include all of the existing members of the segmentation, and the trigger will include any members that qualify for the segmentation in the future. Next, This is a article attached image In the Flow tab, select the Change Data Value action, click Add Choice, and format the action to change your custom field to true when the lead qualifies for your desired segment, and false otherwise This is a article attached image It is important to have both cases, for your lead matching the segmentation and for not matching, because leads can both qualify or be disqualified for segmentations at any point in time. Finally, under the Schedule tab, edit the Smart Campaign Settings so this will apply every time, and Activate the campaign This is a article attached image Set Up Custom Fields in RTP Once you have set up your custom fields in My Marketo, you will also have to set up this field to display in RTP: Go to your Account Settings and navigate to the Database tab This is a article attached image Select your custom fields in the drop down menu at the bottom of the page, then click This is a article attached image This is a article attached image Filter by Custom Fields Finally, once you've set up the custom field in My Marketo and in RTP, you can use the custom field to target the leads that qualify for your segmentation in My Marketo. To do so: Go to the Segments page and create a new segment This is a article attached image Lastly, use the Database filter, select your custom field, and choose either true or false depending on if you want to target those in or out of the segmentation This is a article attached image There you have it! You can now use your segmentations in My Marketo to target your audience in RTP campaigns.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Unable to Abort a Triggered Campaign in Progress

Engagement Program Has No Engagement Score

Custom DKIM Selector

Marketo Forms Not Showing Up in Firefox Private Browsing

SFDC Sync Error - Salesforce setCredential failed with code: {LOGIN_DURING_RESTRICTED_DOMAIN}

Removing Munchkin IDs from Image and File Asset URLs

Unable to Add Users With Universal ID Enabled

Different Email Addresses in the From and Reply-To Lines

Email Performance Report by Subject Line

Email Looks Different on Various Versions of the Same Email Client

Specifying Web Page on Form Fillout Filters or Triggers

URL Parameters with Web Personalization and Predictive Content

Send Sample Fails

Lead shows Clicked Email but no Opened Email in Activity History

Calendar Token Not Working in Email

How Auto Content Discovery Works in Predictive Content

How URL Patterns Work in Predictive Content

Seeing a Lower Number of Emails Sent Than People That Qualified for a Campaign

Troubleshooting Chronic Marketo Errors in Firefox

Web Personalization (RTP) - Use Lead Database Segmentations in RTP