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?

Article Text Included in this Article: Overview The Problem The Solution Rich Media Content Recommendation Engine Info Overview The Content Recommendation Engine (CRE) is a powerful tool that will allow you to promote online content to your visitors based on their behaviors and the performance of the content itself. When the RTP tag is used on multiple domains, it will pull in all available content regardless of which domain it's on. For some marketers, this can be a problem. The Problem With the standard Content Recommendation Engine, this is an expected behavior. You can't limit the the recommendations from one domain to stop showing up on other domains. The content being recommended will show across all domains where the RTP tag is in use. The Solution There are two types of Content Recommendation Engine. The Rich Media Content Recommendation Engine will let you get around this problem. The standard Content Recommendation Engine gives the bar along the bottom of the web page with the content recommendations in it. This recommendation engine is expected to have content extending across all domains where your RTP tag is in use. The Rich Media Content Recommendation Engine will allow you to target which content you want to have in which places by categorizing the content and specifying which categories each web page should pull from. Rich Media Content Recommendation Engine Info For directions on how to utilize the Rich Media Content Recommendation Engine, please see: Enabling the Rich Media Recommendation Engine - Marketo Docs - Product Docs

Article Text Included in this article Overview Editing Labels Deleting Labels Overview RTP will allow you to add labels to your Segments and Campaigns. Here are the directions on how to do so: Label Your Segment - Marketo Docs - Product Docs Label Your Campaigns - Marketo Docs - Product Docs Sometimes Labels need to be changed or removed. Editing Labels Currently it is not possible to edit labels Deleting Labels You can delete labels using following process: 1. Filter the the page by the label you want to remove. 2. For each segment or campaign displayed, click the select box and then click Set Label 3. In the Set Label list, uncheck the label you want to delete. When the label is removed from all segments/campaigns, it will be removed automatically

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

Article Text Included in this Article: Overview Check Tag and Content Discovery are On Check Content Patterns Verify Content Discovery is Working Overview If you notice that RTP is not tracking clicks to your Content Discovery pages, there are a few troubleshooting steps you can take. Check Tag and Content Discovery are On Go to Account Settings Check Tag and Content Discovery "Tag" and "Content Discovery" must both be enabled for Content Discovery to work. Follow this article if you are having issues with your RTP tag or want to verify that it is working correctly. Check Content Patterns In Account Settings, go to the Content tab Check that the URLs entered in the Create Content Patterns section match the URLs you wish to use with Content Discovery Verify Content Discovery is Working Once you've made changes the Content Discovery setup, visit any page in the Create Content Patterns section. If the Content Discovery is working, visiting the page should increase the click count and capture you as the visitor. To check if this worked the way that it should, after visiting the website you should: Go to the Visitors page under Analytics Use the search tool in the visitor database and search for the URL that you visited. It should return a list of visits to that site with your most recent visit at the top. If the Content Discovery is working correctly, the visitor database should have tracked your visit and it should appear among the list. Check to make sure the time stamp matches the time you visited the page. The time stamp can be found under the Visitor Information section after clicking on the visitor.

Article Text Included in this article Overview Include Pages Target URL Use Case Overview Target URL and Include Pages are both RTP terms that sound the same and get confused together, but they have different uses and meanings. This doc will go over what the differences between them are and how each can be used. Include Pages "Include Pages" is a filter used in Segments that will look for visitors who have been to specific pages. This filter will make the segment match for the visitor when they go to the designated page during the visitor’s session. If the visitor goes to one of the "Included Pages" during their session, then they match for the segment. Target URL "Target URL" is used in RTP Campaigns. In the campaign editor, the Target URL defines which page(s) the campaign will be displayed on. So, whenever the campaign is called by a segment, it will only be displayed on those pages specified in the Target URL area of the campaign. If the visitor is not viewing one of these specified pages, the campaign will not show. Use Case By using these together, you can create a campaign that will be displayed on your homepage (the Target URL) only if the visitor first viewed the pricing page (the Included Page). So, let's say your visitor went to the pricing page to look at Product A, then went back to your home page. You can have a campaign display info about Product A on your homepage knowing that the visitor is interested in that product already.

