Knowledgebase

Featured article

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

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 In the Smart List tab, choose the filter for your desired segmentation, and the Segment Changes trigger for the same segmentation 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, 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 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 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 Select your custom fields in the drop down menu at the bottom of the page, then click 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 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 There you have it! You can now use your segmentations in My Marketo to target your audience in RTP campaigns.

Issue You need to locate the Munchkin ID for a specific Marketo instance. Solution What is a Munchkin ID? Marketo's custom JavaScript tracking code, called Munchkin, tracks all individuals who visit your website so you can react to their visits with automated marketing campaigns. Even anonymous visitors are tracked along with their IP addresses and other information. The Munchkin ID is the unique identifier for a specific Marketo instance and insures tracked activity goes to the correct instance. How to find your Munchkin ID 1. Log into the specific Marketo Instance you need the Munchkin ID for. You can verify the instance name by checking the listing in the top left of your browser. This is a article attached image 2. Go to Admin and click Munchkin in the tree on the left in the Integration section. This is a article attached image 3. The Munchkin Account ID will be the first thing listed in the Tracking Code box. This is a article attached image

Issue An email program fails to send emails to a large number of leads/people in the Smart List. Solution Sometimes leads/people in your Email Program's Smart List will be skipped in the email send because they already reached their daily/weekly communication limit. You can confirm if this has occurred by following these steps: Open your Email Program. Change your view to Control Panel. Click on View Results in the top left panel to see a list of all activities attributed to the email program. Click on Filter > Custom. Select the Send Email box. Click the Apply button. Scroll to the bottom of the list. If the leads/people have been skipped due to communication limits, you will see that a large number of leads/people listed as "Skipped Lead already used up Daily/Weekly communication limit." You can check or adjust your Communication Limits in the Admin panel of your Marketo instance.

Note: Please ensure that you have access to an experienced CSS and Jquery developer, because Marketo Technical Support is not set up to assist with troubleshooting custom coding. Advanced solution - requires CSS and jQuery knowledge Issue: Need to set a popup window in Marketo. The rich text editor (hyperlink - popup tab) has this feature but gets overrode by most browsers opening in a new tab. Solution: Use jQuery. Here's a third party site that covers how: http://yensdesign.com/2008/09/how-to-create-a-stunning-and-smooth-popup-using-jquery/ This does work in Marketo landing pages - The header content goes in the custom head HTML Save a copy of the CSS and popup.js to the images and files section of Marketo Update the CSS and .js files to your copies in Marketo I used the same input version in the example here, but you could use a link or content instead. Click here for a sample page in Marketo using the above solution: http://info.dbmayberry.com/popupsolution.html

