Knowledgebase

Featured article

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

Issue Issue Description You noticed that there are form actions missing from the Form Actions dropdown. The following options should be missing: Approve Draft (If form is in a draft state) Preview Clone Form Embed Code Preview Draft (if form is in a draft state) An example of this dropdown may appear as: Solution Issue Resolution This is due to the form having been created using an outdated version of the Marketo Form Editor. You may want to consider re-creating this form with the current Marketo Form Editor, and archiving the outdated form. Keep in mind that if you archive the form, you will want to reference the new form in smart lists and smart campaigns.

Issue Attempting to push a custom audience to Facebook results in a Facebook Authorization Error visible in Notifications. Some custom audiences can be pushed and it appears to be only affecting a certain Ad account. Solution Issue Resolution 1.) Check if the Custom Audience Terms (facebook.com/legal/terms/customaudienc) have been accepted 2.) Log in as the user used in the Facebook Custom Audience service in Marketo and check in Audience Manager to see if there are any custom audiences that have the "Accept Terms" button pop-up similar to this screenshot. 3.) As per our recent release notes at docs.marketo.com/display/public/DOCS/Release+Notes%3A+Winter+%2719: "Facebook now requires a Business Manager account in order to leverage your Custom Audience integration. Your Facebook LaunchPoint service must be associated with a Business Manager account or your integration will no longer work after January 14, 2019. To set up a Business Manager account, please refer to Facebook Help." 4.) Check if the user used in the Facebook Custom Audience service in Marketo is a Business Manager account 5.) After completing the checks above, try to push a custom audience again to the affected ad account. If unsuccessful, recreate the Facebook service and test to push a custom audience from there.

Issue You want to use Slack with webhooks to be able to customize the integration a bit more than using it as a Launchpoint service. Solution We will assume you have already created your App within the Slack API page we will cover everything after that here. 1) Make sure you are logged in so you can access your App through the Slack API page. 2) Select your App: 3) From here you will want to select the "Incoming Webhooks" from underneath "Features": 4) Use the on/off toggle to the right of the title "Activate Incoming Webhooks" 5) Select the "Add New Webhook to Workspace" button to create a new URL that we will use for our webhook within Marketo: 6) Select where you want to post, either at a specific user or channel: 7) Now we are directed back to the page we were one, hit the copy button next to the Webhook URL to copy the URL as we will need it for a later step. 😎 Login to your Marketo instance and navigate to the Admin section. 9) Select Webhooks 10) Select Create Webhook. For the following fields assign the appropriate values: Webhook Name* = What ever you want to name Description = A description of what the webhook is used for URL* = Here is where we paste the URL we copied before Request Type* = POST Template = This is the information you want to send to your slack channel/user It should in the following format: payload={"text": "DEVELOPER SITE ALERT: {{lead.First Name:default=edit me}} {{lead.Company:default=edit me}}, {{lead.Email Address:default=no email address}}" } Request Encoding Token = None (You can change this if you want) Response Type = None 11) Click create and now we are ready to call our webhook and send necessary data to our users in Slack!

Issue You may experience this error when we create campaigns in SFDC using Marketo Campaign sync through a program. Solution The error that we are receiving indicates that the User Profile that Marketo uses to log into Salesforce doesn't have permissions inside of SFDC to create campaigns. To test this, log into Salesforce using the Marketo sync credentials and try to create an SFDC campaign. If you are unable to do so, then Marketo cannot create campaigns via the sync. You would need to work with your SFDC Admin to grant the Marketo sync user permission to create campaigns in SFDC. If still there is an error, please contact the Salesforce support team, since this error is coming from Salesforce.