Article Text Included in this Article: Overview Checking for Segment Matches Reasons for not Matching Typos Non-exact Matches Overview Using segments, you can target specific organizations by using the Named Accounts attribute in the segment editor. With this attribute, you can select all organizations in a Named Account List or by manually selecting organizations. However sometimes we see one of those organizations visiting the website but it doesn't match the segment, even though it is included in the segment list. Checking for Segment Matches If a list was created manually, it's possible the organization wasn't included in the segment list in the first place. To check: Go to the Organizations tab Use the search bar to search the name of the organization in question If the organization was entered in the list correctly, it will be found through the search. If it does not appear in the search results, there are two issues that are likely to have arisen. Reasons for not Matching Typos Luckily, typos are easy to fix. Simply edit the organization's name to match the spelling you wanted it to take on. Non-exact Matches Even if an organization is spelled correctly, it will still not match the organization listed in the segment if the names aren't exactly the same. It is very common for companies to have different names for their organization. To fix these non-exact matches, you'll have to be clever about how you name your organizations. In RTP, an important character to know is the wildcard character, represented by an asterisk (*). A wildcard character will match with any character or sequence of characters For example, the string "Salesforce*" will match all three of the above spellings ("Salesforce.com", "Salesforce.com Inc.", and "Salesforce Ltd") because they all begin with "Salesforce". For more examples on how to use wildcard characters, follow this document: RTP Glossary - Marketo Docs However, you must be careful using wildcards characters, because you could potentially match organizations that you didn't intend to match. For instance, the string "Salesforce*" will not only match the three examples above, but also a company named "Salesforce Finance", a completely different company.

Overview These instructions will show you how to add a filter to Segments that will prevent a visitor from seeing the same campaign twice. When done this way, each visitor will only see the associated Campaign once and won't see it again. This is a article attached image 1. Locate and select the User Context API filter (in the API category). This is a article attached image 2. Select "Campaigns - Viewed" from the "Select field to add" drop down. This is a article attached image 3. Select "is not" and insert the Campaign ID. This is a article attached image Where to find the Campaign ID The Campaign ID is the identifier used by RTP to specify which Campaign you are referencing. It can be found in the URL for the campaign once you've navigated to it. Look for the number in the end of the URL, just after "reactionId=". This is a article attached image 4. Click the plus sign to add a second field to the filter. Choose "Campaigns - Viewed" as the second field, same as the first. 5. Select OR from the AND/OR field. 6. Select "is empty" for the second Campaigns Viewed filter option. S This is a article attached image Finally please make sure that the campaign is not marked as "Sticky", as this will make it appear every time. You're all set! This segment will now only match visitors who have not seen the campaign yet.

Article Text FAQs included in this article How long does it take to see RTP data in Google Analytics? Should I develop any custom code to send the RTP data to Google Analytics? Are the data events sent to Google Universal Analytics marked as non-interation? What needs to be configured in Google Tag Manager to enable to GA integration Important note about getting help from Marketo Support: Overview RTP has great a integration built in with Google Analytics that will pass data through for you. This doc will answer some of the most frequently asked questions about this integration. How long does it take to see RTP data in Google Analytics? Custom Variables (classic Google Analytics version) or Dimensions (Google Universal Analytics version) should show up after up to 24 hours. Custom Events show up in Real-Time Real-Time Data details: About Real-Time - Analytics Help Real-Time Data is available in all Google Analytics accounts. No changes to the tracking code are necessary. To see Real-Time data: Sign in to your Google Analytics account. Navigate to your view. Select the Reporting tab. Select Real-Time. Should I develop any custom code to send the RTP data to Google Analytics? No, all data is sent automatically by RTP to Google Analytics behind the scenes. Here are the related pieces of documentation to get the Google Analytics integration set up successfully: Integrate RTP with Google Analytics - Marketo Docs - Product Docs Integrate RTP with Google Universal Analytics - Marketo Docs - Product Docs Are the data events sent to Google Universal Analytics marked as non-interation? Yes. The RTP script sends data events to Google Analytics (both Classic and Universal) as non-interation, so it has no affect on bounce rate and pageview metrics. Google Universal Analytics version: ga('send', 'event', 'RTP-Segments', 'segmentName', 'organizationName', null, {'nonInteraction': 1} ) Classic Google Analytics version: _gaq.push(['RTP-Segments', 'segmentName', 'organizationName', null, true]); What needs to be configured in Google Tag Manager to enable to GA integration Nothing. Everything is done automatically by the RTP tag and behind the scenes once the integration is set up correctly. Here are the related pieces of documentation to get the Google Analytics integration set up successfully: Integrate RTP with Google Analytics - Marketo Docs - Product Docs Integrate RTP with Google Universal Analytics - Marketo Docs - Product Docs Important note about getting help from Marketo Support:

