Knowledgebase

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

Issue Is it possible to add Lead Partition/Workspace information in a custom Revenue Explorer reporting?     Solution RCE does not have the ability to segment reports by Lead Partition or Workspace. One possible workaround for leads is to create a custom field on a lead's record and populate it with the partition name.  There is no such option, however, for assets in different workspaces.  

Issue Are Marketo forms responsive? Will they auto adjust their layout to the size of the screen depending on if they are mobile or desktop? Solution The form layout can work responsively on mobile and desktop depending on how you have it setup. If your form in whole is never wider than your intended screen size (like a mobile at 480pixels), then the form will not differ on mobile devices from its desktop view. If your form is too wide, you can alter the layout using custom CSS on the form code to make the form fit within the mobile browser screen size bounds. How to edit CSS of a Form is covered here: https://docs.marketo.com/display/public/DOCS/Edit+the+CSS+of+a+Form+Theme    

Issue Email asset does not show which template it was built on and shows the word "none" instead of the name of the template that was used to create that asset. Solution Any edit directly to the HTML code of an email will break the connection between the email and the template. Changes made to the template will no longer flow down to the email. After making those change you will see a template name of None instead of the name of a template. When editing the HTML in the email, you will see this warning message: This is a article attached image

Issue You see one value for Acquisition Program and a different value for Acquired By. What do they mean and how are they different?     Solution Acquired By specifically means 'this program was responsible for creating the lead record'.  Acquisition Program is an attribute that you are able to change, but Acquired By is something controlled by the system that designates when that program is directly responsible for creating the record. For example, if you had an SFDC Campaign that was synced to a Marketo program, and you added a lead to that Campaign, the lead would be synced down to the Marketo program.  You could then use a Smart Campaign to set the value for Acquisition Program.  However, the program would not receive Acquired By credit because the lead came from Salesforce and not from the program directly.      

Issue When we delete the static lists from a program after a period of time, will the leads they contain no longer be member of the program? Solution The individuals should still be a member unless you change their membership status to remove them. Remember lists are simply collections of individuals so you can easily process or associate them, they don't automatically get "membership" unless you had corresponding flow steps that you used when putting them on the list.        

Issue Issue Description Some leads received emails 1, 2 and 3 from an Engagement Program stream but did not receive email 4.   Solution Issue Resolution Check if leads were still a member of the Engagement Program at the time Email 4 was sent.  Check if leads were removed from the Engagement Program before Email 4 was sent Check if leads were moved onto a different stream within the Engagement Program before Email 4 was sent Check if the Engagement Program has been turned off Check if leads were paused from receiving content

Issue Description MS Dynamics Sync shows that it is stuck at a certain percentage after a long period of time.   Issue Resolution This is usually caused by enabling several Custom Entities at a time.   To resolve this issue, you will need to sync the custom entities one by one so that the sync is not bottlenecked.   If that does not resolve the issue, check how many fields are enabled for the custom entity.   A large amount of fields can cause a bottleneck, try to reduce the amount to have only necessary fields.   Who This Solution Applies To Customer with Microsoft Dynamics CRM Is this article helpful ? YesNo

Included in this article Overview Have you ever wanted to have an RTP campaign only show up on specific pages? This article will go over the steps needed to make an RTP campaign do just that and only show up on certain pages. Specifying a Target URL When editing a campaign, there is a section labeled "Target URL" (right under where you choose the Segment the campaign uses). This is where you can specify the URL(s) you would like to display the campaign on. Adding Multiple URLs If you would like to include multiple pages you can use the green plus button to open the multiple value entry option.

Issue Issue Description Unable to limit user access specific to certain programs or assets     Solution Customization of user roles for assets (such as landing pages, emails, etc.) or programs is currently unavailable. However, you can control user access by limiting their permissions to specific workspaces, provided that Workspaces are enabled for your Marketo instance. Configure Protocols for Marketo    

