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

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

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

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

Included in this Article Overview Troubleshooting Workflow Possible Outcomes Overview Sometimes your RTP Campaigns have problems and stop working suddenly. This can obviously cause trouble for your marketing efforts, so this doc will show you steps on how to troubleshoot those issues. Troubleshooting Workflow 1. Check the campaign's last impression time stamp a. Go to Campaigns page b. Locate the relevant campaign and click the Impressions link to see people that viewed the RTP campaign (make sure the time scope corresponds to the right dates when the campaign was active) 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

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

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

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

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

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

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

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

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

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

Article Text Image: Step Flow for Predictive Content for Web and Email What is Auto Content Discovery? This post explains the first part of the flow image above: discovering, mapping and tracking your content assets. Content Discovery is used in the Predictive Content app to auto-discover all the content assets (videos, pdf, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you have the ability to see how your content is performing and to decide which pieces of content should be prepared, approved and enabled for the Predictive Content outcomes on web (either in the recommendation bar or rich media) and email. Setting up Predictive Content and Content Discovery See Set Up Docs: http://docs.marketo.com/display/public/DOCS/Getting+Started+with+Predictive+Content Steps RTP Javascript tag is installed on all your web pages (Note: RTP is now called Web Personalization) Set Asset Discovery to On Asset Discovery auto-discovers extensions (PDFs, PPT, MP4, OFF, WEBM) and a click/view on embedded videos (Youtube, Vimeo, Wistia) Create URL Patterns Setting URL patterns auto-discovers content when a web visitor clicks on the HTML web page relevant to the content pattern The URL syntax pattern determines your ability to optimally use this feature (e.g., to create a pattern for press releases, your press releases should all be stored on a page identified as www.yoursite.com/press-releases/*). How is content auto-discovered? The content discovery technology uses an event listener that runs on every web page (where the RTP Javascript tag is installed) and waits for a web visitor to click on a URL link or arrive directly on that web page in a browser. If that link includes an extension (PDF, ppt, embedded video) or matches the URL pattern defined, then it will be discovered and added to the All Content page in the Predictive Content app. Only content pieces that a web visitor interacted with (clicked on or viewed) once the RTP Javascript tag has been installed are discovered via Content Discovery. If the content is already discovered, then it will add to the tracking and views of those discovered content pieces. You can also manually add new content to be listed and tracked in the All Content page. Image: All Content Page in the Predictive Content app displaying and tracking all discovered content What data is discovered? Visitor Data (Used for Analytics + Predictive Algorithm) Pages Viewed - number of page views by the user in the session Visit Count for Web Visitor Last Content URL Seen Last 5 Content Assets clicked via Predictive Content that have been seen by this visitor in last 90 days Last Web Campaigns Seen - 10 last campaigns per session (within the last 5 sessions) Inferred Organization Inferred, Industry, Size, Revenue Inferred Country, State, City Search Term Content Data Extensions Video (Youtube, Vimeo, Wistia) Video Name Video URL Video Image URL PDF PDF Name PDF URL URL Patterns (HTML pages) Found via metadata of the HTML page Content Name Content URL Content Image URL Content Description What data is auto-populated during the auto-discovery phase? Based on the content data we discover, the aim is to populate as much of the Predictive Content as possible, making it quicker, easier and involving less prep work for you. However, you do still need to review the discovered content, then approve and enable it for the Predictive Source (Email, Rich Media, Recommendation Bar). Assuming we discover an HTML page defined in URL patterns, this HTML content piece will be populated in the following fields in Predictive Content: Predictive Content Fields Auto-Populated Value Notes Content Name (Content Name) Unique Value Content URL (Content URL) The URL is consistent for all sources (email, bar, rich media) Categories Video OR Category Name from URL Pattern If Video discovered, the category is populated as Video. Category populated from defined URL Pattern. e.g. Marketo.com/blog = Blog all discovered content based on this URL will receive Blog as a category Category is consistent for all sources (email, bar, rich media) Content Title (Content Name) Email Title (Content Name) Email URL (Content URL) Email Image URL (Content Image URL) Email Button Label Read More Not Auto-populated. Default is "Read More". Rich Media Title (Content Name) Rich Media URL (Content URL) Rich Media Image URL (Content Image URL) Rich Media Description (Content Description) Bar Title (Content Name) Bar URL (Content URL) Image: Example of Populating Metadata for HTML content into Predictive Content

Article Text Using URL parameters are an important way to organize your web analytics and tracking. With Marketo Web Personalization, when a web visitor clicks on a personalized Web Campaign we add a parameter to the URL. This parameter is "?iesrc=ctr". Having this parameter allows you to report on your web analytics to see and compare all the clicks on Web Personalization campaigns and overall performance of your personalization strategy. The Marketo Predictive Content application also includes a URL parameter every time a visitor clicks on predictive content (from the bar, rich media or email). The URL parameter used here is "?iesrc=rcmd". You can also add your own UTM parameters to the URL link you have in your Web Personalization Campaign or your Predictive Content piece. The most common URL parameter tools we see customers using is the Google Analytics tool. In their words "This tool allows you to easily add campaign parameters to URLs so you can track Custom Campaigns in Google Analytics. See: Campaign URL Builder — Google Analytics Demos & Tools". Make sure to follow the best practices: Best Practices for creating Custom Campaigns - Analytics Help

Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools. Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows: Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2 Step 3 Step 4 If you experience issues, please email marketocares@marketo.com

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

Issue When a piece of predictive content is approved the following error appears: "Action failed. Please contact support. Error code:24 Error message: Invalid email title Error message: internal error, reported to support." Solution Change the title of the content to less than 48 characters. This error indicates that the title for the content is too long. The maximum number of characters for a title in content AI is 48 characters.

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

Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues. Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers. Chrome Clear cache and cookies - Computer - Google Account Help FireFox How to clear the Firefox cache | Firefox Help Internet Explorer https://support.microsoft.com/en-us/help/278835/how-to-delete-cookie-files-in-internet-explorer Microsoft Edge Microsoft Edge, browsing data, and privacy – Microsoft privacy

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

Troubleshooting - Web Personalization (RTP) Content Recommendation Engine Not Working

Troubleshooting Web Personalization (RTP) Content Recommendations Appearing Across Domains

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

Troubleshooting - Web Personalization (RTP) Campaigns suddenly stopped working

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

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

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

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

Web Personalization (RTP) - Google Analytics FAQ

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

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

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

Troubleshooting Web Personalization (RTP) - RTP Tag

How Auto Content Discovery Works in Predictive Content

URL Parameters with Web Personalization and Predictive Content

Support Portal Access Issues

Web Personalization/ContentAI - Content Discovery Date

ContentAI - Error 24

Configuring Additional Domains or Subdomains in Web Personalization (RTP)

How to Clear Cache and Cookies