Article Text Included in this article Overview The Background The Problem The Solution Overview RTP gives a dashboard that provides lots of valuable information about your RTP instance and how everything is performing. One of the widgets in this dashboard is Top Industries. This widget is designed to give you a breakdown of the top performing industries, but sometimes the industry widget is empty: The Background When a segment is saved in RTP, it is automatically assigned a type. If the segment contains only the Industry filter, then it is assigned the 'Industry' type and is included in the Industry widget on the dashboard. So, this widget only contains information on Industry segments. If it is not an Industry segment, it will not be included here. The Problem You can obviously add more filters to the segment other than Industry. However, if the segment contains other filters, then it is assigned the 'Complex' type and is not included in the Industry widget. The only information that will display in the Industry widget is what comes from segments that use only the Industry filter and that alone. The Solution If you'd like a particular segment to display in the Industry widget, there are two options: 1. Remove the other filters other than Industry. 2. Create different additional Industry-only segments.

Overview RTP works very closely with your Marketo Lead Database to pull information about previous visitors, which makes it important for Marketo and RTP to keep accurate and matching information about visitors. There are 3 scenarios that can arise based on how much information is known about the visitor, and each is handled differently. These scenarios are described below. New Lead with no Email Address and no Marketo Cookie When this kind of lead fills out a Marketo form: Their Marketo cookie is created Lead details will be updated and the Marketo-RTP sync process is initiated The lead will then be known to RTP and potentially eligible for personalized campaigns Lead with Email Address but no Marketo Cookie When this kind of lead receives a Marketo email campaign and clicks on a link in the email: A new Marketo cookie is created for them This creation initiates the Marketo-RTP sync process Known Lead with an Email Address and Marketo Cookie Any changes to the lead's data will be synced between Marketo and RTP within 5 minutes

Article Text Explanation: In RTP the tracking is session-based, similar to most web analytics tools. A session starts with the first page view and ends 30 minutes after the last click on the website. For example: Scenario RTP Result Visitor views 1 page on the website and leaves 1 visit & 1 page view Visitor views 2 pages on the website within 30 minutes and then leaves 1 visit / 2 page views Visitor views 1 page on the website, leaves, then returns 45 minutes later and views 1 page 2 visits / 2 page views

Overview SSO Authentication Updating SSO Credentials Tips SSO Only Login Wait to disable the existing certificate Overview Marketo’s Single Sign On (SSO) feature allows your company to use your own company’s SSO service to authenticate your login into your Marketo instance. Your initial setup of the SSO is covered in the documentation here. You may need to change your SSO authentication settings after the initial setup. This document will show you the process on how to do so. SSO Authentication The Identity Provider (IdP) you use will provide you with your SSO authentication credentials and security certificate. Marketo uses this information to validate your login from your IdP, so these credentials come from your IdP. Updating SSO Credentials Once you have retrieved the new security certificate, you can enter it into Marketo. 1. Under Admin click on Single Sign-On. 2. Select Edit in the SAML Settings 3. Enter your Issuer ID, Entity ID, select the User ID Location and click Browse. 4. Select your Identity Provider Certificate file. 5. Click Save. Tips There are a couple things to watch out for when changing your SSO certificate. Here’s a couple tips to avoid trouble along the way. SSO Only Login If your company uses SSO for login, you’ll have an optional setting to restrict login access to your Marketo instance to SSO logins only. This prevents users from logging in directly, forcing the use of SSO. You can check for this setting under Admin > Login Settings These settings do allow the creation of a special User Role that can bypass the SSO restriction. However, sometimes as people come and go within the company, the users enabled with that User Role could no longer be available. TIP: Before changing your SSO certificate, create a new user utilizing this User Role that bypasses the SSO requirement. If something goes wrong while setting up the new certificate, you’ll be glad you have a back door into the Marketo instance! Wait to disable the existing certificate Your IdP will issue a new certificate, but what if something goes wrong while entering the new information into Marketo? TIP: Get the new certificate and set it up in Marketo before you fully disable the existing certificate within your IdP on their side. If something happens to the new certificate, you’ll be glad you have the do-over available and can switch back to the existing certificate that still works!

Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well. Activities in the activity log are only retained for 25 months, or 37 if you have purchased the premium data retention option. The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done. Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed. For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead. An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list. Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs. Example: This approach can work for many different activities, but let’s use form fill outs as an example. Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter. Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it: 1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field. 2. Create a new Smart Campaign 3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List 4. Add these two Flow Steps to the Campaign Flow: Flow Step 1: “Change Score” Score Field Name: your score field name Change: +1 Flow Step 2: “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name” “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing. Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.