Marketo will be performing mandatory maintenance in our London data center from Saturday, April 13, 2019, at 8:00 PM GMT to Sunday, April 14, 2019, at 2:00 AM GMT. Only Marketo instances in the London data center will be affected, and no Marketo instances in any other data center will be impacted.The maintenance is expected to take as little as two hours to complete, however, customers should plan for service disruptions for the entire maintenance window to account for unforeseen complications. Service will be restored as quickly as possible. All Marketo services for customers in the London data center will be disrupted during the maintenance window. To help you plan for the service disruption, we have gathered and answered some frequently asked questions. Why is the maintenance needed? As network traffic increases, we must also scale our infrastructure to prevent unplanned service disruptions. We are replacing our network’s firewall and load balancer devices, which will improve security, add capacity, and increase availability for all customers. The current network devices are processing more traffic than they are designed to handle, so immediate action is required. Upgrading our network infrastructure re-establishes stability to our services, providing better service for all customers Why is the maintenance scheduled on April 13 th ? We never want to interrupt service. However, if we have to, the goal is to minimize impact as much as possible. As a global operation, it’s difficult to find a time that has the lowest traffic in all geographic regions. The maintenance was scheduled for a Saturday because, as a weekend, it doesn’t fall on a workday in any country. We’ve scheduled additional coverage from our Network, Engineering, and Support teams and will be actively monitoring progress throughout the maintenance period. If the maintenance is only expected to take two hours, why is it scheduled for six hours? In previous maintenance replacements of the same devices, we were able to complete the process within the same amount of time. Therefore, we are expecting that it should only take two hours. However, there is always the possibility of unforeseen circumstances that could extend the recovery time. The additional time is to account for this possibility and all customers should plan for service to be disrupted for the entire six-hour timeframe. Timeline: April 13, 8:00 PM GMT - 8:30 PM GMT Status page maintenance notice updated to "In Progress" All Marketo back-end services stopped in the London data center Firewall and load balancer upgrades and maintenance initiated April 13, 8:30 PM GMT - 10:00 PM GMT Firewall and load balancer maintenance completed Begin system recovery process Systems restored, and network system monitoring begins Status page maintenance notice updated April 13, 10:00 PM GMT - April 14, 2:00 AM GMT Ongoing system monitoring and analysis of any abnormalities Where can I get updates during the maintenance process? Marketo's Status page, https://status.marketo.com will be updated with the progress of the maintenance process in real time. Please see the notice "Scheduled Maintenance in London data center, April 13," and subscribe to updates to have the most current information sent directly to you in real time. What services will be affected? During the maintenance process, all Marketo services housed in the London data center will be disrupted. This will include interactive logins, email, landing pages, forms, and all other services that require access to the instance, such as API and LaunchPoint services. Many back-end services will be stopped, therefore campaigns and programs scheduled to run or in progress during this time will be delayed. Will images display in emails? If the images are hosted in your Marketo instance, and your instance is in the London data center, those image files will not be accessible, therefore they will not display during the maintenance downtime. Images hosted externally will display as normal. Will hyperlinks in emails connect to the page they should go to? This depends on whether the link is being tracked or not. If the link is a tracked link, it will not connect to the destination URL. If the link is not being tracked, it will connect as expected. Email links are tracked by default, but that tracking can be disabled. Tracked links operate by first going through a Marketo server to identify which person clicked which link. The page then navigates to the corresponding destination page as expected. While the maintenance is in process, that Marketo server will not be reachable. Therefore, tracked links will not be able to navigate to the destination page. Links that are not tracked do not go through a Marketo server and will not be affected. Will our unsubscribe page be accessible? While the maintenance is in process, the London data center will be offline, therefore unsubscribe pages hosted in London Marketo instances cannot be reached. Any person who navigates to one of these unsubscribe pages will receive an error message. The error message will state that there was a technical issue preventing the unsubscribe request and they will need to re-attempt to unsubscribe later. What happens if a person clicks the unsubscribe link that Marketo adds to email footers? This depends on whether the unsubscribe link is being tracked or not. If the link is a tracked link, it will not connect to the destination URL. If the link is not being tracked, it will connect as expected. The default behavior for unsubscribe links in the email footer is to be tracked. This tracking can be removed by customizing the HTML of the footer as detailed here. However, if the tracking is still in place, the link clicks will result in errors. This will be true for custom unsubscribe pages hosted outside of Marketo as well as those within Marketo. If we use a non-Marketo unsubscribe page and the link is not tracked, will it connect? Yes. However, you should watch for a secondary issue. In most use cases, customers will use the Marketo API to send that unsubscribe data back into Marketo to update the corresponding record as unsubscribed. If that API call is made during the maintenance downtime, the API call will fail and the unsubscribe request will not be logged. Customers should retry these calls after the maintenance window. Will the unsubscribe link added by email providers function during the maintenance? Most email providers will add an unsubscribe link to the top of email messages. When clicking on this link, this unsubscribe request goes through the email provider and doesn’t navigate to your unsubscribe page. The email provider then forwards that unsubscribe request (and any others received for the same email sender) to the email sender in a list. This is known as a list-unsubscribe. If the email provider sends this list-unsubscribe request to Marketo during the maintenance downtime, it will not be able to connect and the unsubscribe request will not be recorded in your instance. Marketo has performed extensive research and testing on this functionality to identify ways to mitigate this risk. List-unsubscribe retries: Most email providers will retry a list-unsubscribe request if the first attempt fails. This helps ensure that, even if the list-unsubscribe is unsuccessful during the maintenance window, it will be retried later. Removal of list-unsubscribe feature: While the list-unsubscribe functionality is added by the email provider, Marketo can control whether or not that functionality is applied. By changing a back-end configuration, Marketo can prevent email providers from supplying their unsubscribe link. By removing this option, it forces people to use the unsubscribe link provided in the email footer. Since the unsubscribe link will take the person to an error page, they will know that there was a technical issue preventing a successful unsubscribe request and will know that they will need to re-attempt to unsubscribe later. This should prevent a situation where a person thinks they have unsubscribed but have not been recorded as so. The list-unsubscribe feature was removed on April 2, 2019. This will remove the list-unsubscribe functionality from all emails sent after the configuration change is made. However, it is not possible to remove the feature from emails sent prior to the configuration change on April 2, 2019. Through extensive testing and trend analysis, we have found that the likelihood of a person using the list-unsubscribe feature two or more weeks after the email is sent is extremely low (between 1.64% and 1.87%). What this means is that the chances of a person using this feature to unsubscribe but not actually being unsubscribed is very low. When combined with the fact that all major email providers retry list-unsubscribes if not successful on the first attempt, the risk of an unsubscribe request not processing successfully is very small. The list-unsubscribe feature will be re-enabled after the maintenance has been completed. If you have any questions, please contact Marketo Customer Support https://support.marketo.com.