Please ensure that you have access to an experienced JavaScript developer. Marketo Technical Support is not set up to assist with troubleshooting JavaScript. Here's our recommendation for how you can collect keyword, search engine, and PPC info in Marketo. It takes a bit of work, and you'll definitely need to know your Javascript. 1. Create custom fields You'll need to create some new fields to store the additional data. If you want these fields to be visible in Salesforce, create them on both Lead and Contact records. All of these should be of type String: Search String -- to store the query that drove the lead to your web page Search Engine -- the search engine or URL which provided the lead your web page Pay Per Click Keyword -- if the link was a PPC (ex. AdWords), the PPC keyword for that link 2. Add the fields to your forms Go to the Design Studio and edit any forms where you want to capture this information. Add the fields you created as hidden fields set to a default value (as opposed to set from a cookie or URL parameter). You'll probably want to leave the default value as blank -- that is, the lead did not come from a PPC -- but feel free to put in another value if appropriate (Making a Field Hidden on a Form) This solution will not update the Lead Source for leads who come to your site via PPC. If you want the lead source updated for PPC leads, you'll need to do that via a Smart Campaign or by adding it as a hidden field to your forms. 3. Put Javascript on your landing pages You MUST edit the Javascript below or it will not work!The code below sets cookies with the search engine, search term, and PPC info as long as it came from a domain outside your website. The script then populates the form fields using the cookie values. The reason for using cookies is because your leads may not fill out your form when they first hit your landing page; they may click your AdWords ad, browse around, and then go to your form. Cookies retain those values for when they're needed -- when the leads complete your form.Using cookies also lets you capture this info on non-Marketo pages too. See step 4 if you're interested in that.If you want this on a single landing page, add it as a Custom HTML block. If you want this on several or all your landing pages, add it to your Landing Page Template.You'll need to change the following variables/strings, highlighted in the Javascript below: Variable Description excludedReferrers All domains where you don't want to check referrers as in "company.com" -- typically these are your own website domains. If you need to exclude multiple domains, separate them with commas. cookieDomain The base domain of your landing pages without any subdomians (like "www." or "pages."). This will be used to store cookie values. If your landing pages are on "pages.yourcompany.com" then this should be "yourcompany.com". payPerClickParameter The URL Parameter with the keyword depending on how you set up your your pay per click URLs. Typically "keyword" or "kw". searchStringField searchEngineField payPerClickKeywordField IDs of the hidden form fields where the cookie values should be inserted. Find them by following the instructions in this article: Setting or Getting a Form Field Value via Javascript on a Landing Page <script src="/js/public/jquery-latest.min.js" type="text/javascript"></script> <script src="/js/public/jquery.cookie.js" type="text/javascript"></script> <script src="/js/public/jQueryString-2.0.2-Min.js" type="text/javascript"></script><script type="text/javascript"> var $jQ = jQuery.noConflict();$jQ(document).ready(function(){ // //--- CHANGE THESE!!! --- // // Change this to match domains of referrers you want to ignore. // You'll want to ignore referrers from your own domains. // Use only the base domain name without subdomains (ex. "company.com") // Separate multiple domains with commas (leave the brackets). var excludedReferrers = [ "yourcompany.com", "yourcompany2.com" ]; // Change this to match the base domain of your company's landing pages. // Cookies will be created with this domain. // Ex. If your landing page domain is "pages.yourcompany.com" then use // "yourcompany.com" var cookieDomain = "yourcompany.com"; // The URL parameter that has your pay-per-click info. // Typically "kw" or "keyword" (depends on how you set up your PPC URLs) var payPerClickParameter = "keyword"; // IDs for the fields to be updated. var searchStringField = "#Search_String__c"; var searchEngineField = "#Search_Engine__c"; var payPerClickKeywordField = "#Pay_Per_Click_Keyword__c"; // //-- you probably shouldn't change anything after this -- // var refer = document.referrer; var searchString; var searchEngine; // if there's no referrer, do nothing if ( (refer == undefined) || (refer == "") ) { ; } else { // get the domain of the referring website -- http://[[this-thing.com]]/ var referrerDomain = refer.substr(refer.indexOf("\/\/") + 2, refer.indexOf("\/",8) - refer.indexOf("\/\/") - 2).toLowerCase(); var excludedDomainFound = false; var i = 0; // search the excluded domain list to see if the referrer domain is on it while ( (i < excludedReferrers.length) && !excludedDomainFound) { var thisExcludedDomain = excludedReferrers[i].toLowerCase(); // weird semantics here -- indexOf returns "-1" if the search string isnt found. // thus excludedDomainFound is true only when indexOf matches an excluded domain (!= -1) excludedDomainFound = (referrerDomain.indexOf(thisExcludedDomain) != -1); i++; } // only if the referrer isn't in our excluded domain list... if( !excludedDomainFound ) { // extract the URL parameters from common search engines // To add your own, each engine needs: // name: how the search engine will appear on your Marketo leads // url: REGEX for matching the engine's referrer. ex. /\.google\./i // query: URL parameter that contains the search query - usually "p" or "q" var searchEngines = [ { name: "Yahoo", url: /\.yahoo\.co/i, query: "p" }, { name: "Google", url: /\.google\./i, query: "q" }, { name: "Microsoft Live", url: /\.live\.com/i, query: "q" }, { name: "MSN Search", url: /search\.msn\./i, query: "q" }, { name: "AOL", url: /\.aol\./i, query: "query" }, { name: "Bing", url: /\.bing\.com/i, query: "q" }, { name: "Ask", url: /\.ask\.com/i, query: "q" } ]; // find the referring search engine (if any) i = 0; while (i < searchEngines.length) { if (refer.match(searchEngines[i].url)) { searchEngine = searchEngines[i].name; searchString = $jQ.getQueryString({ ID: searchEngines[i].query, URL: refer, DefaultValue: "" }); break; } i++; } // If no search engine is found, this person probably used a less // popular one. Use the referring doman, then guess the query parameter if (i == searchEngines.length) { searchEngine = referrerDomain; var queries = ["q","p","query"]; var i = 0; while ((i < queries.length) && (searchString == undefined)) { searchString = $jQ.getQueryString({ ID: queries[i], URL: refer }); i++; } // no search strings found -- use this text instead. if (searchString == undefined) { searchString = "None"; } } // Use the provided URL parameter to get the PPC keyword. var payPerClickWord = $jQ.getQueryString({ID: payPerClickParameter, URL: refer, DefaultValue: "" }); // Put the info into cookies. These values will be extracted // and put into a Marketo form later. Expires in 2 years. $jQ.cookie('mktoPPCKeyword', payPerClickWord, {expires: 730, path: '\/', domain: cookieDomain}); $jQ.cookie('mktoSearchEngine', searchEngine, {expires: 730, path: '\/', domain: cookieDomain}); $jQ.cookie('mktoSearchString', searchString, {expires: 730, path: '\/', domain: cookieDomain}); } } // Get the values from the cookies and put them into the hidden fields $jQ(searchStringField).attr("value",$jQ.cookie('mktoSearchString')); $jQ(searchEngineField).attr("value",$jQ.cookie('mktoSearchEngine')); $jQ(payPerClickKeywordField).attr("value",$jQ.cookie('mktoPPCKeyword'));});</script> 4. Add cookie code on your website (Optional) To close the loop on capturing the keyword, search engine, and PPC, you need to add Javascript to your website similar to that above. This code will store that informaiton in cookies, then those cookies will be read when the user submits the form (with the javascript above on your landing pages).This Javascript uses the jQuery, jQuery Cookies plugin, and jQueryString plugin scripts. Deploy them on your site and note the URL where they're hosted.You'll also need to edit all of your web pages, similar to when you installed Munchkin tracking. You can put the Javascript in the same spot of the webpage.In the code below, change the Javascript src URLs to match where you installed jQuery and the plugins excludedReferrers variable as you did in the Javascript above cookieDomain variable to be "yourcompany.com" as you did above payPerClickParamater variable as you did above <script src="/js/jquery-latest.min.js" type="text/javascript"></script> <script src="/js/jquery.cookie.js" type="text/javascript"></script> <script src="/js/jQueryString-2.0.2-Min.js" type="text/javascript"></script> <script type="text/javascript"> var $jQ = jQuery.noConflict(); $jQ(document).ready(function(){ // CHANGE THESE Change this to match domains of referrers you want to ignore. You'll want to ignore referrers from your own domains. Use only the base domain name without subdomains (ex. "company.com") Separate multiple domains with commas (leave the brackets). var excludedReferrers = [ "yourcompany.com", "yourcompany2.com" ]; // Change this to match the base domain of your company's landing pages. // Cookies will be created with this domain. // Ex. If your landing page domain is "pages.yourcompany.com" then use // "yourcompany.com" var cookieDomain = "yourcompany.com"; // The URL parameter that has your pay-per-click info. // Typically "kw" or "keyword" (depends on how you set up your PPC URLs) var payPerClickParameter = "keyword"; // You probably shouldn't change anything after this // var refer = document.referrer; var searchString; var searchEngine; // if there's no referrer, do nothing if ( (refer == undefined) || (refer == "") ) { ; } else { // get the domain of the referring website -- http://[[this-thing.com]]/ var referrerDomain = refer.substr(refer.indexOf("\/\/") + 2, refer.indexOf("\/",8) - refer.indexOf("\/\/") - 2).toLowerCase(); var excludedDomainFound = false; var i = 0; // search the excluded domain list to see if the referrer domain is on it while ( (i < excludedReferrers.length) && !excludedDomainFound) { var thisExcludedDomain = excludedReferrers[i].toLowerCase(); // weird semantics here -- indexOf returns "-1" if the search string isnt found. // thus excludedDomainFound is true only when indexOf matches an excluded domain (!= -1) excludedDomainFound = (referrerDomain.indexOf(thisExcludedDomain) != -1); i++; } // only if the referrer isn't in our excluded domain list... if( !excludedDomainFound ) { // extract the URL parameters from common search engines // To add your own, each engine needs a: // name: how the search engine will appear on your Marketo leads // url: REGEX for matching the engine's referrer. ex. /\.google\./i // query: URL parameter that contains the search query - usually "p" or "q" var searchEngines = [ { name: "Yahoo", url: /\.yahoo\.co/i, query: "p" }, { name: "Google", url: /\.google\./i, query: "q" }, { name: "Microsoft Live", url: /\.live\.com/i, query: "q" }, { name: "MSN Search", url: /search\.msn\./i, query: "q" }, { name: "AOL", url: /\.aol\./i, query: "query" }, { name: "Bing", url: /\.bing\.com/i, query: "q" }, { name: "Ask", url: /\.ask\.com/i, query: "q" } ]; // find the referring search engine (if any) i = 0; while (i < searchEngines.length) { if (refer.match(searchEngines[i].url)) { searchEngine = searchEngines[i].name; searchString = $jQ.getQueryString({ ID: searchEngines[i].query, URL: refer, DefaultValue: "" }); break; } i++; } // If no search engine is found, this person probably used a less // popular one. Use the referring doman, then guess the query parameter if (i == searchEngines.length) { searchEngine = referrerDomain; var queries = ["q","p","query"]; var i = 0; while ((i < queries.length) && (searchString == undefined)) { searchString = $jQ.getQueryString({ ID: queries[i], URL: refer }); i++; } // no search strings found -- use this text instead. if (searchString == undefined) { searchString = "None"; } } // Use the provided URL parameter to get the PPC keyword. var payPerClickWord = $jQ.getQueryString({ID: payPerClickParameter, URL: refer, DefaultValue: "" }); // Put the info into cookies. These values will be extracted // and put into a Marketo form later. Expires in 2 years. $jQ.cookie('mktoPPCKeyword', payPerClickWord, {expires: 730, path: '\/', domain: cookieDomain}); $jQ.cookie('mktoSearchEngine', searchEngine, {expires: 730, path: '\/', domain: cookieDomain}); $jQ.cookie('mktoSearchString', searchString, {expires: 730, path: '\/', domain: cookieDomain}); } } }); </script>

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.

