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?

Included in this article Overview Description Event listeners Assets from URL Patterns Created content API - Event Sending Function Overview The Content Recommendation Engine will recommend content that your visitors will like, but there must be content to recommend first. You can manually upload all assets and pieces of content you want to use, but you can also let RTP automatically discover what content is already out there, published on your website currently. This process of identifying those assets is called Asset Discovery, or Content Discovery. This doc will show you how the Asset Discovery process works. For documentation on how to enable Asset Discovery please see Enabling Content Discovery - Marketo Docs - Product Docs Description Event listeners The asset discovery process is an event listener. It runs on every page that has the RTP script running on it and waits for visitors to click on links that count as content assets. Once it identifies a click on a content asset, it checks if this is a click on an asset. By default, RTP defines content assets as any external pages or files like PDF, PPT, PPTX, MP4, OGG, WEBM or YouTube. As these pieces of content are discovered, they are added to the list of content pieces that the CRE can recommend to visitors. Assets from URL Patterns Asset discovery automatically identifies assets on your web pages, but you can also manually configure assets based off of URL patterns so that HTML pages with URLs that match these patterns will be auto-discovered as assets. Once the URL patterns are configured, the pages will be identified as individual assets that the CRE can recommend. Created content Users can manually add new content in RTP with the directions in the documentation here: Create New Content - Marketo Docs - Product Docs When the content is created, you specify the content URL. API - Event Sending Function In some cases, the download (submit) button is not a direct link to the asset itself but to a JavaScript that opens the asset. When this is the done, the asset discovery events must be coded into the JavaScript on the page and use an API call. This API calls only work if the RTP script is loaded on the page. An example of the code would be: rtp('send', 'view','/case_study1.pdf'); The Event Sending Function documentation can be found here: RTP JavaScript API » Marketo Developers

Included in this Article Overview Troubleshooting Workflow Possible Outcomes Overview Sometimes your RTP Campaigns have problems and stop working suddenly. This can obviously cause trouble for your marketing efforts, so this doc will show you steps on how to troubleshoot those issues. Troubleshooting Workflow 1. Check the campaign's last impression time stamp a. Go to Campaigns page b. Locate the relevant campaign and click the Impressions link to see people that viewed the RTP campaign (make sure the time scope corresponds to the right dates when the campaign was active) This is a article attached image c. When you see the lists of visitors that viewed the campaign, order by Latest and check for the Last / most recent visit impression time stamp This is a article attached image 2. Check the segment's last visit time stamp a. Go back to the Campaigns page and click the campaign's target segment link listed b. Navigate to the Segments page and identify the corresponding segment there. 3. Click the Matches link to see the visitors who have matched the segment and check the last match time stamp. You're looking to compare the most recent date/time stamps between the Segment matches and the Campaign impressions. This is a article attached image Possible Outcomes CASE A: Both time stamps are similar -- something changed in the segment level Is the segment status pending? Has someone manually changed the segment settings? CASE B: The two time stamps don't match -- something changed in the campaign level Is the campaign status pending? Has someone manually paused the campaign / changed settings? CASE C: The segment kept matching visitors (until the end of that day) while visitors did not see the campaign Does the campaign display properly on the website now? Check JavaScript tag. Is the campaign part of an A/B testing group? Is Auto-Tune enabled? If so, please refer to this KB article on: AB Test Your RTP Campaign - Marketo Docs - Product Docs

Included in this article Overview The Content Recommendation Engine (CRE) allows you to recommend specific content you'd like to promote. However, sometimes you may not want to include it on certain pages. You can exclude these pages from having the CRE on them by specifying those URLs in Account Settings as pages to be excluded. Including and Excluding pages You can select pages to exclude/include for the CRE display: In RTP, go to 'Account Settings' Under the 'Domain Configuration', locate the 'Recommendation Engine' section Choose to 'Include' or 'Exclude' Paste the URLs you want to include/exclude (e.g. /contact_us*; *action=logout*, (use * for wildcards) Use semicolon as separator) Examples of exclude/include configuration entries Maximum number of Inclusions / Exclusions The maximum character limit for the Inclusion / Exclusion field is 1,000 characters. Alternate way of hiding CRE You can place the following HTML code on pages where you want to hide the recommendation engine: <style> .insightera-tab-container-bottom{ visibility: hidden !important; } .insightera-bar{ visibility: hidden !important; } </style> Troubleshooting If you have trouble with your Content Recommendation Engine Bar showing up in places it shouldn't, check out Troubleshooting Web Personalization (RTP) - Content Recommendation Engine Bar shows up on all or excluded pages

