Mike_Reynolds2

Want to gauge how many leads clicked through a link you have in your social media or other outlets? This can be done using URL Parameters at the end of the URLs you use. Basically, you just add a little bit of code to the end of the hyperlinked URL. When leads click through and arrive at your Landing Page, that code can be captured into a hidden Form field. Here’s how to do it.   Quick Overview of URL Parameters In the structure of a URL, there are two main parts. The first part is used for navigation, and the second part is used to pass data along. The two parts are separated by a question mark. For example, let’s look at this URL:   www.myawesomewebsite.com?URLParameter=ThisIsAParameter   The first part of the URL, “www.myawesomewebsite.com” is the main part of the URL used for navigation. The whole rest of the URL from the question mark on, “?URLParameter=ThisIsAParameter” is referred to as a querystring. It isn’t needed for navigation to the page specified, but can be used to pass the extra data you want to include.     The querystring contains the URL Parameters, which are used to push data into the hidden Form fields. In the querystring “?URLParameter=ThisIsAParameter” used here, “URLParameter” corresponds to the name of the parameter you use when designating the value for the hidden Form field, and “ThisIsAParameter” will be the value that is actually entered into that field. You can add additional values into additional other fields by adding those into the format of the URL separated by an ampersand like this:   www.myawesomewebsite.com?URLParameter=ThisIsAParameter&URLParameter2=ThisIsValue2&URLParameter3=ThisIsValue3   In this example, you’ve got the same initial value being pushed into the first hidden field, but now two more hidden fields will store the next two values as well. The name of the parameter for the second hidden field would be “URLParameter2” and the value put into it would be “ThisIsValue2”. The third hidden field parameter name would be “URLParameter3” and the value put into this field would be “ThisIsValue3”.   Applying This to Social Media Use So, how does this let you track leads coming from each of your social media sources? Well, in setting up your different promotional channels, when adding the hyperlink, you can customize the URL parameter for each channel so that the values passed will input the information specific to where they came from. The parameter values will change from one social media outlet to the next, but the structure and format will stay the same.   Let’s use the social media sources of Twitter, LinkedIn and Facebook as examples. Since you’re looking to identify the source of these leads, you’d likely want to name your parameter as “Source” so that it’s easily identifiable. Using the same base URL, let’s see how you’d structure the URLs. For hyperlinks placed on Twitter: www.myawesomewebsite.com?Source=twitter For hyperlinks placed on LinkedIn: www.myawesomewebsite.com?Source=linkedin For hyperlinks placed on Facebook: www.myawesomewebsite.com?Source=facebook   When leads fill out the form on your landing page, the Source field will then tell you exactly where they came from! The best part, this is completely customizable and scalable. You can add more parameters and hidden fields to capture additional information like what campaign it is for.   Documentation How to make form fields hidden: https://docs.marketo.com/display/public/DOCS/Set+a+Form+Field+as+Hidden How to define hidden form field value: https://docs.marketo.com/display/public/DOCS/Set+a+Hidden+Form+Field+Value (Look for the section on URL Parameters in particular) Using the URL builder to generate the URLs you’ll be using: https://docs.marketo.com/display/public/DOCS/Using+the+URL+Builder     ... View more

Overview   After updating or changing an RTP campaign, the natural thing to want to do is test it out and see it live on your website. However, many times your changes just don't show up even after relaunching the campaign.     How to See Your Changes:   1. It can take up to 5 minutes for changes to your campaign to be published after relaunching an edited campaign.   2. If you do not see the new version of your campaign after 5 minutes, you may need to clear your browser cache and cookies in order to see the new changes.       ... View more

Included in this article   Overview Troubleshooting Checklist: Verify that you are using the most updated RTP tag version on your website.   Verify that the RTP tag is the first script in the header of your pages – between the <head> </head> tags. Are you using a tag Manager? Check the campaign itself.   Overview Sometimes you may experience latency when your RTP campaign displays on your webpage and pages appear to load slowly. The following checklist will help you find issues that may be contributing to campaign latency.     Troubleshooting Checklist:   Verify that you are using the most updated RTP tag version on your website. Go to your website > Right click on the page and select "View Page Source" > Search for 'RTP' to find your tag. Verify that this tag matches the code provided for your instance. You can find more information on finding your RTP tag here.   Verify that the RTP tag is the first script in the header of your pages – between the <head> </head> tags. If the tag is not in the recommended placement, follow the documentation on deploying the RTP tag. Moving the tag to the recommended placement will resolve most latency issues.   Are you using a tag Manager? Using a tag manager for your RTP tag is known to affect campaign performance. If you are experiencing campaign latency while loading the RTP tag via a tag manager, we recommend moving the tag into the code itself. You can find more information on deploying the RTP tag here.   Check the campaign itself. Campaign customizations that load additional content can contribute to increased RTP campaign loading times. For example, a campaign with an embedded Marketo form may experience a small delay as the campaign loads the form from your Marketo instance, so it's one code loading another script, which then loads another. That can cause latency while the browser catches up, so the simpler you can make the code, the better.     ... View more