Issue You want to break the link between an email and the template originally used to create it. Solution If you need to delete an email template, or if you need to break the relationship between a template and an email to prevent template changes from affecting the email, you can do the following. Open the email in the Email Editor If you have Email 2.0, click Edit Code. If you have the legacy Email Editor, click Email Actions > HTML Tools > Replace HTML. This will allow you to directly edit the HTML for the email. Make a small edit to the email's HTML outside of the mkteditable sections. Save your changes. If you are concerned that the edit you made will affect the email, you can save the change, re-edit to undo the change, then save again. When you go back to the summary page for the email, the Template: line should now say "None". PLEASE NOTE: It is not possible to reverse this change. They link between the email and the template cannot be re-established once it is broken.

Marketo calls direct complaints received from email recipient Abuse Reports. For more information about Abuse Reports review the links below: Why do people report abuse? What Is the Difference between an Abuse Report and a Feedback Loop Complaint? Abuse Reports: What They Are and How to Avoid Them For additional articles reviewing compliance concerns refer to the articles below: What is a Blacklist? Feedback Loops (FBL) Finding Leads that are Auto Unsubscribed for Email Spam Complaints / Feedback Loop (FBL)

Included in this article: Navigate to the Clickstream module How is Visit Duration Caluclated 00:00 Visit Duration Single page viewed Session timed out Navigate to the Clickstream module Go to the Visitors page Click on a visitor to find the Clickstream module in the bottom right How is Visit Duration Caluclated When a visitor visits a website being tracked by an RTP campaign, it records clicks in the Clickstream module in the RTP platform. Clicking on a visitor allows you to view their viewing information in the Customer Journey section, including: Links clicked Time stamp of each link click Total visit duration Visit duration is calculated by subtracting the first time stamp from the last time stamp. In other words: visit duration = last time stamp - first time stamp. See the image above for an example of this calculation. 00:00 Visit Duration Single page viewed Both RTP and Google Analytics rely on clicks to determine visit duration. This means that if a visitor only views a single page, neither RTP or GA can track when the visitor leaves the page, since there is only the initial time stamp without a time stamp to mark the exit from the page. The visit duration for viewers that didn't view more than one page during the session is recorded at 00:00 since it cannot be calculated. Session timed out Another way that a visit duration can be recorded as 00:00 is if a visitor's session times out. By default, a session will end after 15 minutes of inactivity. For example, if a visitor stays on a page without making any clicks for 25 minutes (perhaps they are reading an article or watching a long video), that session will time out and be recorded with a duration of 00:00. If the visitor finally makes a click after the 25 minutes of inactivity, a new session will begin. In Google Analytics, the session timeout can be customized to be longer or shorter than the default 15 minutes.