Issue Depending on the marketing strategy, Google AdWords can be a significant portion of the marketing mix. With any significant expense, your marketing team will be asked to display a return on investment. Additionally, to help manage the spend, marketers want to compare keyword and ad display with success metrics and revenue results. Solution Keyword Capture Program - Setup Process The Marketo - Google AdWords integration provides deep insights into revenue generated by keyword and can help marketing teams get a much more granular view of revenue results than they would otherwise have without Marketo. Google AdWords spend can be tracked as its own Program Channel and leveraged within the Program Analyzer to make detailed assessments of performance. It provides very granular insight into performance through multiple dimensions and unique reports. Initial setup of Keyword tracking programs is straight-forward and simple to duplicate for each new Keyword. In addition, Marketo automatically connects to Google AdWords to report Customer-specific funnel conversion information by keyword and display ad. Template Program Setup: Add a field named PPC Source to the Lead Database – set field to write only if empty. Setup a Default AdWords Program in Marketo that contains a Keyword Token – this program will be cloned for future AdWords so that the steps below do not have to be repeated. Create a Program Token for Keyword. Configure the Smart List to Look for PPC Source containing the Keyword Token. Set the default flow to Update the Program Stages based on Activity Clicked AdWord (Default) Visited Site Filled Out Form Has Opportunity Set up a Smart Campaign within the Program to look for Closed/Won Opportunities and Activate the Campaign Cloning Process: Once the Default AdWords Program is setup it will only take a few minutes to add new PPC AdWords to Marketo. Clone the default AdWords Program. Update the Token to include the new PPC Keyword. Activate the Closed/Won Opportunity Smart Campaign. Capture Monthly Spend by Keyword Program within Marketo. Example Reports Once setup, reporting on Keywords within Marketo is now simple, easy, and more robust than other platforms. Here are five reports that will help you manage AdWords: A. Basic Keyword – Program Results Report B. Basic Keyword - Opportunity Results Report Fields include: Total Leads Count w/ No Opportunity Days No Opportunity Has Opportunity Has Opportunity % Days Until Opportunity Total Opportunity Amount Avg. Opportunity Amount Total Opportunity Won % Won Total Won Amount Days to Close Days in Sales Stage C. Program Analyzer Program Cost Cost per New Name Cost per Success First-touch Revenue Expected Multi-touch Revenue Expected Members New Names First-touch Pipeline Created Multi-touch Pipeline Created Success (New Names) Success (Total) % New Names D. RCE - Advanced Reporting on Keywords E. Funnel Conversion Data in Google AdWords - By Keyword & Display Ad The information displayed below is passed directly from Marketo into Google AdWords baed on the pre-configured Marketo-to-AdWords connector. Marketo does not currently pass along any information through the connector beyond what is shown in the screen below (Funnel Conversion Information).

Issue A lead has an Unsubscribe activity logged in their activity history, but they continue to receive emails after the Unsubscribe. Solution An Unsubscribe activity is logged when the lead clicks the system Unsubscribe link embedded in a Marketo email. However, if that link takes them to a Preference Center that allows them to select from multiple options, they may not choose the full unsubscribe option and may continue to receive selected emails. To confirm if this is the case, find the Unsubscribe activity in their activity log and double-click on the activity to open it. This will show you the choices they selected in the email preferences form. In the example below, the lead did not fully unsubscribe, they only chose to unsubscribe from specific content. Since they did not choose the global unsubscribe, they will continue to receive some emails.

Issue When you send an email that was cloned from a previous campaign and updated, the sent email shows the old content rather than the new content. Solution This can be caused by Dynamic Content in the email. If you clone an email with Dynamic Content but only update the default content, then the old content will be sent to leads who are not part of the default segmentation. Open the email in the editor and see what email elements are displayed in the Dynamic tab. Check the different segments in the editor and see which ones have the old content. You can update the dynamic content for each segment or simply make the content static, which will make the email use the default content for all leads.

Issue You want to send out an email to a group of people and break it up so that it sends in smaller batches over time. Solution To break up an email send over time, you can use a Smart Campaign with Choices and Wait steps in the flow. Example provided below. Choose the criteria you want to use to break up the send. In the example, we use the first letter of the last name. Use a Send Email flow step with a Choice defining your first group (Last Name starts with A-F) and select the email you want to send. For the rest of the leads, use a Default choice of "Do nothing." Add a Wait step. Repeat 1-3 for the each group, separating them with Wait steps.