Issue When attempting to use the Marketo Sales Insight actions drop-down list, to perform an action for a specific contact in Salesforce, the drop-down does not appear in the MSI section. Solution Check to see if the specific contacts this is occurring on have been recently converted. If they have, then the actions drop down will not appear until the contact has synced back down to Marketo.  

Issue Issue Description You would like to change the order in which the emails are being sent to leads but some of the leads have received several emails from the stream already. If the order of email is changed would those leads receive the same emails again?     Solution Issue Resolution If a lead has received the email previously from any campaign or program then they will NOT receive this email as long as the email ID remains the same. Marketo will go down the list of emails within the stream until it finds one that has not been sent to the lead and this will be sent to the lead at the time of the engagement program cast.

Issue Webinar integration is giving an error "Invalid Username or Password" during setup, even though the username and password are correct. The webinar provider uses your Single Sign-On (SSO) provider for login.     Solution Marketo is not able to access the SSO provider and will not be able to log into the service if SSO is used. Use the following workaround for your integration. Disable SSO for the webinar service so that a user with login and password can be used in the Marketo Launchpoint service.  Create the integration user in the webinar provider and complete the integration Re-enable SSO for your webinar service after the webinar is over.   Who This Solution Applies To Clients leveraging SSO for Launchpoint services    

Here are the steps to bold all of the field labels on your landing page, even the non-required fields: 1) Edit your landing page 2) Add a custom HTML box to your landing page 3) Paste the following into the custom HTML box <style> form.lpeRegForm label {font-weight:bold; } </style> 4) Save the custom HTML box 5) Approve the landing page