Included in this Article: Overview Setup Issues No RTP Tag or GA Integration Differing Filters Differences between RTP and GA Web Bots Visit Duration Sampling Bounce Rates Overview Occasionally you may find differences in comparing RTP analytics and Google Analytics (GA). Some discrepancies may be caused by setup issues with either the RTP or GA platform. However, many small discrepancies are simply due to differences in how RTP and GA handle data, and are unavoidable. Differences of both kinds are highlighted below. Setup Issues No RTP Tag or GA Integration You will need to have the RTP tag turned on in RTP and installed onto any page you wish to track in RTP. You will also need to have GA integrated and turned on in your RTP settings. To learn how to do so, follow these two articles: Deploy the RTP JavaScript - Marketo Docs - Product Docs Integrate RTP with Google Analytics - Marketo Docs - Product Docs Excluded IPs If you have any IPs being excluded by RTP, this data will not be displayed in RTP or used in reporting, but may still be present in GA. To check this: Go to your Account Settings Scroll down and check if you have any IPs being excluded in the Exclude IPs field Differing Filters Some filters exist in GA that don't exist in RTP which can potentially exclude users from their data being reported. If a filter like this is employed in GA, then certain users will be excluded from being tracked in GA, whereas they will be tracked in RTP. Log in to your GA account and navigate to Admin > Filters to check if any exclusive filters have been applied Differences between RTP and GA Web Bots RTP and GA both attempt to detect activity from bots, which are computer programs written to run tasks over the Internet. However, RTP and GA treat the identification of bots or "fake" users differently. For example, when RTP identifies a bot, it may not even send the data on to GA. You can't change that bot activity might be recorded differently, but it should also not affect your data too significantly. Visit Duration A visit from one user automatically ends after a certain period of time in both RTP and GA, but those settings may be different between the two. To learn more, or learn how to change these settings, see How Visit Duration is calculated in RTP. Sampling GA often will actually use a sample of your web traffic data, rather than the entire set of data, to report trends. This will produce very similar results, but most likely will not be 100% accurate. RTP does not make use of sampling, and instead provides summaries using all of the present data. To learn more about sampling in GA, read this article: How sampling works - Analytics Help Bounce Rates Generally, about 50-85% of the traffic to your website actually gets recorded in RTP and GA. This is because both the RTP tag and the GA tag will need to load on the page before they can send data back to RTP or GA. If visitors leave your page before the RTP or GA tags load, then data will not be sent back to the RTP or GA analytics platforms. We recommend that the RTP and GA tags be placed higher in the web page's code in order to give them more time to load, leaving a smaller window for the visitor to leave without data being sent back.