Issue You have Visibility Rules enabled for a field on your form, but the field is not shown or hidden as expected based on the values in the other fields. Solution If you have enabled visibility rules for Field B but the field is not showing/hiding as expected when the correct value is chosen in Field A, one possibility could be the with the setup with the selected operator in the rule. When using visibility rules for Field B, the "is" operator will use and reference the displayed values of Field A, but "contains" will use the stored values. For example, let's say you have a visibility rule that should display the a particular field when 'Marketo Lead Management' is selected for the "Product Interest" field. The displayed value for the field (the one shown to the customer) may be "Marketo Leads Management" but the stored value for the field (the value written to the lead record) is "MLM". If you set up the visibility rule as "Product Interest is Marketo Leads Management", the rule will look at the Display Value and see a match. However, "Product Interest contains Marketo Leads Management" will look at the Stored Value, which is "MLM." It will not see the match, and the field will not be displayed.

Issue A lead skips the send email flow step, but processes through the other flow steps. In the results tab and in the lead activity log there is no mention of the email step. Example: Solution If your lead record is blocked from receiving emails, Marketo will not send an email to that lead. If an email is not sent, there will not be a record in the activity log for the lead record or in the results tab of the smart campaign, but the lead will still go through the other steps as normal.

Included in this Article: Overview Attributes Settings Firmographics Known Profiles Behavioral Device/Browser API Overview In the Web Personalization platform, you can set up segments to target your leads and site visitors into groups based on certain attributes. These attributes can be found in the segment editor. To navigate to the segment editor: Go to the Segments page Click the button to create a new segment, or the Edit button to edit an existing segment Attributes are found in the segment editor, arranged into categories such as Firmographics, Known Profiles, etc. These attributes and the values that they can take on are described below. To learn more about segments, visit RTP Segments - Marketo Docs Attributes Settings Firmographics Known Profiles Behavioral Device/Browser API

Included in this article Overview Troubleshooting To Try and https:// No Munchkin Tracking Code on Web Page No Visitors to the Web Page Yet Tips for Triggers and Filters Selectors Overview Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error. You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem. Troubleshooting To Try There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for. and Using or in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear. No Munchkin Tracking Code on Web Page If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs No Visitors to the Web Page Yet Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page. Check the page for visits. Make sure you have a munchkin installed on the page you are requesting. Create a test lead and visit the targeted page. Tips for Triggers and Filters Here are a couple of things that may help when using these filters and triggers. Selectors "Is" Selector In Triggers and Filters, if you use the selector "Is", (as in "the web page IS xyz.123.com") then the results returned will only be those from an exact URL match. If you want to also find results for the page xyz.123.com/sales, they won't be returned when using the "is" selector. NOTE: The "is" selector will return results in filters much faster since it is only looking for exact matches. "Contains" Selector If you use the selector of "contains", (as in "the web page contains xyz.123.com"), then this would return results for all pages that have xyz.123.com. Therefore, xyz.123.com/sales would match. The page xyz.123.com/products would match. All variations of that site xyz.123.com would match up. NOTE: The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.

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

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

Included in this Article: 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.

When deploying your RTP tag you may have noticed that there are four options in the Generate Tag window. The differences are subtle and technical, but below are the explanations of each version. RTP Tag - CDN, Asynchronous (Recommended) "Asynchronous" means that the page won't wait for the RTP script to load before loading other page elements In the case that RTP is not available, the request will timeout after 2 seconds This tag imports the RTP JavaScript from a network of servers called a Content Delivery Network (CDN). This assures higher availability rates and better loading performance RTP Tag - CDN, Synchronous (High Speed) "Synchronous" means that the RTP tag will load before any other elements on the page load Like the CDN, Asynchronous tag, this tag makes use of a CDN The "High Speed" does not actually mean the script loads faster, it only means that the page won't load before the RTP script completely loaded RTP Tag – Asynchronous Like the CDN, Asynchronous tag, the page loads other page elements while the tag is loading This tag Imports the RTP JavaScript directly from Marketo servers. In the case that RTP is not available the request will timeout after 2 seconds RTP Tag – Synchronous Like the CDN, Synchronous tag, the page will not load while other page elements are loading This tag Imports the RTP JavaScript directly from Marketo servers

