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

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

Marketo Support's Mission is: To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success. Areas of Responsibility: Technical Support Engineers (TSEs) are your initial point of contact for any technical questions or concerns. TSEs are responsible for troubleshooting issues within your Marketo instance and common include: My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community Our TSEs are not web developers and as a result they are unable to troubleshoot most types of custom coding (ie. HTML, JavaScript, XML, etc.). Our support team is able to help with the following types of non-custom code: Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API Our TSEs are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience. Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented. Response Time Our TSEs are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services. We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.

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, pdfs, blog posts, press releases, white papers, etc.) on a website/domain. Once discovered, you can see how your content is performing and 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 use this feature optimally (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, it will add to the tracking and views of those discovered 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 this visitor has seen in the 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 involves less prep work for you. However, you still need to review the discovered content and 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 is 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 would 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

FAQs Included in this Article: Overview How clicks on Web Personalization assets and campaigns are recorded in the activity log How often does Web Personalization sync with Marketo Is it possible to sync multiple Marketo instances with one Web Personalization account What custom field types are supported What is a unique visitor in Web Personalization What is the time zone setting on the Marketo Web Personalization server that is used to count impressions Overview Your Marketo instance and your Web Personalization instance end up interacting and transferring data in many different ways. Below are answers to some of the most frequently asked questions about Web Personalization's integration with the Marketo instance. How clicks on Web Personalization assets and campaigns are recorded in the activity log These activities are recorded as the 'Data Value Change’ Activity Type. The fields 'Web Personalization Assets’ and 'Web Personalization Campaigns’ are changing all the time to include all the assets and campaigns the lead clicked on. How often does Web Personalization sync with Marketo Lead data gets synced every 5 minutes Data regarding programs and smart campaigns is synced every 15 minutes Is it possible to sync multiple Marketo instances with one Web Personalization account Currently, there is no way to do this. Each Web Personalization account will be tied to one account in Marketo and vice versa. What custom field types are supported All field types are supported except for Formula fields. For more information on custom field types, visit Custom Field Type Glossary - Marketo Docs - Product Docs What is a unique visitor in Web Personalization A unique visitor refers to an individual that has visited your web page, regardless of how often they visit. For example, when an individual goes to your web page on Tuesday, then again on Wednesday, this is recorded as two visits from one unique visitor. What is the time zone setting on the Marketo Web Personalization server that is used to count impressions The server is set to record data in U.S. Central Time (CT), but the time stamps you will see in the UI are based on your local time zone. Very rarely, a visitor might show up twice if they visited on separate days according to CT but not your time zone.

Issue You are experiencing slow processing of campaigns, smart lists, and reports. Solution There are three key components that can slow down an instance: Number of trigger campaigns: Trigger campaigns are always on, always listening. If there are 50 campaigns triggering at the same time, all the 50 triggers will be in queue, slowing down your processing and routing inside Marketo. Solution: Reduce the number of Triggers. Convert some of the triggers to batches: Batches also run all the flow steps for every lead at once, instead of serially, which reduces total processing time. Complexity of smart lists: The more complex a smart list, the harder it is for the system to figure it out, which increases backend processing and even creates campaign failures from timeouts. Solution: Reduce the number of nested smart lists called in a smart list. Whenever you ask Marketo to call another Smart List, it has to wait until all of the other smart lists finish, before putting together the final counts. Instead of Marketo looking for the list and running it, just put the filters in the trigger itself. Volume of Leads: With regular cleaning and good systems design, it is fairly easy to keep your system running fast. Reduce the number of leads that can flow through with filters. Clean up the inactive leads at regular intervals.

Included in this Article: Overview Creating Custom Fields Dynamic Updates Set Up Custom Fields in RTP Filter by Custom Fields Overview Unfortunately RTP does not support the option to use Lead Database segmentations as segments in RTP. However, it is still possible with a bit of a workaround. Essentially, you will want to create custom fields for each segmentation, dynamically update them using smart campaigns, and filter by these custom fields in RTP. Below we will describe the steps you will need to take to implement this. Creating Custom Fields To start off, you will have to make a custom field in My Marketo for each segmentation you wish to use in RTP. Follow the steps in this article to get the custom fields set up in My Marketo. Make sure to select Boolean in the Type field. Dynamic Updates Next, you will need to assign these custom fields to those matching their respective segmentations. To do so, we will create a smart campaign, which will also update the list as more leads begin to match the segmentation. In My Marketo, visit the Marketing Activities page and create a new Smart Campaign In the Smart List tab, choose the filter for your desired segmentation, and the Segment Changes trigger for the same segmentation The filter will include all of the existing members of the segmentation, and the trigger will include any members that qualify for the segmentation in the future. Next, In the Flow tab, select the Change Data Value action, click Add Choice, and format the action to change your custom field to true when the lead qualifies for your desired segment, and false otherwise It is important to have both cases, for your lead matching the segmentation and for not matching, because leads can both qualify or be disqualified for segmentations at any point in time. Finally, under the Schedule tab, edit the Smart Campaign Settings so this will apply every time, and Activate the campaign Set Up Custom Fields in RTP Once you have set up your custom fields in My Marketo, you will also have to set up this field to display in RTP: Go to your Account Settings and navigate to the Database tab Select your custom fields in the drop down menu at the bottom of the page, then click Filter by Custom Fields Finally, once you've set up the custom field in My Marketo and in RTP, you can use the custom field to target the leads that qualify for your segmentation in My Marketo. To do so: Go to the Segments page and create a new segment Lastly, use the Database filter, select your custom field, and choose either true or false depending on if you want to target those in or out of the segmentation There you have it! You can now use your segmentations in My Marketo to target your audience in RTP campaigns.

Issue Users for your Marketo instance are unable to log into the instance. Solution Check your landing page URLs and email links. If these are also unavailable, your Marketo instance may have been shut off. Marketo Support can confirm whether your instance has been deactivated, but are not able to reactivate it. In this situation, please contact your Marketo Account Representative to discuss the status of the instance and regaining access.

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.

Knowledgebase

Maintaining a Directory of Leads Bouncing Emails

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

Marketo Support Policies

How Auto Content Discovery Works in Predictive Content

Web Personalization - Marketo Integration Questions

Marketo Running Slow

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

Unable to Access Marketo Instance

Troubleshooting Web Personalization (RTP) - Content Recommendation Engine Bar shows up on all or excluded pages