Article Text Included in this Article: Enabling or Checking if the Tag is Enabled Validating the Tracking Code Checking if the Tag Executes the Tracking and Personalization Code Enabling or Checking if the Tag is Enabled Log in to RTP and enable the tag within the Account Settings page. Confirm the Tag toggle is set to On Validating the Tracking Code Check if the RTP tracking code is injected into your website's pages. In a web browser, open the developers console. Go to Network, Search for rtp. Locate the rtp.js. Checking if the Tag Executes the Tracking and Personalization Code You should see four RTP calls: rtp.js trw msg, appearing twice If you only see the first rtp.js call but not all other calls, check the following: Validate the tag's account ID In RTP, go to Account Settings, click Generate Tag, and confirm the correct Account ID Confirm the Account ID is the same in the code installed on this page (it's case sensitive) Validate there are no javascript errors. In Developers Tools, go to the Console tab and check if there are any error messages related to RTP or to jQuery Validate the tag is injected properly Check if the tag is not cutting code lines or any remark elements are not there. The RTP tag is between remark elements. Some of the RTP code lines are commented In the Developers Tools, go to Sources and add break points in the RTP tag. Refresh the page and see if there are any errors.

Included in this article: Overview Limitations Error Handling and Troubleshooting Overview No-Draft for Snippets allows you to distribute snippet changes without drafting approved assets using it. All assets using the edited snippet get the updates and maintain their respective status: Approved assets get the snippet updates and stay approved Drafts get the snippet updates and stay in draft mode No-Draft is automatically enabled for all Administrator roles. An admin can then enable this feature for any additional role. While No-Draft Snippets are very useful, they do have some limitations and issues that tend to arise. This article will show you what those limitations are and how to troubleshoot issues that can come up. Limitations This feature is designed to save time with the snippet approval workflow. There are a few limitations to be aware of: No-Draft will not work if you replace one segmentation with another one in the same snippet. However, No-Draft will work if you change, add, or delete a segment within a segmentation that is referenced in the snippet No-Draft will not work if you add/remove a segmentation to a previously approved snippet By design, No-Draft will fail if you make a dynamic snippet static, or a static snippet dynamic. If your use case requires this scenario, then we recommend you create a new snippet to be used across your assets. If you must update the existing snippet, then you will need to approve it using the Create Draft option, then re-approve the assets using the snippet (in other words, the old behavior) No-Draft does not auto-approve drafts Users without the No-Draft permission can still approve a snippet, however it will generate drafts of approved assets No-Draft works only when approving one snippet at a time Assets using the snippet are locked for approval until No-Draft is done processing Snippet updates made to approved assets cannot be rolled back No-Draft applies only to snippets Error Handling and Troubleshooting If something goes wrong, an error message is delivered to the Notification section of Marketo. You can subscribe to this notification and receive email alerts in their inbox. Users must subscribe to No-Draft in each workspace with the permission enabled. If an error does occur, chances are that the update process was not completed. Some assets may have the updated snippet content and others may not. To resolve, redraft the snippet and re-approve. 1. Select the snippet and click Edit Draft. 2. Make a small edit in the snippet editor to create a draft (such as pressing the keyboard’s spacebar). 3. Click Approve Snippet. 4. In the dialog box, select Update all to start over. This should fix the issue. Contact Marketo Support if the problem persists.

Article Text 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, pdf, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you have the ability to see how your content is performing and to 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 optimally use this feature (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, then it will add to the tracking and views of those discovered content pieces. You can also manually add new content to be listed and tracked in the All Content page. 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 have been seen by this visitor in 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 involving less prep work for you. However, you do still need to review the discovered content, 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 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 will 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) Image: Example of Populating Metadata for HTML content into Predictive Content

Article Text 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

Any emails being sent as part of 'Forward to Friend' will create that user as a new lead (provided that the lead does not already exist in Marketo). When leads are created in Marketo via the 'Forward to Friend' feature, Marketo automatically unsubscribes the lead records in order to protect our global customers from anti-spam laws. This is because a lead being sent a forwarded email doesn't qualify as opting in to a mailing list and also prevents them from getting any other emails by accident.

NOTE: To secure your Marketo landing pages requires either Marketo SSL for Landing Pages (obsolete service) or Secured Domains for Landing Pages. Please contact your Marketo Customer Success Manager for more information or to purchase. If you have already secured your Marketo landing pages with Secured Domains for Landing Pages and now need to add additional subdomains to be served securely, please follow the steps below: Step 1. Create your new subdomains (CNAMEs and Domain Aliases) Step 2. Submit a support case to secure your new subdomain STEP 3: Create New Landing Pages Step 1. Create your new subdomains (CNAMEs and Domain Aliases) To secure a new subdomain, please create the CNAME(s) and domain alias(es) in your instance. For more information on this, please see: Add Additional Landing Page CNAMEs. Step 2. Submit a support case to secure your new subdomain Once you’ve created the new subdomain (CNAME and domain alias), please click the link below to create a support case. OPEN A NEW SUPPORT CASE Marketo login required. Select Case Type - "Help me setup/create" Select Case Issue - "System Configuration" If you have multiple instances, please provide us with the Munchkin Code (Found in Admin > Munchkin) of the instance that is ready. Format ###-XXX-###. Marketo will have any additional certificate(s) generated and loaded to cover the new subdomain(s). This step may take up to 3-business days. Marketo will contact you when this step has been completed. STEP 3: Create New Landing Pages Once you receive confirmation that the subdomain has been added, you can now create new HTTPS landing pages. Please be sure all images, JavaScript files and other external links in your landing pages are HTTPS. If you previously created landing pages, please review each of these and update all references to HTTPS. Please contact Marketo Support with any issues you may encounter. If you purchased the SSL for Landing Pages service, you may need to upgrade to Secured Domains for Landing Pages, our new solution to secure landing pages. Please contact your Marketo Customer Success Manager to add Secured Domains for Landing Pages to you subscription. Please note, with this upgrade, Marketo will provide the required certificate(s) and manage their ongoing approval.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Troubleshooting Web Personalization (RTP) Content Recommendations Appearing Across Domains

Web Personalization (RTP) - Can I Delete or Edit Lables?

Troubleshooting - Web Personalization (RTP) Campaigns suddenly stopped working

Troubleshooting Web Personalization (RTP) - Content Analytics: Content Discovery Doesn't Work

Web Personalization (RTP) - What is the difference between Target URL and the Include Pages?

Troubleshooting Web Personalization (RTP) - Segment not Matching Organizations Visiting the Website

Web Personalization (RTP) - How to Show a Campaign Only Once Per Visitor

Web Personalization (RTP) - Google Analytics FAQ

Troubleshooting Web Personalization (RTP) -- The Industry widget in the Dashboard is empty

Web Personalization (RTP) - How does Lead Data Syncing Work from RTP to Marketo

How does Web Personalization (RTP) calculate views and visits?

Changing your Single Sign On Certificate

Storing Activity Data Beyond Retention Policy

Troubleshooting Web Personalization (RTP) - RTP Tag

No-Draft Snippet Limitations and Troubleshooting

How Auto Content Discovery Works in Predictive Content

URL Parameters with Web Personalization and Predictive Content

Unsubscribed Occurs When ‘Forward to Friend’ Email Is Received

Building a Lead Lifecycle Program (Video)

Setting Up Secured Domains for Marketo Landing Pages - ADDING NEW SUBDOMAIN