Issue When using Email Script Tokens to generate URLs in an email, the URLs fail to resolve and show the email script in the browser's address bar rather than the URL. Solution Email Script Tokens are written using Velocity Script, this means the Email Script Token must compile on the sending server before the email is delivered. This issue typically happens when you are trying to include a Email Script Token in a tracked link. Tracked links will always appear in your email as either your branded domain and a randomized series of characters, or begin with 'mkto' followed by a randomized series of characters. Marketo uses tracked links to help gather link clicks and cookie leads who are visiting your website. This is awesome, but this stops Email Script Tokens from compiling. You have two options for resolution: Remove the Email Script Token from the link, and consider creating a person attribute to use instead. Custom person attributes can be referenced as Person Tokens in a Email, and Person Tokens work great with tracked links. Disable the tracking on this link. This can be done by adding the following class to the HTML of your link: class="mktNoTrack" More can be read on disabling link tracking here.

Issue Issue Description Under Web Services > IP Restrictions, you would like to add a lot of IP addresses to whitelist for IP-based API access. The steps are described here: docs.marketo.com/display/public/DOCS/Create+a+Whitelist+for+IP-Based+API+Access Solution Issue Resolution Even though this is not mentioned in the doc, there is a character limit for the string value. The limit is 2,000. However, the way it is stored in the backend is a bit different from UI. Therefore, it is possible that you have exceeded the limit even though it doesn't look like so.

Issue Description Additional domains or subdomains need to be configured for Web Personalization (RTP) Issue Resolution If you want to add a new domain, check your subscription or contract to see how many additional domains are included. Your Customer Success Manager should be able to provide this information If not all entitled domains are configured in Marketo, reach out to support to add the domain(s) If all entitled domains are configured in Marketo, reach out to your Customer Success Manager to purchase more. If you wish to add a subdomain, reach out to support as additional subdomains do not incur a cost. Who This Solution Applies To Customers using Web Personalization

Issue Description In an attempt to approve an email, a 'Not Allowed' error message is being displayed with the following details: {{lead.Email Address}} : Token key not found Issue Resolution Check that token syntax is correctly inserted with no missing left or right 'curly' brackets '{{' '}}' Check that the field name of the token does not have any incorrect spelling (e.g. Email Address) If the token syntax is correct and the field name of the token is spelled correctly, it is possible that the field name of the token contains a Unicode non-breaking space (e.g. between 'Email' and 'Address'). This would have been inserted if it was copied across from a platform that was encoded with Unicode (e.g. Microsoft Word) - To rectify this, delete the space in the token and re-insert it with a normal space using the spacebar on the keyboard. Once this is corrected, the email approval should work.