Included in this Article: Overview Email Reports not Being Sent Check Report Preferences Fewer Leads than Expected Check Personal Regions Settings Cross-Domain Tracking Data Includes Own Company Overview All RTP users should be receiving a monthly and quarterly Summary Report. This email evaluates the performance of campaigns and recommended content and compares it to that of the previous month or quarter. Performance is based on click count and number of visitors converted to known leads, whether direct or assisted. Direct leads are visitors that clicked on a campaign or a piece of recommended content and filled out a form in the same visit. Assisted leads are visitors that clicked on a campaign or a piece of recommended content and filled out a form in a separate visit, up to 6 months in the future. If you would like to unsubscribe from the Summary Reports, see this article. Otherwise, several potential issues with Summary Reports are outlined below along with their potential solutions. Email Reports not Being Sent Check Spam Folder As a first step, try checking your spam folder. It's certainly possible that the email reports did not make it past your email client's spam filters. Check Report Preferences In your RTP settings, you will be able to enable or disable email reports. If you are expecting reports but not receiving them, it is possible the reports were disabled in your preferences. To check: Go to User Settings Check the Email Report settings at the bottom of the page Make sure to check the box for Summary Report and whether you would like a monthly or quarterly (or both) report. This page is also where you will be able to manage any other RTP email reports you wish to be subscribed to. Fewer Leads than Expected Check Personal Regions Settings Another page to check is the Personal Regions page. This page will allow you to display data in the Web Personalization platform and send email reports only related to the specified regions. In User Settings, click the Edit Regions button This should take you to the Set Personal Regions page: On this page, you will want to verify that any region you may have leads in is checked (marked as included in your Personal Regions). If regions that you have leads in are not included, the Web Personalization platform will not display data from that region or include it in the email reports. This means that if you have leads that are not included in your Personal Regions, their activity will not be included in Summary Reports. Cross-Domain Tracking If the visitor is shown a recommendation on one domain, but the recommended content is hosted on a different domain, two different sessions will be recorded. This divides the visit into two sessions: The click on the link to the recommended content, on the first domain The content itself and the form fill-out, on the second domain Because the click and the form fill are in two different sessions, the lead will be recorded as an Assisted Lead rather than a Direct Lead. This applies for both top-level domains (firstdomain.com and www.seconddomain.com) and sub-domains (pages.domain.com and www.domain.com/new_page). Cross-domain tracking will ultimately skew your metrics towards more Assisted Leads. To reduce the impact of this limitation, keep content recommendation and the content itself within the same domain when possible. Data Includes Own Company Clicks and visits from your own company can significantly skew your summary data, as your own employees may be visiting the company website on a daily basis. Because of this, it is important to exclude your own company from the organizations contributing to your Web Personalization data. To do this: Go to your Account Settings Scroll to the bottom of the page to find the Exclude IPs field In order to exclude your company's traffic from your data and reports, you will need to know the outbound IP address of your company's network. You should be able to obtain this information from your company's IT department. Once you have your company's outbound IP address, enter it into the Exclude IPs field and press

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.

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.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Top Blocklists - What You Need to Know

Missing Form Action Options in Older Forms

Facebook Authorization Error - Custom Audience

Creating Slack Notifications using Webhooks

SFDC Campaign Sync Error - Failed: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY: entity type cannot be inserted: Campaign

Google AdWords and Revenue Tracking through Marketo

Add/Remove Tout Users

Lead Continues to Receive Emails After Unsubscribe Activity is Logged

Cloned Email Showing New Content But Sending Old Content

How to Break up Email Sends Over Time

Form Visibility Rules not Displaying the Field

Lead Skips the Send Email Flow Step But Runs Through the Other Flow Steps

Web Personalization (RTP) - Segment Attributes

Troubleshooting Visited Web Page Filters/Triggers Giving Invalid URL Message and Red Squiggly Line

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

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

Troubleshooting Web Personalization (RTP) - RTP Tag

RTP - What are the Differences Between the RTP Tag Versions

Troubleshooting Web Personalization (RTP) - Summary Report Issues

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

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