Issue: The web page visit is partially tracked only if users fill out a form otherwise it goes unnoticed. Solution: In several tests the Activity Log shows "Fill out a form" without a page visit. From the traditional standpoint that could be an obscure bug. How users could fill out a form without visiting the page? Google Chrome introduced Incognito. Firefox, Safari, Opera and Internet Explorer implemented as Private Browsing. Pages users visit in Private Browsing/Incognito will not leave traces, like cookies, on users' computers after they close all open windows. A normal visit to any page is not tracked during visits, regardless the navigation path. That includes other pages after the form is filled out. Private browsing is a relatively new feature. It is a new challenge to tracking, applicable to any software and company evaluating users activity. The new Do Not Track feature is a contributing factor for apparently incomplete Activity Logs. When users turn on the Do-not-track feature, the browser tells every website they visit (as well as their advertisers and other content providers) that they do not want their browsing behavior tracked. Honoring this setting is voluntary — individual websites are not required to respect it. Websites that do honor this setting should automatically stop tracking your behavior without any further action from users.

Creating a campaign to redirect a targeted group of visitors is as easy as targeting visitors for a call-to-action campaign. Here are the steps to accomplish a redirect: On the Segments page, click the Create New button and set up the new segment to target the group you wish to send the redirect to Then, in the Campaigns page, create a new campaign In the Target Segment field, choose the segment you just created Finally, scroll down check the Redirect checkbox, enter the URL you wish to redirect to, and hit

