Knowledgebase

Sort by:
Article Text Included in this Article: Overview Check if Data is Being Transferred to GA Troubleshooting Steps Check if GA is Enabled Verify both RTP and GA tags are loading on your website Check GoogleAnalyticsObject customizations   Overview Data from RTP can be linked to Google Analytics (GA) for further analysis. Below we show you how to check if data is being transferred and a few troubleshooting steps if you find that it isn't.   Check if Data is Being Transferred to GA        Log in to GA and navigate to Reporting > Behavior > Events > Top Events You should find events with either the category "Insighterra" or "RTP". If not, another place to check for incoming RTP data is in the Custom Variables tab.      Navigate to Reporting > Audience > Custom > Custom Variables If you use custom variables, you should see RTP data populated here.   If you expected to see populated data in either of these two areas but you aren't seeing any, then you are having issues with your RTP-GA integration. Check out the steps below for some troubleshooting tips.     Troubleshooting Steps If you have confirmed that there is no data flowing to GA, there are a few troubleshooting steps which you can take.   Check if GA is Enabled        Go to Account Settings       At the bottom of the page, verify that Google Analytics or Google Universal Analytics is enabled. Only one of these integrations should be enabled at a time - if both are, disable one of them.   If neither is enabled, go ahead and enable one of them. Follow this article to learn more about enabling and integrating GA with RTP.     Verify both RTP and GA tags are loading on y our website   To verify this, you will need to navigate to your web page and open the browser's developer tools window. Follow this link to learn what the developer tools window is and how to get there on different browsers and operating systems.        Navigate to your browser's developer tools          Click the Network tab and search for "analytics.js" and "rtp.js"   If both "analytics.js" and "rtp.js" show up in your search, then both RTP and GA are loading on your website. If one or both are missing, go through these steps to add an RTP tag to your website, and these steps to add a GA tag.       Check GoogleAnalyticsObject customizations   If you're using Google Universal Analytics, check if customizations have been made to the GoogleAnalyticsObject . Read this article to learn more about this object and its possible customizations. To check for customizations, follow the steps below:        Click on the Console tab in the developer tools and run GoogleAnalyticsObject          Type "GoogleAnalyticsObject" and hit Enter to check the object's type     If the object's name is "ga", then you are in the clear. If not, unfortunately we do not currently support the customization.    
View full article
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 V ariables (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:  
View full article
Article Text 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 full article
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.
View full article
Article Text 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 full article
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.    
View full article
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.
View full article
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 Currentl y 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 full article
Article Text 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 full article
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
View full article
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.  
View full article
Article Text 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 full article
Article Text 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 full article
Article Text Image: Step Flow for Predictive Content for Web and Email What are Content URL Patterns? This post explains the first part of the flow image above: the discovery and tracking of content for the Predictive Content app. During the setup phase, the marketer defines their content URL patterns (See Create Content Patterns for more information), in order for Marketo to discover HTML content (e.g., blog posts, press release, news articles) across a domain. Setting URL patterns allows Marketo to auto-discover content when a web visitor clicks on the HTML web page within the content pattern. This content is then added to the All Content page in Predictive Content. Setting up URL Patterns Go to User Profile > Content Settings > URL Patterns. (For more information, see the Getting Started doc: Getting Started with Predictive Content) Image: URL Patterns Page   Rules for Content URL Patterns Use of a wildcard (*) is permitted throughout the expression. e.g., domain.com/*  or  domain.com/*blog* It's recommended to use /* at end of the expression to continue pattern discovery. e.g., domain.com/blog/* to discover all your blog posts in the blog folder Content Patterns are not case sensitive. URL Pattern: "domain.com/Blog/*" will discover all HTML pages on "domain.com/Blog" and "domain.com/blog" Parameters in URLs are not discovered. Auto-content discovery removes the URL parameters in order to avoid discovering the same content URL multiple time with different parameters.   Examples of Content URL Patterns   Domain URL Pattern Type Result domain.com blog/* Pattern Discovers all your content that matches the pattern domain.com/blog/. Example: domain.com/blog/5-top-tricks domain.com/blog/2017/new-year-solutions domain.com/Blog/3-best-recipes domain.com article/2017/* Pattern Discovers all your content that matches the pattern domain.com/article/2017/ Example: domain.com/article/2017/5-top-tricks domain.com *datasheets* Contains Discovers any URL that contains the word "datasheets" Example: domain.com/datasheets/5-top-tricks domain.com/blog/5-top-datasheets domain.com press-release Exact Only one HTML page is discovered: Example: domain.com/press-release domain.com   Exact If the domain is selected and the URL expression left empty, the URL pattern will discover only the home page Example: domain.com sub.domain.com blog/* Pattern Discovers all your html pages in the folder blog only on the sub domain sub.domain.com
View full article
  Welcome to Marketo Support This guide provides individual links that covers the following topics: Marketo Support Policies Service Level Agreement How to Contact Marketo Support How to Submit a Case Tips on Effective Case Submission Managing Authorized Support Contacts (Support Admins) Managing Your Cases How to Escalate    
View full article
  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 questions or concerns. TSEs are responsible for troubleshoot issues within your Marketo instance. Common areas within a Marketo instances which TSEs will assist with are:   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 technical support engineers 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 Technical Support Engineers 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.
View full article
Article Text 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 full article
  This is a article attached image Upon signing a contract with Marketo you are provisioned a Marketo instance and a Support Service. There are four different types of Support Services which are available to meet different customer support needs: Online (Legacy) Business  or PREMIER SUPPORT BUSINESS (Legacy) Premier or PREMIER SUPPORT ENTERPRISE (Legacy) Elite or PREMIER SUPPORT ELITE Each Support Service has a different Service Level Target (SLT). An SLT is the amount of time Marketo Support targets to make first contact with you after a support case has been submitted. SLTs differ for each Support Service and priority level. Priority levels range from Priority P1 to Priority P4. Here are the SLTs and priority levels for each Support Service:   Priority Online (Legacy) Business PREMIER SUPPORT BUSINESS (Legacy) Premier PREMIER SUPPORT ENTERPRISE (Legacy) Elite PREMIER SUPPORT ELITE P1 1 hour 1 hour 1 hour 30 minutes 30 minutes 30 minutes 15 minutes P2 4 hours 3 hours 2 hours 2 hours 1 hour 2 hours 30 minutes P3 6 hours 5 hours 4 hours 4 hours 2 hours 2 hours 1 hour P4 3 days 1 day 1 day 1 day 1 day 1 day 1 day   Here are the descriptions for each priority level: Priority Description P1 Mission Critical:  Core business function down or potential loss of mission critical data P2 Urgent:  Major feature or workflow is not functioning. Mission critical workflow and majority of user community is not blocked P3 Important:  Normal usability or task completion is impacted but functional, or workaround is available P4 Minor:  Minor issue requiring a correction. Normal workflow is not impacted   Find more information About Support here!  
View full article
    Overview Add Leads to Static Lists Use Custom Fields Overview Lead records have two primary components – lead attributes and activity logs. Lead attributes are the fields and field values within the lead record. For example, Job Title is a lead attribute. Lead Name is a lead attribute. Activity logs record the actions Marketo or the lead themselves have taken. For example, sending an email to a lead is an activity that would show in the activity log. If the lead opens the email or visits a tracked page, those activities would show in the activity log as well.   Activities in the activity log are only retained for 90 days, 25 months, or 37 if you have purchased the premium data retention option. The official Marketo Data Retention Policy can be found here:  Marketo Activities Data Retention Policy   The main way to store activity data beyond the Data Retention Policy timeframe is to use the Bulk Extract API. There are two other ways you can keep a reference of these activities after the end of the Data Retention period, and they can be referenced within the Marketo UI. This article will show you how that can be done.     Add Leads to Static Lists Static lists will retain lead membership even if the activity of adding the lead to the list has been removed. This will let you have lists dedicated to specific criteria that would otherwise be removed after the data retention time period has been passed.   For example, Smart Campaign membership history is not retained after 25 months. If you are searching for members of a Smart Campaign, but a lead first became a member of the Smart Campaign more than 25 months ago, the search results would not include that lead.   An easy way to work around that is to add your leads to a static list as part of the flow of the campaign. When creating your Smart Campaign, create a new static list with the same corresponding name (makes it easier to identify later). When building the flow of your campaign, add the "Add to List" flow step so that all leads going through the campaign will be logged on the list.         Use Custom Fields Lead attributes and their field values are not affected by the Data Retention Policy. Use Smart Campaigns to populate custom fields with values based on activities your leads take. This will allow you to filter leads by these lead attributes that are not affected by the Data Retention Policy. A side benefit to this is that it is faster to search by lead attributes than by searching through lead activity logs.   Example: This approach can work for many different activities, but let’s use form fill outs as an example.   Let’s say you want to be able to identify leads who have been very active and have filled out more than 5 forms over their lifecycle. You could use the filter “Filled Out Form” with the “Min. Number of Times” constraint set to 5. However, if one of those forms filled out occurred more than 25 months ago, the filter would only be able to access 4 form fill activities in the activity log. Therefore, the lead would not pass the filter.   Instead of using the “Filled Out Form” filter, set up a Smart Campaign to write to custom fields that show you how many forms they’ve filled out, and when the first one was. Here’s how to do it:   1. Create two new custom fields in Marketo, one Score Field, and the second a Date Field.   2. Create a new Smart Campaign   3. Add the trigger “Fills Out Form” set to “is any” to the Campaign Smart List     4. Add these two Flow Steps to the Campaign Flow: Flow Step 1 : “Change Score” Score Field Name: your score field name Change: +1   Flow Step 2 : “Change Data Value” Add Choice to Flow Step Choice 1: If “your score field name”  “is empty” Attribute “your score field name” New Value: {{system.date}} Default Choice: Do Nothing       This campaign will listen for any time a lead fills out a form, add +1 to your score field, and if it’s the very first form they’ve ever filled out, it will log the date of when it was done. If the lead has ever filled out a form in the past, there will already be a date value in the date field, so the flow choice would just skip over it and do nothing.       Results You’ll See: With the original goal of identifying leads who have filled out more than 5 forms you’ll be able to filter for leads that have filled out at least 5 forms. In addition, this campaign will let you search for leads based on when they had filled out their very first form, regardless of how long ago it was. Since it’s stored in a lead field, it’s a lead attribute that is not affected by the Data Retention Policy at all.        
View full article
No. You can only have one RTP Javascript tag per web page. Having more than one tag will not work and may cause issues.
View full article