Included in this article   Overview: Root Causes and Solutions: The image is too large and it takes a long time for it to load The image dimensions are not defined in the campaign editor   Overview: In some cases when creating a dialog box campaign that includes only an image, the dialog box won't render properly on the page. This might look like below:     Root Causes and Solutions: The image is too large and it takes a long time for it to load      Solutions: Wait to see if eventually the image loads properly. In this case, you will want to use an image that is a smaller file size.   The image dimensions are not defined in the campaign editor      The dialog box doesn't have any indication for what its height should be (auto-height is enabled by default).      Solutions: Select the image in the editor and click 'Edit Image' button Go to the Appearance tab and verify that the dimensions are defined If the dimensions are not set, manually set them or re-insert the image (this will automatically configure the image's original dimensions) ... View more

Included in this article   Overview The Issue The Explanation   Overview Sometimes you'll see an organization show up as "ISP - Anonymous - Proxy" in your visitors list in RTP.   The Issue RTP is a powerful product with an immense database, but not every ISP can be found.  When we receive a visit from an ISP we can't identify, instead of omitting them from our results, we use the name "ISP - Anonymous - Proxy" and set the location to "United States.     The Explanation Pretty much any free Wifi signal you find like at a library or coffee shop will be listed as an Internet Service Provider (ISP). The admins for that ISP service can configure their network in any way they would like, including whether they allow for identification of their network. If there is no data provided, there's nothing for RTP or any other service to gather. In that case, that's when you'd see the "ISP - Anonymous - Proxy" listing for a visitor in RTP. ... View more

Included in this article   Overview Filter Options Overview When leads click a link in your Marketo email and then visit your website, wouldn't you like to continue delivering the same targeted messaging on your website that you started with the email?  You can do this with a Segment using the Marketo Email Campaign filter. This filter targets leads who are members of a particular Program or Smart Campaign inside of Marketo.   Filter Options Located under the "Known Leads" group of filters, the Marketo Email Campaign filter gives you the choice of targeting Marketo Programs (Program Name) or Smart Campaigns (Campaign Name). Click the plus sign to add another option, or click the X on the right to remove one. The filter allows you to add "And/Or" logic between the Campaigns and Programs selected if using more than one.       Additional information about RTP Segments can be found here: RTP Segments - Marketo Docs - Product Docs ... View more

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

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

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

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

Adding a div id to your website involves modifying the underlying HTML code of the site. This is a task that needs to be handled by your web team.   Before your developers can add a div id tag, they will need to know the name of the corresponding Zone id of the RTP campaign.        Go to Campaigns page             Edit the existing campaign          Find the Zone id in the In Zone tab of the campaign editor     Your web team will be able to add the div ids if you provide the Zone id and point out the regions of the website that you wish to be used for your campaign. We recommend to provide your developers with a PowerPoint including screenshots of your website, marking the areas that should be used by the campaign.   A developer will be able to add the div ids by editing the HTML and simply including id="Zone_id" into the desired div tags, replacing Zone_id with the given Zone id. ... View more

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

Included in this article   Overview Embedding Videos into RTP Campaigns Overview RTP will allow you to embed a form into a campaign, but what about videos? That can be done too!   Embedding Videos into RTP Campaigns To embed videos in your RTP Campaign, you will first need to get the embed code or iFrame code information for the video service you are using.  We have links to instructions for some common video players below.   YouTube Vimeo Wistia Kaltura   Once you have the necessary code, open the RTP Campaign Editor, click on the HTML icon to open the HTML Source Editor, and paste the embed code into the campaign.   ... View more

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

Included in this article   Overview 1. Make sure the dialog box dimensions are set: 2. Make sure your image also has dimensions properly set: 3. Access the HTML for the campaign: 4. Insert the following CSS into the campaign's HTML: 5.Save your changes and preview the campaign. There should be no more scroll bars.   Overview Have you ever had an RTP Dialog box campaign that ended up with scroll bars around the image? This doc will go show you the steps to remove those unwanted scroll bars   1. Make sure the dialog box dimensions are set:       2. Make sure your image also has dimensions properly set:       3. Access the HTML for the campaign:   4. Insert the following CSS into the campaign's HTML:   <style> #trwDialog{     overflow-x: hidden;     overflow-y: hidden; } </style>     5.Save your changes and preview the campaign. There should be no more scroll bars. ... View more

Overview Generally, when running an ad such as a banner or pay-per-click ad, marketers will add URL parameters to their links that identify key features such as the campaign's type, content, and source. So if your campaign "ad_campaign=123" needed to be identified, you could put that "ad_campaign=123" into a URL parameter to track leads that interacted with that specific ad.   You can also leverage these URL parameters inside of RTP to show campaigns tailored and targeted towards these specific leads.     Targeting the Leads To identify these leads, you would create a Segment using the Include Pages filter and searching for this specific URL parameter within the URL. For example, if you had an ad with a link to  "http://www.yourpage.com/page.html?ad_campaign=123" you could use the following Include Pages filter to target your campaign to those leads. Be sure to include asterisks before and after the parameter - these wildcards will allow you specify the parameter value inside the URL rather than the exact URL itself.   ... View more

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

Overview:   In some cases you may want your RTP campaign to display only on your site's hompage. This article will show you how to do just that.        Navigate to your Campaigns page          Edit the existing campaign          Set the "Target URL" to your homepage       This will set the campaign to appear on your homepage. If you are hoping to include the campaign on other pages throughout your website, you must check the "Any Page" field below the Target URL. ... View more

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

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.     ... View more

Included in this article   Overview Testing Overview One of the most important steps in setting up new segments in RTP is testing it to make sure that it's working properly. This article will show how you can test known lead targeting in RTP.     Testing 1. Fill out a Marketo form on your webiste using a brand new email address that doesn't exist in this Marketo instance yet. 2. Go to the Lead Database and locate the new lead 3. Create a segment in RTP that targets known leads with the new email address: 4. Wait 5-10 minutes and refresh the webpage 5. Check if you matched the segment. You can check this by finding the lead under "Leads" and then select the lead to see what Segments it matches on the right:       ... View more

Article Text Included in this article   Included in this article Overview Troubleshooting Steps   Overview The Content Recommendation Engine Bar is a great tool to get promoted content to your web visitors. However, there are times when you only want it to show up on certain pages, or you just want to exclude some specific pages where it won't be allowed to show up. You can make these configuration changes with the documentation here: Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages. However, what happens if you set it up and it still displays in places where it shouldn't? This doc will show you how to address this trouble.   Troubleshooting Steps 1. In RTP, go to 'Account Settings' 2. Under the 'Domain Configuration', locate the 'Recommendation Engine' section. 3. Select whether  you want to 'Include' or 'Exclude.'     4. Check the 'Display (URL)' configurations to confirm they are correct.           ... View more

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. ... View more

Included in this Article: Tracking Clicks Potential Issues Segment Matches Few or No Visitors Segment Numbers Don't Match Google Analytics   Tracking Clicks In order to better track how many people are clicking the content in the Recommendation Engine, you may wish to create a segment called "Recommended Assets" and include "*rcmd*" in the Specific Pages parameter.      Go to the Segments page             Create a new segment          Drag the Include Pages field into the editor and include *rcmd*     Recommended content will have "rcmd" in the URL. With this filter, the segment will only include website visits with "rcmd" somewhere in the URL, meaning it will include all visits to recommended pages.   Potential Issues   Segment Matches Few or No Visitors After making this change, you may see that the segment doesn't match anything or only shows a few visitors.  In that case, verify that your Asset Discovery is working   Segment Numbers Don't Match Google Analytics The numbers you see in the segment may not match the numbers you see in Google Analytics. Unlike Google Analytics, RTP segments count the number of visitors that matched the defined parameters, whereas the 'Site Content' report in GA counts the number of times the pages were viewed by visitors.  This means that if the same visitor clicks on more than one piece of recommended content, in RTP only one segment match will be recorded whereas GA will record 2 page views. ... View more

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

Included in this article   Overview Troubleshooting Steps Verify Global Settings Check for CRE Excluded URLs Verify Content Being Recommended Make Sure the Page Has the RTP Tag Running Clear Your Browser's Cache and Cookies Overview The Content Recommendation Engine allows content assets to be promoted to visitors on your website. But what happens if it stops working? This doc will show you the common things to check and troubleshooting steps to try to get it working again.     Troubleshooting Steps   Verify Global Settings The CRE can be switched on or off for your entire RTP instance whenever you want. It's possible that another user may have switched it off and not turned it back on again (it happens more often than you'd think). To enable or disable the CRE globally, go to the Account Settings page and look for the Recommendation toggle switch. Full directions can be found here.     Check for CRE Excluded URLs You have the ability to prevent the CRE from being added onto specific pages. If you have URLs excluded from allowing the CRE to be displayed, that would cause the CRE to no longer display on those pages. Many times the exclusion can be set and then forgotten, or set by a different user on accident. Directions on how to set up the exclusions can be found here Web Personalization (RTP) - How To Exclude or Include the CRE on Specific Pages     Verify Content Being Recommended Content assets can be switched on or off to designate whether that content should be included in the CRE recommendations or not. Each piece of content can be enabled or disabled individually, but if you don't have any enabled at all, there's nothing for the CRE bar to recommend, so it won't even show up on the page.     To check whether content is enabled, from the menu, select Recommendations     In the Content Recommendations page, look for the Recommendations column. This will list out all pieces of content you have in RTP and display whether they are enabled or disabled. The Red box means it is turned Off and is disabled. The Green circle means it is turned On and is enabled.     Make Sure the Page Has the RTP Tag Running The CRE is a feature of RTP, so if the RTP script tag isn't running on the page, there's no way for the CRE to work. The RTP tag can be implemented in many different ways besides by having it directly in the page's HTML, like having it in a tag manager. These other implementation methods can cause problems so be sure to follow the directions in the documentation here when setting it up: RTP Tag Implementation - Marketo Docs - Product Docs   If you know for sure that the RTP tag is on the page, here's documentation on how to troubleshoot what could be keeping it from loading properly: Troubleshooting Web Personalization (RTP) - RTP Tag   Clear Your Browser's Cache and Cookies Web browsers store cached data from websites, which can frequently cause old versions of webpages to continue showing even if a different newer version of the page should be loading instead. Try clearing both cache and cookies in your browser and then testing the page again. You can also test using a different browser.   ... View more

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. ... View more

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. ... View more

If no data is being sent from RTP to Google Analytics, make sure that the segment in question is linked to GA        Go to the Segments page          Edit the segment in question          Make sure Send segment to web analytics is checked on     Without this field checked, no data will be sent from RTP to GA regarding that segment.   To validate that RTP is sending data to your GA account, first log in to your GA account, and make sure the segment data is being populated in GA.        Navigate to Reporting > Behavior > Events > Top Events > Segments (Event Category) > Event Actions       If you find that some, but not all, of the data is being transferred from RTP to GA, visit this article to learn why there might be discrepancies. ... View more

Included in this article: Overview Missing or Extra Headers Issues with Quotes Invalid Characters Invalid Country or State Names   Overview   The Named Accounts feature is a way to target your RTP Campaigns to specific Accounts in a Segment. It's a powerful tool for targeting specific organizations, but you may encounter errors when uploading the list of Accounts you wish to target. This doc will go over over the most common problems experienced when trying to upload a CSV file to a Named Accounts list. To learn how to upload a Named Accounts list, follow this article.     Missing or Extra Headers   The first line of your CSV file should be, in order: Name, Domain, Country, State. Make sure there are no extra columns or white spaces at the end of the line. See the screenshot below for an example of how to format your headers     Issues with Quotes   Occasionally Excel will use curly quotes, which look like these: “ ”. However, curly quotes are not recognized by the uploader, instead the uploader will recognize straight quotes like these: " ". Any curly quotes will need to be replaced by straight quotes to resolve any uploading issues. To do this:   First, make sure your file is saved as a CSV file (.csv) and not an excel file (.xlsx) Right click on the file to open the CSV file using a text editor (ex. Notepad, TextEdit, etc) Find and replace both opening (“) and closing (”) curly quotes with a regular quote (")   Invalid Characters   This error is caused when there is an invalid character in the CSV file that you are trying to import.  This is particularly common in CSV files using non-English characters.  To rectify this, make sure your CSV file is UTF-8 encoded.  By default, Excel encodes characters in ANSI format, so if your file has non-English characters in it, you will need to convert it to UTF-8.  You can do this in Notepad or similar text editors using the following steps:   Open the CSV file in the text editor and click "Save As" Save as type: All Files (Make sure you include the .csv file extension in the file name) Change the Encoding to UTF-8       Invalid Country or State Names   If the location columns are in use (they are optional), check to verify that the countries and states are input in the correct way:   Country names should be either the full country name, or its two digit country code. Ex: United States or US State names should just be their two digit state code. Ex: CA, NY, OR Make sure that only US states are included in the 'State' column. Named Account lists do not support other countries' states or provinces. ... View more