Issue You want to re-map a synced SFDC field to a different field in Marketo. Solution Yes, it is possible to re-map Salesforce - Marketo fields after initial sync. For this you need to Contact Marketo support with a request for your current field mapping and your desired field mapping. You will need to provide the Marketo Field(s) and the Salesforce API Name(s), then format your request similar to the example below. Important Note Before initiating the re-mapping, please export the records and their field values from Marketo and import the values into their Salesforce or create a smart campaign to write the data from one field into the other. This is important so that there is no data loss after the remapping work has been performed. Marketo will not automatically push these values to SFDC, after the mapping is complete. Example Request Current Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead) Field Label: [Marketo Field Name 2] CRM Field Map: fieldName__c (SFDC Contact) Desired Mapping: Field Label: [Marketo Field Name 1] CRM Field Map: fieldName__c (SFDC Lead) fieldName__c (SFDC Contact) Field Label: [Marketo Field Name 2] CRM Field Map: Limitations - Fields need to be of the same type (String/String, Date/Date, etc) - The losing field must be completely removed from use from any Campaign, Form, etc. - The fields must exist on the same object in Marketo (for example a field on Company cannot be merged into a field on Person or vice versa) - Fields can only have one of each object type (eg: A Marketo Field could be mapped to a SFDC_1 (Lead) field and a SFDC_1(Contact) field, but can not be mapped to both SFDC_1 (Lead) and SFDC_2 (Lead). - Fields can be mapped to a maximum of 2 SFDC fields - SFDC fields can only be mapped to one field in Marketo Please note that there may be additional limitations in certain circumstances. The Marketo Support agent that handles your request will provide any further details should such a situation arise.

For those in highly regulated industries, your company may additionally require that you securely encrypt the Marketo tracking links embedded in Marketo emails. Remember that Marketo takes the URLs you place inside of emails and shortens them using the "Branded Tracking Link" domain (this is another CNAME you set up in Marketo under Admin--> Email). These tracking links are how Marketo enables you to track engagement with your emails. Overview & FAQ - Overview & FAQ: Secured Domains for Tracking Links What's Changing Marketo has discontinued the Secured Page Services: SSL for Tracking Links service and its manual certificate renewal process. This is being replaced with the Marketo Secured Domains for Tracking Links product which provides all needed certificates and manages renewals automatically. Action Required To secure your email tracking links, contact your Marketo Customer Success Manager to add the Secured Domains for Tracking Links product to your subscription. Once you’ve purchased Secured Domains for Tracking Links for your instance: An automated message will be sent to the Support Admin on your account They will need to respond to the message with the Munchkin ID of the instance needing Tracking Links set up. Responding to this case will auto generate a Support Case for a Marketo technical support engineer to help complete the process. Marketo will then have certificates generated to cover all the domains and subdomains that you’ve set up in your instance. Within 3-business days, we will create a secure server endpoint. Please plan accordingly for this 72-hour turn-around-time. Do I need Secured Domains for Tracking Links? Secured Domains for Tracking Links ensure that tracking links can be served securely for domains which have implemented HSTS (HTTP Strict Transport Security). HSTS is a web server directive which forces all subsequent requests for resources on that domain to be loaded through HTTPS. If you have implemented HSTS at your site on any domain that you are choosing for either your Landing Page CNAME or your branded email tracking links domain, you will need Secured Domains for Tracking Links and/or Secured Domains for Landing Pages. How is the new Secured Domains for Tracking Links Better? With Marketo’s new Secured Domains for Tracking Links product, you no longer have to provide renewal/updated certificates to Marketo. We’ll procure any necessary certificates and manage their renewals automatically – giving you a more secure and convenient solution for securing your links in emails! Do I have to upgrade? An upgrade is required. Marketo no longer supports the legacy Secured Page Services: SSL for Tracking Links certificate renewal process. Will my tracking links automatically convert to HTTPS? You will not see tracking links in your Marketo emails changed to HTTPS (they will remain prefixed HTTP). However, when an end user clicks the link, if HSTS is enabled for the domain in the link being clicked and the browser is aware, the request will be automatically changed to HTTPS by the browser and served securely via HTTPS before re-directing to the destination of the link. This means that no insecure connection occurs because the browser recognizes the HSTS security policy. HSTS preload is required for this to work. If a tracking link top level domain is not on the HSTS preload list, then link clicks will be insecure until the browser becomes aware of the HSTS policy on the target domain by visiting the site. Will my old links in emails continue to work? Links in emails will continue to function normally. Is this article helpful ? YesNo

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.

Included in this article Highlights The MLM package in SFDC’s AppExchange is being retired. The MLM package itself doesn’t do much, but was responsible for installing 16 custom fields (16 on the Lead object and 16 on the Contact object) that sync data from Marketo to SFDC like Lead Score and Acquisition program. The configuration update will shut off the sync of data to the MLM package and these fields, so the data in those fields in SFDC will become stale and won’t update. You can keep syncing this data to SFDC but it requires creating new custom fields. When the fields are re-created, a drip process will be triggered to backfill existing data from Marketo into the new fields in SFDC. No Data Will Be Lost Marketo is the source of this data, and the data inside of Marketo will not be touched. The data in Marketo will continue to stay current as it always has. The change being made is in how it is passed into SFDC. No matter what, the data will be preserved inside of Marketo. What is the MLM Package? The MLM package doesn’t actually do a lot on its own. It has been a prerequisite that had to be installed during the Marketo > SFDC integration setup before the MSI package could be installed but it’s a pretty safe bet that hardly anyone actually uses it. It’s the fields that were installed during its installation that get the most usage. The fields that the MLM package created are frequently used by sales teams inside of SFDC. Data from the Marketo fields passes into these fields in SFDC where it can be viewed on Lead and Contact records (if you’ve added it into the page layout). Telling the Difference Between MLM and MSI in SFDC MLM and MSI are two different tabs inside of SFDC. It’s important to know which is which. The Sales Insight tab is the tab labeled “Marketo”. The MLM tab is labeled as “Marketo Lead Management” Fields Affected When the configuration change happens, no data will be synced from these 16 fields in Marketo to the 32 corresponding SFDC fields (16 on the Lead object, 16 on the Contact object). Lead Score Acquisition Program Acquisition Program Id Acquisition Date Original Search Phrase Original Source Info Original Source Type Original Referrer Original Search Engine Inferred Company Inferred Metropolitan Area Inferred Phone Area Code Inferred State Region Inferred City Inferred Postal Code Inferred Country The Changes Being Made For most customers, the only fields commonly used are Lead Score and Acquisition Program. While these fields will stop updating in the Lead detail pages, it’s important to remember that the Lead Score data will still be available through Sales Insight without any changes being made. Effects on Sales Insight MSI will have very little change made. The Stars and Flames will still function the same way, and lead scores will still update and display current information. Only one change will affect MSI, and it will have a very limited scope. Scoring Still Displays in MSI The Sales Insight Score tab on Lead records in SFDC will continue to show up to date score information. This view will not be impacted in any way. Stars and Flames Still Function the Same Way MSI’s Stars and Flames will still update with data the same way that they did before, even if you have set them up to work with custom score fields on the Marketo side. For more information about Sales Insight’s Stars and Flames, please check out the documentation here: Priority, Urgency, Relative Score, and Best Bets - Marketo Docs - Product Docs Customize Stars and Flames - Marketo Docs - Product Docs Set Score Fields to be used for Stars and Flames in Sales Insight - Marketo Docs - Product Docs The Only Change Inside of MSI There is only one small change to the MSI package. If you have "Debug Mode" enabled in Sales Insight Config (pretty rare), then inside of Sales Insight, if you mouse-over the Stars, you’ll see a label that gives the score. This functionality relied on a dependency between MSI and MLM that has been patched and removed now. As a result of that change, the score can’t be displayed in the hover-over label. Again, this score only ever appeared if you had debug mode enabled, which is very uncommon. Exceptions to MSI Patch The MSI patch wasn’t able to upgrade every version of MSI. A very small number of customers who have an older version of MSI currently can’t be updated by the patch and will need to manually upgrade their MSI installation. If your company uses Marketo Sales Insight version 1.38 or below, you will be required to manually upgrade to the newest MSI package version. Identifying Your MSI Version To check what version of MSI you’re currently using, navigate to Admin > Sales Insight, then look for the Version info in the Status box in the middle of the page. Manually Upgrading Your MSI Package If you find that you are using MSI Version 1.38, you’ll need to manually upgrade your Sales Insight package. The directions on how to upgrade MSI can be found here: Upgrade Marketo Sales Insight for Salesforce1 - Marketo Docs - Product Docs If you’d like help with this installation, please feel free to reach out to Marketo Support with the directions found here: Contact Marketo Support Effect on Fields in Lead Layout Page The change that will be noticed will be to the fields shown in the Lead detail pages in SFDC. If you have any of these fields like Lead Score added to the layout of your Lead detail page, these are the fields that will no longer update and will begin displaying stale data. If your sales teams utilize any of this data, you’ll want to recreate the fields in SFDC to pull in the updated data from Marketo. Keeping Field Data in SFDC The sync of data into these 32 fields (16 on the Lead object, 16 on the Contact object) will be shut off. If you want to keep syncing data from these fields to use it in SFDC, that can be done. You’ll need to create new custom fields in SFDC for the Marketo data to sync into, using specific API names to match up to the original Marketo fields. There are different versions of Salesforce, but don't worry, all of the details on how to recreate the affected fields as well as a video tutorial can all be found in the documentation here: Adding Marketo Fields to Salesforce Cut Off Date The MLM package will be officially deprecated as of January 31st, 2017. The data will stop syncing to the fields created by the MLM package after this date. Backfilling Data Creating the new custom fields will kick off a drip process to backfill the data from Marketo to SFDC. That takes all existing data for these fields from Marketo and pushes it back to SFDC into the new custom fields you’ve created. There are some important details to how this process works, so here they all are! The data backfill process will only initiate if you recreate the old fields using the proper API names as specified. The backfill process goes through a separate communication “pipeline” outside of the standard sync cycle. The backfill process will push data at roughly the same rate as the “Push Updates” rate we get now in the regular sync—somewhere between 7k to 12k records per hour. The total time it takes to update all records will vary depending on sync rate in the separate “pipeline” and the number of records being updated. Once the backfill process is complete, an instance notification will be posted in the Marketo notification center. The backfill process updates the new fields in SFDC records with the data that is in the 16 Marketo fields. When this update happens, it will create a SysModStamp on the record in SFDC. Any new SysModStamp will queue the record to resync back to Marketo. If a lead record is in line waiting for the backfill process to pass updates to SFDC and that record gets resynced through the standard SFDC sync cycle before the backfill is done for that lead, that record will be taken out of the queue of records waiting for the backfill process. This is done intentionally to prevent race conditions where old data could potentially overwrite more current data. SFDC Sync Backlog Any time a large number of records are queued to resync between Marketo and SFDC, it could cause a sync backlog. A sync backlog is only a possibility, not a certainty. Most customers will not have any problems. The rollout schedule has been staggered out over time specifically to address this issue and to prevent sync backlogs. The backfill process passes data through a different channel, outside of the standard sync cycle, so it won’t cause a backlog in that process. It’s the resyncing of the records after the backfill that puts stress on the sync cycle. That standard sync cycle is where you may experience slowness if a backlog develops. The resulting resync of leads will increase volume and put a heavier load on the sync. However, whether or not it actually creates a backlog in the sync cycle depends on many factors like your existing sync volume and if you have any other large number of updates being made. If you think your sync cycle is experiencing a backlog, please reach out to Marketo Support. We can check the existing volume for both the standard sync cycle and the backfill process. Cleaning Up SFDC The MLM package and the 32 fields created by it (16 on the Lead object, 16 on the Contact object) will be orphaned and no data will continue to be synced to them, making them obsolete. Since they’ll be unusable, you may want to remove the MLM package and delete the fields. This process is optional, but can be done if you choose. Uninstalling the MLM package deletes fields, data and workflows created by the package. Any dependencies like for reports or workflows inside of SFDC that you have created based off of these fields will need to be removed manually. If these other custom dependencies exist, they’ll need to be removed before uninstalling the MLM package. For information on how to uninstall AppExchange packages from SFDC, please see their documentation here: Uninstalling a Package For detailed information on how to avoid problems elsewhere in SFDC, please see our documentation here: Changes to Marketo Salesforce Sync – Preventative Troubleshooting Preventing Problems in SFDC Since the fields in SFDC are brand new fields that have just been created, everything in SFDC that references the original fields will need to be updated to point to the new fields instead. This includes all Workflows, Apex Triggers, AppExchange packages for 3rd party software and Reports. As soon as the new fields are recreated in SFDC, the Marketo fields are remapped to those new fields. The backfill process begins and the sync is cut off to the older existing fields, so they immediately stop updating. This results in two important things to be aware of: Everything in SFDC referencing the older original fields will be referencing old data that is no longer updating. The backfilled values entered into the newly recreated fields will be seen by SFDC as brand new values, not the existing values that they are in Marketo. This can cause your Workflows, Apex Triggers, AppExchange packages for 3rd party software and Reports to all behave differently. For full details on this, please see Changes to Marketo Salesforce Sync – Preventative Troubleshooting Where to Go for More Information Recap Summary Now that the changes have been completed, and the deprecation date has passed, this doc will give you the overview of what has happened: Changes to Marketo Salesforce Sync - Recap Summary Frequently Asked Questions Check out our FAQ for the answers to the most commonly asked questions. Changes to Marketo Salesforce Sync – Frequently Asked Questions Discussion thread We've created this discussion thread in the community to address any questions you may have. This discussion thread will be monitored by the Marketo team to ensure you get answers to your questions. Changes to Marketo Salesforce Sync – Questions and Discussion Overview Documentation This doc will give you a high level overview of what the configuration changes are and what to expect moving forward: Changes to Marketo Salesforce Sync - Overview Release Schedule The release is being staggered over the course of 6 months. This doc will give you exact details so you can know precisely when your Marketo instance will be updated. Changes to Marketo Salesforce Sync – Release Schedule Recreating Affected Fields There are different versions of Salesforce, but don't worry, all of the details on how to recreate the affected fields as well as a video tutorial can all be found in the documentation here: Adding Marketo Fields to Salesforce Preventing Problems In Salesforce Recreating the new fields in Salesforce can cause your Workflows, Apex Triggers, Reports and AppExchange apps behave differently. They'll need to be updated and this doc will show you what to watch out for: Changes to Marketo Salesforce Sync – Preventative Troubleshooting Contact Marketo Support If you would prefer to talk to someone live, please contact Marketo Support over any of the channel listed here: Contact Marketo Support

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

Included in this article Overview Do you need to create fields in Salesforce and have them connect to specific fields in Marketo like for Lead Score or Acquisition Program? If so, this document will take you right to the instructions on how to get that done! Step by Step Directions for all Salesforce Editions Adding Custom Marketo Fields to Salesforce Video Overview Here's a video tutorial of the entire process that should make it easy to follow along: Salesforce Connector Setup Enjoy!

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

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

How to Find Your Munchkin ID for a Marketo Instance

Email Program Fails to Send Emails

Setting a Popup Window with CSS and Jquery

Blacklist Resolution Flowchart

Capturing Search Engine and PPC info on Landing Pages

Troubleshooting Web Personalization (RTP) - RTP Tag

How to Break the Connection between an Email and the Email Template

Abuse Report Deep Dive

Web Personalization (RTP) - How Visit Duration is Calculated in RTP

Troubleshooting Web Personalization (RTP) - Potential Gaps between RTP Analytics and Google Analytics

Visits to web pages do not reflect actual activity

Web Personalization (RTP) - Redirect Targeted Visitors to Specific Pages

Re-mapping SFDC – Marketo Fields

Which blacklists should I be concerned about?

Setting Up Secured Domains for Tracking Links

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

Changes to Marketo Salesforce Sync – Under The Hood

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

Adding Marketo Fields to Salesforce