Included in this article: Overview Viewing Visits in the Visitors List Example of what this looks like Explanation of How It Works Overview Often when looking at a segment based on "number of visits", you may see some leads who look like they should not qualify. These leads are usually qualified, but it may not be evident by looking at the matched visitors. Viewing Visits in the Visitors List When viewing visits, the data scope is Daily / Weekly / Monthly: Because of this, a visitor might show up here as visiting for the first time (in the selected scope) but in fact, they visited a few times in the past before the selected time range. This is why a segment that is supposed to match visitors on their >2 visits may be matching visitors that show up as on their 1st visit. Example of what this looks like Filter used in Segment: Visitors List Showing less than 2 visits Explanation of How It Works RTP stores the total number of visits each visitor has to your website in a cookie: cookie name cookie example trwv.uid supportqe-1440082006718-df69a80e%3A12 The last number in the cookie represents the number of times the visitor visited this website (in this case it's 12). This cookie is stored in the visitor's browser for 2 years (unless deleted) and is updated every visit. So, if the visitor came to your site 11 times about 7 months ago, then when they came back again to your site the one time today, they would match the filter looking for visitors who had been there more than twice, but the visitor list would only show 1 visit since that's all that has happened within the last month it's looking for.

Included in this Article: Overview Data from RTP can be linked to Google Analytics (GA) for further analysis. Below we show you how to check if data is being transferred and a few troubleshooting steps if you find that it isn't. Check if Data is Being Transferred to GA Log in to GA and navigate to Reporting > Behavior > Events > Top Events You should find events with either the category "Insighterra" or "RTP". If not, another place to check for incoming RTP data is in the Custom Variables tab. Navigate to Reporting > Audience > Custom > Custom Variables If you use custom variables, you should see RTP data populated here. If you expected to see populated data in either of these two areas but you aren't seeing any, then you are having issues with your RTP-GA integration. Check out the steps below for some troubleshooting tips. Troubleshooting Steps If you have confirmed that there is no data flowing to GA, there are a few troubleshooting steps which you can take. Check if GA is Enabled Go to Account Settings At the bottom of the page, verify that Google Analytics or Google Universal Analytics is enabled. Only one of these integrations should be enabled at a time - if both are, disable one of them. If neither is enabled, go ahead and enable one of them. Follow this article to learn more about enabling and integrating GA with RTP. Verify both RTP and GA tags are loading on your website To verify this, you will need to navigate to your web page and open the browser's developer tools window. Follow this link to learn what the developer tools window is and how to get there on different browsers and operating systems. Navigate to your browser's developer tools Click the Network tab and search for "analytics.js" and "rtp.js" If both "analytics.js" and "rtp.js" show up in your search, then both RTP and GA are loading on your website. If one or both are missing, go through these steps to add an RTP tag to your website, and these steps to add a GA tag. Check GoogleAnalyticsObject customizations If you're using Google Universal Analytics, check if customizations have been made to the GoogleAnalyticsObject. Read this article to learn more about this object and its possible customizations. To check for customizations, follow the steps below: Click on the Console tab in the developer tools and run GoogleAnalyticsObject Type "GoogleAnalyticsObject" and hit Enter to check the object's type If the object's name is "ga", then you are in the clear. If not, unfortunately we do not currently support the customization.

Issue How to setup the favicon, aka Favorites Icon for Marketo Landing Pages. Solution Steps to Setting up Favicon 1. Ensure you have the favicon hosted either externally or internally in Marketo. (Don't know how to find the link of a image hosted in Marketo? Check this DOC out) 2. On the Landing Page Settings ensure that option 'Remove default favicon links' is selected. Note that this affects all landing pages globally (scroll down in the settings, it might be hiding) [Related DOC] 3. You can specify the favicon in two ways: a. Directly on the landing page in the custom HTML Header [Related DOC] b. In the Landing Page Template's Header 4. This code would need to be specified in the header <link rel="shortcut icon" href="<favicon url>" type="image/x-icon" > <link rel="icon" href="<favicon url>" type="image/x-icon" > 5. Test the landing page out by either opening it in a different browser or clearing the browser cache and restarting the browser.

Issue: When I resize my landing page, the elements on it do not stay in place. Solution: Marketo Landing pages make heavy use of absolute positioning in CSS. This means that you can drag and drop elements wherever you want, but the template needs to be constructed a certain way. If someone has modified your landing page and eliminated certain required elements, it could break this feature. If this happens, contact Marketo Support Is this article helpful ? YesNo

The imported programs reside in a folder titled “Program Library Imports”. The import operation pulls in all the assets (email, landing page, email template, landing page template) and a Readme file. The Readme file contains the names and sizes of the images referenced by the email. You can replace the images by uploading files of the same name into Marketo. The contents of the emails and landing pages are also editable. Caution: We do not recommend modifying the email template or landing page template as this is a common cause for the templates to break. Is this article helpful ? YesNo

There are 3 kinds of visitors to your website: visitors using their company Wi-Fi, known visitors using an ISP, and unknown visitors using an ISP. RTP handles all three of these cases differently, and they are explained below. Visitors on Company Wi-Fi The visitor's company is recognized by the company's IP address Their visitor information, such as company name, industry, location, etc. is determined by the company who they are registered under Known Visitor on ISP Visitors are recognized by a previous form fill-out RTP will override the ISP name and identify the visitor by their company name and email address RTP does not override the location of known ISP visitors Unknown Visitor on ISP The visitor will be shown as coming from an ISP, such as AT&T, Comcast Cable, etc. His geo-location will be shown as the ISP's data center The location accuracy for ISPs is 95%, though state and city accuracy is less reliable as ISP tend to use proxies Since it's impossible to identify the company that these visitors come from, you can decide to exclude ISP visitors from seeing campaigns. While RTP can't identify the company, it is still possible to target these visitors by their online behavior (search terms, referrals, page visits, etc.

Included in this Article: Overview The Assets feature automatically discovers and tags your already existing digital content (including case studies, blog posts, videos, press releases etc.) from your website, and tracks the number of views or downloads of these materials. The Content Recommendation Engine uses predictive analytics and machine learning algorithms to deliver relevant content to each prospect. The recommendation engine discovers visitors that share digital behavior patterns, content preferences, CRM data and firmographics (location, industries, size and revenue). It then predicts which content would perform best per visitor and channel (website, social, ad networks). The content for the engine is monitored and controlled under the Content/Assets table, helping you optimize your content ROI. View Recommendations On the Recommendations page, you can filter by date, sort by any of the fields in the table, and also perform text searches. The table offers the following fields: Title: Name of the digital asset Clicks: The amount of user engagement with the asset - how many times it has been opened, watched or downloaded Direct Conv.: The number of visitors that viewed the content and filled out a form in the same visit Conversion Rate: Percent of visitors that became direct leads Assisted Conv.: The number of visitors that viewed the content and and later filled out a form Recommendations Bar/Rich Media: Whether the asset is available for the Recommendations Bar or contains rich media Create Content The Content feature organizes all your digital assets (including PDF, blog posts, case studies, videos, presentations, etc…) on your website and tracks the number of views and clicks on these materials. To create new Content: From the Recommendation page, click Add Content. The following screen appears 2. Enter data into the following fields: Title - The name of the asset Link - The full URL link of where the asset is located (include the http://) Bar/Rich Media Recommendation: Enabling the content for recommendation or rich media Industries - The industries related to the digital asset Location - The relevant location (country, state, city) related to the digital asset Content Type - The type of digital asset (white paper, case study, blog post, etc.) Content Stage: The prospect stage most relavent with the content Metadata - An additional description about the digital asset Update Metatext Dynamically - While automatically use the metadata on the Assets page 3. Click Save to create the new digital asset. Edit and Delete Assets Editing To edit an asset: From the Recommendations page, click the edit icon of the asset you wish to edit. The Set Content page opens with the selected asset. Apply any edits or changes. Click Save. Delete an Asset To delete an asset: From the Recommendations page, click on the delete icon of the Asset you wish to delete. A confirmation message appears to confirm that you want to delete the Asset. Configuring Recommendations and the CRE From the Account Settings screen, under Domain In this screen, you have the CRE options. On the right-hand side you have the following toggle keys per domain: Tag - Activates the RTP Javascript tag on your website Recommendation - Activates the Content Recommendation Engine Content Discovery - Activates the tracking of assets Click the toggle On or Off to enable or disable the feature Categorize and Track your Assets with Asset Patterns You can categorize assets into different types of content, for example, blog, press, or case studies. This helps you easily track your assets and understand which asset types perform the best. To categorize your assets: From the Account Settings page, on the left-hand side, select Content. The following dialog box appears. 2. From the drop-down menu, select the website whose assets you wish to track. 3. Add the path corresponding to the type of asset you wish to track. For example, adding the path “/blog/*/” captures all the blog posts under yourdomain.com/blog and automatically displays them in the Content table. (Use * as a wildcard) 4. From the drop-down box on the right-hand side, select the asset group you wish to categorize all assets coming from the path you specified. 5. Click Save to save all changes.

Included in this Article: Testing Campaigns by Sandboxing General Tag Checklist Check the Product Documentation: Verify the tag exists in the HTML code on your website Make sure that the right tag has been inserted properly Verify the tag is enabled Website Checklist Verify there are no jQuery or JavaScript errors Verify In Zone campaign Div IDs Segment Checklist Verify that the segment has had matches. Verify the Segment is set for the relevant domains. Verify ISP setting Verify location settings Campaign Checklist Important notes about Widget campaigns Is this article helpful ? YesNo Testing Campaigns by Sandboxing Sometimes you'll need to see what your campaign looks like live on your website without customers being able to see it. Sandboxing allows you to match a segment and see the campaign live by targeting a specific term added into the URL. Since leads won't randomly guess the value and alter the URL, it's safe to test on a live site. Here's how you do it. 1. Create a new 'Sandbox' segment and call it "Sandbox=1" Add the Included Pages filter and enter *sandbox=1* as the value for the URL matches. Add all other filters you need. When used in combination with the *sandbox=1* URL match, it will match just like your other segment you want to test, but only if you have "sandbox=1" in the URL. 2. Create a campaign called: "Sandbox=1" (or alter the campaign you're working on) to use the "Sandbox=1" segment. Verify that your campaign is set up properly, then launch the campaign. 3. Go to the webpage you're testing with. Let the page load fully. 4. Add ?sandbox=1 at the end of the URL and hit enter. 5. Verify whether the sandbox campaign is being displayed. General Tag Checklist Check the Product Documentation: Troubleshooting Web Personalization (RTP) - RTP Tag Verify the tag exists in the HTML code on your website All pages, all domains, all sub-domains and landing pages need to have the RTP tag in the code in order for it to work properly. The RTP tag can be loaded through a tag manager like Google Tag Manager, Adobe Tag Manager or Tealium Tag Manager. If the RTP tag is not directly in the HTML of the page, remove it from the tag manager and load it directly into the HTML of the page. RTP tags can be used with tag managers, but removing it and placing the tag into the HTML of the page directly will let you test whether there is a problem being introduced by the tag manager itself. Make sure that the right tag has been inserted properly Check the Deploy the RTP JavaScript - Marketo Docs - Product Docs documentation for how to locate the RTP script tag. This will show you how to actually locate and deploy the RTP script tag. If your instance has more than one domain configured, you will have access to more than one RTP tag that can be deployed. Each domain that is configured in your instance will have its own unique script tag. If you use the wrong one in the wrong place, your campaigns will not execute as planned. Verify the tag is enabled 1. Go to 'Account Settings' 2. Make sure the tag is enabled Website Checklist Verify there are no jQuery or JavaScript errors Navigate to your site and open the developer's tool Console panel. Check for any errors such as this: Verify In Zone campaign Div IDs In Zone campaigns utilize a Zone ID to identify where the RTP campaign should be inserted into the body of the page. This is the Div ID in the HTML code of you website. Verify the Div ID exists in the HTML code on the page where the campaign should be displayed. Even small differences in the Div ID will cause it to not match, resulting in the campaign not displaying. Segment Checklist Verify that the segment has had matches. When viewing you list of segments, make sure that there have actually been matches. If your segment hasn't matched any leads, there's no way the campaign can be called to action Verify the Segment is set for the relevant domains. Segments can be set to only apply to certain domains configured in your instance. If your segment is only applying to one of multiple domains you need, that would stop the segments from matching very often, and stop the the associated campaign from being called to action. Verify ISP setting When using the "Exclude ISP" filter, it's important to make sure when testing that you aren't showing up as an ISP. The network you're on plays a very big part in how you appear to the RTP system. Verify location settings If you have a location filter in use, you could be not matching the segment because the filter thinks you're coming from a different location based on your network's settings. Are you physically in the location your filter is searching for? Is your network representing the correct location? Campaign Checklist Check for target URL If the campaign is set for a specific target URL and you aren't viewing that exact page, the campaign will not display. Are there any JavaScripts in the campaign? JavaScript running inside of an RTP campaign can cause conflicts. Try removing the JavaScript and testing it. If the campaign displays as it should, then you know the JavaScript caused the issues. Important notes about Widget campaigns Widget campaigns will only show up once per session. A session lasts for 30 minutes since the last click on a tracked web page, so the session times out after 30 minutes of inactivity. To view your campaign again, clear your cookies, use an incognito mode, or use a different browser

Issue Description You have the Munchkin tracking code on your non-Marketo web page but visits to the page are not being tracked. Issue Resolution If you have customized the Munchkin tracking code, it may not work. Marketo only supports the Munchkin code as it is provided in your instance. If you need to alter the code, you would need to work with your web developer to determine why the customized code is not working. To find the supported Munchkin tracking code: Go to Admin > Munchkin. Select the version of Munchkin you intend to use. Place the Munchkin code on your page as outlined in our document on adding Munchkin tracking to your site. Is this article helpful ? YesNo

Follow these steps to add a graphical date picker to your form date fields. When you're done, it will look something like this: First, you need a form with at least one date field. In the Form Editor, date fields appear with a date icon in the Template Form Fields list. Drag one into your form if you haven't already. Next, edit a landing page that uses the form (or create a new one and add the form). Click the form and make sure the box around it has some padding, shown below. If the padding is too small, the calendar icon next to your date field will wrap onto the next line. Now add this custom Javascript to your webpage as a Custom HTML element: <link type="text/css" href="https://nation.marketo.com/js/public/css/redmond/jquery-ui-1.7.1.custom.css" rel="stylesheet" /> <script type="text/javascript" src="google.com/jsapi"></script> <script type="text/javascript" > google.load("jquery", "1"); google.load("jqueryui", "1"); </script> <script type="text/javascript"> var $jQ = jQuery.noConflict(); $jQ(document).ready(function() { $jQ(".mktFormDate").datepicker({showOn: 'both', buttonImage: '/images/icons16/calendar_31.png', changeMonth: true, changeYear: true, buttonImageOnly: true }); }); </script> Finally, preview your page and click the calendar icon next to the date field. The graphical calendar will appear below the field. Is this article helpful ? YesNo

Issue Description You want to find the day that a piece of predictive content was discovered. Issue Resolution There isn't a direct way to see the exact date a piece of content was discovered. What you can do is filter the results to content discovered during a specific time frame. Go to the "All Content" tab. Select the Calendar on the upper right side Choose the time frame and click Apply. Result: You will see only the content that was discovered during that time frame. Who This Solution Applies To Customers with Real-Time Personalization (RTP) or Predictive Content. Is this article helpful ? YesNo

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Web Personalization (RTP) - How does Asset Discovery work?

Troubleshooting - Web Personalization (RTP) Campaigns suddenly stopped working

Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages

Email Script Token Not Resolving in a URL Link

The max number of the IP addresses to add to API whitelist

Configuring additional domains or subdomains in Web Personalization (RTP)

Error Approving Email - Token Key not found

Troubleshooting: Web Personalization (RTP) - Segment Based on Number of Visits Matching Incorrect Leads

SSO Login for CRM Integration User

Troubleshooting Web Personalization (RTP) - RTP Data not Flowing into Google Analytics (GA) Instance

Setting up Favicon for Marketo Landing Pages

Content in Landing Page not staying in position

Where do I find my Imported Templates in Marketo?

RTP - How does RTP collect data on visitors

Web Personalization (RTP) - Content Recommendations and Assets

Troubleshooting - Web Personalization (RTP) Campaigns Not Showing

Munchkin Not Tracking Page Visits

Advanced Landing Page Template Development

Adding a Date Picker to a Form

Content Discovery Date