Issue When retrieving result sets from the /rest/v1/activities.json end-point using a Paging Token, the result set returned by the API appears to be less data than what is in the Marketo UI. In this scenario, we're going to explore how and why Paging Tokens work when utilizing them in REST API calls. SCENARIO Say we wanted to grab all 'Send Email' activities (activityType = 6) that have occurred since 2024-04-12T12:00:00Z, and we're planning to pull these activities every two hours, and increment our paging token every two hours prior to making the /activities.json call to obtain the latest data. Current Time Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z What We Want 1. Retrieve all Send Email activities SINCE  Apr 12, 2024, 6:00:00 AM (MST) == 2024-04-12T12:00:00Z We would start by retrieving our Paging Token with the sinceDateTime parameter = 2024-04-12T12:00:00Z: /rest/v1/activities/pagingtoken.json?sinceDatetime=2024-04-12T12:00:00Z Our response would contain the nextPageToken representing the sinceDateTime: { "requestId": "1607c#14884f3e74e", "success": true, "nextPageToken": "RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====" } We would then pass that nextPageToken into our GET /rest/v1/activities.json end-point, as well as our activityTypeId = 6 to target all 'Send Email' activities that have occurred since 2024-04-12T12:00:00Z. /rest/v1/activities.json?nextPageToken=RW6ZK46LKV36BMJ2QARX3BFZHQNHRVPPEW4IZVEELI45V2OH6RCA====&activityTypeIds=6 After paging through all of the results (now leveraging the returned nextPageToken from the /activities.json end-point to page through all results), we've returned 15,000 Send Email activities.      PROBLEM We know that, from our Marketing team, that we were expecting ~20,000 email sends since 2024-04-12T12:00:00Z. So why does the result set appear to be missing 5,000 records? Let's examine this further. 'Send Email' activities aren't committed to the Marketo database until the message has successfully been sent from our mail servers. Prior to that, the email is queued, awaiting it's launch to it's receiving mail server. This can present a delay from the time the email is sent, to when the activity is recorded to the Marketo database. For example, say there were two campaigns sending 10K emails each: First Campaign Send: 2024-04-12T12:30:00Z (30 minutes after our sinceDateTime token) Second Campaign Send: 2024-04-12T13:45:00Z (110 minutes after our sinceDateTime token, 10 minutes prior to when the call was made) While the first campaign send is most likely accounted for in the database (Send Email activities have been committed), Campaign #2 is still processing and sending out all 10K emails in the background. For this scenario, Marketo has only committed 5K out of 10K email sends to the database at the time the call was made. Without noticing the missing data, you repeat this process two hours from now, incrementing your sinceDateTime token by two hours as well, assuming you'll get all the new Send Email activities for the past two hours. This would now lead to you missing the 5K Send Email activities that were still being processed, but not yet committed to the database. SOLUTION The nextPagingToken returned in the /activities.json end-point is position based, and can only pull data that has been committed to the Marketo database, which inherently changes as records are being processed. If, for instance, you made the original /activities.json call at (Apr 12, 2024, 8:00:00 AM (MST) == 2024-04-12T14:00:00Z), and used the same sinceDateTime token 5-10 minutes later (Apr 12, 2024, 8:10:00 AM (MST)), you would now notice that campaign #2 has fully finished it's processing AND committed the 'Send Email' activities to the Marketo database with dateTime stamps less than Apr 12, 2024, 8:00:00 AM (MST). So, what's the best way to ensure you're retrieving all the data? Solution #1 Increment your sinceDateTime token based on the MAX(created_at) dateTime returned in the latest result set, rather than incrementing it based on an interval (every two hours). This would help ensure you're not missing records that were processing, but not yet committed to the Marketo database. Solution #2 If the data you're retrieving does not need to be live, we would recommend using the Bulk Extract API to pull this data at a lower frequency (such as twice per day 12AM & 12PM). This would greatly decrease the chances of missing records that weren't committed to the database.